FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Ferry Route Line

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the ferry service. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
9999 / 9999 / 9999

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

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

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:100 000 Revision source material will be provided for ferry routes to be shown.

At 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.

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 1mm to scale, parallel to each other and carrying the same attributese 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 1mm to scale, parallel to each other and carrying different attributes will be symbolised as a single line. In this case the additional Ferry Route Lines will have a symbol number 0.

Only operational ferry routes will be shown. Ferry routes not connected on both ends to either the road and/or rail network, must be greater than 3mm in length at map scale to be captured.

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.  

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

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 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.  

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.

Railway , Road  

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Foot Bridge

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / -

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

268  

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]
 

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

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

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.
 

Foot Track 

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Foot Track

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the foot track. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

22
0 - Where associated with a road

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:250 000 details of foot tracks to be included will be supplied, only tracks of national significance will be included.

At 1:100 000 scale popular scenic / tourist foot or bridle paths will be shown.
 
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 revision source material they are to be labelled ' (position approximate)'

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.

Foot Tracks coincident with roads should have a symbol equal to '0'. A descriptive note may be added to the Textnote field, for example ‘Hume and Hovell Walking Trail follows track’.

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.)  

Foot Bridge, Road

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Ford Line

SUBTYPE NUMBER (TYPE) [Long Integer; No; 5; Pop_Req] The numeric value assigned to sub classify the feature
1

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
FordLine

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the ford. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

21
0 (non printing line)

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

Currently not used by symbology; 0

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

All feature occurrences on the base material/digital data or the latest previous edition map will be shown unless there is clear evidence they no longer exist.

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

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

All fords, including those not symbolised, are to be TextNoted ‘ford’.  

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.

 

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.

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.

Road, Road Bridge Line, Road Bridge Point, Road Causeway , Watercourse, Watercourse Area 

Section 3 chapters 5.10 and 5.11.2  

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Ford Point

SUBTYPE NUMBER (TYPE) [Long Integer; No; 5; Pop_Req] The numeric value assigned to sub classify the feature
1

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
FordPoint

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the ford. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

0

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

Currently not used by symbology; 0

ORIENTATION (ORIENTATION) [Short Integer; Yes; 3; Pop_Dep] Orientation in whole degrees from East going anti-clockwise;
Currently not used for symbology; 0

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

All feature occurrences on the base material/digital data or the latest previous edition map will be shown unless there is clear evidence they no longer exist.

Where a ford creates a gap in the road network it will be closed by a Ford Line.  
Fords shorter than 3 mm at map scale, including point features, will not be symbolised (symbol = 0).

All fords, including those not symbolised, are to be TextNoted ‘ford’.  

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

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

Ford Points must be coincident with a vertex on a linear watercourse.

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

Road, Road Bridge Line, Road Bridge Point, Road Causeway , Watercourse, Watercourse Area 

Section 3 chapters 5.9, 5.10 and 5.11.2  

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Gate

SUBTYPE NUMBER (TYPE) [Long Integer; No; 5; Pop_Req] The numeric value assigned to sub classify the feature
1

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
Gate

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

26

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

Currently not used by symbology; 0

ORIENTATION (ORIENTATION) [Short Integer; Yes; 3; Pop_Dep] Orientation in whole degrees from East going anti-clockwise;
0 - 360

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:100 000 this feature will only be shown 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.

At 1:250 000 this feature will only be shown 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.

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 or Dog-proof fences which will be shown in all areas. 

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

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.

Gates cannot appear in;
Building Area, Sea, Lake, Canal Area, Watercourse Area or Flood Irrigation Storage, Town Rural Storage.  

The underlying fence symbol will be masked out for the gate symbol.  

Fence, Road , Grid 

Section 3 chapters 5.9 and 5.11.2
Appendix C  

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Grid

SUBTYPE NUMBER (TYPE) [Long Integer; No; 5; Pop_Req] The numeric value assigned to sub classify the feature
2

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
Grid

MAP NUMBER (MAPNUMBER) [String; Yes; 8; Pop_Dep] The number that defines the map index to which the feature is related.

Number should not be populated for this feature.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

25

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

Currently not used by symbology; 0

ORIENTATION (ORIENTATION) [Short Integer; Yes; 3; Pop_Dep] Orientation in whole degrees from East going anti-clockwise;
0 - 360  

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:100 000 this feature will only be shown in sparsely settled regions as defined by Appendix C ‘Fence and Water Facilities Guide’ except for Grids on Vermin Proof fences which will be shown in all areas.

At 1:250 000 this feature will only be shown 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.

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

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

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.

Grids cannot overlap;
Lake, Flood Irrigation Storage, Town Rural Storage, Watercourse Area, Canal Area, Building Area or Sea.  

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

Fence, Gate , Road 

Section 3 chapters 5.9 and 5.11.2
Appendix C  

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Road

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the road. (see Geodatabase Rules and Section 3 chapter 6.7.1)

CLASSIFICATION (CLASS) [String; No;40; Pop_Req] The entities classification or status;
Applicable field entries

Dual Carriageway
Principal Road
Secondary Road
Minor Road
Track

FORMATION (FORMATION) [String; No; 18; Pop_Req] Type of road surface;
Applicable field entries

Sealed
Unsealed
Unknown
Under Construction

NATIONAL ROUTE NUMBER (NRN) [String; Yes; 12; 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; Pop_Wk] 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; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

250 – Dual carriageway
251 - Principal sealed
258 - Principal unsealed
256 - Secondary sealed
259 - Secondary unsealed
257 - Minor sealed
253 - Minor unsealed
254 - Vehicular track
252 - Under construction
0 - non-printing (see Geodatabase Rules)

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

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:

Feature width; Road class;
0.9 - Dual carriageway
0.9 - Principal road
0.6 - Secondary road
0.4 - Minor road

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 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.

At 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.

At 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.

Road classifications will be as shown on the roads revision source 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 revision source 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.

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 1 mm at map scale the dual carriageway will be symbolised using symbol 250. If the separation of the carriageways is greater than 1mm at map scale, each carriageway will be shown in its true position, classified as principal road and have symbol number 251.

All vehicular tracks will be considered as formation unsealed. When source 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 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.

At 1:250 000 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 revision source 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 revision source 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.

At 1: 100 000 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 revision source material supplied.


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 under construction will be textnoted ‘under construction’.

Roads whose position is questionable will be textnoted ‘position approximate’.

Roads will have nodes at all intersections.  

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.

Roads cannot overlap;
Sea, Flood Irrigation Storage, Town Rural Storage, Lake perennial, Canal Areas, Watercourse Area perennial.

Roads cannot intersect;
Cliff, Cutting, Razorback and Embankment.

For detailed rules regarding situations involving roads, vehicle tracks, fences and vermin proof fences please refer to the Fence feature type in Appendix A.

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

At 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 shown. 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.

At 1:100 000 minor roads entering a builtup 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 minor roads will be shown to reflect the Built-up Area’s road pattern. Select the major through routes (from Primary 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.

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

At 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.

At 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.


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’. 

The road subclass ‘Dual Carriageway’ will mask all other road subclasses (e.g. ‘Principle Road’, ’Secondary Road’, ’Minor Road’, ’Track’).

Built Up Area, Cemetery Area, RecreationAreas (Feature Class), Ferry Route Line, Ford Line, Ford Point, Gate, Distance Indicator, Gorge, Pass, Road Junction, Place Name, Populated Place, Prohibited Area Boundary Line, Road Bridge Line, Road Bridge Point, Road Causeway, Arrow, Road Tunnel Line, Road Tunnel Point, Road Marker National, Road Marker State, Reserve Boundary Line, Grid , Transition point 

Section 2 chapter 2.2.3
Section 3 chapters 5.8, 5.11.2 and 6.7
Appendix C  
Appendix U chapters 2.2.1, 2.2.2, 2.2.4, 2.2.5, 2.4.4

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Road Bridge Line

SUBTYPE NUMBER (TYPE) [Long Integer; No; 5; Pop_Req] The numeric value assigned to sub classify the feature
2

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
RoadBridgeLine

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the road bridge. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

260

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

The width of the symbol determined by the road classification (in millimetres);

Width; Road class;
0.9 - Dual Carriageway
(note; width varies)
0.9 - Principal road
0.6 - Secondary road
0.4 - Minor road
0.2 - Vehicular track

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:100 000 size and any other selection criteria apply to all feature occurrences. Road bridges will not be included when the road crossing the bridge has been removed within a Built-up area (see Road).

At 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).

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.

Bridges will be shown as points when they are shorter than 0.4 mm to scale.

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 which carry both road and rail traffic will be held as coincident road bridge and railway bridge features in their respective layers.
 
Bridges of distinctive construction may be TextNoted (e.g 'drawbridge','swing bridge').  

At 1:100 000, 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.

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.

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 of distinctive construction may be labelled (e.g 'drawbridge','swing bridge').

Road bridges may be named, where name is known. 

Ford Line, Ford Point, Railway Bridge Line, Railway Bridge Point, Road , Road Causeway 

Section 3 chapters 5.8, 5.11.2 and 6.7  

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Road Bridge Point

SUBTYPE NUMBER (TYPE) [Long Integer; No; 5; Pop_Req] The numeric value assigned to sub classify the feature
2

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
RoadBridgePoint

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the road bridge. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

260
0 - When in close proximity to other features causing clutter.

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

The width of the symbol determined by the road classification (in millimetres);

Width; Road class;
0.9 - Dual Carriageway
(note; width varies)
0.9 - Principal road
0.6 - Secondary road
0.4 - Minor road
0.2 - Vehicular track

ORIENTATION (ORIENTATION) [Short Integer; Yes; 3; Pop_Dep] Orientation in whole degrees from East going anti-clockwise;
0 - 360

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:100 000 size and any other selection criteria apply to all feature occurrences. Road bridges will not be included when the road crossing the bridge has been removed within a Built-up area (see Road).

At 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).

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.

Bridges will be shown as points when they are shorter than 0.4 mm to scale. When the length is longer than 0.4 mm to scale, bridges will be shown as chains.

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 which carry both road and rail traffic will be held as coincident road bridge and railway bridge features in their respective layers.
 
Bridges of distinctive construction may be TextNoted (e.g 'drawbridge','swing bridge').  

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

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.

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.

Ford Line, Ford Point, Railway Bridge Line, Railway Bridge Point, Road , Road Causeway 

Section 3 chapters 5.8, 5.9, 5.11.2 and 6.7  

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Road Causeway

SUBTYPE NUMBER (TYPE) [Long Integer; No; 5; Pop_Req] The numeric value assigned to sub classify the feature
3

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
RoadCauseway

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the road causeway. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

245

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

The width of the symbol determined by the road classification (in millimetres);

Width; Road class;
0.9 - Dual Carriageway
(note; width varies)
0.9 - Principal road
0.6 - Secondary road
0.4 - Minor road
0.2 - Vehicular track

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:100 000 size and any other selection criteria apply to all feature occurrences.

At 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.

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.
 
Road causeways will be textnoted ‘causeway’.  

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.

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

Ford Line, Ford Point, Railway Causeway, Road , Road Bridge Line, Road Bridge Point 

Section 3 chapters 5.8 and 5.11.2  

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Road Overpass

SUBTYPE NUMBER (TYPE) [Long Integer; No; 5; Pop_Req] The numeric value assigned to sub classify the feature
5

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
RoadOverpass

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the road overpass. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / -

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

267

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

The width of the symbol determined by the road classification (in millimetres);

Width; Road class;
0.9 - Dual Carriageway
(note; width varies)
0.9 - Principal road
0.6 - Secondary road
0.4 - Minor road
0.2 - Vehicular track

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:100 000 size and any other selection criteria apply to all feature occurrences. Road overpasses will not be included when the road crossing the overpass has been removed within a Built-up area (see Road).

Only significant overpasses will be shown. 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.

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.

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

Road overpasses may be named, where name is known. 

Ford Line, Ford Point, Railway Bridge Line, Railway Bridge Point, Road Bridge Line, Road Bridge Point, Railway Causeway, Road Causeway, Railway Overpass

Section 3 Chapters 5.8, 5.11.2, 6.7

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Road Tunnel Line

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

205

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

Currently not used by symbology; 0

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:100 000 size and any other selection criteria apply to all feature occurrences.

At 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 1 mm to scale.
 
Road tunnels may be named, the name will be held in the textnote field. 

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.

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

Road tunnels may be named.  

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

Railway Tunnel Point, Road , Transition point 

Section 3 chapters 5.11.2 and 6.7  

FEATURE TYPE (FEATURETYPE) [String; No; 32; Pop_Req] The code which identifies the type of topographic feature represented

Road Tunnel Point

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 40 / 100

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

0

FEATURE WIDTH (FEATUREWIDTH) [Double; Yes; 8; 4; Pop_Dep]

Currently not used by symbology; 0

ORIENTATION (ORIENTATION) [Short Integer; Yes; 3; Pop_Dep] Orientation in whole degrees from East going anti-clockwise;
Currently not used by symbology; 0

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

At 1:100 000 size and any other selection criteria apply to all feature occurrences.

At 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.

When the length is longer than 1 mm to scale, tunnels will be shown as Road Tunnel Line features.

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

Road tunnels may be named, the name will be held in the textnote field. 

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

Road tunnels may be named.  

Railway Tunnel Line, Road , Transition point 

Section 3 chapters 5.11.2 and 6.7