Updated: 31/01/2012

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

Community Or Commercial Building

BuildingAreas

Habitation

Polygon

A permanent walled and roofed construction or the ruin of such a construction, capable of being represented at scale. Community Or Commercial Buildings refer to either buildings in which activities support community groups or interests (eg Performing Arts Centre) or buildings in which a commercial (non - industrial) activity is occurring (eg Post Office).

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 625  

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

Data Attributes

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

Community Or Commercial Building

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.

CommunityOrCommercialBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionCoC;
Abattoir
Art Gallery
Cinema
Commercial Accommodation
Commercial Office Premises
Commercial Retail Premises
Community Centre
Correctional Centre
Court House
Day Care Centre
Detention Centre
Embassy
Fitness Centre
Function Centre
Government Building
Library
Multi Level Car Park
Museum
Park Headquarters
Performing Arts Centre
Place Of Worship
Post Office
Public Hall
Public Toilet
Shopping Centre
Sports Centre
Sports Or Community Club
Stadium
Tourist Attraction
Tourist Information Centre
Winery
Zoological Support Building

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by some Community Or Commercial Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

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

BuildingAreas (feature class polygons) can not cross the edge of a Built Up Area.

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

BuildingAreas (feature class polygons) cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingAreas (feature class polygons) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

General - All Scales

If black type falls unavoidably over the building symbol, the feature's symbol attribute will be Polygon No Draw.

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.

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

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.11.2, 5.19, 6.5 and 5.18
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Educational Building

BuildingAreas

Habitation

Polygon

A permanent walled and roofed construction or the ruin of such a construction, capable of being represented at scale. Educational Buildings refer to buildings that house government or privately run organisations that provide educational services to the public.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 625  

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

Data Attributes

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

Educational Building

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.

EducationalBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionEdu;
Academy
Community Education College
Kindergarten Or PreSchool
Primary And Secondary School
Primary School
Secondary School
Special Needs School
Technical College
Tertiary Institution

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15.1 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by Educational Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

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

BuildingAreas (feature class polygons) can not cross the edge of a Built Up Area.

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

BuildingAreas (feature class polygons) cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingAreas (feature class polygons) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

General - All Scales

If black type falls unavoidably over the building symbol, the feature's symbol attribute will be Polygon No Draw.

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.

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

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.11.2, 5.19, 6.5 and 5.18
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Emergency Services Building

BuildingAreas

Habitation

Polygon

A permanent walled and roofed construction or the ruin of such a construction, capable of being represented at scale. Emergency Services Buildings refer to buildings that house government or community funded organisations whose primary function is to assist those in life threatening situations.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 625  

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

Data Attributes

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

Emergency Services Building

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.

EmergencyServicesBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionEm;
Ambulance Station
Aviation Medical And Rescue Facility
Aviation Rescue And Fire Fighting Station
Emergency Services Coordination Centre
Fire Station Marine
Fire Station Metro
Fire Station Rural
Marine Rescue Or Coast Guard Station
Police Station
State Emergency Service Facility
Surf Life Saving Club
Water Police Facility

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes


For clarification of Building Functions used by Emergency Services Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

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

BuildingAreas (feature class polygons) can not cross the edge of a Built Up Area.

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

BuildingAreas (feature class polygons) cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingAreas (feature class polygons) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

General - All Scales

If black type falls unavoidably over the building symbol, the feature's symbol attribute will be Polygon No Draw.

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.

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

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.11.2, 5.19, 6.5 and 5.18
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Health And Welfare Building

BuildingAreas

Habitation

Polygon

A permanent walled and roofed construction or the ruin of such a construction, capable of being represented at scale. Health and Welfare Buildings refer to buildings that house government or privately funded organisations that provide medical treatment and services to the public.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 625  

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

Data Attributes

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

Health And Welfare Building

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.

HealthAndWelfareBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionHW;
Allied Health Centre
Childrens Hospital
Community Health Centre
Crematorium
Dental Clinic
Dental Hospital
Emergency Hospital
Eye Or Ear Hospital
General Hospital
Hospice
Indigenous Health Centre
Medical Centre
Morgue
Nursing Home
Psychiatric Hospital
Rehabilitation Centre
Respite Centre

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by Health And Welfare Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

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

BuildingAreas (feature class polygons) can not cross the edge of a Built Up Area.

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

BuildingAreas (feature class polygons) cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingAreas (feature class polygons) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

General - All Scales

If black type falls unavoidably over the building symbol, the feature's symbol attribute will be Polygon No Draw.

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.

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

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.11.2, 5.19, 6.5 and 5.18
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Industry Infrastructure Building

BuildingAreas

Habitation

Polygon

A permanent walled and roofed construction or the ruin of such a construction, capable of being represented at scale. Industry or Infrastructure Buildings are used for two main purposes. Firstly to support fundamental infrastructure such as transport, electricity or communication (eg Railway Control Centre). Secondly to support industrial or farming practices. (eg Desalination Plants or Saw Mill).

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 625  

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

Data Attributes

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

Industry Infrastructure Building

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.

IndustryInfrastructureBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionII;
Aircraft Hanger
Airport Terminal
Bus Terminal
Control Tower
Desalination Plant
Factory
Freight Hub
Greenhouse
Hazardous Waste Treatment Plant
Incinerator Building
Liquid Fuel Terminal
Mail Sorting Centre
Modal Interchange
Potable Water Treatment Plant
Power Station
Pumping Station
Radio Station
Railway Control Centre
Railway Station
Refinery
Saw Mill
Service Station
Sewage Treatment Plant
Shed Or Warehouse
Sub Station
Telephone Exchange
Television Station
Traffic Control Centre
Transport Depot
Waste Recycling Plant
Waste Transfer Station
Weighbridge Station

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by some Industry or Infrastructure Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

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

BuildingAreas (feature class polygons) can not cross the edge of a Built Up Area.

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

BuildingAreas (feature class polygons) cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingAreas (feature class polygons) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

General - All Scales

If black type falls unavoidably over the building symbol, the feature's symbol attribute will be Polygon No Draw.

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.

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

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.11.2, 5.19, 6.5 and 5.18
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Other Building

BuildingAreas

Habitation

Polygon

A permanent walled and roofed construction or the ruin of such a construction, capable of being represented at scale. Other buildings are used when other feature types in the Building Areas feature class are not reflective of the function.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 625  

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

Data Attributes

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

Other Building

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.

OtherBuilding

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_Wk] Function of Operational Building;

Description of function, when known, of building which does not fall into any other category (eg crypt).

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

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

BuildingAreas (feature class polygons) can not cross the edge of a Built Up Area.

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

BuildingAreas (feature class polygons) cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingAreas (feature class polygons) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

General - All Scales

If black type falls unavoidably over the building symbol, the feature's symbol attribute will be Polygon No Draw.

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.

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

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.11.2, 5.19, 6.5 and 5.18
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000
1:1 000 000
1:2 500 000 &
1:5 000 000

Residential Building

BuildingAreas

Habitation

Polygon

A permanent walled and roofed construction or the ruin of such a construction, capable of being represented at scale. Residential Buildings are used principally as dwellings.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 625  

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000 625  
1:100 000 22500  
1:250 000 140625  
1:1 000 000    
1:2 500 000    
1:5 000 000    

Data Attributes

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

Residential Building

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.

ResidentialBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionRes;
Apartment Block
Convent Or Monastery
Homestead
House
Hut
Retirement Village
Terrace
Transportable Home

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by Residential Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

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

BuildingAreas (feature class polygons) can not cross the edge of a Built Up Area.

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

BuildingAreas (feature class polygons) cannot overlap each other.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingAreas (feature class polygons) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

General - All Scales

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

If black type falls unavoidably over the building symbol, the feature's symbol attribute will be 'Polygon No Draw.

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.

Operational homesteads that fail the rules for inclusion as Homestead feature type may still be shown as unnamed buildings or Dwellings. 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).

Related Features

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.11.2, 5.19, 6.5 and 5.18
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Community Or Commercial Building

BuildingPoints

Habitation

Point

A permanent walled and roofed construction or the ruin of such a construction. Community Or Commercial Buildings refer to either buildings in which activities support community groups or interests (eg Performing Arts Centre) or buildings in which a commercial (non - industrial) activity is occurring (eg Post Office).

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 49  

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

Data Attributes

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

Community Or Commercial Building

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.

CommunityOrCommercialBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionCoC;
Abattoir
Art Gallery
Cinema
Commercial Accommodation
Commercial Office Premises
Commercial Retail Premises
Community Centre
Correctional Centre
Court House
Day Care Centre
Detention Centre
Embassy
Fitness Centre
Function Centre
Government Building
Library
Multi Level Car Park
Museum
Park Headquarters
Performing Arts Centre
Place Of Worship
Post Office
Public Hall
Public Toilet
Shopping Centre
Sports Centre
Sports Or Community Club
Stadium
Tourist Attraction
Tourist Information Centre
Winery
Zoological Support Building

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by some Community Or Commercial Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

BuildingPoints (feature class points) cannot overlap each other.

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

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingPoints (feature class points) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

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 Point No Draw.

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.

Buildings will be masked by Built Up Area.

Related Features

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.11.1
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Educational Building

BuildingPoints

Habitation

Point

A permanent walled and roofed construction or the ruin of such a construction. Educational Buildings refer to buildings that house government or privately run organisations that provide educational services to the public.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 49  

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

Data Attributes

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

Educational Building

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.

EducationalBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionEdu;
Academy
Community Education College
Kindergarten Or PreSchool
Primary And Secondary School
Primary School
Secondary School
Special Needs School
Technical College
Tertiary Institution

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by Educational Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

BuildingPoints (feature class points) cannot overlap each other.

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

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingPoints (feature class points) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

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 Point No Draw.

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.

Buildings will be masked by Built Up Area.

Related Features

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.11.1
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Emergency Services Building

BuildingPoints

Habitation

Point

A permanent walled and roofed construction or the ruin of such a construction. Emergency Services Buildings refer to buildings that house government or community funded organisations whose primary function is to assist those in life threatening situations.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 49  

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

Data Attributes

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

Emergency Services Building

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.

EmergencyServicesBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionEm;
Ambulance Station
Aviation Medical And Rescue Facility
Aviation Rescue And Fire Fighting Station
Emergency Services Coordination Centre
Fire Station Marine
Fire Station Metro
Fire Station Rural
Marine Rescue Or Coast Guard Station
Police Station
State Emergency Service Facility
Surf Life Saving Club
Water Police Facility

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by Emergency Services Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

BuildingPoints (feature class points) cannot overlap each other.

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

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingPoints (feature class points) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

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 Point No Draw.

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.

Buildings will be masked by Built Up Area.

Related Features

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.11.1
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Health And Welfare Building

BuildingPoints

Habitation

Point

A permanent walled and roofed construction or the ruin of such a construction. Health and Welfare Buildings refer to buildings that house government or privately funded organisations that provide medical treatment and services to the public.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 49  

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

Data Attributes

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

Health And Welfare Building

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.

HealthAndWelfareBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionHW;
Allied Health Centre
Childrens Hospital
Community Health Centre
Crematorium
Dental Clinic
Dental Hospital
Emergency Hospital
Eye Or Ear Hospital
General Hospital
Hospice
Indigenous Health Centre
Medical Centre
Morgue
Nursing Home
Psychiatric Hospital
Rehabilitation Centre
Respite Centre

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by Health And Welfare Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

BuildingPoints (feature class points) cannot overlap each other.

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

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingPoints (feature class points) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

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 Point No Draw.

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.

Buildings will be masked by Built Up Area.

Related Features

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.11.1
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Industry Infrastructure Building

BuildingPoints

Habitation

Point

A permanent walled and roofed construction or the ruin of such a construction. Industry or Infrastructure Buildings are used for two main purposes. Firstly to support fundamental infrastructure such as transport, electricity or communication (eg Railway Control Centre). Secondly to support industrial or farming practices. (eg Desalination Plants or Saw Mill).

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 49  

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

Data Attributes

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

Industry Infrastructure Building

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.

IndustryInfrastructureBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionII;
Aircraft Hanger
Airport Terminal
Bus Terminal
Control Tower
Desalination Plant
Factory
Freight Hub
Greenhouse
Hazardous Waste Treatment Plant
Incinerator Building
Liquid Fuel Terminal
Mail Sorting Centre
Modal Interchange
Potable Water Treatment Plant
Power Station
Pumping Station
Radio Station
Railway Control Centre
Railway Station
Refinery
Saw Mill
Service Station
Sewage Treatment Plant
Shed Or Warehouse
Sub Station
Telephone Exchange
Television Station
Traffic Control Centre
Transport Depot
Waste Recycling Plant
Waste Transfer Station
Weighbridge Station

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

For clarification of Building Functions used by some Industry or Infrastructure Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

BuildingPoints (feature class points) cannot overlap each other.

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

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingPoints (feature class points) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

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 Point No Draw.

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.

Buildings will be masked by Built Up Area.

Related Features

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.11.1
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

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

Other Building

BuildingPoints

Habitation

Point

A permanent walled and roofed construction or the ruin of such a construction. Other buildings are used when other feature types in the Building Points feature class are not reflective of the function.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 49  

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

Data Attributes

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

Other Building

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.

OtherBuilding

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_Wk] Function of Operational Building;

Description of function, when known, of building which does not fall into any other category (eg crypt).

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

BuildingPoints (feature class points) cannot overlap each other.

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

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingPoints (feature class points) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

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 Point No Draw.

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.

Buildings will be masked by Built Up Area.

Related Features

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.11.1
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000
1:1 000 000
1:2 500 000 &
1:5 000 000

Residential Building

BuildingPoints

Habitation

Point

A permanent walled and roofed construction or the ruin of such a construction. Residential Buildings are used principally as dwellings.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 49  

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000 49  
1:100 000 49  
1:250 000 49  
1:1 000 000 49  
1:2 500 000 49  
1:5 000 000 49  

Data Attributes

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

Residential Building

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.

ResidentialBuilding

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_Wk] Function of Operational Building;

Acceptable Domain Entries from dm_BuildingFunctionRes;
Apartment Block
Convent Or Monastery
Homestead
House
Hut
Retirement Village
Terrace
Transportable Home

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

Acceptable Domain Entries from dm_BuildingStatus;
Abandoned
Operational
Ruin

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level.

SIGNIFICANCE (SIGNIFICANCE) [String;Yes;35;0;0;Pop_Wk] The national significance of the entity;

Acceptable Domain Entries from dm_HeritageSignificance;
Commonwealth Heritage List
Historical Significance General
National Heritage List
National Trust Property
Register of National Estate
State Or Territory Register
World Heritage List

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

General - All Scales

Core Geodatabase Rules are consistent for all BuildingAreas and BuildingPoints feature class subtypes are have been centralised to minimise duplication, please refer to Section 3 Chapter 6.15 Consistent Geodatabase Rules for all Building Area and Building Point Subtypes


For clarification of Building Functions used by Residential Buildings please refer to Section 3 Chapter 6.15.2 Clarification of Building Functions

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

BuildingPoints (feature class points) cannot overlap each other.

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

BuildingAreas (feature class polygons) can not overlap;
BuildingPoints (feature class)

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

BuildingPoints (feature class points) will be shown in Recreation Area and Cemetery Area.

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.

Map Rules

General - All Scales

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

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 Point No Draw.

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.

Operational homesteads that fail the rules for inclusion as Homestead feature type may still be shown as unnamed buildings or Dwellings. 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).

Related Features

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.3, 5.11.1
Appendix U Chapter 2.1, 2.3, 2.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: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000
1:1 000 000
1:2 500 000 &
1:5 000 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 Inclusion: Area (sq m) Criterion Length (m) Criterion
All features 62500  

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000 62500  
1:100 000 62500  
1:250 000 390625  
1:1 000 000 1000000  
1:2 500 000 1000000  
1:5 000 000 1000000  

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

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

Geodatabase Rules

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.

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.

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

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

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.

Areas of open space which are not Recreation Areas and have an area greater than the minimum size for a defined hole (see Section 3 5.18 for more details) will be excluded from the built-up area.

Unless they are disconnected sections of a larger area, Built Up Areas less than minimum size criteria for capture/inclusion will be represented by a featuretype Place Name or Populated Place. Where Built Up Areas are broken into disconnected sections each with identical attributes, the minimum size criteria for capture/inclusion will be based on the sum total of its component parts. The parts will not be merged to form a multi-part polygon but remain as separate sections.

When assigning Upperscale values the following will apply:


  • For Upperscale of 250 000 and larger scales (smaller areas) the eligibility of a Built Up Area will be based on the minimum size criteria for map representation. If the Built Up Area is broken into disconnected sections each with identical attributes, the minimum size criteria for map representation will be based on the sum total of its component parts.
  • For Upperscale of 1 000 000 the population of the Built Up Area must be 5000 or greater persons. Upperscale assignment will not be based on a map representation size criterion.
  • For Upperscale of 2 500 000 the population of the Built Up Area must be 50 000 or greater persons. Upperscale assignment will not be based on a map representation size criterion.
  • For Upperscale of 5 000 000 the population of the Built Up Area must be 100 000 or greater persons. Upperscale assignment will not be based on a map representation size criterion.

In general, when a Built Up Area has been deemed applicable for a certain scale representation as per above, each component of the Built Up Area will be symbolised. The only exception is when a component's size is so small as to result is a slither effect when symbolised, in which case the specific component can be given a symbol of 3 - PolygonNoDraw.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Built Up Area features cannot overlap each other.

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)

BuildingAreas (feature class) can not cross the edge of a Built Up Area.

For every unique Built Up Area name a corresponding feature must exist in either the Populated Place or Place Name feature types (dependant on population) of the same name. Only one Populated Place or Place Name feature type entity should exist to correlate to a Built Up Area which is broken into disconnected sections each with identical attributes.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

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 (feature type polygon)
Landmark Area (feature type polygon)
Waste Management Area (feature type polygon)
Sea (feature type polygon)
RecreationAreas (feature class polygon)
Edges of Waterbody Polygons from the Waterbodies feature dataset

Built Up Area features cannot overlap;
Recreation Areas (feature class), Cemetery Area, Waste Management Area, Lake, WatercourseAreas (feature class), Canal Area, Mangrove, Reservoirs (feature class), Land Subject to Inundation and Sea features.

The upperscaling of road features is dependant on there relationship to Built Up Area. 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 Roads)

For every unique Built Up Area name a corresponding feature must exist in either the Populated Place or Place Name feature types (dependant on population) of the same name. Only one Populated Place or Place Name feature type entity should exist to correlate to a Built Up Area which is broken into disconnected sections each with identical attributes.

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.

Built Up Areas represented on map products must reflect the minimum size criteria for defined holes at the applicable scale.

Related Features

Related Chapters

Section 2 Chapter 5.3
Section 3 Chapter 5.3, 6.5, 6.7.3, 5.11.2, 5.16, 5.19 and 5.18
Appendix U Chapter 2.1, 2.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: 31/01/2012

Scales 1:100 000

Habitation Anno 100K

HabitationAnno100K

Habitation

Annotation

Type associated with the Habitation Feature Dataset for 1:100 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptCenter
ArialNarrow7ptLeft
ArialNarrow7ptRight
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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification documentation for ease of reference.

Only Annotation associated with, or derived from, entities in feature classes grouped within the 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.

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

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

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: 31/01/2012

Scales 1:250 000

Habitation Anno 250K

HabitationAnno250K

Habitation

Annotation

Type associated with the Habitation Feature Dataset for 1:250 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptCenter
ArialNarrow7ptLeft
ArialNarrow7ptRight
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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification documentation for ease of reference.

Only Annotation associated with, or derived from, entities in feature classes grouped within the 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.

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

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, 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: 31/01/2012

Scales 1:1 000 000

Habitation Anno WAC

HabitationAnnoWAC

Habitation

Annotation

Type associated with the Habitation Feature Dataset for 1:1 000 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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;
ArialNarrow10ptCenter
ArialNarrow10ptLeft
ArialNarrow10ptRight
ArialNarrow12ptCenter
ArialNarrow12ptLeft
ArialNarrow12ptRight
ArialNarrow14ptCenter
ArialNarrow14ptLeft
ArialNarrow14ptRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptItalicCenter
ArialNarrow7ptItalicLeft
ArialNarrow7ptItalicRight
ArialNarrow7ptCenter
ArialNarrow7ptLeft
ArialNarrow7ptRight
ArialNarrow8ptCenter
ArialNarrow8ptLeft
ArialNarrow8ptRight
ArialNarrow9ptCenter
ArialNarrow9ptLeft
ArialNarrow9ptRight

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification documentation for ease of reference.

Only Annotation associated with, or derived from, entities in feature classes grouped within the 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 Lambert Conic Conformal Projection (with two standard parallels and a central meridian per each chart's requirements) to ensure the spatial position of type on the map face can be correctly represented.

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

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, 11

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: 31/01/2012

Scales 1:2 500 000

Habitation Anno 2_5MIL

HabitationAnno2_5MIL

Habitation

Annotation

Type associated with the Habitation Feature Dataset for 1:2 500 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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;
Arial6ptCenter
Arial6ptLeft
Arial6ptRight
Arial7ptCenter
Arial7ptLeft
Arial7ptRight
Arial8ptCenter
Arial8ptLeft
Arial8ptRight
Arial8ptBoldCenter
Arial8ptBoldLeft
Arial8ptBoldRight
Arial10ptBoldCenter
Arial10ptBoldLeft
Arial10ptBoldRight
Arial12ptBoldCenter
Arial12ptBoldLeft
Arial12ptBoldRight
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification documentation for ease of reference.

Only Annotation associated with, or derived from, entities in feature classes grouped within the 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 Simple Conic Projection with two standard parallels of 18 degrees south and 36 degrees south to ensure the spatial position of type on the map face can be correctly represented.

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

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, 12

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: 31/01/2012

Scales 1:5 000 000

Habitation Anno 5MIL

HabitationAnno5MIL

Habitation

Annotation

Type associated with the Habitation Feature Dataset for 1:5 000 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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;
Arial10ptBoldCenter
Arial10ptBoldLeft
Arial10ptBoldRight
Arial12ptBoldCenter
Arial12ptBoldLeft
Arial12ptBoldRight
ArialNarrow6pt5Center
ArialNarrow6pt5Left
ArialNarrow6pt5Right
ArialNarrow6pt5ItalicCenter
ArialNarrow6pt5ItalicLeft
ArialNarrow6pt5ItalicRight
ArialNarrow8pt5Center
ArialNarrow8pt5Left
ArialNarrow8pt5Right
ArialNarrow10ptCenter
ArialNarrow10ptLeft
ArialNarrow10ptRight

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification documentation for ease of reference.

Only Annotation associated with, or derived from, entities in feature classes grouped within the 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 Simple Conic Projection with two standard parallels of 18 degrees south and 36 degrees south to ensure the spatial position of type on the map face can be correctly represented.

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

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, 13

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: 31/01/2012

Scales 1:10 000 000

Habitation Anno 10MIL

HabitationAnno10MIL

Habitation

Annotation

Type associated with the Habitation Feature Dataset for 1:10 000 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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;
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptBoldCenter
ArialNarrow7ptBoldLeft
ArialNarrow7ptBoldRight
ArialNarrow7ptCenter
ArialNarrow7ptLeft
ArialNarrow7ptRight
ArialNarrow9ptBoldCenter
ArialNarrow9ptBoldLeft
ArialNarrow9ptBoldRight

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

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification documentation for ease of reference.

Only Annotation associated with, or derived from, entities in feature classes grouped within the 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 Simple Conic Projection with two standard parallels of 18 degrees south and 36 degrees south to ensure the spatial position of type on the map face can be correctly represented.

Annotation should only occur where the associated feature either has a sufficient dimension size or Upperscale value to be shown at 1:10 000 000 scale.

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, 14

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: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000
1:1 000 000
1:2 500 000
1:5 000 000 &
1:10 000 000

Populated Place

PopulatedPlaces

Habitation

Point

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

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6) ; Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

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

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

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

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

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

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

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

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

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

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 vertex 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 vertex 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

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.

For every unique Built Up Area name a corresponding feature must exist in either the Populated Place or Place Name feature types (dependant on population) of the same name. Only one Populated Place or Place Name feature type entity should exist to correlate to a Built Up Area which is broken into disconnected sections each with identical attributes.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

For every unique Built Up Area name a corresponding feature must exist in either the Populated Place or Place Name feature types (dependant on population) of the same name. Only one Populated Place or Place Name feature type entity should exist to correlate to a Built Up Area which is broken into disconnected sections each with identical attributes.

Map Rules

General - All Scales

Populated places will be named.

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

Related Features

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]



Topic contact: mapfeedback@ga.gov.au Last updated: January 20, 2012