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

Canal Line

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

The name of the Canal. 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 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.

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

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;

947

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

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

1:25 000

Features wider than 25m will be shown as Canal Area.

When a new undersized length of canal line exists between two water pipelines which meet their selection criterion, then the section of canal line should be represented as a pipeline feature, accepting the attributes of its adjoining pipelines.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Features wider than 100m will be shown as Canal Area.

When a new undersized length of canal line under 125m exists between two water pipelines which meet their selection criterion, then the section of canal line should be represented as a pipeline feature, accepting the attributes of its adjoining pipelines. However when a new undersized length of canal line between 125m and 500m exists between two water pipelines which meet their selection criterion, then the section of canal line should be captured as a canal line feature as an exception to the minimum size criteria rules.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

When a new undersized length of canal line exists between two water pipelines which meet their selection criterion, then the section of canal line should be represented as a pipeline feature, accepting the attributes of its adjoining pipelines

Features wider than 250m will be shown as Canal Area.

General - All Scales

The intention is to only capture canals that are significant irrigation canals
used for intensive farming/ agriculture that transports water in an active
manner (i.e. via pumping) for specific use and not isolated insignificant passive
canals or drains that simply redirect run-off.

Canals should only be captured when they exist within either a natural or man-made hydrological network. Both the entry and exit points of the canal must either:
-Join to a watercourse, pipeline or another canal; or
-Be derived from or flow into a hydrological feature such as a lake, pondage areas (eg. Salt evaporator, settling pond), Reservoir, swamp etc.

The exception to the above will be a canal used for irrigation which may be terminated by a control device such as a sprinkler or a flow control valve. Please note that the control device will not be represented in the data.


Features should not be captured where they are:
-Small linear features that carry water away from point features such as water tanks or a bore/windpump to an animal watering device;
-A natural watercourse which has had its banks re-contoured or normal path dredged to provide better water flow;
-Isolated drains associated with non-intensive land use;or
-Elongated man-made mounds of earth that generally follow the contour line to divert water and prevent erosion.

If not included in the name canals will have a TextNote eg 'canal', 'drain'.

General - All Scales

Canal Lines cannot overlap;
Any feature in any feature class within the drainage feature dataset.

General - All Scales

Canal lines will be masked for roads. The break will be the same as the width of the road it crosses.

If not included in the name canal lines will have a descriptive note eg 'canal', 'drain'.

Connector, Junction, Salt evaporator, Salt evaporator internal line, Limit of Data, Watercourse, Watercourse Area , Shoreline, WaterbodyBoundaries (Feature Class)

Section 2 chapter 2.2.3
Section 3 Chapter 5.3
Appendix U chapter 2.2.2, 2.3.2, 2.5.3

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

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

Connector

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.

Connector

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

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

PERENNIALITY (PERENNIALITY) [String;Yes(No);14;0;0;Pop_Req] Code for perenniality;

Acceptable Domain Entries from dm_Perenniality at 25K and 100K as well as acceptable entries for the 250K field;
Not Applicable
Perennial
Non Perennial - 25K and 100K only
Non-perennial - 250K only

HIERARCHY (HIERARCHY) [String;Yes(No);14;0;0;Pop_Req] Importance of associated watercourse;

Acceptable Domain Entries from dm_Hierarchy at 25K and 100K as well as acceptable entries for the 250K field;
Not Applicable
Major
Minor

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

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

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;

0

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

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

General - All Scales

Where a connector joins two canals, or joins a canal to another connector it will have a perenniality of 'Not Applicable' and a hierarchy of 'Not Applicable'. A connector joining a canal to a stream will take the perenniality of the stream. See Section 1 3.11.3

General - All Scales

No connectors will be added unless there is a logical basis for, or clear evidence to, confirm that a flow of water links, either:
-disconnected linear features in the drainage feature dataset, through a waterbody or mangrove feature, or
- provides connectivity of a linear feature in the drainage feature dataset through a waterbody feature or mangrove feature to the sea.

Connectors will carry the attributes of the watercourse they represent ie. the classification and perenniality shown in the supplied Water Guide in Appendix D (see Section 1, chapter 3.8.3).

Connectors will be used to extend the stream network to the coastline where applicable.

Connectors will not be shown around both sides of an island. That is, only one main connector will appear, with associated tributary connectors coming in from one or both sides.

1:25 000

Connectors must fall wholly within waterbodies or mangrove except where there is evidence that a loss in hydrological connectivity would occur eg. A connector may be used to duplicate a water pipeline to provide hydrological connectivity. Such a connector may also be used in areas where a watercourse feature flows underground and re-emerges.

The number of vertices used to define connectors should be sufficient only to keep it well within the waterbody area.

Connectors may be used through all waterbodies except Salt Evaporators, Aquaculture Areas and Settling ponds.

A connector may cross a mangrove (without an associated waterbody) when a watercourse enters a mangrove but there is no defined channel to the sea.

It is preferable that the ends of connectors are positioned perfectly over a node or vertice in the underlying waterbodies perimeter, and at worst should fall within 1 metre of the features perimeter line.

Connectors will pass through Reservoirs to connect to the Spillway linear feature.

1:100 000

Connectors must fall wholly within waterbodies or mangrove except where there is evidence that a loss in hydrological connectivity would occur eg. A connector may be used to duplicate a water pipeline to provide hydrological connectivity. Such a connector may also be used in areas where a watercourse feature flows underground and re-emerges.

The number of vertices used to define connectors should be sufficient only to keep it well within the waterbody area.

Connectors may be used through all waterbodies except Salt Evaporators, Aquaculture Areas and Settling ponds.

A connector may cross a mangrove (without an associated waterbody) when a watercourse enters a mangrove but there is no defined channel to the sea.

It is preferable that the ends of connectors are positioned perfectly over a node or vertice in the underlying waterbodies perimeter, and at worst should fall within 1 metre of the features perimeter line.

Connectors will pass through Reservoirs to connect to the Spillway linear feature.

1:250 000

Connectors must fall wholly within waterbodies or mangrove except where there is evidence that a loss in hydrological connectivity would occur eg. A connector may be used to duplicate a water pipeline to provide hydrological connectivity. Such a connector may also be used in areas where a watercourse feature flows underground and re-emerges.

The number of vertices used to define connectors should be sufficient only to keep it well within the waterbody area.

Connectors may be used through all waterbodies except Salt Evaporators, Aquaculture Areas and Settling ponds.

A connector may cross a mangrove (without an associated waterbody) when a watercourse enters a mangrove but there is no defined channel to the sea.

It is preferable that the ends of connectors are positioned perfectly over a node or vertice in the underlying waterbodies perimeter, and at worst should fall within 1 metre of the features perimeter line.

Connectors will pass through Reservoirs to connect to the Spillway linear feature.

General - All Scales

Connectors must fall wholly within waterbodies or mangrove except where there is evidence that a loss in hydrological connectivity would occur eg. A connector may be used to duplicate a water pipeline to provide hydrological connectivity. Such a connector may also be used in areas where a watercourse feature flows underground and re-emerges.

The number of vertices used to define connectors should be sufficient only to keep it well within the waterbody area.

Connectors may be used through all waterbodies except Salt Evaporators, Aquaculture Areas and Settling ponds.

A connector may cross a mangrove (without an associated waterbody) when a watercourse enters a mangrove but there is no defined channel to the sea.

It is preferable that the ends of connectors are positioned perfectly over a node or vertice in the underlying waterbodies perimeter, and at worst should fall within 1 metre of the features perimeter line.

Connectors will pass through Reservoirs to connect to the Spillway linear feature.

Canal Area, Canal Line, Junction, Lake, Land subject to inundation, Lock, Mangrove, Marine swamp, Rapid Area, Rapid Line, Reservoir, Spillway, Swamp, Watercourse, Watercourse Area and Waterhole

Section 3 chapters 5.3, 5.11.2, 5.11.3 and 6.9

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

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 DrainageAnno;
Arial18ptItalicLeft
Arial6ptItalicLeft
ArialNarrow10ptItalicLeft
ArialNarrow12ptItalicLeft
ArialNarrow14ptItalicLeft
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptItalicLeft
ArialNarrow8ptItalicLeft

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_DrainageFCs;
CanalLines
Locks
RapidLines
Spillways
WatercourseLines
WaterfallPoints

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.

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 Drainage feature dataset should exist within the DrainageAnno 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.

Section 2 chapters 5, 9, 10

NTMS 100K

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

Lock

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

The name of the lock. 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 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.

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;

754

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;

0 - 360

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

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

General - All Scales

The lock should appear central to the watercourse area passage width.

The symbol will be oriented so the point faces upstream.

Features should be labelled or named appropriately.

1:25 000

Locks must be coincident with a vertex on the connector or watercourse feature.

1:100 000

Locks must be coincident with a vertex on the connector or watercourse feature.

1:250 000

Locks must be coincident with a vertex on the connector feature.

1:25 000

At 1:25 000 Locks must be coincident with the middle vertex on a Lock Line.

1:100 000

At 1:100 000 Locks must be coincident with the middle vertex on a Lock Line.

General - All Scales

Locks must appear in a watercourse area.

General - All Scales

Locks are to have an accompanying descriptive note 'lock' unless the word 'lock' is included in the name.

Features should be labelled or named appropriately.

Locks will mask Lock Lines.

Connector, Watercourse, Watercourse Area , Lock Line

Section 3 chapters 5.9 and 5.11.2

GEODATA TOPO250K, NTMS 100K, NTMS 250K

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

Rapid Line

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

The name of the Rapid.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 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.

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;

881 - In a Major linear watercourse
882 - In a Minor linear watercourse

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

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

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

1:25 000

Size and any other selection criteria apply to all feature occurrences.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

1:250 000

At 1:250 000 size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist or they are on a non-perennial stream.

General - All Scales

Rapids are only to be shown in perennial streams.

Rapids will be digitised with the start node at the upstream end.

Rapids in double line streams will be shown as Rapid Area features. Rapids on watercourse (lines) will be captured as rapid lines.

General - All Scales

Rapid line must be a clone of the equivalent section of the associated watercourse line. There must be a vertex in the watercourse feature at the exact location of the start and end points of the Rapid line.

1:250 000

Rapids cannot overlap;
Sea, or Building areas.

General - All Scales

Rapids cannot overlap;
Building areas (Ruin).

General - All Scales

Rapids will be labelled 'rapid' if rapid is not included in the name.

Connector, Rapid Area, Rapid Boundary Line, Limit of Data, Watercourse, Watercourse Area , Shoreline, WaterbodyBoundaries (Feature Class)

Section 3 chapter 5.7

GEODATA TOPO250K, NTMS 100K, NTMS 250K

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

Spillway

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

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;

926

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

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

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

1:25 000

Size and any other selection criteria apply to all feature occurrences.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

General - All Scales

A Spillway feature will represent the spillway chute and any associated stilling basins. Where water overtops the dam wall a spillway will not be shown e.g. Hume Dam or Scrivener Dam. (see Dam)

General - All Scales

Spillways must be a clone of the equivalent section of the associated watercourse. There must be a vertex in the watercourse feature at the exact location of the start and end points of the Spillway.

Spillways start on the node of connectors across reservoirs and end on the node of a connector or watercourse below a dam wall.

General - All Scales

Spillways must be adjacent to a Reservoir (feature class).

Spillways can not overlap;
Built Up Area, Sea, Flood Irrigation Storage, Town Rural Storage, Lake, Canal Area or Watercourse Area.

Spillways start on the node of connectors across reservoirs (feature class) and end on the node of a connector or watercourse below a dam wall.

Connector, Dam Wall , Flood Irrigation Storage, Town Rural Storage

GEODATA TOPO250K, NTMS 100K, NTMS 250K

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

Watercourse

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.

Watercourse

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

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

PERENNIALITY (PERENNIALITY) [String;Yes(No);14;0;0;Pop_Req] Code for perenniality;

Acceptable Domain Entries from dm_Perenniality at 25K and 100K as well as acceptable entries for the 250K field;
Perennial
Non Perennial - 25K and 100K only
Non-perennial - 250K only

HIERARCHY (HIERARCHY) [String;Yes(No);14;0;0;Pop_Req] Importance of associated watercourse;

Acceptable Domain Entries from dm_Hierarchy at 25K and 100K as well as acceptable entries for the 250K field;
Major
Minor

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

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

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;

Lines (250K only) :
92 - Major
940 - Minor
95 - Warburton Groove only


Lines (25K & 100K only) :
91 - Major Non Perennial
92 - Major Perennial
940 - Minor Perennial
944 - Minor Non Perennial
95 - Warburton Groove only

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

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.

1:25 000

Size and any other selection criteria apply to all feature occurrences.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

1:250 000

Size and any other selection criteria apply to all feature occurrences.Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

General - All Scales

Watercourses shown as double line streams on the latest previous edition map or compilation material at the comparable scale will be shown as watercourse area polygons. Other watercourses will be shown as watercourse area polygons where they are wider than 1 mm at scale and meet the area criteria.

The perenniality and hierarchy of Watercourses will be classified according to Appendix D - Inland water features guide where the watercourse is shown on the guide. If there is strong evidence on imagery that the main alignment of the stream differs to the guide, then the image position should be given precedence, as long as it does not break the logical drainage attribute connectivity and does not deviate for a significant distance.

Perenniality of watercourses not on the guide will be non-perennial unless there is strong evidence to the contrary. Watercourse not shown on the guide will be classified as minor-non perennial except for tidal watercourses in mangrove. Once a watercourse enters or bounds a mangrove, that watercourse will become perennial and then remains perennial from that point to the shoreline.

A watercourse may be classified on the guide as perennial but shown as an area with one or more channels running down its length. The channels will be coded as perennial watercourse lines and the watercourse areas will be coded as non-perennial watercourse areas. In this situation a channel may at times be in close proximity to or coincident with the waterbody boundary that defines the edge of the watercourse area. Both the linear and area instances will be coded as major. See Geodatabase Rules for the handling of braided streams.

Braided streams fall into two categories; those that flow within clearly defined primary banks and those that don't. There is slightly different handling of each category. Section 3 chapter 6.9.4 shows the handling of braided streams lying in primary banks
For braided streams within clearly defined primary banks all channels will carry the name and perenniality of the Watercourse. All channels will have a planimetric accuracy of 9999. For Watercourses with hierarchy major the channel(s) identified in Appendix D will be coded as major. Remaining channels will have a hierarchy of minor. The area between the primary banks will be shown as a watercourse area.

For braided streams not in clearly defined banks, at least one channel will carry the name and perenniality of the watercourse. Other channels that form part of the watercourse should carry the name and perenniality. However, if it is unclear whether the channel is part of the named watercourse it should be left unnamed and follow the rules for watercourses not shown on Appendix D. For Watercourses with hierarchy major a contiguous channel will be coded as major. Where possible this channel will be an identifiable main channel. Where there is no identifiable main channel a channel will be selected which follows the general course of the stream and, where possible, links waterholes. Remaining channels will have a hierarchy of minor

There is no polygon infill associated with a braided watercourse. Braided streams with a hierarchy of major will have only the channel coded as major shown with symbol 92 (major watercourse).

The Warburton Groove is a natural phenomena unique to the landscape, it will be captured as a non perennial, minor watercourse with a symbol of 95.

General - All Scales

Watercourses will have nodes at all intersections.

1:250 000

Watercourses cannot overlap Lake perennial, Flood Irrigation Storage, Town Rural Storage, Watercourse Area Perennial and Canal Area.

1:250 000

The perenniality of single line watercourses will not be represented on the map.

General - All Scales

There is no polygon infill associated with a braided watercourse. Braided streams with a hierarchy of major will have only the channel coded as major shown with symbol 92 (major watercourse).

Canal Area, Canal Line, Connector,Flow Direction Arrow, Ford Line, Ford Point, Junction, Lake, Gorge, Lock, Mangrove, Prohibited Area Boundary Line, Rapid Area, Rapid Line, Rapid Boundary Line, Reserve Boundary Line, Flood Irrigation Storage, Town Rural Storage, Limit of Data, Waterfall Point, Waterhole , Shoreline, WaterbodyBoundaries (Feature Class)

Section 1 chapters 3.8.1
Section 2 chapters 2.2.3, 5.3 and 5.16
Section 3 chapters 5.3, 5.7, 5.11.2, 5.18, 6.9 and 6.10

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

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

Waterfall Point

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

The name of the Waterfall. 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 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.

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

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;

89 - printing
0 - where coincident with a cliff symbol

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

Width of symbol in millimetres; minimum feature width is 1.

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

0 - 360

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

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

1:25 000

Size and any other selection criteria apply to all feature occurrences.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

General - All Scales

Whether or not they are symbolised Waterfalls are to have an accompanying textnote 'falls' or 'numerous falls' unless the word 'falls' or 'waterfall' is included in the name.

General - All Scales

Waterfalls must be coincident with a vertex on a watercourse chain or fall within a watercourse area.

General - All Scales

Waterfalls will be symbolised except where the waterfall is associated with a symbolised cliff, in which case the Waterfall symbol will not be shown (e.g. symbol 0).

Waterfalls must be coincident with a vertex on a watercourse chain or fall within a watercourse area.

Where waterfalls are known to exist on the perimeter of one of the following features they must be made coincident with a vertex on the respective polygon edge of a;
Lake, Town Rural Storage, Watercourse Area.

Waterfalls cannot overlap;
Sea, Lakes, Canal areas or Reservoirs.

General - All Scales

Whether or not they are symbolised Waterfalls are to have an accompanying descriptive note 'falls' or 'numerous falls' unless the word 'falls' or 'waterfall' is included in the name.

Cliff , Watercourse, Watercourse Area

Section 3 chapters 5.3, 5.9, 5.11.2

GEODATA TOPO250K, NTMS 100K, NTMS 250K