Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Building Area

BuildingAreas

Habitation

Polygon

A permanent walled and roofed construction or the ruin of such a construction, capable of being represented at scale.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m) 625 625 140625
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m) 625 22500 140625
Data Capture and
Map Representation
Length (m)      

Data Attributes

FEATURE 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;
Abattoir
Aged Care Facility
Ambulance Station
Community Centre
Conference Centre
Control Tower
Day Care Centres/Kindergartens
Doctors Surgery
Dwelling
Embassy
Emergency Services Centre
Fire Station
Historical Building
Homestead
Hospital
Other Or Function Unknown
Place Of Worship
Police Station
Post Office
Power Station
Public Hall
Refinery
Saw Mill
School
SES Facility
Shopping Centre
Special Care Facility
Sports Centre
Substation
Telephone Exchange
Tourist Information Centre

BUILDING STATUS (BUILDINGSTATUS) [String;Yes;12;0;0;Pop_Req] The entities operational status;

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

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

Abandoned
Abandoned Homestead
Operational
Ruin

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
0 - Ruin at 250K only
60 - Ruin at 25K and 100K Only

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 Rules

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

Buildings whose area is between 49 square metres and 625 square metres will be shown as 'Building Points'.

Buildings of known function should have the item 'BUILDINGFUNCTION' populated. Buildings whose function is not known or not in the represented list should be coded as 'Other or Function Unknown' and Text Noted with an appropriate description, where available.

A place of residence will be defined as a Building Function 'Dwelling' unless it has a more specific function such as Homestead, Aged Care Facility, etc.

All homesteads will be captured in the data and for this scale will not be subject to the rules set out in Appendix C.

Buildings will be named where named in the base material, reference material, supporting material or where they are of historical, cultural or national significance. E.g. Australian War Memorial, National Art Gallery, Sydney Opera House.

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.

All Buildings between 49 sq m and 625 sq m will be captured as Building Points. New features between 49 sq m and 22 500 sq m will be shown as a Building Point. New features equal to or greater than 22 500 sq m will be shown as a Building Area. For existing features between 625 sq m and 22 500 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Building Area or Building Point).

Buildings of known function should have the item 'BUILDINGFUNCTION' populated. Buildings whose function is not known or not in the represented list should be coded as 'Other or Function Unknown' and Text Noted with an appropriate description, where available.

A place of residence will be defined as a Building Function 'Dwelling' unless it has a more specific function such as Homestead, Aged Care Facility, etc.

All homesteads will be captured in the data and for this scale will not be subject to the rules set out in Appendix C.

Buildings will be named where named in the base material, reference material, supporting material or where they are of historical, cultural or national significance. E.g. Australian War Memorial, National Art Gallery, Sydney Opera House.

1:250 000

All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Buildings with a known function will be Text Noted with the appropriate description, where known. These description, should be consistent with the BUILDING FUNCTION listing for 1:25 000 and 1:100 000, where applicable.

A group of buildings that cannot be shown individually may also be shown by a representative pattern of building features.

Operational homesteads will be shown as a Homestead feature type and cloned as a building point subject to the rules for inclusion of homesteads. Operational homesteads that fail the rules for inclusion as Homestead feature type may still be shown as unnamed buildings. Abandoned homesteads will be named in a similar manner to the method of capture for Homestead feature type in reference to Appendix C. (i.e In densely settled areas Homesteads are not captured unless considered significant (e.g. historical), therefore buildings of classification 'Abandoned Homestead' should not be named in densely settled regions unless they are also considered significant).

Operational homesteads will be shown by the feature type 'Homestead' subject to the rules for inclusion of homesteads. Abandoned homesteads and operational homesteads that fail the rules for inclusion as Homesteads feature type may still be shown as buildings

Buildings other than homesteads will be named where named in the base material/digital data or where they are of historical, cultural or national significance. E.g. Australian War Memorial, National Art Gallery, Sydney Opera House.

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.

A group of buildings will not be aggregated to form a building area.

A significant building such as a papermill that cannot be drawn to scale will be shown using symbol 40. Significant buildings should have landmark value. It is not intended that farm or poultry sheds would be considered significant, particularly in areas where there are many such features. Some examples of significant buildings may be: power stations, hospitals, oil refineries. In remote areas features may take on more significance than in populated centres for example: large roadhouses, paper mills, etc.

Outstations will be considered as Homesteads.

Outcamps will be considered as Place Names. If buildings are present they should be shown as building areas with no text_note. The Place Name should be coincident with a designated building.

Substations will only be included as buildings when there is clear evidence of it meeting the definition of a building. Substations shall not be named unless instructions are provided to do so by GEOSCIENCE AUSTRALIA.

Buildings other than homesteads may be textnoted where the description expands on the distinctive function category eg. Building Function is 'Fire Station' and Textnote is 'rural' or Building Function is 'Other or Function Unknown' and Textnote is 'museum' or Building Function is 'School' and Textnote is 'Technical College'.

Only permanent structures will be captured as buildings within Caravan Parks.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

Buildings will be captured or retained within Built Up Area, where information is available.

Building Areas can not cross the edge of a Built Up Area.

Building Area polygon can not overlap;
Building Point

1:100 000

Buildings will be captured or retained within Built Up Area, where information is available.

Building Areas can not cross the edge of a Built Up Area.

Building Area polygon can not overlap;
Building Point

1:250 000

Buildings will not be shown within Built-up areas. Building Points will be shown in 'defined holes' in Built Up Area.

Each Building Area polygon will contain a single building point feature centred within its extents. The attributes of the Building Area and its associated Building Point should be identical where items coincide with the exception of the PID values.

General - All Scales

Building Area feature cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

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

Buildings with a function of 'Hospital','School','Power Station' and 'Refinery' should be fully surrounded by an associated Landmark Areas of 'Hospital','Educational Institution','Power Generation Facility' and 'Landmark Area General' respectively, where the grounds of the facility meets or exceeds the minimum size criteria. This should also apply for other buildings with unique functions which are related to a Landmark Area feature type.

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.

Buildings with a function of 'Hospital','School','Power Station' and 'Refinery' should be fully surrounded by an associated Landmark Areas of 'Hospital','Educational Institution','Power Generation Facility' and 'Landmark Area General' respectively, where the grounds of the facility meets or exceeds the minimum size criteria. This should also apply for other buildings with unique functions which are related to a Landmark Area feature type.

General - All Scales

Building Areas will be shown in Recreation Area and Cemetery Area.

Map Rules

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

Buildings other than homesteads will be named or labelled where they have a distinctive function, eg. 'factory', 'sawmill', 'Wikipin Agricultural College', or where they were labelled on the latest previous edition map.

Abandoned homesteads will be labelled 'abandoned'.

When a Landmark Area and Ruin to Scale are adjacent then the ruin boundary symbology should take precedence. When a Landmark Area or Ruin to Scale is adjacent to an operational building then the symbology for Landmark Area or Ruin to Scale should take precedence.

Buildings will be masked by Built Up Area.

Related Features

Building Point, Vertical Obstruction, Homestead, Place Name, Landmark Area

Related Chapters

Section 2 chapter 2.2.3
Section 3 chapters 5.11.2, 5.19, 6.5.2 and 5.18
Appendix U chapter 2.1.2, 2.1.3, 2.1.4, 2.3.3, 2.4.4

Related Products

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


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Building Point

BuildingPoints

Habitation

Point

A permanent walled and roofed construction or the ruin of such a construction.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m) 49 49  
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m) 49 49  
Data Capture and
Map Representation
Length (m)      

Data Attributes

FEATURE 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;
Abattoir
Aged Care Facility
Ambulance Station
Community Centre
Conference Centre
Control Tower
Day Care Centres/Kindergartens
Doctors Surgery
Dwelling
Embassy
Emergency Services Centre
Fire Station
Historical Building
Homestead
Hospital
Other Or Function Unknown
Place Of Worship
Police Station
Post Office
Power Station
Public Hall
Refinery
Saw Mill
School
SES Facility
Shopping Centre
Special Care Facility
Sports Centre
Substation
Telephone Exchange
Tourist Information Centre

BUILDING STATUS (BUILDINGSTATUS) [String;Yes;12;0;0;Pop_Req] The entities operational status;

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

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

Abandoned
Abandoned Homestead
Operational
Ruin

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;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable;

430 - Operational/Abandoned building & Abandoned homestead
41 - Ruin
40 - Significant Building
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 Rules

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

Buildings whose area is above 625 square metres will be captured as 'Building Areas'.

Buildings of known function should have the item 'BUILDINGFUNCTION' populated. Buildings whose function is not known or not in the represented list should be coded as 'Other or Function Unknown' and Text Noted with an appropriate description, where available.

A place of residence will be defined as a Building Function 'Dwelling' unless it has a more specific function such as Homestead, Aged Care Facility, etc.

All homesteads will be captured in the data and for this scale will not be subject to the rules set out in Appendix C.

Buildings will be named where named in the base material, reference material, supporting material or where they are of historical, cultural or national significance. E.g. Australian War Memorial, National Art Gallery, Sydney Opera House.

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.

All Buildings between 49 sq m and 625 sq m will be captured as Building Points. New features between 49 sq m and 22 500 sq m will be shown as a Building Point. New features equal to or greater than 22 500 sq m will be shown as a Building Area. For existing features between 625 sq m and 22 500 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Building Area or Building Point).

Buildings of known function should have the item 'BUILDINGFUNCTION' populated. Buildings whose function is not known or not in the represented list should be coded as 'Other or Function Unknown' and Text Noted with an appropriate description, where available.

A place of residence will be defined as a Building Function 'Dwelling' unless it has a more specific function such as Homestead, Aged Care Facility, etc.

All homesteads will be captured in the data and for this scale will not be subject to the rules set out in Appendix C.

Buildings will be named where named in the base material, reference material, supporting material or where they are of historical, cultural or national significance. E.g. Australian War Memorial, National Art Gallery, Sydney Opera House.

1:250 000

All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

A group of buildings that cannot be shown individually may also be shown by a representative pattern of building features.

The point entity will be used to represent the location of a group of buildings as well as an individual building. However, individual buildings will be shown as far as the scale permits.

A new homestead may be shown by a single feature representing a group of buildings, in which case it will be situated as to identify the main residence.

Operational homesteads will be shown as a Homestead feature type and cloned as a building subject to the rules for inclusion of homesteads. Operational homesteads that fail the rules for inclusion as a Homestead feature type may still be shown as unnamed buildings.

Abandoned homesteads will named in a similar manner to the method of capture of the Homestead feature type in the Habitation feature class in reference to Appendix C. (i.e In densely settled areas homesteads are not captured unless considered significant (e.g. historical) therefore abandoned homesteads should not be named in densely settled regions unless they are also considered significant).

Buildings other than homesteads will be named where named in the base material/digital data or where they are of historical, cultural or national significance. E.g. Australian War Memorial, National Art Gallery, Sydney Opera House.

Buildings with a known function will be Text Noted with the appropriate description, where known. These descriptions should be consistent with the BUILDING FUNCTION listing for 1:25 000 and 1:100 000, where applicable.

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.

A group of buildings will not be aggregated to form a Building Area.

A significant building such as a papermill that cannot be drawn to scale will be shown using symbol 40. Significant buildings should have landmark value. It is not intended that farm or poultry sheds would be considered significant, particularly in areas where there are many such features. Some examples of significant buildings may be: power stations, hospitals, oil refineries. In remote areas features may take on more significance than in populated centres for example: large roadhouses, paper mills, etc.

Buildings coincident will chimneys will be given symbol 0 non printing.

Outstations will be considered as Homesteads.

Outcamps will be considered as Place Names. If buildings are present they should be shown as building points with no text_note. The Place Name should be coincident with a designated building.

Substations will only be included as buildings when there is clear evidence of it meeting the definition of a building. Substations shall not be named unless instructions are provided to do so by GEOSCIENCE AUSTRALIA.

Buildings other than homesteads may be textnoted where the description expands on the distinctive function category eg. Building Function is 'Fire Station' and Textnote is 'rural' or Building Function is 'Other or Function Unknown' and Textnote is 'museum' or Building Function is 'School' and Textnote is 'Technical College'.

Only permanent structures will be captured as buildings within Caravan Parks.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

Buildings will be captured or retained within Built Up Area, where information is available.

Building Area polygon can not overlap;
Building Point

1:100 000

Buildings will be captured or retained within Built Up Area, where information is available.

Building Area polygon can not overlap;
Building Point

1:250 000

Buildings will not be shown within Built-up areas. Building Points will be shown in 'defined holes' in Built Up Area.

Each Building Area polygon will contain a single building point feature centred within its extents. The attributes of the Building Area and its associated Building Point should be identical where items coincide with the exception of the PID values.

General - All Scales

Building Point features cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

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

Buildings with a function of 'Hospital','School','Power Station' and 'Refinery' should be fully surrounded by an associated Landmark Areas of 'Hospital','Educational Institution','Power Generation Facility' and 'Landmark Area General' respectively, where the grounds of the facility meets or exceeds the minimum size criteria. This should also apply for other buildings with unique functions which are related to a Landmark Area feature type.

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.

Buildings with a function of 'Hospital','School','Power Station' and 'Refinery' should be fully surrounded by an associated Landmark Areas of 'Hospital','Educational Institution','Power Generation Facility' and 'Landmark Area General' respectively, where the grounds of the facility meets or exceeds the minimum size criteria. This should also apply for other buildings with unique functions which are related to a Landmark Area feature type.

General - All Scales

Building Points will be shown in Recreation Area and Cemetery Area.

Map Rules

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

If black type falls unavoidably over the building symbol, the feature's symbol attribute will be '0' (non-printing).

Buildings other than homesteads will be named or labelled where they have a distinctive function, eg. 'factory', 'sawmill', 'Wikipin Agricultural College', or where they were labelled on the latest previous edition map.

Abandoned homesteads will be labelled 'abandoned'.

Buildings will be masked by Built Up Area.

Related Features

Building Area, Vertical Obstruction, Homestead, Place Name, Landmark Area

Related Chapters

Section 2 chapter 2.2.3
Section 3 chapters 5.3, 5.11.1
Appendix U chapter 2.1.2, 2.1.3, 2.1.4, 2.1.10, 2.3.3, 2.4.4

Related Products

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


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Built Up Area

BuiltUpAreas

Habitation

Polygon

A concentration of buildings surrounding a network of roads and supported by other associated infrastructure.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m) 62500 62500 390625
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m) 62500 62500 390625
Data Capture and
Map Representation
Length (m)      

Data Attributes

FEATURE 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;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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 Rules

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

Unless they are disconnected sections of a larger area, Built Up Areas less than 62500 sq m. at 1:25 000 will be represented by a featuretype Place Name or Populated Place. Where Built Up Areas are broken into disconnected sections each with indentical attributes they will be merged to form a multi-part polygon.

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.

Unless they are disconnected sections of a larger area, Built Up Areas less than 62500 sq m. at 1:100 000 will be represented by a featuretype Place Name or Populated Place. Where Built Up Areas are broken into disconnected sections each with indentical attributes they will be merged to form a multi-part polygon.

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.

Unless they are disconnected sections of a larger area, Built Up Areas less than 390625 sq m. at 1:250 000 will be represented by a featuretype Place Name or Populated Place. Where Built Up Areas are broken into disconnected sections each with indentical attributes they will be merged to form a multi-part polygon.

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.

In some instances, parts or suburbs of a town or city may be split from the main body of the built-up-area by open land or a double sided stream, in which case the separate Built Up Area polygons will carry the same name, eg 'Melbourne' which may be attached to a number of Built Up Area polygon features.

Built Up Area names will be as listed 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 seperately.

Names of suburbs of a city or town will be included as features with the code Place Name.

The boundaries of a Built Up Area should be defined with consideration to the surrounding landscape and location in Australia (e.g. middle of the Northern Territory versus older suburbs in a capital city versus newer suburbs in a fast growing satellite town)

The following sentence is a guideline and should be used with consideration to the rules noted above, the definition of Built Up Area and examples shown in Appendix U Imagery Interpretation Guide (Built Up Area Delineation) :

In General, Built Up Area should consist of the majority of land parcels being less than 3600 sq m and man-made structures (e.g pools, homes, garages, etc) should occupy greater than approximately 15 percent of the land parcel.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1: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;
Another Built Up Area edge (feature type polygon)

Building Areas can not cross the edge of a Built Up Area.

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;
Another Built Up Area edge (feature type polygon)

Building Areas can not cross the edge of a Built Up Area.

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:
Another Built Up Area edge (feature type polygon)
Building Area edge (feature type polygon)

General - All Scales

Built-up area features cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

1: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;
Cemetery Area edge (feature type polygon)
Landmark Area edge (feature type polygon)
Rubbish Tip edge (feature type polygon)
Sea edge (feature type polygon)
RecreationAreas edge (feature class polygon)
Edges of Waterbody Polygons from the Waterbodies feature dataset

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;
Cemetery Area edge (feature type polygon)
Landmark Area edge (feature type polygon)
Rubbish Tip edge (feature type polygon)
Sea edge (feature type polygon)
RecreationAreas edge (feature class polygon)
Edges of Waterbody Polygons from the Waterbodies feature dataset

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)

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:
Road
Railway
Sea wall
Shoreline
WaterbodyBoundaries (except junction and Limit Of Data)
Cemetery Area edge (feature type polygon)
Foreshore Flat edge (feature type polygon)
Landmark Area edge (feature type polygon)
Prohibited Area edge (feature type polygon)
Rubbish Tip edge (feature type polygon)
MarineHazardAreas edge (feature class polygon)
RecreationAreas edge (feature class polygon)
Reserves edge (feature class polygon)
Vegetation edge (feature dataset polygon)

General - All Scales

Built-up area features cannot overlap;
Recreation Area (feature Class), Cemetery Area, Rubbish Tip, Lake, Watercourse Area, Canal Area, Mangrove, Reservoir, Land Subject to Inundation and Sea features.

Map Rules

General - All Scales

Built-up areas will be named.

Built-up areas will mask contours, powerlines and pipelines.

Buildings will be masked by Built Up Area.

Related Features

Distance Indicator, Populated Place, Place Name

Related Chapters

Section 2 chapter 5.3
Section 3 chapter 5.3, 6.5.1, 6.7.3, 5.11.2, 5.16, 5.19 and 5.18
Appendix U chapter 2.1.11, 2.4.4

Related Products

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


[back to top]



Updated: 1/12/2007

Scales 1:25 000 &
1:100 000

Habitation Anno

HabitationAnno

Habitation

Annotation

Type associated with the Habitation Feature Dataset

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m)      

Data Attributes

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

The following annotation classes exist in HabitationAnno;
Arial16ptBoldCenter
Arial18ptBoldCenter
ArialNarrow10ptCenter
ArialNarrow12ptCenter
ArialNarrow14ptCenter
ArialNarrow16ptCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow8ptCenter
ArialNarrow8ptLeft
ArialNarrow8ptRight
PalatinoLinotype6ptLeft
PalatinoLinotype6ptRight
PalatinoLinotype7ptLeft
PalatinoLinotype7ptRight
PalatinoLinotype8ptLeft
PalatinoLinotype8ptRight

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;
BuildingAreas
BuildingPoints
BuiltUpAreas
PopulatedPlaces

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 Rules

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

Only Annotation associated with, or derived from, entities in feature classes grouped within the Habitation feature dataset should exist within the HabitationAnno feature class.

Wherever possible annotation should be stored using the subclasses indicated under AnnotationClassID. Annotation stored as inline text should be kept to a minimum.

Type for large polygons and long linear features may be held in an annotation feature for each word to allow for spacing and differences in orientation, see Section 2 chapter 4.

Annotation should not contain any HTML tags within the blob element, nor should it contain any special characters.

Editing and placement of Annotation should be conducted in the appropriate MGA 1994 zone to ensure the spatial position of type on the map face can be correctly represented.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules


Related Features


Related Chapters

Section 2 Chapter 5, 9, 10

Related Products

NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Updated: 1/12/2007

Scales 1:250 000

Homestead

Homesteads

Habitation

Point

A named prominent building or set of buildings which is/are the place of permanent residence in rural areas.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m)      

Data Attributes

FEATURE 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 Rules

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

Only operational homesteads will have this classification. Outstations are to be considered as homesteads. Outcamps will be shown as a Place Name not as a Homestead.

Homestead names will be captured as shown on the reference material supplied.

The homestead feature should be located, using imagery, so as to identify the main residence.

Homesteads of historical significance will be shown as homesteads (regardless of Appendix C) if operational otherwise if it is abandoned but the building still exists, they will be represented as a building with the classification of an 'Abandoned Homestead'. In both cases a text_note ,'historic', should be included with the feature.

A homestead may be shown by a single feature representing a group of buildings.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Abandoned homesteads will not be shown as a Homestead feature but rather as a building point.

Homesteads will be cloned as Building Points

Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules

General - All Scales

Homestead names will be named where named in the NTDB.

Related Features

Building Area, Building Point, Built Up Area, Kilometric distance marker, Railway Station, Road, Place Name.

Related Chapters

Section 3 chapters 5.11.1, 5.11.2
Appendix U chapter 2.1.1

Related Products

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


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Populated Place

PopulatedPlaces

Habitation

Point

A named settlement with a population of 200 or more persons.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m)      

Data Attributes

FEATURE 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
420 - limited use, see Geodatabase rules for when this case applies.

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 Rules

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

The feature point for a populated place will be positioned coincident with a node or vertice on the road network unless there is no road within 250 metres of the built-up area associated with the populated place. If necessary, a vertice will be created on the road coincident with the locality populated place feature. For populated places with a population over 20 000 the point should be placed as near as possible on the road network to the location of the central post office.

Populated places will be named.

The name of some populated places may appear two or three times in the NTDB eg. if there is also a Railway Station or a Built-up area polygon of the same name.

Inter-Feature Relationship Rules - Internal to Associated Dataset

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

Populated places will not be symbolised on the map if they fall within a Built Up Area but will have symbol 420 when no Built Up Area polygon exists.

Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules

General - All Scales

Populated places will be named.

Where symbol 420 is used, the symbol will mask all other detail.

Related Features

Building Area, Building Point, Built Up Area, Kilometric distance marker, Place Name, Railway Station, Road.

Related Chapters

Section 1 chapters 3.8.1
Section 3 chapters 5.11.1, 5.11.2 and 6.5

Related Products

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


[back to top]



Unless otherwise noted, all Geoscience Australia material on this website is licensed under the Creative Commons Attribution 3.0 Australia Licence.