Data Attributes

The name of the ferry service. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

20
0 - Ferry Route Lines running too close to another Ferry Route Line to be shown.

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

All ferry routes on existing base material should be retained unless information is available indicating the ferry service has been discontinued. Reference Material will be provided for new ferry routes.

Ferry routes not connected on both ends to either the road and/or rail network, must be greater than 300 metres in length to be captured.

1:100 000

All ferry routes on existing base material should be retained unless information is available indicating the ferry service has been discontinued. Reference Material will be provided for new ferry routes.

Ferry routes not connected on both ends to either the road and/or rail network, must be greater than 300 metres in length to be captured.

1:250 000

All feature occurances existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. Revision source material will be provided for new ferry routes to be shown.

Ferry routes not connected on both ends to either the road and/or rail network, must be greater than 750 metres in length to be captured.

General - All Scales

Where one Ferry Route Line crosses another Ferry Route Line a node will be shown at their intersection point. i.e. The arcs will be split.

Two or more Ferry Route Lines running closer that 250 metres, parallel to each other and carrying the same attributes will be shown/captured as a single feature (ie. Physically combined to form one section of Ferry Route Line) .Two or more Ferry Route Lines running closer than 250 metres, parallel to each other and carrying different attributes will be both be represented in the data. In this case the additional Ferry Route Lines will have a symbol number 0.

Only operational ferry routes will be shown.

Trans- Tasman and other long distance Ferry routes will be shown.

Ferry routes that form part of the road network will connect to the road network.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Ferry Route Lines will have as their starting point the appropriate terminating point of Road or Railway features. That is, the end node of the Road/Railway will be a shared node used for the starting point of the Ferry Route. This is required to ensure network connectivity.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Ferry Route Lines will have as their starting point the appropriate terminating point of Road or Railway features. That is, the end node of the Road/Railway will be a shared node used for the starting point of the Ferry Route. This is required to ensure network connectivity.

Ferry Route Lines will only appear over Watercourse Area, Lake, Reservoir and Sea. A vertex should exist in the polygon and its associated bounding line at the entry and exit location of the Ferry Route Line.

Map Rules

General - All Scales

Two or more Ferry Route Lines running closer than 1mm to scale, parallel to each other and carrying different attributes will both be labelled where they can be shown legibly.

All ferry routes, including those not symbolised, are to be labelled 'ferry' if the word ferry or equivalent is not included in the name.

Where a Ferry route crosses the edge of the map a note will be placed along the route close to the edge giving the main destination eg 'Sydney to Devonport.'

Ferry Routes will be masked by Annotation.

Related Features

Railway , Road

Related Chapters

Section 3 Chapter 5.3

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

General - All Scales

The name of a foot bridge may be held in the TextNote field.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Foot Bridges will be coincident with the equivalent section of the Foot Track. There must be a vertex in the Foot Track feature at the exact location of the start and end points of the Foot Bridge.

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

Related Features

Foot Track

Related Chapters

Related Products

NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Foot Track

FootTracks

RoadTransport

Polyline

A path either beaten by the passage of feet (usually unformed and not maintained) or constructed by an authority to enable access to an area or provide a connection from one location to another. The path is primarily designed to carry pedestrian traffic only but may also allow access to other forms of non-vehicular transport.

Data Attributes

The name of the foot track. This item should be populated where name is known.

TRACK NAME (TRACKNAME) [String;Yes;60;0;0;Pop_Wk]

The name of the foot track in its entirety.

SECTION NAME (SECTIONNAME) [String;Yes;60;0;0;Pop_Wk]

The name of individual section along a foot track

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;10;0;0;Pop_Req] The national significance of the entity;

Acceptable Domain Entries from dm_Significance;
National
Regional
State

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Details of new foot tracks to be included will be supplied. Only tracks of national, state and regional significance will be included.

Foot tracks with the significance of 'Regional', 'State' and 'National' should have a default upperscale value of '50000','100000' and '250000' respectively. However the final Upperscale value will be downgraded if the foot track does not comply with the 'data capture and map representation' length criteria (In this case, it will have the highest acceptable upperscale to which its length criteria conforms).

1:100 000

Details of new foot tracks to be included will be supplied. Only tracks of national, state and regional significance will be included.

Foot tracks with the significance of 'Regional', 'State' and 'National' should have a default upperscale value of '50000','100000' and '250000' respectively. However the final Upperscale value will be downgraded if the foot track does not comply with the 'data capture and map representation' length criteria (In this case, it will have the highest acceptable upperscale to which its length criteria conforms).

1:250 000

Details of new foot tracks to be included will be supplied. Only tracks of national significance will be included.

General - All Scales

Foot tracks are to have an accompanying TextNote 'foot track' unless 'foot track' or an equivalent term is included in the name.

Where the position of new foot tracks can not be verified on the imagery or other reference material they are to be labelled ' (position approximate)'

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:250 000

Where the foot track is associated with or uses a section of road it should be made coincident with that portion of the road. A vertex on the road should exist at the exact location of the entry and exit points of the foot track.

General - All Scales

A descriptive note may be added to the Textnote field, for example 'Hume and Hovell Walking Trail follows track' where a foot track is coincident with a road.

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

General - All Scales

Foot tracks are to have an accompanying descriptive note 'foot track' unless 'foot track' or an equivalent term is included in the name. Where the position of new foot tracks can not be verified on the imagery or other revision source material they are to be labelled ' (position approximate)'

A descriptive note may be added on the map where a Foot track is not included because it follows a road, for example 'Hume and Hovell Walking Trail follows track'.

Foot tracks will be masked where black type unavoidably overprints the feature. The break measurement will be 0.2 mm on either side of the type where it crosses the feature. (Note: the feature will be masked only on the map and will be complete in the data.)

Related Features

Foot Bridge, Road

Related Chapters

Section 3 Chapter 5.3

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the ford. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Fords Lines shorter than 300 metres and ford point features, will not be symbolised (e.g. symbol = 0).

1:100 000

Fords Lines shorter than 300 metres and ford point features, will not be symbolised (e.g. symbol = 0).

1:250 000

Fords Lines shorter than 750 metres and ford point features, will not be symbolised (e.g. symbol = 0).

General - All Scales

Existing crossing lines (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist.

Where new crossing lines are identified on Reference Material of suitable positional quality (refer to associated metadata statement) they can be captured and attributed according.

When attempting to capture crossing lines solely from imagery, if there is evidence of man-made construction then producers should determine whether the feature constitutes a causeway or bridge. Refer to Appendix U for examples of road bridges to assist in interpretation. If the classification or existence of the feature is unclear due to resolution of the supplied imagery an Action Request should be raised seeking clarification.

When attempting to capture crossing lines solely from imagery, if there is little or no evidence of man-made construction then producers should not assume a crossing line exists at that location. However, if the road appears to traverse an obstacle such as a watercourse or gully an Action Request should be raised seeking clarification.

Where a ford crosses a entity in the waterbody dataset it will be classified as a ford line.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Ford Line must be a clone of the equivalent section of the associated Road. There must be a vertex in the Road feature at the exact location of the start and end points of the Ford Line. The road must continue outwards from both endpoints of the Ford Line.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Named fords will be cloned as Place Names in the Framework feature dataset.

Linear Fords can only appear over Watercourse areas or Lakes; a vertex should exist in the polygon and its associated bounding line at the entry and exit location of the linear ford.

Map Rules

General - All Scales

All fords, including those not symbolised, are to be labelled 'ford'.

The equivalent section of road associated with linear fords must not be symbolised on the map.

Fords shorter than 3 mm at map scale, including point features, will not be symbolised (e.g. symbol = 0).

Related Features

Related Chapters

Section 3 chapters 5.10 and 5.11.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the ford. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Fords Lines shorter than 300 metres and ford point features, will not be symbolised (e.g. symbol = 0).

1:100 000

Fords Lines shorter than 300 metres and ford point features, will not be symbolised (e.g. symbol = 0).

1:250 000

Fords Lines shorter than 750 metres and ford point features, will not be symbolised (e.g. symbol = 0).

General - All Scales

Existing crossing points (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist.

Where new crossing points are identified on Reference Material of suitable positional quality (refer to associated metadata statement) they can be captured and attributed according.

When attempting to capture crossing points solely from imagery, if there is evidence of man-made construction then producers should determine whether the feature constitutes a bridge. Refer to Appendix U for examples of road bridges to assist in interpretation. If the classification or existence of the feature is unclear due to resolution of the supplied imagery an Action Request should be raised seeking clarification.

When attempting to capture crossing points solely from imagery, if there is little or no evidence of man-made construction then producers should not assume a crossing points exists at that location. However, if the road appears to traverse an obstacle such as a watercourse or gully an Action Request should be raised seeking clarification.

Where a ford creates a gap in the road network it will be closed by a Ford Line.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Point Fords must be coincident with a vertex in the road network.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Named fords will be cloned as Place Names in the Framework feature dataset.

Related Features

Related Chapters

Section 3 chapters 5.3, 5.9, 5.10 and 5.11.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

This feature will only be captured when requested by Geoscience Australia. The feature must be derived from either field inspection information or Authorised Reference Material, it can not be captured from imagery alone. Existing gates will be retained unless directed otherwise.

1:100 000

All Gates existing in base material will be retained. New features will only be captured in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' except for gates on Vermin Proof fences which will be shown in all areas.

Only gates within sparsely settled regions or situated on a vermin proof fence will be eligible be classified with an upperscale value of 100000 or higher.

1:250 000

This feature will only be captured/retained in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide', regardless of whether it previously existed in the base material/digital data, except for gates on Vermin Proof fences which will be shown in all areas.

General - All Scales

Only gates associated with a road network will be captured.

Gates will not be shown on vehicle tracks with the exception of gates in Vermin Proof Fences which will be shown in all areas.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Only gates associated with a road network will be captured.Gates must be coincident with a vertex in the road network.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Gates must fall exactly on the Fence. A vertex will be added to the fence to ensure the fence, road and gate are coincident with each other.

Map Rules

Related Features

Fence, Road , Grid

Related Chapters

Section 3 chapters 5.3, 5.9, 5.11.2Appendix C

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

This feature will only be captured when requested by Geoscience Australia. The feature must be derived from either field inspection information or Authorised Reference Material, it can not be captured from imagery alone. Existing grids will be retained unless directed otherwise.

1:100 000

All Grids existing in base material will be retained. New features will only be captured in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' except for gates on Vermin Proof fences which will be shown in all areas.

Only grids within sparsely settled regions or situated on a vermin proof fence will be eligible be classified with an upperscale value of 100000 or higher.

1:250 000

This feature will only be captured/retained in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide', regardless of whether it previously existed in the base material/digital data, except for grids on Vermin Proof fences which will be shown in all areas.

General - All Scales

Grids will not be shown on vehicle tracks. The only exception is when the Grids is associated with a 'Vermin Proof Fence'.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Grids must be coincident with a vertex in the road network.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Grids must fall exactly on the fence. A vertex will be added to the fence to ensure the fence, road and Grid are coincident with each other.

Map Rules

The underlying fence symbol will be masked out for the stock grid symbol.

Related Features

Fence, Gate , Road

Related Chapters

Section 3 chapters 5.3, 5.9, 5.11.2Appendix C

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Acceptable Domain Entries from dm_RoadFormation at 25K and 100K as well as acceptable entries for the 250K field;
Sealed
Unsealed
Unknown
Under Construction

NATIONAL ROUTE NUMBER (NRN) [String;Yes;12;0;0;Pop_Wk] The national route number/s assigned to the road ( if multiple numbers, delimited by a minus sign). Alpha characters in this field are to be in upper case.

STATE ROUTE NUMBER (SRN) [String;Yes;12;0;0;Pop_Req] The state route number/s assigned to the road ( if multiple numbers, delimited by a minus sign). Alpha characters in this field are to be in upper case.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

Feature width is only used for roads under construction (symbol 252). All other roads will have a feature width of '0'. The width of symbol 252 reflects the road classification, the following values will be used:

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurances.

Roads less than 200m will not be captured where they lead to a building, are a circular driveway or end between closely spaced buildings.

Minor roads and vehicular tracks will be named where named on the base material/digital data (e.g. state mapping source) unless there is clear evidence they no longer exist. New names for Minor roads and Vehicular Tracks will be added where named on road reference material supplied. Naming for Minor Roads and Vehicular Tracks will not be subject to Appendix C.

Where the carriageways of a dual carriageway are separated by less than 25 metres the dual carriageway will be symbolised using symbol 250. If the separation of the carriageways is greater than 25 metres, each carriageway will be shown in its true position, classified as principal road and have symbol number 251.

1:100 000

Size and any other selection criteria apply to all feature occurrences. An exception will be minor roads in built up areas which will be treated as per the rules stated in Inter-Feature Relationship Rules - External.

Minor roads and vehicular tracks will be named where named on the base material/digital data (e.g. state mapping source) unless there is clear evidence they no longer exist. New names for Minor roads and vehicular tracks will be added where named on road reference material supplied. Naming for Minor Roads and Vehicular Tracks will not be subject to Appendix C.

Roads will not be added only from interpretation of the imagery. However obvious road realignments may be captured when significant.

Where existing dual carriages are separated by less than 25 metres the dual carriageway they will be symbolised using symbol 250. If the separation of the carriageways is between 25 metres and 100 metres, each carriageway will be shown in its true position, classified as principal road and have symbol number 0. A new representation of this feature will be created in the 'CartoGeneralisationLine' feature class down the centre of the two carriageways and symbolised as a dual carriageway with symbol 250. It is this representation which will be shown on the map face.

When capturing new dual carriageways and they are separated by less than 100 metres the dual carriageway will be symbolised using symbol 250. If the separation of the carriageways is greater than 100 metres, each carriageway will be shown in its true position, classified as principal road and have symbol number 251.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. An exception will be minor roads in built up areas which will be treated as per the rules stated in Inter-Feature Relationship Rules - External.

Minor roads and vehicular tracks will be named where named on the default version of the TOPO250K geodatabase unless there is clear evidence they no longer exist. No new names for Minor roads and vehicular tracks will be added in densely settled regions as defined by Appendix C. New names for Minor roads and vehicular tracks will be added in sparsely settled regions as defined by Appendix C where named on road reference material supplied. A selection of new names for Minor roads and vehicular tracks may be added in moderately settled regions as defined by Appendix C, these should be taken from the roads reference material supplied. In moderately settled regions preference should be given to minor roads and vehicular tracks which consititute through routes and/or lead to cultural or natural features.

Roads will not be added only from interpretation of the imagery. However obvious road realignments may be captured when significant.

Where the carriageways of a dual carriageway are separated by less than 250 metres the dual carriageway will be symbolised using symbol 250. If the separation of the carriageways is greater than 250 metres, each carriageway will be shown in its true position, classified as principal road and have symbol number 251.

General - All Scales

Road classifications will be as shown on the road reference material supplied.

Classifications are:Dual carriageway - Divided Highway, Freeway, Tollway, or other major roads with separated carriageways in opposite directions.Principal Road: - Highways, major through routes and major connecting roads.Secondary road: - Connecting roads that provide a connection between major through routes and/or major connecting roads, or connections between regional centres.Minor road: - All other roads which form part of the public roads system between Principal roads and Secondary roads.Vehicle tracks: - Public or private roadways of minimum or no construction which are not necessarily maintained.

Roads not shown on the authorised roads reference material will maintain the classification on the latest previous edition map at scale or base material/digital data. Where the latest previous edition map uses a different road classification the least important class will be used. For example, where latest previous edition map specifies road with no clarifing information to determine its classification, it will be classified as minor road. Where the use of the latest previous edition map or data would result in an illogical connection, for example if a secondary road connects only to minor roads, a logical connection will be used.

All vehicular tracks will be considered as formation unsealed. When reference material indicates a section of the route is sealed, the classification should default to minor road. If this results in an illogical connection with the abutting roads, this should be resolved via action request to GA.

Roads with a formation 'Unknown' should be symbolised as if the formation was 'Unsealed'. Only Secondary and Minor roads will be subject to the formation 'Unknown'. The practice of applying the 'Unknown' formation to roads should be limited to exceptional circumstances.

Roads identified by GEOSCIENCE AUSTRALIA to be captured in the geodatabase but not displayed on the map face due to security or sensitivity reasons using the 'Restrictions' field will be given the symbol number '0'.

Roundabout features will be captured as standard intersections.

All dual carriageways and principal roads will be named. Secondary roads should be named where name is known.

Roads with multiple National or State Route Numbers should have these values shown in numeric order. When there is a combination of numeric and alphanumeric identifiers i.e. 32-B2-C110, the numeric value/s should be listed first followed by the alphanumeric value/s. Values will be separated by a hyphen with no internal spacing to be used between the hyphen and value.

Roads whose position is questionable will be textnoted 'position approximate'.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:250 000

Where the foot track is associated with or uses a section of road it should be made coincident with that portion of the road. A vertex on the road should exist at the exact location of the entry and exit points of the foot track.

General - All Scales

Roads will have nodes at all intersections.

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

The General Interrelationship - External rule stating 'Roads cannot overlap Town Rural Storage and Lake Perennial' does not apply when it is clear on imagery that a land holder has established a road through a portion of the feature which has dryed due to the drought conditions within Australia. When this occurs the road should be symbolised to zero and a representation of the feature should be created in the 'CartoGeneralisationLine' feature class. This representation will only show the portions of the feature which does not exist within the extents of the high water mark of the waterbody. The feature in the 'CartoGeneralisationLine' will have the symbol of the classification and formation of the road (e.g. vechicular track).

1:100 000

All roads existing in the base material/digital data entering or within Built Up Area will be retained. New minor roads entering a Built Up Area will be continued to the first intersection with a major through route (preference should be given to intersections with dual carriageways, principal or secondary roads). In addition, sufficient new minor roads will be captured to reflect the Built-up Area's road pattern. Select the major through routes (from Reference material) to reflect the road pattern within the area whilst avoiding clutter. This rule will also extend to other features (including defined holes, areas of universe polygon) in the built-up area layer where they are surrounded by a built- up area. See Section 3 Chapter 6.7.3.

The General Interrelationship - External rule stating 'Roads cannot overlap Town Rural Storage and Lake Perennial' does not apply when it is clear on imagery that a land holder has established a road through a portion of the feature which has dryed due to the drought conditions within Australia. When this occurs the road should be symbolised to zero and a representation of the feature should be created in the 'CartoGeneralisationLine' feature class. This representation will only show the portions of the feature which does not exist within the extents of the high water mark of the waterbody. The feature in the 'CartoGeneralisationLine' will have the symbol of the classification and formation of the road (e.g. vechicular track).

1:250 000

Minor roads entering a builtup area will be continued to the first intersection with a dual carriageway, principal or secondary road. Minor roads totally contained in built-up areas will not be captured. This rule extends to other features (including defined holes, areas of universe polygon) in the built-up area layer where they are surrounded by a built-up area. See Section 3 Chapter 6.7.3.

All dual carriageways, principal and secondary roads will be shown including those in built-up areas.

Map Rules

1:25 000

Naming of minor roads and vehicular tracks should give preference to features which consititute through routes and/or lead to cultural or natural features. Density of detail should determine the number of names shown. If a previous edition 1:100 000 map has been supplied this should be used as a guide for which roads are to be named in the new product.

Minor Roads entering and contained within a builtup area will be given a symbol of '242'. The only exception will be when this application results in illegibilty of detail or road capture is inconsistent and therefore creates a misleading result. In these cases the application of the symbol 242 should be applied to minor roads entering a builtup area to the first intersection with a major through route (preference should be given to intersections with dual carriageways, principal or secondary roads). In addition, sufficient minor roads will be symbolised with 242 to reflect the Built-up Area's road pattern. Select the major through routes (from Reference material) to reflect the road pattern within the area whilst avoiding clutter. This rule will also extend to other features (including defined holes, areas of universe polygon) in the built-up area layer where they are surrounded by a built- up area. See Section 3 Chapter 6.7.3.

In addition some minor roads outside builtup area may require a symbol 242 to be applied to provide a pleasing cartographic result but this will be an exception and conducted by Geoscience Australia.

When representing a road established by a land holder through a portion of the feature which has dryed due to the drought conditions within Australia. This representation will be derived from the 'CartoGeneralisationLine' feature class. See Geodatabase Rules for more information.

1:100 000

Naming of minor roads and vehicular tracks should give preference to features which consititute through routes and/or lead to cultural or natural features. Density of detail should determine the number of names shown. If a previous edition 1:100 000 map has been supplied this should be used as a guide for which roads are to be named in the new product.

Minor Roads entering and contained within a builtup area will be given a symbol of '242'. The only exception will be when this application results in illegibilty of detail or road capture is inconsistent and therefore creates a misleading result. In these cases the application of the symbol 242 should be applied to minor roads entering a builtup area to the first intersection with a major through route (preference should be given to intersections with dual carriageways, principal or secondary roads). In addition, sufficient minor roads will be symbolised with 242 to reflect the Built-up Area's road pattern. Select the major through routes (from Reference material) to reflect the road pattern within the area whilst avoiding clutter. This rule will also extend to other features (including defined holes, areas of universe polygon) in the built-up area layer where they are surrounded by a built- up area. See Section 3 Chapter 6.7.3.

In addition some minor roads outside builtup area may require a symbol 242 to be applied to provide a pleasing cartographic result but this will be an exception and conducted by Geoscience Australia.

When representing dual carriageways and the individual carriageways are separated by less 100 metres, they will be represented by a single line down the centre of the two carriageways with symbol of 250. This representation may be derived from either the 'Road' feature class or the 'CartoGeneralisationLine' feature class as appropriate. See Geodatabase rules for more information.

When representing a road established by a land holder through a portion of the feature which has dryed due to the drought conditions within Australia. This representation will be derived from the 'CartoGeneralisationLine' feature class. See Geodatabase Rules for more information.

1:250 000

Naming of minor roads and vehicular tracks should be consistent with name content in the digital data, subject to generalisation rules and clutter considerations.

General - All Scales

All dual carriageways, principal & secondary roads will be named where name is known.

Outside built-up areas, roads and highways should be named as above. The main roads through built-up areas may be named where space permits.

Roads under construction will be labelled 'under construction'.

Roads whose position is questionable will be labelled 'position approximate'.

Vehicle tracks labelled as 'four-wheel drive' on previous edition maps will not be labelled as such on the new product, as legend indicates 'access and condition not assured'.

Related Chapters

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the road bridge. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

For linear features, where the structure has been constructed only to prevent an intersection with other road or rail traffic the road overpass feature type should be utilised instead of the road bridge line feature type.

Bridges will be shown as points when they are shorter than 40 metres.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

For linear features, where the structure has been constructed only to prevent an intersection with other road or rail traffic the road overpass feature type should be utilised instead of the road bridge line feature type.

Bridges will be shown as points when they are shorter than 40 metres.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist or unless the road crossing the bridge has been removed within a Built-up area (see Road).

Bridges will be shown as points when they are shorter than 100 metres.

Only significant bridges will be shown. The significance of the bridge depends on the number of bridges in the vicinity, the importance of the road etc.

General - All Scales

Existing crossing lines (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist.

Where new crossing lines are identified on Reference Material of suitable positional quality (refer to associated metadata statement) they can be captured and attributed according.

When attempting to capture crossing lines solely from imagery, if there is evidence of man-made construction then producers should determine whether the feature constitutes a causeway or bridge. Refer to Appendix U for examples of road bridges to assist in interpretation. If the classification or existence of the feature is unclear due to resolution of the supplied imagery an Action Request should be raised seeking clarification.

When attempting to capture crossing lines solely from imagery, if there is little or no evidence of man-made construction then producers should not assume a crossing line exists at that location. However, if the road appears to traverse an obstacle such as a watercourse or gully an Action Request should be raised seeking clarification.

The road for which the bridge was made need no longer exist, however, to be shown the bridge must still exist.(see built up area exception above)

Bridges of distinctive construction may be TextNoted (e.g 'drawbridge','swing bridge').

When load limits are known, they should be stored in the textnote field (e.g. 'load limit 6 tons')

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Road Bridge Lines may be shown off the road network if they are on a dismantled road.

Road Bridge Lines will be coincident with the equivalent section of the Road. There must be a vertex in the Road feature at the exact location of the start and end points of the Road Bridge Line.

Inter-Feature Relationship Rules - External to Associated Dataset

1:250 000

A bridge may be required to be extended to ensure that the map symbol endpoints (wings) effectively fall outside the width of its associated waterbody.

General - All Scales

Bridges which carry both road and rail traffic will be held as coincident road bridge and railway bridge features in their respective layers.

Map Rules

1:25 000

A bridge may be required to be extended to ensure that the map symbol endpoints (wings) effectively fall outside the width of its associated waterbody.

Bridges on minor roads in built up areas will be symbolised to '0' with a feature width of '0.2'. The only exception will be bridges on minor roads in built up area overlapping a feature in the Waterbodies feature dataset (e.g. watercourse area), in this case the bridge will be symbolised '260' with a feature width of '0.2'.

1:100 000

A bridge may be required to be extended to ensure that the map symbol endpoints (wings) effectively fall outside the width of its associated waterbody.

Bridges on minor roads in built up areas will be symbolised to '0' with a feature width of '0.2'. The only exception will be bridges on minor roads in built up area overlapping a feature in the Waterbodies feature dataset (e.g. watercourse area), in this case the bridge will be symbolised '260' with a feature width of '0.2'.

General - All Scales

Bridges of distinctive construction may be labelled (e.g 'drawbridge','swing bridge').

Related Features

Related Chapters

Section 3 chapters 5.8, 5.11.2 and 6.7

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the road bridge. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Bridges will be shown as Lines when they are greater than 40 metres.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Bridges will be shown as Lines when they are greater than 40 metres.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist or unless the road crossing the bridge has been removed within a Built-up area (see Road).

Bridges will be shown as Lines when they are greater than 100 metres.

Only significant bridges will be shown. The significance of the bridge depends on the number of bridges in the vicinity, the importance of the road etc.

General - All Scales

Existing crossing points (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist.

Where new crossing points are identified on Reference Material of suitable positional quality (refer to associated metadata statement) they can be captured and attributed according.

When attempting to capture crossing points solely from imagery, if there is evidence of man-made construction then producers should determine whether the feature constitutes a bridge. Refer to Appendix U for examples of road bridges to assist in interpretation. If the classification or existence of the feature is unclear due to resolution of the supplied imagery an Action Request should be raised seeking clarification.

When attempting to capture crossing points solely from imagery, if there is little or no evidence of man-made construction then producers should not assume a crossing points exists at that location. However, if the road appears to traverse an obstacle such as a watercourse or gully an Action Request should be raised seeking clarification.

The road for which the bridge was made need no longer exist, however, to be shown the bridge must still exist. (see built up area exception above)

Bridges of distinctive construction may be TextNoted (e.g 'drawbridge','swing bridge').

When load limits are known, they should be stored in the textnote field (e.g. 'load limit 6 tons')

Where clutter would occur by symbolising a point bridge feature, the point bridge may be symbolised to symbol number '0' non-printing value.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Road bridges may be shown off the road network if they are on a dismantled road.

Road bridge Points must fall exactly over a vertex on the Road feature.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Bridges which carry both road and rail traffic will be held as coincident road bridge and railway bridge features in their respective layers.

Map Rules

1:25 000

Point Bridges on minor roads in built up areas will be symbolised to '0' with a feature width of '0.2'.

1:100 000

Point Bridges on minor roads in built up areas will be symbolised to '0' with a feature width of '0.2'.

General - All Scales

Bridges of distinctive construction may be labelled (e.g 'drawbridge','swing bridge').

Road bridges may be named, where name is known.

Where clutter would occur by symbolising a point bridge feature, the point bridge may be symbolised to symbol number '0' non-printing value.

Related Features

Related Chapters

Section 3 chapters 5.3, 5.8, 5.9, 5.11.2 and 6.7

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the road causeway. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

General - All Scales

Existing crossing lines (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist.

Where new crossing lines are identified on Reference Material of suitable positional quality (refer to associated metadata statement) they can be captured and attributed according.

When attempting to capture crossing lines solely from imagery, if there is evidence of man-made construction then producers should determine whether the feature constitutes a causeway or bridge. Refer to Appendix U for examples of road bridges to assist in interpretation. If the classification or existence of the feature is unclear due to resolution of the supplied imagery an Action Request should be raised seeking clarification.

When attempting to capture crossing lines solely from imagery, if there is little or no evidence of man-made construction then producers should not assume a crossing line exists at that location. However, if the road appears to traverse an obstacle such as a watercourse or gully an Action Request should be raised seeking clarification.

The road for which the causeway was made need no longer exist, however, to be shown the causeway must still exist.

Causeways which carry both road and rail traffic will be held as coincident road causeway and railway causeway features in their respective layers.

When load limits are known, they should be stored in the textnote field (e.g. 'load limit 6 tons')

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Road Causeway must be a clone of the equivalent section of the associated Road. There must be a vertex in the Road feature at the exact location of the start and end points of the Road Causeway.The road must continue outwards from both endpoints of the causeway.

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

General - All Scales

Road causeways will be labelled 'causeway'. Where road and railway causeways are coincident only one label 'causeway' will appear on the map face.

Related Features

Related Chapters

Section 3 chapters 5.8 and 5.11.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the road overpass. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

General - All Scales

Size and any other selection criteria apply to all feature occurrences.

Existing crossing lines (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist.

Where new crossing lines are identified on Reference Material of suitable positional quality (refer to associated metadata statement) they can be captured and attributed according.

When attempting to capture crossing lines solely from imagery, if there is evidence of man-made construction then producers should determine whether the feature constitutes a causeway or bridge. Refer to Appendix U for examples of road bridges to assist in interpretation. If the classification or existence of the feature is unclear due to resolution of the supplied imagery an Action Request should be raised seeking clarification.

When attempting to capture crossing lines solely from imagery, if there is little or no evidence of man-made construction then producers should not assume a crossing line exists at that location. However, if the road appears to traverse an obstacle such as a watercourse or gully an Action Request should be raised seeking clarification.

When a road overpasses another road (only), the overpass will not be shown if there are related on and off ramps for full road inter-access. These cases will be shown as standard intersections. When this information is not available then the assumption should be that there is no inter-access.

When load limits are known, they should be stored in the textnote field (e.g. 'load limit 6 tons')

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Road Overpass must be a clone of the equivalent section of the associated Road. There must be a vertex in the Road feature at the exact location of the start and end points of the Road Overpass.The road must continue outwards from both endpoints of the Road Overpass.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Overpasses which carry both road and rail traffic will be held as coincident road overpass and rail overpass features in their respective layers.

Related Features

Related Chapters

Section 3 Chapters 5.8, 5.11.2, 6.7

Related Products

GEODATA LITE TOPO100K, NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specifcation documentation for ease of reference.

Only Annotation associated with, or derived from, entities in feature classes grouped within the RoadTransport feature dataset should exist within the RoadTransportAnno feature class.

Wherever possible annotation should be stored using the subclasses indicated under AnnotationClassID. Annotation stored as inline text should be kept to a minimum.

Type for large polygons and long linear features may be held in an annotation feature for each word to allow for spacing and differences in orientation, see Section 2 chapter 4.

Annotation should not contain any HTML tags within the blob element, nor should it contain any special characters.

Editing and placement of Annotation should be conducted in the appropriate MGA 1994 zone to ensure the spatial position of type on the map face can be correctly represented.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

Related Features

Related Chapters

Section 2 Chapter 5, 9, 10

Related Products

NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

The name of the Road Tunnel.This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Road tunnels will be shown as points when they are shorter than 25m.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

All Road Tunnels will be represented in the TOPO100K NTDB either as a Road Tunnel Line or as a Road Tunnel Point. All road tunnels less than 25m will be shown as Road Tunnel Points. New Road Tunnels less than 100m will be shown as a Road Tunnel Point. For existing tunnels between 25m and 100m the tunnel information will be retained in the same geometry as captured in the base material/digital data.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Road tunnels will be shown as points when they are shorter than 250 metres.

General - All Scales

Road tunnels may be named, where name is known.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Road Tunnel Line must be a clone of the equivalent section of the associated Road. There must be a vertex in the Road feature at the exact location of the start and end points of the Road Tunnel Line. The road must continue outwards from both endpoints of the Road Tunnel Line.

A Road Tunnel Line and a Road Tunnel Point can not represent the same tunnel.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Tunnels which carry both road and railway traffic will be held as a coincident road tunnel and railway tunnel feature in their respective layers.

The points of disappearance and emergence of Road Tunnel Lines features will be shown by the feature Transition Point.

Map Rules

General - All Scales

Road tunnels may be named, where name is known.

The equivalent section of road associated with Road Tunnel Line must not be symbolised on the map.

Related Features

Railway Tunnel Point, Road , Transition point

Related Chapters

Section 3 chapters 5.11.2 and 6.7

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

The name of the Road Tunnel.This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6);
Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Road tunnels will be shown as lines when they are longer than 25m.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

All Road Tunnels will be represented in the TOPO100K NTDB either as a Road Tunnel Line or as a Road Tunnel Point. All road tunnels less than 25m will be shown as Road Tunnel Points. New Road Tunnels less than 100m will be shown as a Road Tunnel Point. For existing tunnels between 25m and 100m the tunnel information will be retained in the same geometry as captured in the base material/digital data.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Road tunnels will be shown as lines when they are longer than 250 metres.

General - All Scales

Road tunnels may be named, where name is known.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

RoadTunnelPoints must fall exactly over a vertex on the Road feature.

A Road Tunnel Line and a Road Tunnel Point can not represent the same tunnel.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Tunnels which carry both road and railway traffic will be held as a coincident road tunnel and railway tunnel feature in their respective layers.

Map Rules

General - All Scales

Road tunnels may be named, where name is known.

Related Features

Railway Tunnel Line, Road , Transition point

Related Chapters

Section 3 chapters 5.3, 5.11.2 and 6.7

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.