NTDB & NTMS Specifications (250K & 100K) |
Updated: 1/12/2007
BayLocations Framework Point A named wide, open and curving indentation into the land formed by the sea or inland waterbody. 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. Bay 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. Bay NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Bay. This item must 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 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 RulesGeneral - All Scales Inlcudes features such as bays, inlets and coves. This feature type will be used for an indentation of the sea into the land and for the equivalent features in inland waterbodies. Inter-Feature Relationship Rules - Internal to Associated DatasetInter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Where a locality name refers to a wide area the name may appear on a number of overlapping Map Indexes eg 'Port Phillip Bay'. A locality of the same code and name should not be repeated within the same Map Index unless it relates to a number of entities sharing the same name. Map RulesRelated FeaturesPlace Name, Sea, Waterbodies (Feature Dataset), Map Indexes, Locations (Feature Class) Related ChaptersSection 3 chapters 5.3, 5.11.1, 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
BeachLocations Framework Point A named strip of land or terrace bordering the sea, usually lying between high and low tides. 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. Beach 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. Beach NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Beach. This item must 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 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 RulesGeneral - All Scales Only named beaches on the base material/digital data and authorised revision source material are to be included. Inter-Feature Relationship Rules - Internal to Associated DatasetInter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Where a locality name refers to a wide area the name may appear on a number of overlapping Map Indexes eg 'Ten Mile Beach'. A locality of the same code and name should not be repeated within the same Map Index unless it relates to a number of entities sharing the same name. Map RulesGeneral - All Scales The names of all beaches on the previous edition map are to be included except where they are adjacent to a populated place with the same root-name. ie. 'Bondi Beach' would not appear if there is an adjacent populated place named 'Bondi' on the map. Related FeaturesBuilt Up Area,Place Name, Populated Place, Shoreline, WaterbodyBoundaries (feature class), Mainland, Island, Sand, Sand Dunes. Related ChaptersSection 3 chapters 5.3, 5.11.1, 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
CapeLocations Framework Point A named prominent headland projecting into the sea or inland waterbody. 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. Cape 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. Cape NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Cape. This item must 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 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 RulesGeneral - All Scales Includes features such as capes, headlands, heads and points. This code will be used for a section of land protruding into the sea and for the equivalent features in inland waterbodies. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Capes must not overlap; Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Where a locality name refers to a wide area the name may appear on a number of overlapping Map Indexes eg 'Cape York Peninsula'. A locality of the same code and name should not be repeated within the same Map Index unless it relates to a number of entities sharing the same name. Map RulesRelated FeaturesMainland, Island, Waterbodies (feature dataset). Related ChaptersSection 3 chapters 5.3, 5.11.1, 5.11.2 and 6.6 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
Framework AnnoFrameworkAnno Framework Annotation Type associated with the Framework 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 FrameworkAnno; 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_FrameworkFCs; 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
GorgeLocations Framework Point A named deep and narrow, steep-sided, usually rocky river valley. 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. Gorge 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. Gorge NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Gorge. This item must 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 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 RulesGeneral - All Scales The locality point will be placed approximately half way along the length of the gorge. The locality point will be coincident with a vertice on the main watercourse in the gorge, where there is a watercourse. Where there is no watercourse the locality point will be placed central to the gorge. Inter-Feature Relationship Rules - Internal to Associated DatasetInter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Where a locality name refers to a wide area the name may appear on a number of overlapping Map Indexes eg 'Ironbark Gorge'. A locality of the same code and name should not be repeated within the same Map Index unless it relates to a number of entities sharing the same name. Map RulesRelated FeaturesContours, Hypsometric Areas, Horizontal control point, Spot elevation, Watercourse, Watercourse Area Related ChaptersSection 3 chapters 5.3, 5.11.1, 5.11.2 and 6.6 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
IslandIslands Framework Polygon An area of land fully surrounded by the sea. 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. Island NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the island. This item should be populated where name is known. STATE/TERRITORY (STATE) [String;Yes(No);30;0;0;Pop_Req] Australian/Foreign State or Territory identifier code; At 25K and 100K the acceptable Domain Entries from dm_IslandState are; 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; 0 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 This feature refers to offshore islands only. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Islands are bounded by Junction, Shoreline and Limit of Data Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Islands may also be bounded by Sea wall features. Map RulesGeneral - All Scales The island name will appear on the map, where known. Related FeaturesJunction, Sea Wall, Limit of Data , Shoreline, WaterbodyBoundaries (Feature Class), Large Area Feature Related ChaptersSection 3 chapters 5.16, 5.17, 5.18 and 6.9 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
JunctionFrameworkBoundaries Framework Polyline An artificial line used to separate adjacent hydrographic areas which have differing attributes and across which flow can occur. 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. Junction 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. Junction 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; 0 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 RulesInter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales FrameworkBoundaries (feature class) bound all polygons in the Framework Dataset except Large Area Features. For more information on the use of Junction See Section 3 Chapter 5.17. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Junctions must be bordered by waterbodies in the Waterbodies Dataset or by the sea on one side in the Framework Dataset. Map RulesRelated FeaturesCanal Area, Canal Line, Connector, Connector Discontinuity, Connector Standard, Depression Contour, Interpolated Contour, Standard Contour, Island, Lake, Land subject to inundation, Large Area Feature, Mainland, Flood Irrigation Storage, Town Rural Storage, Sea, Saline coastal flat, Swamp and Watercourse, Watercourse Area Related ChaptersSection 3 chapters 5.11.1, 5.11.3, 5.17, 6.2 and 6.9 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
Large Area FeatureLargeAreaFeatures Framework Polygon A representation that is indicative of the extent of nationally recognized significant regions. 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. Large Area Feature NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the significant region. This item must 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 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. 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; 0 - non printing 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 Revision of Large Area Features will only be conducted when specifically directed by GEOSCIENCE AUSTRALIA. The only exception to this rule is when the shoreline is spatially adjusted, in which case Large Areas Features will be also be adjusted to maintain consistency. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Large Area Features cannot overlap; Inter-Feature Relationship Rules - External to Associated DatasetMap RulesGeneral - All Scales When a Large Area Feature occupies a spatial extent greater than or equal to 5% of the applicable map index (including the bleed edges), it will be labeled with its name. Annotation representing a Large Area Features will be placed within its polygon boundary. Related FeaturesFrameworkBoundaries, Mainland, Island, Sea Related ChaptersSection 3 chapter 6.11, 5.17, 5.18 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
Limit Of DataFrameworkBoundaries Framework Polyline The line bounding the limits of known source material or the edge of the defined NTDB. 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. Limit Of Data 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. LimitOfData 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; 0 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 RulesInter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales The limit of Data feature will bound or complete all polygon features whose extent can not be fully determined by source material or where the associated polygon feature is adjacent to the edge of the database.For more information on the use of Limit Of Data Line See Section 3 Chapter 5.17. Inter-Feature Relationship Rules - External to Associated DatasetMap RulesRelated FeaturesIsland, Mainland, Sea, SeriesIndex (feature dataset), Limit Of Data (framework) Related ChaptersSection 1 chapters 3.4 and 3.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
MainlandMainlands Framework Polygon The area of continental Australia including Tasmania. 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. Mainland STATE/TERRITORY (STATE) [String;Yes(No);30;0;0;Pop_Req] Australian/Foreign State or Territory identifier code; At 25K and 100K the acceptable Domain Entries from dm_MainlandState are; 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; 0 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:250 000 The following is a listing of the acronyms used in the State field and their associated meanings: Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales The Mainland feature will be bounded by a combination of Shoreline, State border and Junction features. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Mainland cannot overlap MarineAreas except Foreshore flats in estuarine areas (see Foreshore flat). Map RulesRelated FeaturesForeshore Flat, Junction, Large Area Feature, Sea wall, State border, Shoreline, WaterbodyBoundaries (Feature Class) , Limit of Data Related ChaptersSection 1 chapter 3.1 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
MountainLocations Framework Point A named markedly elevated landform bounded by steep slopes and rising to prominent ridges and individual peaks. 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. Mountain 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. Mountain NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Mountain. This item must 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 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 - non printing 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 RulesGeneral - All Scales Includes features such as mountains, peaks and hills: The locality point will be positioned exactly as shown on the base material/digital data. If a positioning point is not shown on the map then other compilations or large scale maps may be used to position the locality feature at its true planimetric position. Inter-Feature Relationship Rules - Internal to Associated DatasetInter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Where a locality name refers to a wide area the name may appear on a number of overlapping Map Indexes eg 'The Three Brothers'. A locality of the same code and name should not be repeated within the same Map Index unless it relates to a number of entities sharing the same name. Map RulesGeneral - All Scales Mountains, peaks & hills will be named. See Section 2 chapter 5.10 for naming conventions. Related FeaturesHorizontal Control Point, Spot Elevation, Contours (feature class), Hypsometric Areas. Related ChaptersSection 3 chapters 5.3, 5.11.1, 5.11.2 and 6.6 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
PassLocations Framework Point A named low and passable gap through a mountain range. 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. Pass 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. Pass NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the pass. This item must 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 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 RulesGeneral - All Scales Named passes on the road network will be included. Any other named passes included on the latest previous edition map or base material/digital data will be included. The locality point will be at the highest point on the pass. Where a pass is traversed by a road feature, the point will be coincident with a vertice on the road. If necessary, a vertice will be created on the road coincident with the highest point on the road. Inter-Feature Relationship Rules - Internal to Associated DatasetInter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Where a locality name refers to a wide area the name may appear on a number of overlapping Map Indexes eg 'Hamilton Gap'. A locality of the same code and name should not be repeated within the same Map Index unless it relates to a number of entities sharing the same name. Map RulesRelated FeaturesHorizontal control point, Road, Spot elevation, Contour (feature class), Hypsometric Areas. Related ChaptersSection 3 chapters 5.3, 5.11.1, 5.11.2 and 6.6 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
Place NameLocations Framework Point A named place or area. 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. Place Name 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. PlaceName NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name given to the place. This item must 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 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 - non printing 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:250 000 Where a Place Name point has previously been captured to represent a Large Area Feature (in the Framework Feature Dataset), it should not be retained within the NTDB. General - All Scales This category will be used to show localities that do not fall in any other category. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales A Place Name (feature type) should not duplicate the representation of features already defined in the Large Area Features feature class. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Where a locality name refers to a wide area the name may appear on a number of overlapping Map Indexes eg 'GREAT DIVIDING RANGE'. A Location of the same feature type and name should not be repeated within the same Map Index unless it relates to a number of entities sharing the same name. Map RulesGeneral - All Scales Where symbol 420 is used, the symbol will mask all other detail. Related FeaturesBuilding Area, Building Point, Built Up Area, Homestead, Kilometric distance marker, Large Area Feature, Populated Place, Railway Station, Sea. Related ChaptersSection 1 chapters 3.8.1 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 JunctionLocations Framework Point A named intersection of two or more roads. 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 Junction 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. RoadJunction NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Road Junction. This item must 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 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 RulesGeneral - All Scales Only named road junctions are included. Inter-Feature Relationship Rules - Internal to Associated DatasetInter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales The position of the location will be coincident with the node of the road intersection. Map RulesRelated FeaturesKilometric distance marker, Road. Related ChaptersSection 3 chapters 5.3, 5.11.1, 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
SeaSeas Framework Polygon The water area surrounding the Australian continent and its offshore islands. 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. Sea OCEAN NAME (OCEANNAME) [String;Yes;20;0;0;Pop_Req] Ocean Name of represented area. (See Appendix E.) Acceptable Domain Entries from dm_OceanNames at 25K and 100K as well as acceptable entries for the 250K field; SEA NAME (SEANAME) [String;Yes;12;0;0;Pop_Wk] Sea Name of represented area. (See Appendix E.) Acceptable Domain Entries from dm_SeaNames at 25K and 100K as well as acceptable entries for the 250K field; OTHER WATER NAME (OTHERWATERNAME) [String;Yes;22;0;0;Pop_Wk] Other Waters Name of represented area. (See Appendix E) Acceptable Domain Entries from dm_OtherWaterNames at 25K and 100K as well as acceptable entries for the 250K field; 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; 10 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 boundaries and names of Seas will be as defined by Appendix E - 'Limits of Oceans and Seas'. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales The boundary between two seas/oceans/other waters will be shown by a junction feature. Inter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Sea may also be partially bounded by Sea wall features. Map Rules1:100 000 Where space permits, areas of sea will include the note: 1:250 000 Where space permits, areas of sea will include the note: General - All Scales The names of seas and oceans and other waters will be shown. Related FeaturesAnnotation, Junction, Large Area Feature, Limit of Data, Sea wall, Shoreline, WaterbodyBoundaries (Feature Class) Related ChaptersSection 1 chapter 3.1 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
ShorelineFrameworkBoundaries Framework Polyline A line depicting the boundary of a mainland, island or sea. 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. Shoreline 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. Shoreline 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; 94 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 When bounding sea and estuarine areas, the line is indicative of the position of mean high water. The exception is in Mangroves, where the line is indicative of the position of the seaward side of the mangroves. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales FrameworkBoundaries (feature class) bound all polygons in the Framework Dataset except Large Area Features. For more information on the use of Shoreline See Section 3 Chapter 5.17. Inter-Feature Relationship Rules - External to Associated Dataset1:250 000 WaterbodyBoundaries bounding saline coastal flats will be coincident with the Shoreline in the framework feature dataset where the saline costal flat abuts the sea. Map RulesRelated FeaturesBuilt Up Area, Cemetery Area, RecreationAreas (Feature Class), Canal Area, Canal Line, Cliff, Connector Discontinuity, Connector Standard, Depression Contour, Interpolated Contour, Standard Contour, Island, Lake, Land subject to inundation, Large Area Feature, Mainland, Marine swamp, Foreshore Flat, Marine Hazard Areas (Feature Class), Prohibited Area Boundary Line, Rapid Area, Rapid Line, Reserve Boundary Line, Flood Irrigation Storage, Town Rural Storage, Saline coastal flat, Salt evaporator, Sea, Aquaculture Area, Settling Pond, Swamp, Orchard, Plantation, Rainforest, Forest Or Shrub, Mangrove and Watercourse, Watercourse Area, Junction 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
State BorderFrameworkBoundaries Framework Polyline The boundary defining the division of the Commonwealth of Australia into State/Territory administrations. 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. State Border 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. StateBorder 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; 80 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 State Borders which do not follow physical features will be imported from the Geoscience Australia GEODATA 100K Coast Product. State borders which follow physical features will be coincident with those features. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales FrameworkBoundaries (feature class) bound all polygons in the Framework Dataset except Large Area Features. For more information on the use of State Border See Section 3 Chapter 5.17. Inter-Feature Relationship Rules - External to Associated DatasetMap RulesGeneral - All Scales State borders will be labelled with State names (See Section 2, 4.6) Related FeaturesInternational Boundary , Mainland Related ChaptersSection 3 chapters 5.11.2, 5.17and 6.8 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
Waterbody IslandLocations Framework Point A named island within an inland waterbody or forming part of the shoreline. 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. Waterbody Island 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. WaterbodyIsland NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Waterbody Island. This item must 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 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 RulesGeneral - All Scales Only named inland islands and named islands which form part of the shoreline will be depicted. (See Section 3 6.9.7). The locality point will be placed on land at the approximate centre of the island. Offshore islands will be named as an attribute of the polygon, see Island. Inter-Feature Relationship Rules - Internal to Associated DatasetInter-Feature Relationship Rules - External to Associated DatasetGeneral - All Scales Where a locality name refers to a wide area the name may appear on a number of overlapping Map Indexes eg 'Murdie Island'. A locality of the same code and name should not be repeated within the same Map Index unless it relates to a number of entities sharing the same name. Map RulesRelated FeaturesWatercourse, Watercourse Area Related ChaptersSection 3 chapters 5.3, 5.11.1, 5.11.2, 5.18, 6.9 and 6.5 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.
|