NTDB & NTMS Specifications (250K & 100K) |
Updated: 1/12/2007
Building AreaBuildingAreas Habitation Polygon A permanent walled and roofed construction or the ruin of such a construction, capable of being represented at scale. 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. Building Area NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the building. (see Geodatabase Rules for population requirements.) BUILDING FUNCTION (BUILDINGFUNCTION) [String;Yes;50;0;0;Pop_Req] Function of Operational Building; Acceptable Domain Entries from dm_BuildingFunction; BUILDING STATUS (BUILDINGSTATUS) [String;Yes;12;0;0;Pop_Req] The entities operational status; Acceptable Domain Entries from dm_BuildingStatus; CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status; Abandoned 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; 26 - Operational/Abandoned building & Abandoned homestead 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 All Building Areas above the minimum size criteria of 625 square metres will be captured as 'Building Areas' where there is strong evidence of their existence from the imagery/orthophotography. 1:100 000 All Buildings above the size criteria of 49 square metres will be captured where there is strong evidence of their existence from the imagery/orthophotography either as a Building Point or a Building Area. 1:250 000 All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. General - All Scales New buildings will be captured from supplied imagery where there is strong evidence on the image to support the interpretation or where other reference or supporting material assists the interpretation. Inter-Feature Relationship Rules - Internal to Associated Dataset1:25 000 Buildings will be captured or retained within Built Up Area, where information is available. 1:100 000 Buildings will be captured or retained within Built Up Area, where information is available. 1:250 000 Buildings will not be shown within Built-up areas. Building Points will be shown in 'defined holes' in Built Up Area. General - All Scales Building Area feature cannot overlap each other. Inter-Feature Relationship Rules - External to Associated Dataset1:25 000 Buildings with a function of 'Substation' or 'Power Station' will be cloned as 'Sub Station' or 'Power Station' respectively in the Utility Feature Dataset. 1:100 000 Buildings with a function of 'Substation' or 'Power Station' will be cloned as 'Sub Station' or 'Power Station' respectively in the Utility Feature Dataset. General - All Scales Building Areas will be shown in Recreation Area and Cemetery Area. Map Rules1:100 000 Homesteads may be filtered for cartographic representation based on the rules set out for data capture at 1:250 000 in Appendix C. Operational Homesteads will have precedence over Abandoned Homesteads. In addition, Homesteads will take precedence over buildings with a function of 'Dwelling' or 'Other Or Unknown Function'. 1:250 000 Operational homesteads will be shown by the feature class Locality code 'Homestead' subject to the rules for inclusion of homesteads. Abandoned homesteads and operational homesteads that fail the rules for inclusion as Locality homesteads may still be shown as buildings General - All Scales If black type falls unavoidably over the building symbol, the feature's symbol attribute will be '0' (non-printing). Related FeaturesBuilding Point, Vertical Obstruction, Homestead, Place Name, Landmark Area 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
Building PointBuildingPoints Habitation Point A permanent walled and roofed construction or the ruin of such a construction. 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. Building Point NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the building. (see Geodatabase Rules for population requirements.) BUILDING FUNCTION (BUILDINGFUNCTION) [String;Yes;50;0;0;Pop_Req] Function of Operational Building; Acceptable Domain Entries from dm_BuildingFunction; BUILDING STATUS (BUILDINGSTATUS) [String;Yes;12;0;0;Pop_Req] The entities operational status; Acceptable Domain Entries from dm_BuildingStatus; CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status; Abandoned 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; 430 - Operational/Abandoned building & Abandoned homestead 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 All Building Points above the size criteria of 49 square metres will be captured where there is strong evidence of their existence from the imagery/orthophotography. 1:100 000 All Buildings above the size criteria of 49 square metres will be captured where there is strong evidence of their existence from the imagery/orthophotography either as a Building Point or a Building Area. 1:250 000 All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. General - All Scales New buildings will be captured from supplied imagery where there is strong evidence on the image to support the interpretation or where other reference or supporting material assists the interpretation. Inter-Feature Relationship Rules - Internal to Associated Dataset1:25 000 Buildings will be captured or retained within Built Up Area, where information is available. 1:100 000 Buildings will be captured or retained within Built Up Area, where information is available. 1:250 000 Buildings will not be shown within Built-up areas. Building Points will be shown in 'defined holes' in Built Up Area. General - All Scales Building Point features cannot overlap each other. Inter-Feature Relationship Rules - External to Associated Dataset1:25 000 Buildings with a function of 'Substation' or 'Power Station' will be cloned as 'Sub Station' or 'Power Station' respectively in the Utility Feature Dataset. 1:100 000 Buildings with a function of 'Substation' or 'Power Station' will be cloned as 'Sub Station' or 'Power Station' respectively in the Utility Feature Dataset. General - All Scales Building Points will be shown in Recreation Area and Cemetery Area. Map Rules1:100 000 Homesteads may be filtered for cartographic representation based on the rules set out for data capture at 1:250 000 in Appendix C. Operational Homesteads will have precedence over Abandoned Homesteads. In addition, Homesteads will take precedence over buildings with a function of 'Dwelling' or 'Other Or Unknown Function'. General - All Scales The building symbol will be aligned parallel to the map grid. Related FeaturesBuilding Area, Vertical Obstruction, Homestead, Place Name, Landmark Area 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
Built Up AreaBuiltUpAreas Habitation Polygon A concentration of buildings surrounding a network of roads and supported by other associated infrastructure. 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. Built Up Area NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the Built-Up Area. 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; 420 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 Areas of open space which are not Recreation Areas and have an area greater than 62500 square metres at 1:25 000 will be excluded from the built-up area. 1:100 000 Areas of open space which are not Recreation Areas and have an area greater than 62500 square metres at 1:100 000 will be excluded from the built-up area. 1:250 000 Areas of open space which are not Recreation Areas and have an area greater than 390625 square metres at 1:250 000 will be excluded from the built-up area. General - All Scales A Built Up Area will be representative of all buildings which are set out on street patterns and which are too close to be shown using individual symbols at map scale. Inter-Feature Relationship Rules - Internal to Associated Dataset1:25 000 A Built Up Area (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality; 1:100 000 A Built Up Area (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality; 1:250 000 Where a Built Up Area edge (feature type polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature: General - All Scales Built-up area features cannot overlap each other. Inter-Feature Relationship Rules - External to Associated Dataset1:25 000 A Built Up Area (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality; 1:100 000 A Built Up Area (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality; 1:250 000 Dual carriageways, highways/principal roads and secondary roads will be shown through Built-up areas. The selection of minor roads within Built-up Area varies according to scale. (See Road) General - All Scales Built-up area features cannot overlap; Map RulesGeneral - All Scales Built-up areas will be named. Related FeaturesDistance Indicator, Populated Place, Place Name Related ChaptersSection 2 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
Habitation AnnoHabitationAnno Habitation Annotation Type associated with the Habitation 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 HabitationAnno; 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_HabitationFCs; 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
HomesteadHomesteads Habitation Point A named prominent building or set of buildings which is/are the place of permanent residence in rural areas. 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. Homestead NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the homestead. 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 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. 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; 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; 40 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. Geodatabase RulesGeneral - All Scales The homestead feature will only be captured/retained in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' when considered significant. This will be regardless of whether it was shown in the TOPO250K NTDB. For information on capture and display of the homesteads feature (Code 4) in moderately and sparsely settled areas refer to Appendix C. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Abandoned homesteads will not be shown as a Homestead feature but rather as a building point. Inter-Feature Relationship Rules - External to Associated DatasetMap RulesGeneral - All Scales Homestead names will be named where named in the NTDB. Related FeaturesBuilding Area, Building Point, Built Up Area, Kilometric distance marker, Railway Station, Road, Place Name. Related ChaptersSection 3 chapters 5.11.1, 5.11.2 Related ProductsGEODATA TOPO250K, 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
Populated PlacePopulatedPlaces Habitation Point A named settlement with a population of 200 or more persons. 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. Populated Place NAME (NAME) [String;Yes;60;0;0;Pop_Dep] The name of the populated place. This item must be populated. POPULATION (POPULATION) [Integer;Yes;0;8;0;Pop_Wk] The population (number of persons) indicated by the ABS Census figures that exist for this locality 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 - 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 Populated places have a population of 200 or more. All populated places in the supplied Census database clip will be included as populated place localities. The names of populated places will be as named for the census. Where names have been combined for the census (eg hyphenated) they will be combined unless separate populations are given for the components in which case the components will be named separately. Inter-Feature Relationship Rules - Internal to Associated DatasetGeneral - All Scales Where a locality name refers to a wide area the name may appear on a number of adjacent tiles eg 'North Melbourne'. A locality of the same code and name should not be repeated on the same tile unless it relates to a number of entities sharing the same name. Inter-Feature Relationship Rules - External to Associated DatasetMap RulesGeneral - All Scales Populated places will be named. Related FeaturesBuilding Area, Building Point, Built Up Area, Kilometric distance marker, Place Name, Railway Station, Road. 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. |
Unless otherwise noted, all Geoscience Australia material on this website is licensed under the Creative Commons Attribution 3.0 Australia Licence.
|