Updated: 1/12/2007

Scales 1:25 000 &
1:100 000

Auxiliary Contour

Contours

Relief

Polyline

A line augmenting relief presentation where significant topographic features are not shown by the prescribed contour interval. The line represents an imaginary line on the ground joining points of equal elevation in relation to the Australian Height Datum.

Minimum Size Criterion:


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

Data Attributes

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

Auxiliary Contour

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

7

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

AuxiliaryContour

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

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

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

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

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

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

ELEVATION ACCURACY (ELEVATIONACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the vertical 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.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

59

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

Geodatabase Rules

1:25 000

Auxilary Contour heights must not represent any multiple of the standard 10m contour interval.

1:100 000

Auxilary Contour heights must not represent any multiple of the standard 20m contour interval.

General - All Scales

Auxiliary Contours will be reclassified as connector standard where they cross Waterbodies such as Watercourse Areas ( Non Perennial or Braided), Salt Evaporators, Settling Ponds and Aquaculture Areas. No gap should exist between the auxiliary contour and the connector standard feature in these cases.

Auxilary Contours will not be used to represent depressions.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

No auxiliary contour can cross itself, another auxilary contour or other entities in the contours feature class.

Contours of different height must not touch each other. No contour can cross itself or another contour.

Spot elevations must not contradict Auxiliary contours.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Auxilary Contours cannot fall over Sea, Lake perennial, Flood Irrigation Storage and Town Rural Storage or Mine Area.

Survey Marks must not contradict Auxilary contours.

Contours can exist in a Mine Area but should not exist within open cut pit associated with the mine area.

Map Rules

General - All Scales

All Auxiliary Contours will be labelled with their elevation, where space permits.

Auxiliary Contours will be masked by Built Up Areas.

Related Features

Hypsometric Area, Standard Contour, Interpolated Contour, Depression Contour, Connector Discontinuity, Connector Standard, Limit Of Data (Relief), Bench Mark, Cliff, Horizontal Control Point, Razorback, Spot Elevation, Waterbodies (Feature Dataset (polygons)), Sea, Mine Area

Related Chapters

Section 1 chapter 3.7.5
Section 2 chapter 2.8
Section 3 chapter 6.2

Related Products

GEODATA LITE TOPO100K, NTMS 100K

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


[back to top]



Updated: 1/12/2007

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

Connector Discontinuity

Contours

Relief

Polyline

A line which represents an imaginary line on the ground joining points of equal elevation in relation to the Australian Height Datum. Connector Discontinuity is to be utilised where contours on the repromat were broken for either a cliff, cutting, embankment or razorback symbol.

Minimum Size Criterion:


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

Data Attributes

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

Connector Discontinuity

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.

ConnectorDiscontinuity

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

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

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

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

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

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

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

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

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

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

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

0

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

Geodatabase Rules

General - All Scales

See Section 3 chapter 6.1.

Connector Discontinuity will not be shown on the map (symbolised to zero).

One contour is to be shown at each contour interval height.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Contours of different height must not touch each other. No contour can cross itself or another contour.

Connector Discontinuities will adhere to the rules in Section 3 chapter 6.1.1. These coincidence rules do not apply to connector discontinuity passing through cuttings and embankments.

No gaps should appear in contours.

Spot Elevations must not contradict contours.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Shoreline, Junctions & other features forming the coastline will be cloned as 0 (zero) elevation contours. The 0 contour will have a classification of Standard contour except where there are coastal cliffs in which case it will have a classification of connector discontinuity or where it is cloned from a junction in which case it will have a classification of connector standard.

Survey Marks (feature dataset) must not contradict contours.

Contours (feature class) cannot fall over Sea, Perennial lake, Flood Irrigation Storage and Town Rural Storage polygons.

Contours can exist in a Mine Area but should not exist within open cut pit associated with the mine area.

Map Rules

General - All Scales

Contours will be masked by Built Up Area.

Related Features

Hypsometric Area, Standard Contour, Interpolated Contour, Depression Contour, Connector Standard, Auxiliary Contour, Limit Of Data (Relief), Bench Mark, Cliff, Horizontal control point, Junction, Razorback, Sea wall , Shoreline, WaterbodyBoundaries (Feature Class)

Related Chapters

Section 1 chapter 3.7.5
Section 2 chapter 2.8
Section 3 chapters 5.11.1 and 6.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

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


[back to top]



Updated: 1/12/2007

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

Connector Standard

Contours

Relief

Polyline

A line which represents an imaginary line on the ground joining points of equal elevation in relation to the Australian Height Datum.Connector Standard is to be utilised where the contour's position is not known, for example in a Watercourse Area or Mine Area.

Minimum Size Criterion:


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

Data Attributes

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

Connector Standard

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.

ConnectorStandard

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

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

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

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

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

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

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

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

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB ; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

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

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

0

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

Geodatabase Rules

1:25 000

The Standard contour interval is 10m.

Contours will be classified as connector standard where they cross Waterbodies such as Watercourse areas (Non Perennial), Salt evaporators, Settling Ponds, Aquaculture Area;
There will be no gap between the contour and the feature it is broken for.

1:100 000

The Standard contour interval is 20m.

Contours will be classified as connector standard where they cross Waterbodies such as Watercourse areas (Non Perennial), Salt evaporators, Settling Ponds, Aquaculture Area;
There will be no gap between the contour and the feature it is broken for.

1:250 000

The Standard contour interval is 50m.

Contours will be classified as connector standard where they cross Waterbodies such as Watercourse areas, Salt evaporators, Settling Ponds, Aquaculture Area, Canal Area and Rapid Area;
There will be no gap between the contour and the feature it is broken for.

General - All Scales

At the entry and exit point of the connector standard feature through the waterbody feature, a vertex should exist in the boundary of the waterbody polygon and its associated boundary line.

One contour is to be shown at each contour interval height.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Contours of different height must not touch each other. No contour can cross itself or another contour.

No gaps should appear in contours.

Spot Elevations must not contradict contours.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Shoreline, Junctions & other features forming the coastline will be cloned as 0 (zero) elevation contours. The 0 contour will have a classification of Standard contour except where there are coastal cliffs in which case it will have a classification of connector discontinuity or where it is cloned from a junction in which case it will have a classification of connector standard.

Survey Marks (feature dataset) must not contradict contours.

Contours (feature class) cannot overlap;
Flood Irrigation Storage, Sea, Lake perennial and Town Rural Storage

Contours can exist in a Mine Area but should not exist within open cut pit associated with the mine area.

Map Rules

General - All Scales

Contours will be masked by Built Up Area.

Related Features

Hypsometric Area, Standard Contour, Interpolated Contour, Depression Contour, Connector Discontinuity, Auxilary Contour, Limit Of Data (Relief), Bench Mark, Cliff, Horizontal control point, Junction, Razorback, Sea wall , Shoreline, WaterbodyBoundaries (Feature Class)

Related Chapters

Section 1 chapter 3.7.5
Section 2 chapter 2.8
Section 3 chapters 5.11.1 and 6.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

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


[back to top]



Updated: 1/12/2007

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

Depression Contour

Contours

Relief

Polyline

A line which represents an imaginary line on the ground joining points of equal elevation in relation to the Australian Height Datum. Depression contours are to be utilised where a portion of a landform dips below its surrounding area crossing a contour interval. The depression must be fully contained within the surrounding landform.

Minimum Size Criterion:


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

Data Attributes

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

Depression Contour

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.

DepressionContour

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

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

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

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

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

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

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

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

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

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

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

58 - Standard depression
57 - Index depression

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

Geodatabase Rules

1:25 000

The Standard contour interval is 10m.

Contours will carry the Symbol code for Index contours at every 50m taken from elevation 0.

1:100 000

The Standard contour interval is 20m.

Contours will carry the Symbol code for Index contours at every 100m taken from elevation 0.

1:250 000

The Standard contour interval is 50m.

Contours will carry the Symbol code for Index contours at every 250m taken from elevation 0.

General - All Scales

For depression contours the ticks will be on the downhill side of the line.

Depression contours shall be digitised such that the downhill side is on the left going from start node to end node.

One contour is to be shown at each contour interval height.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Contours of different height must not touch each other. No contour can cross itself or another contour.

No gaps should appear in contours.

Spot Elevations must not contradict contours.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Contours (feature class) cannot fall over Sea, Perennial lake, Flood Irrigation Storage and Town Rural Storage polygons.

Survey Marks (feature dataset) must not contradict contours.

Contours can exist in a Mine Area but should not exist within open cut pit associated with the mine area.

Map Rules

General - All Scales

Contours will be masked by Built Up Area.

For depression contours the ticks will be on the downhill side of the line.

Related Features

Hypsometric Area, Standard Contour, Interpolated Contour, Connector Discontinuity, Connector Standard, Auxilary Contour, Limit Of Data (Relief), Bench Mark, Cliff, Horizontal control point, Junction, Razorback, Sea wall , Shoreline, WaterbodyBoundaries (Feature Class)

Related Chapters

Section 1 chapter 3.7.5
Section 2 chapter 2.8
Section 3 chapters 5.7, 5.11.1, 6.2 and 6.6

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

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


[back to top]



Updated: 1/12/2007

Scales 1:250 000

Hypsometric Area

HypsometricAreas

Relief

Polygon

The area enclosed between adjacent contours, with the exception of auxiliary contours.

Minimum Size Criterion:


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

Data Attributes

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

Hypsometric Area

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

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

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

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

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

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

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

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

0

Geodatabase Rules

General - All Scales

Hypsometric Areas are retained for historical purposes only. No alterations or maintenance will be conducted on this feature class. The remaining rules for this feature type are retained purely for reference purposes.

The elevation of the hypsometric areas is defined as the minimum elevation of all the bounding contours (excluding auxiliary contours).

Areas enclosed by one depression contour will carry for elevation the value of the depression contour minus the contour interval.

Where hypsometric areas meet the edge of the working database the elevations must match those of any adjoining areas which have working data available.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Hypsometric Area are bounded by features in the Contours feature class.

Adjacent Hypsometric Areas must have their elevations differing by only one contour interval.

Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules


Related Features

Connector Discontinuity, Connector Standard, Depression Contour, Interpolated Contour, Standard Contour and Limit of Data

Related Chapters

Section 1 chapter 3.1
Section 3 chapter 5.18 and 6.2

Related Products


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


[back to top]



Updated: 1/12/2007

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

Interpolated Contour

Contours

Relief

Polyline

A line which represents an imaginary line on the ground joining points of equal elevation in relation to the Australian Height Datum.Interpolated contour to be utilised to join discontinued contours or to replace a contour absent in the source material for cartographic reasons. This feature type is not to be utilised where contours have been broken for features from the discontinuity feature class.

Minimum Size Criterion:


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

Data Attributes

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

Interpolated Contour

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.

InterpolatedContour

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

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

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

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

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

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

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

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

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

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

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

56 - Standard
55 - Index standard
58 - Standard depression
57 - Index depression
0 - see geodatabase rules

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

Geodatabase Rules

1:25 000

The Standard contour interval is 10m.

Contours will carry the Symbol code for Index contours at every 50m taken from elevation 0.

1:100 000

The Standard contour interval is 20m.

Contours will carry the Symbol code for Index contours at every 100m taken from elevation 0.

1:250 000

The Standard contour interval is 50m at 1:250 000.

Contours will carry the Symbol code for Index contours at every 250m from elevation 0.

General - All Scales

Interpolated Contours will be shown on the map where the contours were previously deleted from symbols such as highway shields and the new symbols are smaller on the revised map or shown in a different location. In some instances contours were unnecessarily deleted well before cliff symbols or broken for sand ridges. These contours should also be interpolated and shown on the map, provided they do not run into each other.

Where contours in steep terrain were deleted from previous maps to avoid them running into each other, they must be interpolated to close the Hypsometric polygons but they should not print ie they will be given symbol 0.

One contour is to be shown at each contour interval height.

Interpolated contours will be given a symbol of 0 when the 0 elevation contour is cloned from Waterlines, Junctions and other features forming the coastline.

Interpolated contours;
These may or may not be printed on the map, according to requirements (e.g. clarity and benefit to map face). Use 0 for non printing lines, and the appropriate class symbol no. above for printable lines.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Contours of different height must not touch each other. No contour can cross itself or another contour.

No gaps should appear in contours.

Spot Elevations must not contradict contours.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Shoreline, Junctions & other features forming the coastline will be cloned as 0 (zero) elevation contours. The 0 contour will have a classification of Standard contour except where there are coastal cliffs in which case it will have a classification of connector discontinuity or where it is cloned from a junction in which case it will have a classification of connector standard.

Contours (feature class) cannot fall over Sea, Perennial lake, Flood Irrigation Storage and Town Rural Storage polygons.

Survey Marks (feature dataset) must not contradict contours.

Contours can exist in a Mine Area but should not exist within open cut pit associated with the mine area.

Map Rules

General - All Scales

Contours will be masked by Built Up Area.

For depression contours the ticks will be on the downhill side of the line.

Related Features

Hypsometric Area, Standard Contour, Depression Contour, Connector Discontinuity, Connector Standard, Auxilary Contour, Limit Of Data (Relief), Bench Mark, Cliff, Horizontal control point, Junction, Razorback, Sea wall , Shoreline, WaterbodyBoundaries (Feature Class)

Related Chapters

Section 1 chapter 3.7.5
Section 2 chapter 2.8
Section 3 chapters 5.11.1 and 6.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

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


[back to top]



Updated: 1/12/2007

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

Limit Of Data

Contours

Relief

Polyline

The line bounding the limits of known source material or the edge of the defined NTDB.

Minimum Size Criterion:


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

Data Attributes

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

Limit Of Data

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

6

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

LimitOfData

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

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

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

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

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

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

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

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

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

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

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

0

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

Geodatabase Rules


Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

The limit of Data feature will bound or complete all polygon features whose extent can not be fully determined by source material or where the associated polygon feature is adjacent to the edge of the database.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Where Limit Of Data represents the edge of the database these sections must be coincident with the Limit Of Data in the Framework Dataset, with the exception of their entry and exit locations.

Map Rules


Related Features

Hypsometric Area, Standard Contour, Interpolated Contour, Depression Contour, Connector Discontinuity, Connector Standard, Auxilary Contour, SeriesIndex (feature dataset), Limit Of Data (framework)

Related Chapters

Section 1 chapters 3.7
Section 3 chapters 5.11.2, 5.12 and 6.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

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


[back to top]



Updated: 1/12/2007

Scales 1:25 000 &
1:100 000

Relief Anno

ReliefAnno

Relief

Annotation

Type associated with the Relief Feature Dataset

Minimum Size Criterion:


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

Data Attributes

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

The following annotation classes exist in ReliefAnno;
Arial6ptItalicLeft
Arial6ptItalicRight
ArialNarrow5ptItalicLeft

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_ReliefFCs;
Contours
SpotElevations

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

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

Geodatabase Rules

General - All Scales

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

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

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

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

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

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

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules


Related Features


Related Chapters

Section 2 Chapters 5, 9, 10

Related Products

NTMS 100K

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


[back to top]



Updated: 1/12/2007

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

Spot Elevation

SpotElevations

Relief

Point

A point on the earth’s surface, of known elevation, above or below the Australian Height Datum (AHD66).

Minimum Size Criterion:


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

Data Attributes

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

Spot Elevation

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

Acceptable Domain Entries from dm_SpotElevationClass at 25K and 100K as well as acceptable entries for the 250K field;
Spot Elevation
Spot Elevation Inside Depression Contour
Spot Elevation On Sand Ridge
Spot Elevation Captured From Contour

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

SOURCE OF SPOT ELEVATION (SOURCETYPE) [String;Yes(No);24;0;0;Pop_Req] Code for the source of the Spot elevation;

Printed Map
Compilation material
Digital Topographic Data

ORIGIN (ORIGIN) [String;Yes;24;0;0;Pop_Req] Code for the source of the Spot elevation;

Acceptable Domain Entries from dm_SpotElevationOrigin;
Compilation Material
Digital Topographic Data
Printed Map

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

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

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

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

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

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

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

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

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

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

52
0 - see Section 3 chapter 6.6

FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep]

Currently not used by symbology; 0

ORIENTATION (ORIENTATION) [SmallInteger;Yes;0;3;0;Pop_Dep] Orientation in whole degrees from East going anti-clockwise;

Currently not used by symbology; 0

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

Geodatabase Rules

1:25 000

The classification "Spot elevation captured from contour" may be included in the data but should be symbolised to '0'.

1:100 000

The classification "Spot elevation captured from contour" may be included in the data but should be symbolised to '0'.

1:250 000

Permission is required from Geoscience Australia to use the classification of "Spot elevation captured from contour", see section 3 chapter 6.6.1 Spot Elevations.

General - All Scales

Spot elevations will be selected to best show terrain shape, change of slope and high and low points.
In any group of related features (ridges, peaks, saddles), the highest elevation shall be shown. See Section 3 chapter 6.6.1

The highest spot elevation on the map index shall be shown.
The highest spot elevation within the geodata index will be shown. See Section 3 chapter 6.6 for treatment of Spot elevations in close proximity to Mountains and Horizontal Control Points and chapter 6.6.1 for selection rules for Spot Elevations.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Contours (feature class) & Hypsometric Areas must fit logically with Spot elevations.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Spot elevations cannot overlap;
Lake, Flood Irrigation Storage, Town Rural Storage, Watercourse Area, Canal Area, Sea, Building Area.

Map Rules

General - All Scales

Spot elevations will be labelled with their elevation (See Section 2 chapter 5.12)

Related Features

Bench Mark, Horizontal control point, Vertical Obstruction, Mountain, Pinnacle , Reef, Shoal

Related Chapters

Section 1 chapter 3.7.5
Section 3 chapters 5.3, 5.11.1 and 6.6

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

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


[back to top]



Updated: 1/12/2007

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

Standard Contour

Contours

Relief

Polyline

A line which represents an imaginary line on the ground joining points of equal elevation in relation to the Australian Height Datum.

Minimum Size Criterion:


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

Data Attributes

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

Standard Contour

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

5

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

StandardContour

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

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

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

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

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

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

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

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

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

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

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

56 - Standard
55 - Index standard
0 - 0 elevation contour when cloned from Shoreline, Junctions and other features forming the coastline.

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

Geodatabase Rules

1:25 000

The Standard contour interval is 10m.

Contours will carry the Symbol code for Index contours at every 50m taken from elevation 0.

1:100 000

The Standard contour interval is 20m.

Contours will carry the Symbol code for Index contours at every 100m taken from elevation 0.

1:250 000

The Standard contour interval is 50m.

Contours will carry the Symbol code for Index contours at every 250m taken from elevation 0.

General - All Scales

One contour is to be shown at each contour interval height.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Contours of different height must not touch each other. No contour can cross itself or another contour.

No gaps should appear in contours.

Spot Elevations must not contradict contours.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Shoreline, Junctions & other features forming the coastline will be cloned as 0 (zero) elevation contours. The 0 contour will have a classification of Standard contour except where there are coastal cliffs in which case it will have a classification of connector discontinuity or where it is cloned from a junction in which case it will have a classification of connector standard.

Survey Marks (feature dataset) must not contradict contours.

Contours (feature class) cannot fall over Sea, Perennial lake, Flood Irrigation Storage and Town Rural Storage polygons.

Contours can exist in a Mine Area but should not exist within open cut pit associated with the mine area.

Map Rules

General - All Scales

Contours will be masked by Built Up Area.

Related Features

Hypsometric Area, Interpolated Contour, Depression Contour, Connector Discontinuity, Connector Standard, Auxilary Contour, Limit Of Data (Relief), Bench Mark, Cliff, Horizontal control point, Junction, Razorback, Sea wall , Shoreline, WaterbodyBoundaries (Feature Class)

Related Chapters

Section 1 chapter 3.7.5
Section 2 chapter 2.8
Section 3 chapters 5.11.1 and 6.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

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


[back to top]



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