Updated: 31/01/2012

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

Cave

Caves

Physiography

Point

A naturally formed, subterranean open area or chamber.

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.

Cave

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the Cave/s. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (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

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

Caves shown on the base material, reference material or the latest previous edition map (if provided) will be captured/retained.

This feature will be used to represent the location of an individual cave as well as groups of caves.

All caves are to have an accompanying TextNote 'cave', 'sinkhole', etc. unless the word 'cave', 'sinkhole', etc. is included in the name.

When defining the Upperscale value for caves, consideration should be made regarding proximity between cave entrances. When two or more caves entrances exist within (UpperScale/1000)m then only a selection of the cave entrances (separated by at least Upperscale/1000m from each other) should be assigned the Upperscale value to form a representative pattern.

Only Caves of National or Historical Significance will be shown at an Upperscale of 250000, guidance should be taken from, but not restricted to, the latest previous edition 1:250000 NTMS.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Named caves will be cloned as Place Name in the locations feature class.

Caves cannot fall within the following polygons;
Lake, Reservoirs (feature class polygon), WatercourseAreas (feature class polygon), Canal Area, BuildingAreas (feature class polygon), Sea.

Map Rules

General - All Scales

Caves will be named where they are named in the associated geodatabases.

All caves are to have an accompanying descriptive note 'cave', 'sinkhole', etc. unless the word 'cave', 'sinkhole', etc. is included in the name.

Related Features


Related Chapters

Section 3 Chapter 5.3, 5.11.1

Related Products

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

Cliff

Discontinuities

Physiography

Polyline

A high, steep, significant or overhanging face of rock.

Minimum Size Criterion:


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

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

Data Attributes

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

Cliff

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.

Cliff

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

Cliffs will be named where named on the base material/digital or reference material, name will be held in the textnote field.

Geological faults will be shown as cliffs when there is a relative vertical displacement of the land mass at the fault.

Coastal cliffs will be treated in the same way as inland cliffs.

No differentiation will be made between cliffs and escarpments.

The feature shall be digitised such that the down hill side is on the left going from start node to end node.

The Upperscale value will be assigned for 250,000 and larger scales (smaller areas) based solely on the map representation size criteria. An Upperscale value of 1,000,000 will be assigned if the feature either:

  • meets the map representation size criteria; or
  • is below the map representation size criteria but appeared on the previous edition World Aeronautical Chart

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Where a DeformationAreas edge (feature class polygon) have a similar shape to another natural feature such as a cliff, the relevant section of DeformationAreas edge will be made coincident with this other feature.

Cliffs cannot cross;
other features in the discontinuity feature class

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Contours & Auxiliary Contours will be broken for cliffs using the feature type Connector Discontinuity.

Cliffs cannot appear in;
Sea, Lake, Reservoirs (feature class), BuildingArea (feature class), Reef, Shoal and Foreshore Flat.

Height of high cliffs and escarpments are to be indicated by the use of spot elevations where available.

A cliff will be symbolised to 0 a maximum of 0.8 mm either side of the location point of a lighthouse or horizontal control point symbol where the symbol touches the cliff.

A node on a watercourse, or connector, must exist coincident with a vertex on a cliff feature where they cross. Where a waterfall exists at the same location it must be coincident with the node on the watercourse or connector.

Map Rules

1:100 000

Cliffs will be named where named in the associated geodatabase, unless adjacent development means this would lead to clutter.

1:250 000

Cliffs will be named where named on the previous edition map, unless adjacent development means this would lead to clutter.

General - All Scales

Cliff symbols will be masked where black type unavoidably overprints the feature. The break measurement will be 0.2 mm on either side of the type where it crosses the feature. (Note: the feature will be masked only on the map and will be complete in the data.)

Related Features

Related Chapters

Section 3 Chapters 5.3, 5.7 and 6.6

Related Products

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

Crater

Craters

Physiography

Polygon

A bowl shaped natural depression with steep slopes at the rim, formed by volcanic activity or meteor impact.

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 10000  
1:250 000 62500  

Data Attributes

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

Crater

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the crater. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (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.

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

Crater polygons will be defined by the perimeter of the crater rim.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

The crater perimeter cannot cross the perimeter of other physiography polygon features.

Craters must not overlap;
Other Physiography feature dataset polygons.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Crater features cannot overlap;
Sea.

The crater perimeter cannot cross the perimeter of a Mine Area feature.

Map Rules

General - All Scales

All craters are to have an accompanying descriptive note 'crater' unless the word 'crater' is included in the name.

Related Features


Related Chapters

Section 3 Chapter 5.18, 5.19

Related Products

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

Cutting

Discontinuities

Physiography

Polyline

An open excavation of the Earth's surface to provide passage for a road, railway, canal or similar entity.

Minimum Size Criterion:


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

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

Data Attributes

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

Cutting

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.

Cutting

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

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences on the previous edition map, in the base material/digital data or NTDB meeting the minimum size for 'inclusion' will be captured/retained unless there is clear evidence they no longer exist. New cuttings should meet the minimum height criterion of 5m.

The linear feature for which the cutting was made need no longer exist, eg a dismantled railway line.

A cutting may be either on one side of the linear feature (or its former position) or may be paired with a second cutting on the other side. The combination of a cutting on one side and an embankment on the other is permissible.

A Cutting feature represents the base of the entity, and will always be oriented so that the upslope will be on the right going from start node to end node.

The upperscale value will be based on the following two factors:

  • an cutting must meet the map representation size criteria for the applicable scale; and
  • If the linear feature (eg minor road) for which the cutting was made is not being represented at the applicable scale then the associated cutting feature should not be considered suitable for that scale unless it has historical significance (embankments with historical significance will be highlight by Geoscience Australia if they occur).

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Cuttings cannot cross;
the feature for which the cutting was created or other features in the Discontinuities feature class, Cave, Pinnacle.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Cuttings cannot cross;
the feature for which the cutting was created, Roads (feature class), Railway, Canal Line, Canal Area, Watercourses, WatercourseAreas (feature class), Dam Wall.

Cuttings cannot appear in;
Sea, Lake, Reservoirs (feature class), WatercourseAreas (feature class), Canal Area and BuildingAreas (feature class).

Map Rules


Related Features

Related Chapters

Section 3 Chapter 5.3, 5.7

Related Products

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

Distorted Surface

DeformationAreas

Physiography

Polygon

An area over which vehicular movement is difficult or impossible due to the fractured nature of the ground, or rock debris lying on the surface.

Minimum Size Criterion:


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

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

Data Attributes

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

Distorted Surface

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.

DistortedSurface

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

This field is not applicable to this subtype and therefore is currently not to 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

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

New Distorted Surface polygons that are under the minimum size for data capture but form clusters with other new or existing Distorted Surface polygons (which either meet, or are below, the minimum size for data capture) will be considered applicable for that capture scale if the resultant cluster/s are equal to, or exceed, the minimum size for data capture. The only exception is when the resultant cluster misrepresents the true extent/significance of the feature. A cluster will only be considered legitimate in this context where the separation between polygons is equal to or less than ((Capture Scale/1000) * 0.2)) metres and each component part is above the minimum size for inclusion. In this situation, the Distorted Surface polygons should be captured as their individual components not as the cluster upon which its applicability is based.

The UPPERSCALE value will be applied based on a Distorted Surface polygon meeting the applicable minimum size for map representation. Where Distorted Surface polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature.

This feature can include distinctive broken country characterised by fractures, joints, faults, gilgai, or broken stone.

All distorted surfaces are to have an accompanying TextNote, eg 'gilgai', 'lava flow'.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Where a DeformationAreas edge (feature class polygon) have a similar shape to another natural feature such as a cliff, the relevant section of DeformationAreas edge will be made coincident with this other feature.

Distorted surfaces can not overlap other polygons in the physiography dataset.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Distorted Surfaces cannot appear in or overlap;
Lake (Non Perennial), Watercourse Area (Non Perennial or Braided) or polygons in the industry dataset.

Where a DeformationAreas edge (feature class polygon) have a similar shape to another natural feature such as a Watercourse, the relevant section of DeformationAreas edge will be made coincident with this other feature.

Map Rules

General - All Scales

All distorted surfaces are to have an accompanying descriptive note, eg 'gilgai', 'lava flow'.

Related Features


Related Chapters

Section 3 Chapter 5.18, 5.19

Related Products

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

Embankment

Discontinuities

Physiography

Polyline

An artificial bank of earth and or stone built above the natural surface.

Minimum Size Criterion:


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

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

Data Attributes

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

Embankment

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.

Embankment

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

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences on the previous edition map, in the base material/digital data or NTDB meeting the minimum size for 'inclusion' will be captured/retained unless there is clear evidence they no longer exist. New cuttings should meet the minimum height criterion of 5m.

The linear feature for which the embankment was made need no longer exist, eg a dismantled railway line.

An embankment may be either on one side of the linear feature (or its former position) or may be paired with a second embankment on the other side. The combination of an embankment on one side and a cutting on the other is permissible.

An embankment feature represents the top of the embankment entity. The feature will always be oriented so that the downslope will be on the right going from start node to end node.

The upperscale value will be based on the following two factors:

  • an embankment must meet the map representation size criteria for the applicable scale; and
  • If the linear feature (eg minor road) for which the embankment was made is not being represented at the applicable scale then the associated embankment feature should not be considered suitable for that scale unless it has historical significance (embankments with historical significance will be highlight by Geoscience Australia if they occur).

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Embankments cannot cross;
the feature for which the embankment was created, any other feature from the Discontinuities feature class, Cave or Pinnacle.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Embankments cannot cross;
the feature for which the embankment was created or Roads (feature class), Railway, Canal Line, Canal Area, Watercourse, WatercourseAreas (feature class) and Dam Wall.

Embankments cannot appear over the following;
Sea, Lake, Reservoirs (feature class) and BuildingAreas (feature class).

Map Rules


Related Features

Related Chapters

Section 3 Chapter 5.3, 5.7

Related Products

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

Levee

Discontinuities

Physiography

Polyline

A low earth wall erected to restrain flood waters or to contain irrigation water.

Minimum Size Criterion:


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

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

Data Attributes

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

Levee

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.

Levee

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

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences on the previous edition map, in the base material/digital data or NTDB meeting the minimum size for 'inclusion' will be captured/retained unless there is clear evidence they no longer exist.

All levees must meet the minimum height for inclusion of 2m except those within Salt Evaporators which have no minimum height criteria.

Where a levee and a road co-exist and the road travels the whole length of the levee then an embankment feature should be used instead of a levee.

The upperscale value will be based on the following two factors:

  • a levee must meet the map representation size criteria for the applicable scale; and
  • If the feature for which the levee was made to protect is not being represented at the applicable scale then the associated levee feature should not be considered suitable for that scale unless it has historical or regional significance (levees with historical or regional significance will be highlight by Geoscience Australia if they occur).

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Levees cannot cross;
themselves, other features in the Discontinuities feature class.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Levees cannot overlap;
Sea, BuildingAreas (feature class).

Map Rules


Related Features

Related Chapters

Section 3 Chapter 5.3

Related Products

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

Outcrop

DeformationAreas

Physiography

Polygon

An area of land where large rocks or boulders protrude from or rest on the surface.

Minimum Size Criterion:


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

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

Data Attributes

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

Outcrop

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.

Outcrop

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the outcrop. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (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

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

New Outcrop polygons that are under the minimum size for data capture but form clusters with other new or existing Outcrop polygons (which either meet ,or are below, the minimum size for data capture) will be considered applicable for that capture scale if the resultant cluster/s are equal to, or exceed, the minimum size for data capture. The only exception is when the resultant cluster misrepresents the true extent/significance of the feature. A cluster will only be considered legitimate in this context where the separation between polygons is equal to or less than ((Capture Scale/1000) * 0.2)) metres and each component part is above the minimum size for inclusion. In this situation, the Outcrop polygons should be captured as their individual components not as the cluster upon which its applicability is based.

The UPPERSCALE value will be applied based on an Outcrop polygon meeting the applicable minimum size for map representation. Where Outcrop polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Where a DeformationAreas edge (feature class polygon) have a similar shape to another natural feature such as a cliff, the relevant section of DeformationAreas edge will be made coincident with this other feature.

Outcrops cannot overlap;
Other Deformation Areas (feature class), Crater, Sand Area, Sand Dunes, Mine Area.

Inter-Feature Relationship Rules - External to Associated Dataset

1:250 000

Outcrops cannot overlap;
AircraftFacilityPoints, AircraftFacilityAreas (feature class), Airport Area, Built Up Area, Sea, BuildingAreas (feature class), ForestOrShrub, Lake, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, WatercourseAreas (feature class), Canal Area.

General - All Scales

Where a DeformationAreas edge (feature class polygon) have a similar shape to another natural feature such as a Watercourse, the relevant section of DeformationAreas edge will be made coincident with this other feature.

Outcrops cannot overlap;
AircraftFacilityPoints, AircraftFacilityAreas (feature class), Airport Area, BuildingAreas feature class (Ruin), Lake (Non Perennial), Flood Irrigation Storage, Watercourse Area ( Non Perennial)

Map Rules

General - All Scales

Rocky outcrops are to have an accompanying note 'rocky outcrops'.

Related Features

Related Chapters

Section 3 Chapters 5.18, 5.19

Related Products

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

Physiography Anno 100K

PhysiographyAnno100K

Physiography

Annotation

Type associated with the Physiography 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 PhysiographyAnno;
Arial10ptItalicCenter
Arial12ptItalicCenter
Arial14ptItalicCenter
Arial18ptItalicCenter
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
Arial8ptItalicCenter
Arial8ptItalicLeft
Arial8ptItalicRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight

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_PhysiographyFCs;
Caves
Craters
DeformationAreas
Discontinuities
Pinnacles
SandRidges
Sands

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 Physiography feature dataset should exist within the PhysiographyAnno 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 Chapters 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

Physiography Anno 250K

PhysiographyAnno250K

Physiography

Annotation

Type associated with the Physiography 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 PhysiographyAnno;
Arial10ptItalicCenter
Arial12ptItalicCenter
Arial14ptItalicCenter
Arial18ptItalicCenter
Arial24ptItalicCenter
Arial5ptItalicCenter
Arial5ptItalicleft
Arial5ptItalicRight
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
Arial7ptitalicCenter
Arial7ptItalicLeft
Arial8ptItalicCenter
Arial8ptItalicLeft
Arial8ptItalicRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight

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_PhysiographyFCs;
Caves
Craters
DeformationAreas
Discontinuities
Pinnacles
SandRidges
Sands

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 Physiography feature dataset should exist within the PhysiographyAnno 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 Chapters 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:25 000
1:100 000
1:250 000 &
1:1 000 000

Pinnacle

Pinnacles

Physiography

Point

A tall, slender spire shaped rock; projecting from a level or gently sloping surface, or the top of a mountain.

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.

Pinnacle

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the Pinnacle. This item should be populated where name is known.

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (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_Physiography.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_Physiography.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_Physiography.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

All feature occurrences in the base material/digital data will be retained unless there is clear evidence they no longer exist.

Rocks shown as point features on the previous edition map or reference material which do not meet the definition of a pinnacle will be represented as a Place Name with a symbol of 52 (these features must contain a name to be captured).

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

If the elevation of the top of the Pinnacle is known it will be cloned as a Spot elevation.

Pinnacles cannot appear in the following;
Sea, Lake, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Canal Area, WatercourseAreas (feature class), BuildingAreas (feature class), AircraftFacilityAreas (feature class), Airport Area.

Map Rules

General - All Scales

Pinnacles will be named where known.

Where a pinnacle is coincident with a spot elevation feature the elevation of the spot elevation will be shown on the map.

Related Features

Related Chapters

Section 3 Chapter 5.3, 5.11.1

Related Products

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

Razorback

Discontinuities

Physiography

Polyline

A long and narrow upland with steep sides.

Minimum Size Criterion:


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

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

Data Attributes

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

Razorback

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature.

8

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.

Razorback

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

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

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

Razorbacks will be named where named is known. The name will be held in the textnote field.

The upperscale field will be based on the map representation size criteria for the applicable scale.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Where a DeformationAreas edge (feature class polygon) have a similar shape to another natural feature such as a cliff, the relevant section of DeformationAreas edge will be made coincident with this other feature.

Razorbacks cannot cross;
other features in the discontinuity feature class

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Razorbacks cannot appear in;
Sea, Lake, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, BuildingAreas (feature class).

Razorbacks cannot intersect Watercourse, WatercourseAreas (feature class), Roads (feature class) and Railway

Height of razorbacks are to be indicated by the use of spot elevations where available.

Contour & Auxiliary Contours will be broken for razorbacks using the feature type Connector Discontinuity

Map Rules

General - All Scales

Razorbacks will be named where named on the latest previous edition map unless adjacent development means this would lead to clutter.

Razorback symbols will be masked where black type unavoidably overprints the feature. The break measurement will be 0.2 mm on either side of the type where it crosses the feature. (Note: the feature will be masked only on the map and will be complete in the data.)

Related Features

Related Chapters

Section 3 Chapter 5.3, 6.2, 6.6

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

Sand Area

Sands

Physiography

Polygon

An area predominantly covered with sand and devoid of vegetation.

Minimum Size Criterion:


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

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

Data Attributes

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

Sand Area

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.

SandArea

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

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

New Sand Area polygons that are under the minimum size for data capture but form clusters with other new or existing Sand Area polygons (which either meet, or are below, the minimum size for data capture) will be considered applicable for that capture scale if the resultant cluster/s are equal to, or exceed, the minimum size for data capture. The only exception is when the resultant cluster misrepresents the true extent/significance of the feature. A cluster will only be considered legitimate in this context where the separation between polygons is equal to or less than ((Capture Scale/1000) * 0.2)) metres and each component part is above the minimum size for inclusion. In this situation, the Sand Area polygons should be captured as their individual components not as the cluster upon which its applicability is based.

The UPPERSCALE value will be applied based on a Sand Area polygon meeting the applicable minimum size for map representation. Where Sand Area polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Where a Sands edge (feature class polygon) have a similar shape to another natural feature such as a cliff, the relevant section of Sands edge will be made coincident with this other feature.

Sand Area cannot overlap;
Deformation Areas (feature class), Crater, Other Sand Area, Sand Dunes, Mine Area.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Sand Area will not be shown in braided watercourses.

Sand Area cannot overlap;
Lake (Non Perennial), Flood Irrigation Storage, Watercourse Area (Non Perennial).

Where a Sands edge (feature class polygon) have a similar shape to another natural feature such as a cliff, the relevant section of Sands edge will be made coincident with this other feature.

Map Rules


Related Features

Related Chapters

Section 3 Chapters 5.11.2, 5.18 and 5.19

Related Products

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

Sand Dune

Sands

Physiography

Polygon

Mounds of loose sand usually crescent shaped transverse to the prevailing winds.

Minimum Size Criterion:


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

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

Data Attributes

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

Sand Dune

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.

SandDune

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

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

New Sand Dune polygons that are under the minimum size for data capture but form clusters with other new or existing Sand Dune polygons (which either meet, or are below, the minimum size for data capture) will be considered applicable for that capture scale if the resultant cluster/s are equal to, or exceed, the minimum size for data capture. The only exception is when the resultant cluster misrepresents the true extent/significance of the feature. A cluster will only be considered legitimate in this context where the separation between polygons is equal to or less than ((Capture Scale/1000) * 0.2)) metres and each component part is above the minimum size for inclusion. In this situation, the Sand Dune polygons should be captured as their individual components not as the cluster upon which its applicability is based.

The UPPERSCALE value will be applied based on a Sand Dune polygon meeting the applicable minimum size for map representation. Where Sand Dune polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Where a Sands edge (feature class polygon) have a similar shape to another natural feature such as a cliff, the relevant section of Sands edge will be made coincident with this other feature.

Sand Dunes cannot overlap;
Deformation Areas (feature class), Crater, Sand Area, Other Sand Dunes, Mine Area.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Sand Dunes cannot overlap;
Lake (Non Perennial), Flood Irrigation Storage, Watercourse Area (Non Perennial).

Where a Sands edge (feature class polygon) have a similar shape to another natural feature such as a Watercourse, the relevant section of Sands edge will be made coincident with this other feature.

Map Rules


Related Features

Related Chapters

Section 3 Chapters 5.11.2, 5.18 and 5.19

Related Products

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

Sand Ridge

SandRidges

Physiography

Polyline

Sand drifts in long ridges tending parallel to and elongating in the direction of the prevailing winds.

Minimum Size Criterion:


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

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

Data Attributes

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

Sand Ridge

AVERAGE HEIGHT (AVERAGEHEIGHT) [SmallInteger;Yes;0;2;0;Pop_Wk] The average height of the Sand ridges above the surrounding country;

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

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

The average height of the sand ridges attribute is to be populated, where the average height is shown on the base material/digital data, NTDB, latest previous edition map or compilation. Where the average height was not shown this attribute will be retained as 0.

The UpperScale assignment of Sandridges is based on the minimum size for map representation for each scale and where additional filtering is required due to density a selection should be based on the optimal depiction of the landscape.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Sand Ridges cannot overlap;
Lake (Non Perennial), Flood Irrigation Storage, Watercourse, Watercourse Area (Non Perennial), Canal Line.

Map Rules

General - All Scales

Descriptive notes indicating the average height of the sand ridges are to be included, where the average height is shown on the latest previous edition map or compilation.

Related Features


Related Chapters

Section 3 Chapter 5.3, 6.6

Related Products

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