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

Dual Carriageway

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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.

DualCarriageway

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the road. (see Geodatabase Rules and Section 3 chapter 6.7.1)

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

CONTROLLING AUTHORITY (AUTHORITY) [String;Yes;100;0;0;Pop_Req] Name of controlling authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status;

Acceptable Domain Entries from dm_RoadClassification;
Principal Road
Secondary Road
Minor Road

FORMATION (FORMATION) [String;Yes(No);18;0;0;Pop_Req] Type of road surface;

Acceptable Domain Entries from dm_RoadFormation;
Sealed
Unimproved
Unknown
Unsealed

FUNCTIONAL ROAD CLASSIFICATION (FUNCTION) [String;Yes(No);25;0;0;Pop_Dep] The functional hierarchy classification for roads allowing cross jurisdictional translation;

Acceptable Domain Entries from dm_RoadFunction;
National Or State Highway
Arterial Road
Sub Arterial Road
Collector Road
Local Road
Access Road
Service Road
Unknown

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

MAINTENANCE AUTHORITY (MAINTAINER) [String;Yes;50;0;0;Pop_Wk] Name of maintenance authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

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.

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

Acceptable Domain Entries from dm_NumberOfLanes;
More Than Two
One
Two
Unknown

OPERATIONAL STATUS OF ROAD (ROADSTATUS) [String;Yes(No);20;0;0;Pop_Req] The roads operational status;

Acceptable Domain Entries from dm_RoadStatus;
Closed
Notional
Operational
Proposed
Under Construction

SPEED LIMIT FOR ROAD SECTION (SPEEDLIMITKM) [SmallInteger;Yes(No);0;3;0;Pop_Wk] The speed limit in kms per hour for the designated section of road.

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.

LIMITATION TO TRAFFIC ACCESS (TRAFFICABILITY) [String;Yes(No);20;0;0;Pop_Wk] The limitation of a given vehicle to gain through access along a section of road.

Acceptable Domain Entries from RoadAccess;
No Known Limitations
Seasonal
Weather Permitting

DIRECTION OF TRAVEL (TRAVELDIRECTION) [String;Yes(No);12;0;0;Pop_Wk] The direction of travel of vehicles along a section of road.

Acceptable Domain Entries from dm_TravelDirection;
Alternating
One Way
Two Way
Unknown

ROAD USER ACCESS (USERACCESS) [String;Yes(No);10;0;0;Pop_Wk] The type of user restriction placed on road access.

Acceptable Domain Entries from dm_UserAccess;
Authorised
Public
Restricted
Tollway

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

METHOD OF CAPTURE (CAPTUREMETHOD) [String;Yes(No);60;0;0;Pop_Dep] The method of capture of a feature. This field is to be used to hold translated information from stakeholders and should not be altered unless specifically instructed by Geoscience Australia.

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 2 500 000 PRODUCTS (SYMBOL2_5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 5 000 000 PRODUCTS (SYMBOL5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 10 000 000 PRODUCTS (SYMBOL10Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

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

See Section 3 Chapter 6.7.4 Attribute Fields Defined for Roads Feature Class for further explanation of the domain options utilised within the Data Attributes Component.

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

Roads will not be added only from interpretation of the imagery (unless specifically requested by Geoscience Australia). However obvious road realignments may be captured when significant.

The practice of applying the 'Unknown' formation to roads should be limited to exceptional circumstances.

All dual carriageways will be named.

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

Feature width values assigned for road under construction symbol representations should reflect the associated road classifications see Feature Width Meaning for more details.

When assigning Upperscale values to Dual Carriageways, the separation of the carriageways is a consideration:

• All carriageways will be assigned a minimum upperscale of 25 000
• Where the separation between carriageways is less than 100m, one carriageway will be assigned a maximum upperscale of 25 000 and one carriageway will be assigned a minimum upperscale of 100 000
• Where the separation between carriageways is equal to or greater than 100m but less than 250m, one carriageway will be assigned a maximum upperscale of 100 000 and one carriageway will be assigned a minimum upperscale of 250 000
• Where the separation between carriageways is equal to or greater than 250m but less than 1000m, one carriageway will be assigned a maximum upperscale of 250 000 and one carriageway will be assigned a minimum upperscale of 1 000 000
• Only one of the two carriageways will be eligible for upperscales of 2 500 000 and smaller scales (eg 10 000 000).

General - All Scales

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 will have nodes at all intersections.

General - All Scales

Roads cannot overlap the following features unless associated with a Road Crossing Line;
Sea, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Lake (Perennial), Canal Areas, WatercourseAreas (feature class) (Perennial).

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

The General Interrelationship - External rule stating 'Roads cannot overlap Town Water Storage, Rural Water 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 dried due to the drought conditions within Australia. When this occurs the representation of the road in the appropriate scale symbol fields (eg SYMBOL100K, SYMBOL 250K, etc) should be adjusted to show only the portions of the feature which does not exist within the extents of the high water mark of the waterbody.

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.

When assigning an Upperscale of 250000 or smaller scale (larger area), minor roads entering a built up 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 eligible for an Upperscale of 250000 or smaller scale (larger area). 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.

1:100 000

Naming of minor roads and vehicular tracks should give preference to features which constitute 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 built up area will be given a symbol of '242'. The only exception will be when this application results in illegibility 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 built up 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 built up 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.

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

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, Ferry Route Line, Ford Line, Ford Point, Fence Standard, Fence Vermin Proof, Gate, Distance Indicator, Gorge, Grid, Pass, Place Name, Populated Place, Road Bridge Line, Road Causeway, Road Junction, Road Overpass, Arrow, Road Tunnel Line, Road Marker National, Road Marker State, Transition Point

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.8, 5.11.2, 5.20, 6.7
Appendix C
Appendix U Chapters 2.2, 2.4

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

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

Culvert Line

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

7

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

CulvertLine

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

This field is not applicable to this subtype and therefore is currently not to be populated;

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

Culvert Lines should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for RoadCrossingLines Feature Class.

General - All Scales

Convert 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 Culvert Line. The road must continue outwards from both endpoints of the Culvert Line.

Ford Line, Ford Point, Railway Bridge Line, Railway Causeway, Dual Carriageway, Standard Road, Vehicular Track, Road Bridge Line, Road Overpass

Section 3 Chapters 5.8 and 5.11.2

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

Culvert Point

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

7

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

CulvertPoint

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

This field is not applicable to this subtype and therefore is currently not to be populated;

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

Culvert Points should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for RoadCrossingPoints Feature Class.

General - All Scales

Culvert Points must be coincident with a vertex in the road network.

General - All Scales

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

Dual Carriageway, Standard Road, Vehicular Track, Road Bridge Line, Road Bridge Point, Road Causeway , Watercourse, Watercourse Area, Ford Line

Section 3 Chapters 5.3, 5.9, 5.10 and 5.11.2

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

Ferry Route Line

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

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

PASSENGER CAPACITY NUMBER (PASSENGERCAPACITY) [Integer;Yes(No);0;5;0;Pop_Wk] The number of passengers legally allowed to be transported on vessel, vehicle or aircraft.

VEHICLE CAPACITY NUMBER (VEHICLECAPACITY) [Integer;Yes(No);0;5;0;Pop_Wk] The number of vehicles legally allowed on to be transported on vessel, vehicle or aircraft.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

All ferry routes on existing base material/digital data 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 ((3 * Capture Scale)/1000) metres in length to be captured (eg for 1:25,000 the length is required to be greater than or equal to ((3 * 25000)/1000) m = 75m).

To be assigned a specific Upperscale Value a Ferry Route Line must be:

• connected on both ends to either the road and/or rail network which has the equivalent or higher upperscale value; or


• the ferry route line must have a length greater than or equal to ((3 * Upperscale Value)/1000) m (eg for 25000 the length is required to be greater than or equal to ((3 * 25000)/1000) m = 75m).

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.

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 WatercourseAreas (feature class), Lake, Reservoirs (feature class) 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.

General - All Scales

To be assigned a symbol value other than line no draw at a certain scale a Ferry Route Line must be:

• connected on both ends to either the road and/or rail network which has the equivalent or higher upperscale value; or


• the ferry route line must have a length greater than or equal to ((3 * Upperscale Value)/1000)m. eg for 25000 the length is required to be greater than or equal to ((3 * 25000)/1000)m = 75m.

Railway, Dual Carriageway, Standard Road, Vehicular Track,

Section 3 Chapter 5.3

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

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

Fixed Speed Camera

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

8

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

FixedSpeedCamera

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

This field is not applicable to this subtype and therefore is currently not to be populated;

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

New Fixed Speed Cameras should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for TrafficControlDevice Feature Class.

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

Foot Bridge

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

Acceptable Domain Entries from dm_CrossingStructure;
Arch
Beam
Cable Stayed
Cantilever
Drawbridge
Suspension
Truss

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

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

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.

Foot Track

NTMS 100K

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

Foot Track

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

FORMATION (FORMATION) [String;Yes(No);18;0;0;Pop_Req] Type of road surface;

Acceptable Domain Entries from dm_FoottrackFormation;
Boardwalk
Sealed
Unimproved
Unknown
Unsealed

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

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

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

General - All Scales

Where the foot track 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.

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.

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

Foot Bridge, Dual Carriageway, Standard Road, Vehicular Track

Section 3 Chapter 5.3

GEODATA TOPO250K, NTMS 100K, NTMS 250K, Global Map,

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

Ford Line

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

This field is not applicable to this subtype and therefore is currently not to be populated;

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
UNKNOWN

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

Existing crossing lines (e.g. bridges, causeways, fords) on the base material/digital data should be retained or on the latest previous (1:25000 or 1:100 000 topographic) edition map should be captured 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 transverse an obstacle such as a watercourse or gully an Action Request should be raised seeking clarification.

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

Fords Lines shorter than 300 metres for SYMBOL100K and shorter than 750 metres for SYMBOL250K will be given symbol 1 - line no draw. In addition, if the associated road/s are not applicable to 1:100000 or 1:250000 then SYMBOL100K and SYMBOL250K respectively will be given symbol 1 - line no draw. All other features will have symbol 21 - ford line.

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.

The same entity can not be captured as both a Ford Line and Ford Point.

General - All Scales

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

Linear Fords can only appear over WatercourseAreas (feature class) or Lakes; a vertex should exist in the polygon at the entry and exit location of the linear ford.

General - All Scales

All fords, including those not symbolised, are to be labelled 'ford' where the associated roads are applicable for the map scale.

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 = 1 - LineNoDraw).

Dual Carriageway, Standard Road, Vehicular Track, Road Bridge Line, Road Bridge Point, Road Causeway , Watercourse, Watercourse Area, Ford Point

Section 3 Chapters 5.10 and 5.11.2
Appendix U Chapters 2.2

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

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

Ford Point

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

This field is not applicable to this subtype and therefore is currently not to be populated;

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
UNKNOWN

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

Existing crossing points (e.g. bridges, fords) on the base material/digital data should be retained or on the latest previous (1:25000 or 1:100 000 topographic) edition map should be captured 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 point exists at that location. However, if the road appears to transverse an obstacle such as a watercourse or gully an Action Request should be raised seeking clarification.

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

Ford Points will be given a SYMBOL100K and SYMBOL250K value of 2 - point no draw.

General - All Scales

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

General - All Scales

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.

General - All Scales

All fords, including those not symbolised, are to be labelled 'ford' where the associated roads are applicable for the map scale.

Dual Carriageway, Standard Road, Vehicular Track, Road Bridge Line, Road Bridge Point, Road Causeway , Watercourse, Watercourse Area, Ford Line

Section 3 Chapters 5.3, 5.9, 5.10 and 5.11.2
Appendix U Chapters 2.2

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

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

Gate

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

6

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

Gate

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

This field is not applicable to this subtype and therefore is currently not to be populated;

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

Existing gates in base material/digital data will be retained unless directed otherwise.

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.

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 or gates crossing public roads (not entry driveways to private land) limiting through access which will be shown in all areas. New features must be derived from either field inspection information or Authorised Reference Material, it can not be captured from imagery alone.

Only gates within sparsely settled regions, situated on a vermin proof fence or limiting through access on a public road (not entry driveways to private land) will be eligible to be classified with an upperscale value of 100000 or smaller scale (larger area).

The Upperscale of the gate is dependant on the Upperscale of it's associated road. (eg If the associated road is assigned an Upperscale of 250000 then the Upperscale of the Gate is only eligible to be classified 250000 or larger scale (smaller area). The gate can not be assigned an Upperscale of 1000000.)

General - All Scales

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

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.

Gates cannot appear in;
BuildingAreas (feature class), Sea, Lake, Canal Area, WatercourseAreas (feature class), Flood Irrigation Storage, Town Water Storage, Rural Water Storage.

General - All Scales

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

The gate symbol should be oriented along the path of its associated fence as per the following diagram:

Fence Standard, Fence Vermin Proof , Dual Carriageway, Standard Road, Vehicular Track, Grid

Section 3 Chapters 5.3, 5.9, 5.11.2
Appendix C

GEODATA TOPO250K, NTMS 100K, NTMS 250K

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

Grid

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

7

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

Grid

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

This field is not applicable to this subtype and therefore is currently not to be populated;

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

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 grids on Vermin Proof fences which will be shown in all areas. The feature must be derived from either field inspection information or Authorised Reference Material, it can not be captured from imagery alone.

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

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

The Upperscale of the grid is dependant on the Upperscale of it's associated road. (eg If the associated road is assigned an Upperscale of 100000 then the Upperscale of the Grid is only eligible to be classified 100000 or larger scale (smaller area).The grid can not be assigned an Upperscale of 250000.)

General - All Scales

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

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.

Grids cannot overlap;
Lake, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, WatercourseAreas (feature class), Canal Area, BuildingAreas (feature class) or Sea.

General - All Scales

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

The grid symbol should be oriented along the path of its associated road as per the following diagram:

Fence Standard, Fence Vermin Proof, Dual Carriageway, Standard Road, Vehicular Track, Gate

Section 3 Chapters 5.3, 5.9, 5.11.2
Appendix C

GEODATA TOPO250K, NTMS 100K, NTMS 250K

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

Level Crossing

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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.

LevelCrossing

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

This field is not applicable to this subtype and therefore is currently not to be populated;

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

New Level Crossing should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for TrafficControlDevice Feature Class.

General - All Scales

Level Crossings must fall exactly on the Road. A vertex will be added to the Road to ensure the Railway, Road and Level Crossing are coincident with each other.

General - All Scales

Level Crossings must fall exactly on the Railway. A vertex will be added to the Railway to ensure the Railway, Road and Level Crossing are coincident with each other.

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

Pedestrian Crossing

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

9

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

PedestrianCrossing

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

This field is not applicable to this subtype and therefore is currently not to be populated;

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

New Pedestrian Crossings should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for TrafficControlDevice Feature Class.

General - All Scales

Pedestrian Crossings must be coincident with a vertex in the road network.

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

Permanent Barrier

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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.

PermanentBarrier

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

This field is not applicable to this subtype and therefore is currently not to be populated;

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

New Permanent Barriers should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for TrafficControlDevice Feature Class.

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

Ramp

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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.

Ramp

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the road. (see Geodatabase Rules and Section 3 chapter 6.7.1)

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

CONTROLLING AUTHORITY (AUTHORITY) [String;Yes;100;0;0;Pop_Req] Name of controlling authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status;

Acceptable Domain Entries from dm_RoadClassification;
Principal Road
Secondary Road
Minor Road
Vehicular Track

FORMATION (FORMATION) [String;Yes(No);18;0;0;Pop_Req] Type of road surface;

Acceptable Domain Entries from dm_RoadFormation;
Sealed
Unimproved
Unknown
Unsealed

FUNCTIONAL ROAD CLASSIFICATION (FUNCTION) [String;Yes(No);25;0;0;Pop_Dep] The functional hierarchy classification for roads allowing cross jurisdictional translation;

Acceptable Domain Entries from dm_RoadFunction;
National Or State Highway
Arterial Road
Sub Arterial Road
Collector Road
Local Road
Access Road
Service Road
Unknown

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

MAINTENANCE AUTHORITY (MAINTAINER) [String;Yes;50;0;0;Pop_Wk] Name of maintenance authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

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.

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

Acceptable Domain Entries from dm_NumberOfLanes;
More Than Two
One
Two
Unknown

OPERATIONAL STATUS OF ROAD (ROADSTATUS) [String;Yes(No);20;0;0;Pop_Req] The roads operational status;

Acceptable Domain Entries from dm_RoadStatus;
Closed
Notional
Operational
Proposed
Under Construction

SPEED LIMIT FOR ROAD SECTION (SPEEDLIMITKM) [SmallInteger;Yes(No);0;3;0;Pop_Wk] The speed limit in kms per hour for the designated section of road.

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.

LIMITATION TO TRAFFIC ACCESS (TRAFFICABILITY) [String;Yes(No);20;0;0;Pop_Wk] The limitation of a given vehicle to gain through access along a section of road.

Acceptable Domain Entries from RoadAccess;
No Known Limitations
Seasonal
Weather Permitting

DIRECTION OF TRAVEL (TRAVELDIRECTION) [String;Yes(No);12;0;0;Pop_Wk] The direction of travel of vehicles along a section of road.

Acceptable Domain Entries from dm_TravelDirection;
Alternating
One Way
Two Way
Unknown

ROAD USER ACCESS (USERACCESS) [String;Yes(No);10;0;0;Pop_Wk] The type of user restriction placed on road access.

Acceptable Domain Entries from dm_UserAccess;
Authorised
Public
Restricted
Tollway

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

METHOD OF CAPTURE (CAPTUREMETHOD) [String;Yes(No);60;0;0;Pop_Dep] The method of capture of a feature. This field is to be used to hold translated information from stakeholders and should not be altered unless specifically instructed by Geoscience Australia.

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 2 500 000 PRODUCTS (SYMBOL2_5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 5 000 000 PRODUCTS (SYMBOL5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 10 000 000 PRODUCTS (SYMBOL10Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

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

See Section 3 Chapter 6.7.4 Attribute Fields Defined for Roads Feature Class for further explanation of the domain options utilised within the Data Attributes Component.

Roads will not be added only from interpretation of the imagery (unless specifically requested by Geoscience Australia). However obvious road realignments may be captured when significant.

Ramps will be assigned the lower Function Classification of the two roads the ramp is connecting. Ramps will be given a Classification of 'Minor'.

The practice of applying the 'Unknown' formation to roads should be limited to exceptional circumstances.

All principal roads will be named. Secondary roads should be named where name is known. 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.

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

Feature width values assigned for road under construction symbol representations should reflect the associated road classifications see Feature Width Meaning for more details.

Upperscale of Ramps will be based on the minimum size for map representation and consideration of the resultant clutter which may occur when reviewed with the surrounding road selection.

Ramps which meet the appropriate Upperscale assignments will be symbolised as per their classification.

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 '1' - line no draw.

General - All Scales

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 will have nodes at all intersections.

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.

General - All Scales

Roads cannot overlap the following features unless associated with a Road Crossing Line;
Sea, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Lake Perennial, Canal Areas, WatercourseAreas (feature class) Perennial.

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

The General Interrelationship - External rule stating 'Roads cannot overlap Town Water Storage, Rural Water 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 dried due to the drought conditions within Australia. When this occurs the representation of the road in the appropriate scale symbol fields (eg SYMBOL100K, SYMBOL 250K, etc) should be adjusted to show only the portions of the feature which does not exist within the extents of the high water mark of the waterbody.

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.

When assigning an Upperscale of 250000 or smaller scale (larger area), minor roads entering a built up 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 eligible for an Upperscale of 250000 or smaller scale (larger area). 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.

1:100 000

Naming of minor roads and vehicular tracks should give preference to features which constitute 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 built up area will be given a symbol of '242'. The only exception will be when this application results in illegibility 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 built up 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 built up 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.

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

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

Built Up Area, Cemetery Area, Ferry Route Line, Ford Line, Ford Point, Fence Standard, Fence Vermin Proof, Gate, Distance Indicator, Gorge, Grid, Pass, Place Name, Populated Place, Road Bridge Line, Road Causeway, Road Junction, Road Overpass, Arrow, Road Tunnel Line, Road Marker National, Road Marker State, Transition Point

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.8, 5.11.2, 5.20, 6.7
Appendix C
Appendix U Chapters 2.2, 2.4

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

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

Road Bridge Line

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

Acceptable Domain Entries from dm_CrossingStructure;
Arch
Beam
Cable Stayed
Cantilever
Drawbridge
Suspension
Truss

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
UNKNOWN

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

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

All new bridges should be captured as Road Bridge Lines.

Existing Road Bridge Points on the base material/digital data or the latest previous edition map should be recaptured as Road Bridge Lines during maintenance/revision processes unless there is evidence that they no longer exist. When applicable the associated Road Bridge Point in the base material/digital data should be deleted.

The minimum size criteria for Data Capture and Map Representation of a new Road Bridge Line during a 1:100 000 revision process of 30m applies only to Sparsely Settled Areas as defined by Appendix C, in all other areas the minimum size criteria for Data Capture and Map Representation size is 40m.

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.

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

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

For SYMBOL 100K, only bridges above the minimum size for map representation (taking note of the different size criteria based on appendix C) and associated with a road classified as UPPERSCALE 100000 should be shown with a symbol other than line no draw. The only exception would be a bridge of historical significance or a bridge no longer associated with a defined road which still meets the minimum size for map representation. For Bridges below 50m in length the appropriate Bridge Line to Point symbol should be used dependant on road classification. For Bridges greater than 50m these can be represented as linear bridges. Where clutter occurs 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 on minor roads and vehicular tracks in built up areas will be given a value of 1 - line no draw; 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 with the appropriate linear symbol value.

For SYMBOL 250K, only bridges above the minimum size for map representation and associated with a road classified as UPPERSCALE 250000 should be shown with a symbol other than line no draw. The only exception would be a bridge of historical significance or a bridge no longer associated with a defined road which still meets the minimum size for map representation. For Bridges between 40m and 100m in length the appropriate Bridge Line to Point symbol should be used dependant on road classification. For Bridges greater than 100m these can be represented as linear bridges. Where clutter occurs 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.

Feature width values assigned in the Road Bridge Line symbol representations should reflect the associated road classifications see Feature Width Meaning for more details.

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.

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.

General - All Scales

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, Dual Carriageway, Standard Road, Vehicular Track, Road Causeway, Road Overpass, Road Bridge Point

Section 3 Chapters 5.8, 5.11.2 and 6.7

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

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

Road Bridge Point

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

Acceptable Domain Entries from dm_CrossingStructure;
Arch
Beam
Cable Stayed
Cantilever
Drawbridge
Suspension
Truss

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
UNKNOWN

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

All new bridges should be captured as Road Bridge Lines.

Existing Road Bridge Points on the base material/digital data or the latest previous edition map should be recaptured as Road Bridge Lines during maintenance/revision processes unless there is evidence that they no longer exist. When applicable the associated Road Bridge Point in the base material/digital data should be deleted.

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 '2' non-printing value.

Feature width values assigned in the Road Bridge Point symbol representations should reflect the associated road classifications see Feature Width Meaning for more details.

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.

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.

1:100 000

Point Bridges on minor roads in built up areas will be symbolised to '2 - PointNoDraw'.

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 '2' PointNoDraw.

Ford Line, Ford Point, Railway Bridge Line, Railway Bridge Point, Dual Carriageway, Standard Road, Vehicular Track, Road Causeway, Road Overpass

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

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

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

Road Causeway

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

This field is not applicable to this subtype and therefore is currently not to be populated;

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
UNKNOWN

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

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

Feature width values assigned in the Road Causeway symbol representations should reflect the associated road classifications see Feature Width Meaning for more details.

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.

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.

Ford Line, Ford Point, Railway Bridge Line, Railway Causeway, Dual Carriageway, Standard Road, Vehicular Track, Road Bridge Line, Road Overpass

Section 3 Chapters 5.8 and 5.11.2

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

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

Road Connector

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

8

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

RoadConnector

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the road. (see Geodatabase Rules and Section 3 chapter 6.7.1)

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

CONTROLLING AUTHORITY (AUTHORITY) [String;Yes;100;0;0;Pop_Req] Name of controlling authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status;

Acceptable Domain Entries from dm_RoadClassification;
Dual Carriageway
Principal Road
Secondary Road
Minor Road
Vehicular Track

FORMATION (FORMATION) [String;Yes(No);18;0;0;Pop_Req] Type of road surface;

Acceptable Domain Entries from dm_RoadFormation;
Sealed
Unimproved
Unknown
Unsealed

FUNCTIONAL ROAD CLASSIFICATION (FUNCTION) [String;Yes(No);25;0;0;Pop_Dep] The functional hierarchy classification for roads allowing cross jurisdictional translation;

Acceptable Domain Entries from dm_RoadFunction;
National Or State Highway
Arterial Road
Sub Arterial Road
Collector Road
Local Road
Access Road
Service Road
Unknown

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

MAINTENANCE AUTHORITY (MAINTAINER) [String;Yes;50;0;0;Pop_Wk] Name of maintenance authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

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.

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

Acceptable Domain Entries from dm_NumberOfLanes;
More Than Two
One
Two
Unknown

OPERATIONAL STATUS OF ROAD (ROADSTATUS) [String;Yes(No);20;0;0;Pop_Req] The roads operational status;

Acceptable Domain Entries from dm_RoadStatus;
Closed
Notional
Operational
Proposed
Under Construction

SPEED LIMIT FOR ROAD SECTION (SPEEDLIMITKM) [SmallInteger;Yes(No);0;3;0;Pop_Wk] The speed limit in kms per hour for the designated section of road.

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.

LIMITATION TO TRAFFIC ACCESS (TRAFFICABILITY) [String;Yes(No);20;0;0;Pop_Wk] The limitation of a given vehicle to gain through access along a section of road.

Acceptable Domain Entries from RoadAccess;
No Known Limitations
Seasonal
Weather Permitting

DIRECTION OF TRAVEL (TRAVELDIRECTION) [String;Yes(No);12;0;0;Pop_Wk] The direction of travel of vehicles along a section of road.

Acceptable Domain Entries from dm_TravelDirection;
Alternating
One Way
Two Way
Unknown

ROAD USER ACCESS (USERACCESS) [String;Yes(No);10;0;0;Pop_Wk] The type of user restriction placed on road access.

Acceptable Domain Entries from dm_UserAccess;
Authorised
Public
Restricted
Tollway

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

METHOD OF CAPTURE (CAPTUREMETHOD) [String;Yes(No);60;0;0;Pop_Dep] The method of capture of a feature. This field is to be used to hold translated information from stakeholders and should not be altered unless specifically instructed by Geoscience Australia.

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 2 500 000 PRODUCTS (SYMBOL2_5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 5 000 000 PRODUCTS (SYMBOL5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 10 000 000 PRODUCTS (SYMBOL10Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

Road Connectors will carry the attributes of the road they represent.

See Section 3 Chapter 6.7.4 Attribute Fields Defined for Roads Feature Class for further explanation of the domain options utilised within the Data Attributes Component.

Upperscale will be assigned based on their associated Road.

For Symbol100K, where the associated roundabout has been symbolised, the associated road connectors will have a symbol of 1 Line No Draw.

At all other scales, symbolisation of the road connector should reflect its associated road's symbolisation.

General - All Scales

Roads will have nodes at all intersections.

General - All Scales

Roads cannot overlap the following features unless associated with a Road Crossing Line;
Sea, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Lake Perennial, Canal Areas, WatercourseAreas (feature class) Perennial.

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

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 Water Storage, Rural Water 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 dried due to the drought conditions within Australia. When this occurs the representation of the road in the appropriate scale symbol fields (eg SYMBOL100K, SYMBOL 250K, etc) should be adjusted to show only the portions of the feature which does not exist within the extents of the high water mark of the waterbody.

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 and associated road connectors will be shown including those in built-up areas.

When assigning an Upperscale of 250000 or smaller scale (larger area), minor roads entering a built up 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 eligible for an Upperscale of 250000 or smaller scale (larger area). 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.

1:100 000

Naming of minor roads and vehicular tracks should give preference to features which constitute 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 built up area will be given a symbol of '242'. The only exception will be when this application results in illegibility 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 built up 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 built up 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.

1:250 000

Minor roads and vehicular tracks will be named where named on the previous 1: 250 000 NTMS 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 constitute through routes and/or lead to cultural or natural features.

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

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, Ferry Route Line, Ford Line, Ford Point, Fence Standard, Fence Vermin Proof, Gate, Distance Indicator, Gorge, Grid, Pass, Place Name, Populated Place, Road Bridge Line, Road Causeway, Road Junction, Road Overpass, Arrow, Road Tunnel Line, Road Marker National, Road Marker State, Transition Point

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.8, 5.11.2, 5.20, 6.7
Appendix C
Appendix U Chapters 2.2, 2.4

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

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

Road Overpass

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

Acceptable Domain Entries from dm_CrossingStructure;
Arch
Beam
Cable Stayed
Cantilever
Drawbridge
Suspension
Truss

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
UNKNOWN

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

Feature width values assigned in the Road Causeway symbol representations should reflect the associated road classifications see Feature Width Meaning for more details.

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.

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.

General - All Scales

Road overpasses may be named, where name is known.

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

Section 3 Chapters 5.8, 5.11.2, 6.7

GEODATA LITE TOPO100K, NTMS 100K

ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.

The following annotation classes exist in RoadTransportAnno;
Arial5ptItalicCenter
Arial5ptItalicLeft
Arial5ptItalicRight
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptLeft
ArialNarrow7ptRight
ArialNarrow8ptCenter

FEATURE (FEATURE) [String;Yes;32;0;0;Pop_Req] The code which identifies the class of topographic feature represented by the annotation. This field must be a legitimate feature class name.

Acceptable Domain Entries from dm_RoadTransportFCs;
FerryRouteLines
FootBridges
FootTracks
RoadCrossingLines
RoadCrossingPoints
Roads
TrafficControlDevices

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification 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.

Annotation should only occur where the associated feature either has a sufficient dimension size or Upperscale value to be shown at 1:100 000 scale or a smaller scale/larger extent (eg 1:250 000, 1:1 000 000)

Section 2 Chapter 5, 9

NTMS 100K

ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.

The following annotation classes exist in RoadTransportAnno;
Arial5ptItalicLeft
Arial5ptItalicRight
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptLeft
ArialNarrow7ptRight
ArialNarrow8ptCenter

FEATURE (FEATURE) [String;Yes;32;0;0;Pop_Req] The code which identifies the class of topographic feature represented by the annotation. This field must be a legitimate feature class name.

Acceptable Domain Entries from dm_RoadTransportFCs;
FerryRouteLines
FootBridges
FootTracks
RoadCrossingLines
RoadCrossingPoints
Roads
TrafficControlDevices

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification 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.

Annotation should only occur where the associated feature either has a sufficient dimension size or Upperscale value to be shown at 1:250 000 scale or a smaller scale/larger extent (eg 1:1 000 000, 1:5 000 000)

Section 2 Chapter 5, 10

NTMS 100K

ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.

The following annotation classes exist in RoadTransportAnno;
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight

FEATURE (FEATURE) [String;Yes;32;0;0;Pop_Req] The code which identifies the class of topographic feature represented by the annotation. This field must be a legitimate feature class name.

Acceptable Domain Entries from dm_RoadTransportFCs;
FootTracks
RoadCrossingLines
Roads
TrafficControlDevices

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification 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 Lambert Conic Conformal Projection ( with two standard parallels and a central meridian per each chart's requirements) to ensure the spatial position of type on the map face can be correctly represented.

Annotation should only occur where the associated feature either has a sufficient dimension size or Upperscale value to be shown at 1:1 000 000 scale or a smaller scale/larger extent (eg 1:2 500 000, 1:10 000 000)

Section 2 Chapter 5, 11

NTMS 100K

ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.

The following annotation classes exist in RoadTransportAnno;
Arial6ptItalic80M73YCenter
Arial6ptItalic80M73YLeft
Arial6ptItalic80M73YRight

FEATURE (FEATURE) [String;Yes;32;0;0;Pop_Req] The code which identifies the class of topographic feature represented by the annotation. This field must be a legitimate feature class name.

Acceptable Domain Entries from dm_RoadTransportFCs;
Roads

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification 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 Simple Conic Projection with two standard parallels of 18 degrees south and 36 degrees south to ensure the spatial position of type on the map face can be correctly represented.

Annotation should only occur where the associated feature either has a sufficient dimension size or Upperscale value to be shown at 1:2 500 000 scale or a smaller scale/larger extent (eg 1:5 000 000, 1:10 000 000)

Section 2 Chapter 5, 12

NTMS 100K

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

Road Tunnel Line

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

6

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

RoadTunnelLine

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

This field is not applicable to this subtype and therefore is currently not to be populated;

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
UNKNOWN

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

All new road tunnels should be captured as Road Tunnel Lines.

Existing Road Tunnel Points on the base material/digital data or the latest previous edition map should be recaptured as Road Tunnel Lines during maintenance/revision processes unless there is evidence that they no longer exist. When applicable the associated Road Tunnel Point in the base material/digital data should be deleted. When the extent on a tunnel is unclear, an Action Request should be sent to Geoscience Australia seeking locational information (eg imagery, plans, etc).

Road tunnels may be named, where name is known.

For SYMBOL 100K, only Road Tunnel Lines above 100m and associated with a road classified as UPPERSCALE 100000 should be shown with a symbol other than 1 - line no draw. The only exception would be a tunnel of historical significance or a tunnel no longer associated with a defined road which still meets the minimum size for map representation. For Road Tunnel Lines greater than 100m these can be represented as linear Tunnels (205 - Tunnel Line).

For SYMBOL 250K, only Road Tunnel Lines above 250m and associated with a road classified as UPPERSCALE 250000 should be shown with a symbol other than line 1 - line no draw. The only exception would be a tunnel of historical significance or a tunnel no longer associated with a defined road which still meets the minimum size for map representation. For Road Tunnel Lines greater than 250m these can be represented as linear Tunnels (205 - Tunnel Line).

For SYMBOL WAC1Mil, only Road Tunnel Lines above 1000m and associated with a road classified as UPPERSCALE 1000000 should be represented as linear Tunnels (205 - Tunnel Line), all other tunnels will be shown with a symbol 1 - line no draw.

For all of the 3 above paragraphs the following applies: Where clutter occurs only significant tunnels will be shown. The significance of the tunnel depends on the number of tunnels in the vicinity, the importance of the road etc. Tunnels on minor roads and vehicular tracks in built up areas will be given a value of 1 - line no draw; The only exception will be tunnels 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 with the appropriate linear symbol value.

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.

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 greater than 100m will be shown by the feature Transition Point.

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.

Road Tunnel Point, Dual Carriageway, Standard Road, Vehicular Track, Transition Point

Section 3 Chapters 5.11.2 and 6.7

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

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

Road Tunnel Point

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

6

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

RoadTunnelPoint

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

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

CROSSING STRUCTURE (CROSSINGSTRUCTURE) [String;Yes(No);20;0;0;Pop_Wk] The type of structure of a feature used to cross an obstacle (eg type of bridge).

This field is not applicable to this subtype and therefore is currently not to be populated;

FLOOD LIMIT IN METRES (FLOODLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended flood water height limit before crossing a feature (eg a vehicle crossing a bridge) is prevented due to risk of injury or possible failure of the features structure.

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
UNKNOWN

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

Existing Road Tunnel Points on the base material/digital data or the latest previous edition map should be recaptured as Road Tunnel Lines during maintenance/revision processes unless there is evidence that they no longer exist. When applicable the associated Road Tunnel Point in the base material/digital data should be deleted. When the extent on a tunnel is unclear, an Action Request should be sent to Geoscience Australia seeking locational information (eg imagery, plans, etc).

All new road tunnels should be captured as Road Tunnel Lines.

Road tunnels may be named, where name is known.

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.

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.

General - All Scales

Road tunnels may be named, where name is known.

Road Tunnel Line, Dual Carriageway, Standard Road, Vehicular Track, Transition Point

Section 3 Chapters 5.3, 5.11.2 and 6.7

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

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

Roundabout

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

4

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

Roundabout

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the road. (see Geodatabase Rules and Section 3 chapter 6.7.1)

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

CONTROLLING AUTHORITY (AUTHORITY) [String;Yes;100;0;0;Pop_Req] Name of controlling authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status;

Acceptable Domain Entries from dm_RoadClassification;
Principal Road
Secondary Road
Minor Road
Vehicular Track

FORMATION (FORMATION) [String;Yes(No);18;0;0;Pop_Req] Type of road surface;

Acceptable Domain Entries from dm_RoadFormation;
Sealed
Unimproved
Unknown
Unsealed

FUNCTIONAL ROAD CLASSIFICATION (FUNCTION) [String;Yes(No);25;0;0;Pop_Dep] The functional hierarchy classification for roads allowing cross jurisdictional translation;

Acceptable Domain Entries from dm_RoadFunction;
National Or State Highway
Arterial Road
Sub Arterial Road
Collector Road
Local Road
Access Road
Service Road
Unknown

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

MAINTENANCE AUTHORITY (MAINTAINER) [String;Yes;50;0;0;Pop_Wk] Name of maintenance authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

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.

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

Acceptable Domain Entries from dm_NumberOfLanes;
More Than Two
One
Two
Unknown

OPERATIONAL STATUS OF ROAD (ROADSTATUS) [String;Yes(No);20;0;0;Pop_Req] The roads operational status;

Acceptable Domain Entries from dm_RoadStatus;
Closed
Notional
Operational
Proposed
Under Construction

SPEED LIMIT FOR ROAD SECTION (SPEEDLIMITKM) [SmallInteger;Yes(No);0;3;0;Pop_Wk] The speed limit in kms per hour for the designated section of road.

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.

LIMITATION TO TRAFFIC ACCESS (TRAFFICABILITY) [String;Yes(No);20;0;0;Pop_Wk] The limitation of a given vehicle to gain through access along a section of road.

Acceptable Domain Entries from RoadAccess;
No Known Limitations
Seasonal
Weather Permitting

DIRECTION OF TRAVEL (TRAVELDIRECTION) [String;Yes(No);12;0;0;Pop_Wk] The direction of travel of vehicles along a section of road.

Acceptable Domain Entries from dm_TravelDirection;
Alternating
One Way
Two Way
Unknown

ROAD USER ACCESS (USERACCESS) [String;Yes(No);10;0;0;Pop_Wk] The type of user restriction placed on road access.

Acceptable Domain Entries from dm_UserAccess;
Authorised
Public
Restricted
Tollway

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

METHOD OF CAPTURE (CAPTUREMETHOD) [String;Yes(No);60;0;0;Pop_Dep] The method of capture of a feature. This field is to be used to hold translated information from stakeholders and should not be altered unless specifically instructed by Geoscience Australia.

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 2 500 000 PRODUCTS (SYMBOL2_5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 5 000 000 PRODUCTS (SYMBOL5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 10 000 000 PRODUCTS (SYMBOL10Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

See Section 3 Chapter 6.7.4 Attribute Fields Defined for Roads Feature Class for further explanation of the domain options utilised within the Data Attributes Component.

A minimum size for inclusion of linear Roundabouts are Roundabouts with a diameter of greater than 20m. Roundabouts below this diameter may be represented by the feature type 'Roundabout Point' upon direction from Geoscience Australia (see Roundabout Point) for more details.

Attribute connectivity of roads entering and exiting roundabouts will be dealt with by the road connectors and will not be reflected on the attributes of the roundabout.

Roads will not be added only from interpretation of the imagery (unless specifically requested by Geoscience Australia). However obvious road realignments may be captured when significant.

The practice of applying the 'Unknown' formation to roads should be limited to exceptional circumstances.

All principal roads will be named. Secondary roads should be named where name is known. 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.

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

Feature width values assigned for road under construction symbol representations should reflect the associated road classifications see Feature Width Meaning for more details.

Upperscale will be assigned based on the Diameter of the Roundabout. Roundabouts equal to, or greater than, 140m in diameter will be eligible for an Upperscale of 100 000.

Where a roundabout is symbolised for a particular scale (eg 100 000) the associated road connectors will have a symbol of 1 Line No Draw.

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 '1' - line no draw.

General - All Scales

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 will have nodes at all intersections.

General - All Scales

Roads cannot overlap the following features unless associated with a Road Crossing Line;
Sea, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Lake Perennial, Canal Areas, WatercourseAreas (feature class) Perennial.

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

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

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.

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

When assigning an Upperscale of 250000 or smaller scale (larger area), minor roads entering a built up 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 eligible for an Upperscale of 250000 or smaller scale (larger area). 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.

1:100 000

Naming of minor roads and vehicular tracks should give preference to features which constitute 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 built up area will be given a symbol of '242'. The only exception will be when this application results in illegibility 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 built up 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 built up 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.

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

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, Ferry Route Line, Ford Line, Ford Point, Fence Standard, Fence Vermin Proof, Gate, Distance Indicator, Gorge, Grid, Pass, Place Name, Populated Place, Road Bridge Line, Road Causeway, Road Junction, Road Overpass, Arrow, Road Tunnel Line, Road Marker National, Road Marker State, Transition Point

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.8, 5.11.2, 5.20, 6.7
Appendix C
Appendix U Chapters 2.2, 2.4

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

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

Roundabout Point

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

4

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

RoundaboutPoint

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

Acceptable Domain Entries from dm_NumberOfLanes;
More Than Two
One
Two
Unknown

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

New Roundabout Points should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for TrafficControlDevice Feature Class.

A minimum size for inclusion of linear Roundabouts are Roundabouts with a diameter of greater than 20m. Roundabouts below this diameter may be represented by the feature type 'Roundabout Point' upon direction from Geoscience Australia (see Roundabout Point) for more details.

General - All Scales

Pedestrian Crossings must be coincident with a node in the road network at the intersection of the associated roads.

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

Standard Road

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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.

StandardRoad

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the road. (see Geodatabase Rules and Section 3 chapter 6.7.1)

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

CONTROLLING AUTHORITY (AUTHORITY) [String;Yes;100;0;0;Pop_Req] Name of controlling authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status;

Acceptable Domain Entries from dm_RoadClassification;
Principal Road
Secondary Road
Minor Road

FORMATION (FORMATION) [String;Yes(No);18;0;0;Pop_Req] Type of road surface;

Acceptable Domain Entries from dm_RoadFormation;
Sealed
Unimproved
Unknown
Unsealed

FUNCTIONAL ROAD CLASSIFICATION (FUNCTION) [String;Yes(No);25;0;0;Pop_Dep] The functional hierarchy classification for roads allowing cross jurisdictional translation;

Acceptable Domain Entries from dm_RoadFunction;
National Or State Highway
Arterial Road
Sub Arterial Road
Collector Road
Local Road
Access Road
Service Road
Unknown

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

MAINTENANCE AUTHORITY (MAINTAINER) [String;Yes;50;0;0;Pop_Wk] Name of maintenance authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

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.

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

Acceptable Domain Entries from dm_NumberOfLanes;
More Than Two
One
Two
Unknown

OPERATIONAL STATUS OF ROAD (ROADSTATUS) [String;Yes(No);20;0;0;Pop_Req] The roads operational status;

Acceptable Domain Entries from dm_RoadStatus;
Closed
Notional
Operational
Proposed
Under Construction

SPEED LIMIT FOR ROAD SECTION (SPEEDLIMITKM) [SmallInteger;Yes(No);0;3;0;Pop_Wk] The speed limit in kms per hour for the designated section of road.

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.

LIMITATION TO TRAFFIC ACCESS (TRAFFICABILITY) [String;Yes(No);20;0;0;Pop_Wk] The limitation of a given vehicle to gain through access along a section of road.

Acceptable Domain Entries from RoadAccess;
No Known Limitations
Seasonal
Weather Permitting

DIRECTION OF TRAVEL (TRAVELDIRECTION) [String;Yes(No);12;0;0;Pop_Wk] The direction of travel of vehicles along a section of road.

Acceptable Domain Entries from dm_TravelDirection;
Alternating
One Way
Two Way
Unknown

ROAD USER ACCESS (USERACCESS) [String;Yes(No);10;0;0;Pop_Wk] The type of user restriction placed on road access.

Acceptable Domain Entries from dm_UserAccess;
Authorised
Public
Restricted
Tollway

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

METHOD OF CAPTURE (CAPTUREMETHOD) [String;Yes(No);60;0;0;Pop_Dep] The method of capture of a feature. This field is to be used to hold translated information from stakeholders and should not be altered unless specifically instructed by Geoscience Australia.

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 2 500 000 PRODUCTS (SYMBOL2_5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 5 000 000 PRODUCTS (SYMBOL5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 10 000 000 PRODUCTS (SYMBOL10Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

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

See Section 3 Chapter 6.7.4 Attribute Fields Defined for Roads Feature Class for further explanation of the domain options utilised within the Data Attributes Component.

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

Roads will not be added only from interpretation of the imagery (unless specifically requested by Geoscience Australia). However obvious road realignments may be captured when significant.

The practice of applying the 'Unknown' formation to roads should be limited to exceptional circumstances.

All principal roads will be named. Secondary roads should be named where name is known. 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.

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

Feature width values assigned for road under construction symbol representations should reflect the associated road classifications see Feature Width Meaning for more details.

Upperscale assignment will be based on a variety of factors, including:

• Minimum map representation size criteria
• Maintaining a representative road network selection appropriate for a particular scale, while maintaining connectivity between major population centres and locations/features of regional, state or national importance as appropriate
• Consideration should be given to maintaining higher classification/functional classification order networks as roads filtering occurs
• Consideration should be given to National and State Routes
• Guidance should be taken from selections made for previously released Geoscience Australia Topographic Scaled Products

General - All Scales

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 will have nodes at all intersections.

General - All Scales

Roads cannot overlap the following features unless associated with a Road Crossing Line;
Sea, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Lake perennial, Canal Areas, Watercourse Area perennial.

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

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

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 Water Storage, Rural Water 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 dried due to the drought conditions within Australia. When this occurs the representation of the road in the appropriate scale symbol fields (eg SYMBOL100K, SYMBOL 250K, etc) should be adjusted to show only the portions of the feature which does not exist within the extents of the high water mark of the waterbody.

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

When assigning an Upperscale of 250000 or smaller scale (larger area), minor roads entering a built up 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 eligible for an Upperscale of 250000 or smaller scale (larger area). 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.

1:100 000

Naming of minor roads and vehicular tracks should give preference to features which constitute 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 built up area will be given a symbol of '242'. The only exception will be when this application results in illegibility 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 built up 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 built up 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.

1:250 000

Minor roads and vehicular tracks will be named where named on the previous 1: 250 000 NTMS 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 constitute through routes and/or lead to cultural or natural features.

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

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, Ferry Route Line, Ford Line, Ford Point, Fence Standard, Fence Vermin Proof, Gate, Distance Indicator, Gorge, Grid, Pass, Place Name, Populated Place, Road Bridge Line, Road Causeway, Road Junction, Road Overpass, Arrow, Road Tunnel Line, Road Marker National, Road Marker State, Transition Point

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.8, 5.11.2, 5.20, 6.7
Appendix C
Appendix U Chapters 2.2, 2.4

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

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

Toll

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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.

Toll

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

This field is not applicable to this subtype and therefore is currently not to be populated;

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

New Tolls should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for TrafficControlDevice Feature Class.

General - All Scales

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

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

Traffic Control Device Gen

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

10

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

TrafficControlDeviceGen

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

This field is not applicable to this subtype and therefore is currently not to be populated;

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

New Traffic Control Device Gen should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for TrafficControlDevice Feature Class.

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

Traffic Light

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;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.

TrafficLight

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

This field is not applicable to this subtype and therefore is currently not to be populated;

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

New Traffic Lights should only be captured/maintained upon direction from Geoscience Australia and not part of standard maintenance for TrafficControlDevice Feature Class.

Where multiple Traffic Lights occur at an intersection of two roads or at the same point along a road, only one representative point should be captured in the database.

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

Vehicular Track

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

6

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

VehicularTrack

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the road. (see Geodatabase Rules and Section 3 chapter 6.7.1)

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

CONTROLLING AUTHORITY (AUTHORITY) [String;Yes;100;0;0;Pop_Req] Name of controlling authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status;

Acceptable Domain Entries from dm_RoadClassification;
Vehicular Track

FORMATION (FORMATION) [String;Yes(No);18;0;0;Pop_Req] Type of road surface;

Acceptable Domain Entries from dm_RoadFormation;
Unimproved

FUNCTIONAL ROAD CLASSIFICATION (FUNCTION) [String;Yes(No);25;0;0;Pop_Dep] The functional hierarchy classification for roads allowing cross jurisdictional translation;

Acceptable Domain Entries from dm_RoadFunction;
National Or State Highway
Arterial Road
Sub Arterial Road
Collector Road
Local Road
Access Road
Service Road
Unknown

HEIGHT LIMIT IN METRES (HEIGHTLIMITMETRES) [Double;Yes(No);0;3;1;Pop_Wk] The recommended limit of vehicle height able to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

MAINTENANCE AUTHORITY (MAINTAINER) [String;Yes;50;0;0;Pop_Wk] Name of maintenance authority.

Acceptable Domain Entries from dm_RoadAuthority;
Local Authority
Other
Other Government Authority
Private
State Authority
Undetermined Government Authority

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.

NUMBER OF LANES (NUMBEROFLANES) [String;Yes(No);15;0;0;Pop_Wk] The number of lanes which exist along a section of road.

Acceptable Domain Entries from dm_NumberOfLanes;
More Than Two
One
Two
Unknown

OPERATIONAL STATUS OF ROAD (ROADSTATUS) [String;Yes(No);20;0;0;Pop_Req] The roads operational status;

Acceptable Domain Entries from dm_RoadStatus;
Closed
Notional
Operational
Proposed
Under Construction

SPEED LIMIT FOR ROAD SECTION (SPEEDLIMITKM) [SmallInteger;Yes(No);0;3;0;Pop_Wk] The speed limit in kms per hour for the designated section of road.

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.

LIMITATION TO TRAFFIC ACCESS (TRAFFICABILITY) [String;Yes(No);20;0;0;Pop_Wk] The limitation of a given vehicle to gain through access along a section of road.

Acceptable Domain Entries from RoadAccess;
No Known Limitations
Seasonal
Weather Permitting

DIRECTION OF TRAVEL (TRAVELDIRECTION) [String;Yes(No);12;0;0;Pop_Wk] The direction of travel of vehicles along a section of road.

Acceptable Domain Entries from dm_TravelDirection;
Alternating
One Way
Two Way
Unknown

ROAD USER ACCESS (USERACCESS) [String;Yes(No);10;0;0;Pop_Wk] The type of user restriction placed on road access.

Acceptable Domain Entries from dm_UserAccess;
Authorised
Public
Restricted
Tollway

WEIGHT LIMIT IN TONNES (WEIGHTLIMITTONNES) [SmallInteger;Yes(No);0;4;0;Pop_Wk] The recommended limit of weight allowed to cross (or be supported by) a feature (eg a vehicle crossing a bridge) prior to risk of damage or possible failure of the features structure.

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. (See Section 1 Chapter 3.7 Positional Accuracy for more information);

METHOD OF CAPTURE (CAPTUREMETHOD) [String;Yes(No);60;0;0;Pop_Dep] The method of capture of a feature. This field is to be used to hold translated information from stakeholders and should not be altered unless specifically instructed by Geoscience Australia.

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 2 500 000 PRODUCTS (SYMBOL2_5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 5 000 000 PRODUCTS (SYMBOL5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

SYMBOL FOR 10 000 000 PRODUCTS (SYMBOL10Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RoadTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

General - All Scales

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

See Section 3 Chapter 6.7.4 Attribute Fields Defined for Roads Feature Class for further explanation of the domain options utilised within the Data Attributes Component.

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

Vehicular tracks are not graded and should be considered to have a formation of 'Unimproved'.

Roads will not be added only from interpretation of the imagery (unless specifically requested by Geoscience Australia). However obvious road realignments may be captured when significant.

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.

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 '1' - line no draw.

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

Feature width values assigned for road under construction symbol representations should reflect the associated road classifications see Feature Width Meaning for more details.

Upperscale assignment will be based on a variety of factors, including:

• Minimum map representation size criteria
• Maintaining a representative road network selection appropriate for a particular scale, while maintaining connectivity between major population centres and locations/features of regional, state or national importance as appropriate
• Consideration should be given to maintaining higher classification/functional classification order networks as roads filtering occurs
• Consideration should be given to National and State Routes
• Guidance should be taken from selections made for previously released Geoscience Australia Topographic Scaled Products

General - All Scales

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 will have nodes at all intersections.

General - All Scales

Roads cannot overlap the following features unless associated with a Road Crossing Line;
Sea, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Lake perennial, Canal Areas, WatercourseAreas (feature class) Perennial.

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

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 Water Storage, Rural Water 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 dried due to the drought conditions within Australia. When this occurs the representation of the road in the appropriate scale symbol fields (eg SYMBOL100K, SYMBOL 250K, etc) should be adjusted to show only the portions of the feature which does not exist within the extents of the high water mark of the waterbody.

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

When assigning an Upperscale of 250000 or smaller scale (larger area), minor roads entering a built up 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 eligible for an Upperscale of 250000 or smaller scale (larger area). 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.

1:100 000

Naming of minor roads and vehicular tracks should give preference to features which constitute 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 built up area will be given a symbol of '242'. The only exception will be when this application results in illegibility 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 built up 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 built up 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.

1:250 000

Minor roads and vehicular tracks will be named where named on the previous 1: 250 000 NTMS 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 constitute through routes and/or lead to cultural or natural features.

General - All Scales

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, Ferry Route Line, Ford Line, Ford Point, Fence Standard, Fence Vermin Proof, Gate, Distance Indicator, Gorge, Grid, Pass, Place Name, Populated Place, Road Bridge Line, Road Causeway, Road Junction, Road Overpass, Arrow, Road Tunnel Line, Road Marker National, Road Marker State, Transition Point

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.8, 5.11.2, 5.20, 6.7
Appendix C
Appendix U Chapters 2.2, 2.4

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