NTDB & NTMS Specifications (250K & 100K) |
Updated: 1/12/2007
Ferry Route LineFerryRouteLines RoadTransport Polyline A route across a river, lake, reservoir or sea used by a vessel for the regular transport of vehicles or passengers from one terminal point to another. Minimum Size Criterion:
Data AttributesFEATURE 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. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation; Acceptable Domain Entries from dm_UpperScale; UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity; Acceptable Domain Entries from dm_USCertainty; SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 20 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 All ferry routes on existing base material should be retained unless information is available indicating the ferry service has been discontinued. Reference Material will be provided for new ferry routes. 1:100 000 All ferry routes on existing base material should be retained unless information is available indicating the ferry service has been discontinued. Reference Material will be provided for new ferry routes. 1:250 000 All feature occurances existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. Revision source material will be provided for new ferry routes to be shown. General - All Scales Where one Ferry Route Line crosses another Ferry Route Line a node will be shown at their intersection point. i.e. The arcs will be split. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Ferry Route Lines will have as their starting point the appropriate terminating point of Road or Railway features. That is, the end node of the Road/Railway will be a shared node used for the starting point of the Ferry Route. This is required to ensure network connectivity. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - 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. Map RulesGeneral - All Scales Two or more Ferry Route Lines running closer than 1mm to scale, parallel to each other and carrying different attributes will both be labelled where they can be shown legibly. Related FeaturesRailway , Road Related ChaptersSection 3 Chapter 5.3 Related ProductsGEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Foot BridgeFootBridges RoadTransport Polyline A structure erected over a depression or obstacle to carry foot traffic. Minimum Size Criterion:
Data AttributesFEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented. Foot Bridge FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 268 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] Currently not used by symbology; 0 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase RulesGeneral - All Scales The name of a foot bridge may be held in the TextNote field. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Foot Bridges will be coincident with the equivalent section of the Foot Track. There must be a vertex in the Foot Track feature at the exact location of the start and end points of the Foot Bridge. Inter-Feature Relationship Rules - External to Associated DatasetMap RulesRelated FeaturesFoot Track Related ChaptersRelated ProductsNTMS 100K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Foot TrackFootTracks RoadTransport Polyline A path either beaten by the passage of feet (usually unformed and not maintained) or constructed by an authority to enable access to an area or provide a connection from one location to another. The path is primarily designed to carry pedestrian traffic only but may also allow access to other forms of non-vehicular transport. Minimum Size Criterion:
Data AttributesFEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented. Foot Track NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the foot track. This item should be populated where name is known. TRACK NAME (TRACKNAME) [String;Yes;60;0;0;Pop_Wk] The name of the foot track in its entirety. SECTION NAME (SECTIONNAME) [String;Yes;60;0;0;Pop_Wk] The name of individual section along a foot track SIGNIFICANCE (SIGNIFICANCE) [String;Yes;10;0;0;Pop_Req] The national significance of the entity; Acceptable Domain Entries from dm_Significance; FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation; Acceptable Domain Entries from dm_UpperScale; UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity; Acceptable Domain Entries from dm_USCertainty; SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 22 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 Details of new foot tracks to be included will be supplied. Only tracks of national, state and regional significance will be included. 1:100 000 Details of new foot tracks to be included will be supplied. Only tracks of national, state and regional significance will be included. 1:250 000 Details of new foot tracks to be included will be supplied. Only tracks of national significance will be included. General - All Scales Foot tracks are to have an accompanying TextNote 'foot track' unless 'foot track' or an equivalent term is included in the name. Inter-Feature Relationship Rules - Internal to Associated Dataset1:250 000 Where the foot track is associated with or uses a section of road it should be made coincident with that portion of the road. A vertex on the road should exist at the exact location of the entry and exit points of the foot track. General - All Scales A descriptive note may be added to the Textnote field, for example 'Hume and Hovell Walking Trail follows track' where a foot track is coincident with a road. Inter-Feature Relationship Rules - External to Associated DatasetMap RulesGeneral - 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. Related FeaturesFoot Bridge, Road Related ChaptersSection 3 Chapter 5.3 Related ProductsGEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Ford LineRoadCrossingLines RoadTransport Polyline A shallow or flat portion of the bed of a watercourse or lake where a crossing may be effected. Minimum Size Criterion:
Data AttributesFEATURE 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. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 21 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] Currently not used by symbology; 0 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 Fords Lines shorter than 300 metres and ford point features, will not be symbolised (e.g. symbol = 0). 1:100 000 Fords Lines shorter than 300 metres and ford point features, will not be symbolised (e.g. symbol = 0). 1:250 000 Fords Lines shorter than 750 metres and ford point features, will not be symbolised (e.g. symbol = 0). General - All Scales Existing crossing lines (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Ford Line must be a clone of the equivalent section of the associated Road. There must be a vertex in the Road feature at the exact location of the start and end points of the Ford Line. The road must continue outwards from both endpoints of the Ford Line. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Named fords will be cloned as Place Names in the Framework feature dataset. Map RulesGeneral - All Scales All fords, including those not symbolised, are to be labelled 'ford'. Related FeaturesRoad, Road Bridge Line, Road Bridge Point, Road Causeway , Watercourse, Watercourse Area, Ford Point Related ChaptersSection 3 chapters 5.10 and 5.11.2 Related ProductsGEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Ford PointRoadCrossingPoints RoadTransport Point A shallow or flat portion of the bed of a watercourse or lake where a crossing may be effected. Minimum Size Criterion:
Data AttributesFEATURE 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. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation; Acceptable Domain Entries from dm_UpperScale; UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity; Acceptable Domain Entries from dm_USCertainty; SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 0 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] Currently not used by symbology; 0 ORIENTATION (ORIENTATION) [SmallInteger;Yes;0;3;0;Pop_Dep] Orientation in whole degrees from East going anti-clockwise; Currently not used for symbology; 0 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 Fords Lines shorter than 300 metres and ford point features, will not be symbolised (e.g. symbol = 0). 1:100 000 Fords Lines shorter than 300 metres and ford point features, will not be symbolised (e.g. symbol = 0). 1:250 000 Fords Lines shorter than 750 metres and ford point features, will not be symbolised (e.g. symbol = 0). General - All Scales Existing crossing points (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Point Fords must be coincident with a vertex in the road network. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Named fords will be cloned as Place Names in the Framework feature dataset. Map RulesGeneral - All Scales All fords, including those not symbolised, are to be labelled 'ford'. Related FeaturesRoad, Road Bridge Line, Road Bridge Point, Road Causeway , Watercourse, Watercourse Area, Ford Line Related ChaptersSection 3 chapters 5.3, 5.9, 5.10 and 5.11.2 Related ProductsGEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
GateBarrierPoints RoadTransport Point An opening in a fence or wall for the passage of vehicles, people or animals and which may contain a device to limit passage. Minimum Size Criterion:
Data AttributesFEATURE 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 1 DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification. Gate FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation; Acceptable Domain Entries from dm_UpperScale; UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity; Acceptable Domain Entries from dm_USCertainty; SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 26 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] Currently not used by symbology; 0 ORIENTATION (ORIENTATION) [SmallInteger;Yes;0;3;0;Pop_Dep] Orientation in whole degrees from East going anti-clockwise; 0 - 360 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 This feature will only be captured when requested by Geoscience Australia. The feature must be derived from either field inspection information or Authorised Reference Material, it can not be captured from imagery alone. Existing gates will be retained unless directed otherwise. 1:100 000 All Gates existing in base material will be retained. New features will only be captured in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' except for gates on Vermin Proof fences which will be shown in all areas. 1:250 000 This feature will only be captured/retained in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide', regardless of whether it previously existed in the base material/digital data, except for gates on Vermin Proof fences which will be shown in all areas. General - All Scales Only gates associated with a road network will be captured. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Only gates associated with a road network will be captured.Gates must be coincident with a vertex in the road network. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Gates must fall exactly on the Fence. A vertex will be added to the fence to ensure the fence, road and gate are coincident with each other. Map RulesGeneral - All Scales The underlying fence symbol will be masked out for the gate symbol. Related FeaturesFence, Road , Grid Related ChaptersSection 3 chapters 5.3, 5.9, 5.11.2 Related ProductsGEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
GridBarrierPoints RoadTransport Point A grid at the opening in a fence to prevent livestock crossing but allowing for the free passage of vehicles. Minimum Size Criterion:
Data AttributesFEATURE 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 2 DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification. Grid FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation; Acceptable Domain Entries from dm_UpperScale; UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity; Acceptable Domain Entries from dm_USCertainty; SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 25 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] Currently not used by symbology; 0 ORIENTATION (ORIENTATION) [SmallInteger;Yes;0;3;0;Pop_Dep] Orientation in whole degrees from East going anti-clockwise; 0 - 360 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 This feature will only be captured when requested by Geoscience Australia. The feature must be derived from either field inspection information or Authorised Reference Material, it can not be captured from imagery alone. Existing grids will be retained unless directed otherwise. 1:100 000 All Grids existing in base material will be retained. New features will only be captured in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' except for gates on Vermin Proof fences which will be shown in all areas. 1:250 000 This feature will only be captured/retained in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide', regardless of whether it previously existed in the base material/digital data, except for grids on Vermin Proof fences which will be shown in all areas. General - All Scales Grids will not be shown on vehicle tracks. The only exception is when the Grids is associated with a 'Vermin Proof Fence'. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Grids must be coincident with a vertex in the road network. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Grids must fall exactly on the fence. A vertex will be added to the fence to ensure the fence, road and Grid are coincident with each other. Map RulesGeneral - All Scales The underlying fence symbol will be masked out for the stock grid symbol. Related FeaturesFence, Gate , Road Related ChaptersSection 3 chapters 5.3, 5.9, 5.11.2 Related ProductsGEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
RoadRoads RoadTransport Polyline A route for the movement of vehicles, people or animals. Minimum Size Criterion:
Data AttributesFEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented. Road NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the road. (see Geodatabase Rules and Section 3 chapter 6.7.1) CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status; Acceptable Domain Entries from dm_RoadClassification at 25K and 100K as well as acceptable entries for the 250K field; FORMATION (FORMATION) [String;Yes(No);18;0;0;Pop_Req] Type of road surface; Acceptable Domain Entries from dm_RoadFormation at 25K and 100K as well as acceptable entries for the 250K field; NATIONAL ROUTE NUMBER (NRN) [String;Yes;12;0;0;Pop_Wk] The national route number/s assigned to the road ( if multiple numbers, delimited by a minus sign). Alpha characters in this field are to be in upper case. STATE ROUTE NUMBER (SRN) [String;Yes;12;0;0;Pop_Req] The state route number/s assigned to the road ( if multiple numbers, delimited by a minus sign). Alpha characters in this field are to be in upper case. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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; RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usagage as defined by licence agreements, land owners, agreements with other agencies supplying the data. Acceptable Domain Entries from dm_Restrictions; REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation; Acceptable Domain Entries from dm_UpperScale; UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity; Acceptable Domain Entries from dm_USCertainty; SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 250 - Dual carriageway FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] Feature width is only used for roads under construction (symbol 252). All other roads will have a feature width of '0'. The width of symbol 252 reflects the road classification, the following values will be used: TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 Size and any other selection criteria apply to all feature occurances. 1:100 000 Size and any other selection criteria apply to all feature occurrences. An exception will be minor roads in built up areas which will be treated as per the rules stated in Inter-Feature Relationship Rules - External. 1:250 000 Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. An exception will be minor roads in built up areas which will be treated as per the rules stated in Inter-Feature Relationship Rules - External. General - All Scales Road classifications will be as shown on the road reference material supplied. Inter-Feature Relationship Rules - Internal to Associated Dataset1:250 000 Where the foot track is associated with or uses a section of road it should be made coincident with that portion of the road. A vertex on the road should exist at the exact location of the entry and exit points of the foot track. General - All Scales Roads will have nodes at all intersections. Inter-Feature Relationship Rules - External to Associated Dataset1:25 000 The General Interrelationship - External rule stating 'Roads cannot overlap Town Rural Storage and Lake Perennial' does not apply when it is clear on imagery that a land holder has established a road through a portion of the feature which has dryed due to the drought conditions within Australia. When this occurs the road should be symbolised to zero and a representation of the feature should be created in the 'CartoGeneralisationLine' feature class. This representation will only show the portions of the feature which does not exist within the extents of the high water mark of the waterbody. The feature in the 'CartoGeneralisationLine' will have the symbol of the classification and formation of the road (e.g. vechicular track). 1:100 000 All roads existing in the base material/digital data entering or within Built Up Area will be retained. New minor roads entering a Built Up Area will be continued to the first intersection with a major through route (preference should be given to intersections with dual carriageways, principal or secondary roads). In addition, sufficient new minor roads will be captured to reflect the Built-up Area's road pattern. Select the major through routes (from Reference material) to reflect the road pattern within the area whilst avoiding clutter. This rule will also extend to other features (including defined holes, areas of universe polygon) in the built-up area layer where they are surrounded by a built- up area. See Section 3 Chapter 6.7.3. 1:250 000 Minor roads entering a builtup area will be continued to the first intersection with a dual carriageway, principal or secondary road. Minor roads totally contained in built-up areas will not be captured. This rule extends to other features (including defined holes, areas of universe polygon) in the built-up area layer where they are surrounded by a built-up area. See Section 3 Chapter 6.7.3. General - All Scales Roads cannot overlap the following features unless associated with a Road Crossing Line; Map Rules1:25 000 Naming of minor roads and vehicular tracks should give preference to features which consititute through routes and/or lead to cultural or natural features. Density of detail should determine the number of names shown. If a previous edition 1:100 000 map has been supplied this should be used as a guide for which roads are to be named in the new product. 1:100 000 Naming of minor roads and vehicular tracks should give preference to features which consititute through routes and/or lead to cultural or natural features. Density of detail should determine the number of names shown. If a previous edition 1:100 000 map has been supplied this should be used as a guide for which roads are to be named in the new product. 1:250 000 Naming of minor roads and vehicular tracks should be consistent with name content in the digital data, subject to generalisation rules and clutter considerations. General - All Scales All dual carriageways, principal & secondary roads will be named where name is known. Related FeaturesBuilt Up Area, Cemetery Area, RecreationAreas (Feature Class), Ferry Route Line, Ford Line, Ford Point, Standard Fence, Fence, Vermin Proof Fence, Gate, Distance Indicator, Gorge, Pass, Road Junction, Place Name, Populated Place, Prohibited Area Boundary Line, Road Bridge Line, Road Bridge Point, Road Causeway, Road Overpass, Arrow, Road Tunnel Line, Road Tunnel Point, Road Marker National, Road Marker State, Reserve Boundary Line, Grid , Transition point Related ChaptersSection 2 chapter 2.2.3 Related ProductsGEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Road Bridge LineRoadCrossingLines RoadTransport Polyline A structure erected over a depression or obstacle to carry road traffic. Minimum Size Criterion:
Data AttributesFEATURE 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. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 260 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] The width of the symbol determined by the road classification (in millimetres); TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 Size and any other selection criteria apply to all feature occurrences. 1:100 000 Size and any other selection criteria apply to all feature occurrences. 1:250 000 Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist or unless the road crossing the bridge has been removed within a Built-up area (see Road). General - All Scales Existing crossing lines (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Road Bridge Lines may be shown off the road network if they are on a dismantled road. Inter-Feature Relationship Rules - External to Associated Dataset1:250 000 A bridge may be required to be extended to ensure that the map symbol endpoints (wings) effectively fall outside the width of its associated waterbody. General - All Scales Bridges which carry both road and rail traffic will be held as coincident road bridge and railway bridge features in their respective layers. Map Rules1:25 000 A bridge may be required to be extended to ensure that the map symbol endpoints (wings) effectively fall outside the width of its associated waterbody. 1:100 000 A bridge may be required to be extended to ensure that the map symbol endpoints (wings) effectively fall outside the width of its associated waterbody. General - All Scales Bridges of distinctive construction may be labelled (e.g 'drawbridge','swing bridge'). Related FeaturesFord Line, Ford Point, Railway Bridge Line, Railway Bridge Point, Road , Road Causeway, Road Overpass Related ChaptersSection 3 chapters 5.8, 5.11.2 and 6.7 Related ProductsGEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Road Bridge PointRoadCrossingPoints RoadTransport Point A structure erected over a depression or obstacle to carry road traffic. Minimum Size Criterion:
Data AttributesFEATURE 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. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation; Acceptable Domain Entries from dm_UpperScale; UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity; Acceptable Domain Entries from dm_USCertainty; SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 260 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] The width of the symbol determined by the road classification (in millimetres); ORIENTATION (ORIENTATION) [SmallInteger;Yes;0;3;0;Pop_Dep] Orientation in whole degrees from East going anti-clockwise; 0 - 360 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 Size and any other selection criteria apply to all feature occurrences. 1:100 000 Size and any other selection criteria apply to all feature occurrences. 1:250 000 Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist or unless the road crossing the bridge has been removed within a Built-up area (see Road). General - All Scales Existing crossing points (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Road bridges may be shown off the road network if they are on a dismantled road. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Bridges which carry both road and rail traffic will be held as coincident road bridge and railway bridge features in their respective layers. Map Rules1:25 000 Point Bridges on minor roads in built up areas will be symbolised to '0' with a feature width of '0.2'. 1:100 000 Point Bridges on minor roads in built up areas will be symbolised to '0' with a feature width of '0.2'. General - All Scales Bridges of distinctive construction may be labelled (e.g 'drawbridge','swing bridge'). Related FeaturesFord Line, Ford Point, Railway Bridge Line, Railway Bridge Point, Road , Road Causeway, Road Overpass Related ChaptersSection 3 chapters 5.3, 5.8, 5.9, 5.11.2 and 6.7 Related ProductsGEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Road CausewayRoadCrossingLines RoadTransport Polyline An embankment of earth or masonry erected across open water or an area subject to inundation and carrying a road. Minimum Size Criterion:
Data AttributesFEATURE 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. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 245 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] The width of the symbol determined by the road classification (in millimetres); TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 Size and any other selection criteria apply to all feature occurrences. 1:100 000 Size and any other selection criteria apply to all feature occurrences. 1:250 000 Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. General - All Scales Existing crossing lines (e.g. bridges, causeways, fords) on the base material/digital data or the latest previous edition map should be retained unless there is evidence that they no longer exist. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Road Causeway must be a clone of the equivalent section of the associated Road. There must be a vertex in the Road feature at the exact location of the start and end points of the Road Causeway.The road must continue outwards from both endpoints of the causeway. Inter-Feature Relationship Rules - External to Associated DatasetMap RulesGeneral - All Scales Road causeways will be labelled 'causeway'. Where road and railway causeways are coincident only one label 'causeway' will appear on the map face. Related FeaturesFord Line, Ford Point, Railway Causeway, Road , Road Bridge Line, Road Bridge Point, Road Overpass Related ChaptersSection 3 chapters 5.8 and 5.11.2 Related ProductsGEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Road OverpassRoadCrossingLines RoadTransport Polyline A separation of surface levels constructed to prevent direct intersection with other road or rail networks. Minimum Size Criterion:
Data AttributesFEATURE 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. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 267 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] The width of the symbol determined by the road classification (in millimetres); TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase RulesGeneral - All Scales Size and any other selection criteria apply to all feature occurrences. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Road Overpass must be a clone of the equivalent section of the associated Road. There must be a vertex in the Road feature at the exact location of the start and end points of the Road Overpass.The road must continue outwards from both endpoints of the Road Overpass. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - 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. Map RulesGeneral - All Scales Road overpasses may be named, where name is known. Related FeaturesFord Line, Ford Point, Railway Bridge Line, Railway Bridge Point, Road Bridge Line, Road Bridge Point, Railway Causeway, Road Causeway, Railway Overpass Related ChaptersSection 3 Chapters 5.8, 5.11.2, 6.7 Related ProductsGEODATA LITE TOPO100K, NTMS 100K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
RoadTransport AnnoRoadTransportAnno RoadTransport Annotation Type associated with the Road Transport Feature Dataset Minimum Size Criterion:
Data AttributesANNOTATION 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; 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; REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase RulesGeneral - All Scales No feature type field exists for this annotation feature class. The feature type has only been included throughout the specifcation documentation for ease of reference. Inter-Feature Relationship Rules - Internal to Associated DatasetInter-Feature Relationship Rules - External to Associated DatasetMap RulesRelated FeaturesRelated ChaptersSection 2 Chapter 5, 9, 10 Related ProductsNTMS 100K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Road Tunnel LineRoadTunnelLines RoadTransport Polyline An artificial underground or underwater passage carrying a road. Minimum Size Criterion:
Data AttributesFEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented. Road Tunnel Line NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Road Tunnel.This item should be populated where name is known. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 205 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] Currently not used by symbology; 0 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 Size and any other selection criteria apply to all feature occurrences. 1:100 000 Size and any other selection criteria apply to all feature occurrences. 1:250 000 Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. General - All Scales Road tunnels may be named, where name is known. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - 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. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Tunnels which carry both road and railway traffic will be held as a coincident road tunnel and railway tunnel feature in their respective layers. Map RulesGeneral - All Scales Road tunnels may be named, where name is known. Related FeaturesRailway Tunnel Point, Road , Transition point Related ChaptersSection 3 chapters 5.11.2 and 6.7 Related ProductsGEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Updated: 1/12/2007
Road Tunnel PointRoadTunnelPoints RoadTransport Point An artificial underground or underwater passage carrying a road. Minimum Size Criterion:
Data AttributesFEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented. Road Tunnel Point NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Road Tunnel.This item should be populated where name is known. FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature. ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification. ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature. 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. DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA. UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product; FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA. UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation; Acceptable Domain Entries from dm_UpperScale; UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity; Acceptable Domain Entries from dm_USCertainty; SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable; 0 FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep] Currently not used by symbology; 0 ORIENTATION (ORIENTATION) [SmallInteger;Yes;0;3;0;Pop_Dep] Orientation in whole degrees from East going anti-clockwise; Currently not used by symbology; 0 TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature. EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated. Geodatabase Rules1:25 000 Size and any other selection criteria apply to all feature occurrences. 1:100 000 Size and any other selection criteria apply to all feature occurrences. 1:250 000 Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. General - All Scales Road tunnels may be named, where name is known. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales RoadTunnelPoints must fall exactly over a vertex on the Road feature. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Tunnels which carry both road and railway traffic will be held as a coincident road tunnel and railway tunnel feature in their respective layers. Map RulesGeneral - All Scales Road tunnels may be named, where name is known. Related FeaturesRailway Tunnel Line, Road , Transition point Related ChaptersSection 3 chapters 5.3, 5.11.2 and 6.7 Related ProductsGEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed. |
Unless otherwise noted, all Geoscience Australia material on this website is licensed under the Creative Commons Attribution 3.0 Australia Licence.
|