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

Aquaculture Area

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

1

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

AquacultureArea

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

23

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

Individual adjacent ponds separated only by either artificial barriers or access paths will be captured as one polygon. The separations caused by artificial barrirers or access paths will be represented by Settling pond internal lines.

Aquaculture Areas are to have an accompanying TextNote eg 'fish hatchery', 'fish pen', 'aquaculture area' unless the words 'fish hatchery', 'fish pen' or 'aquaculture area' are included in the name.

General - All Scales

Aquaculture Area will be bounded by entities in the WaterbodyBoundaries feature class.

Aquaculture Area cannot overlap;
Other polygon features in the Waterbodies Dataset.

General - All Scales

Aquaculture Area cannot overlap;
Aviation (feature dataset), Sea, NativeVegetationAreas (feature class), CultivatedAreas (feature class).

General - All Scales

Aquaculture Areas are to have an accompanying descriptive note eg 'fish hatchery', 'fish pen', 'aquaculture area' unless the words 'fish hatchery', 'fish pen' or 'aquaculture area' are included in the name.

AircraftFacilityArea (Feature Class), Airport Area, Sea, Forest Or Shrub, Rainforest, Plantation, Orchard, Mangrove, Settling pond internal line, Limit of Data , Shoreline, WaterbodyBoundaries (Feature Class)

Section 3 chapters 5.3, 5.17, 5.18 and 6.9
Appendix U chapter 2.3.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.

Bore

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

The name of the Bore. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

11
0 - non printing, see Inter Feature Relationship Rules External.

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

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

1:25 000

All bores in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured, no filtering should occur. Bores inside densely settled regions will be captured upon direction from Geoscience Australia.

Only bores in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Bores within Built Up Areas will not be classified with an upperscale equal to, or greater than, '100000'. 'Greater than' refers to smaller scales such as '250000','1000000'.

1:100 000

Bores existing in approved Geoscience Australia base material will be included unfiltered regardless of location within Australia (e.g. data derived through the 1:25 000 data capture program).

New features should only be captured in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', size and any other selection criteria apply to all feature occurrences.

Only Bores in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Bores within Built Up Areas will not be classified with an upperscale equal to, or greater than, '100000'. 'Greater than' refers to smaller scales such as '250000','1000000'.

1:250 000

This feature will not be shown in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' regardless of whether it was shown on/in the base material/digital data. Refer to Appendix C for more information on when to capture this feature.

At 1:250 000 in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', 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

Bores must not overlap;
Aquaculture Area, Canal Area, Lake (Perennial), Salt Evaporator, Settling Pond, Town Rural Storage, Watercourse Area (Perennial)

General - All Scales

Where a bore and a windpump are situated together, both will be included in the data but only the windpump will be symbolised as it usually has the greater landmark value. Bore should be symbolised to 0 (non – printing on the map face).

Where a bore and a water tank are situated together, both will be included in the data but only the water tank will be symbolised as it usually has the greater landmark value. Bore should be symbolised to 0 (non – printing on the map face).

Bores plotted within 2.5 mm at map scale of a populated place will not be shown (symbolised to 0 non-printing).

General - All Scales

Names of these features will be shown.

When due to the density of general map detail, the symbols are omitted, a suitable note will be added, eg, 'numerous bores'.

Bores will mask all other detail except dry docks, kilometric distance indicators, route markers and annotation.

Spring, Water tank , Windpump, Dam

Section 3 Chapter 5.3
Appendix C

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.

Canal Area

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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

10

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 less than 25m wide will be shown as Canal Line.

1:100 000

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

Features less than 100m wide will be shown as Canal less.

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.

Features less than 250m wide will be shown as Canal Line.

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 Areas are bounded by entities in the WaterbodyBoundaries feature class.

Canal Areas cannot overlap;
Any feature in any feature class (except WaterbodyBoundaries) within the waterbodies feature dataset.

1:25 000

Connectors will be placed through Canal Areas to complete stream networking.

1:100 000

Connectors will be placed through Canal Areas to complete stream networking.

1:250 000

Canal Areas cannot overlap;
NativeVegetationAreas (feature class), CultivatedAreas (feature class).

Connectors will be placed through Canal Areas to complete stream networking.

With respect to contours, only standard connectors can cross Canal Areas.

The following cannot overlap or fall within polygon canals;
Homesteads,Windbreaks.

General - All Scales

Canal Areas cannot overlap;
Built Up Area.

The following cannot overlap or fall within polygon canals;
Building Point, Building Area, Spot elevations, Locations (feature class), Populated Place, Cemetery Point, Discontinuities (feature class), Cave, Pinnacle, Horizontal Control Points, Bench Marks, AircraftFacilityPoints (feature class), AircraftFacilityAreas (feature class), Airport Area and Sea.

General - All Scales

Canals 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 canals will have a descriptive note eg 'canal', 'drain'.

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

Section 2 chapter 2.2.3
Section 3 chapter 5.3, 5.17, 5.18 and 6.9
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.

Canal Boundary Line

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.

CanalBdyLine

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

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

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

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

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

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

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

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

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

94

General - All Scales

WaterbodyBoundaries (Feature Class) will bound all polygons within the Waterbodies Dataset, see Section 3 Chapter 5.17 for details on Feature Type hierarchy and when using Canal Boundary Line is applicable.

AdministrationBoundaries (feature class),Canal Area, Canal Line, Cliff, Contours (feature class), Flats (feature class), Island, Lake, Mainland, PondageAreas (feature class), Rapid Area, Rapid Line, Reservoir, Sea, Shoreline and Watercourse, Watercourse Area, WaterbodyBoundaries (feature class)

Section 2 chapter 2.2.3
Section 3 chapters 5.11, 5.15, 5.17 and 6.9

NTMS 250K

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

Flat Boundary Line

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.

FlatBdyLine

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

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

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

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

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

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

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

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

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

0

General - All Scales

WaterbodyBoundaries (Feature Class) will bound all polygons within the Waterbodies Dataset, see Section 3 Chapter 5.17 for details on Feature Type hierarchy and when using Flat Boundary Line is applicable.

General - All Scales

WaterbodyBoundaries bounding Saline Coastal Flats will be coincident with the Shoreline in the framework layer where the Saline Costal Flat abuts the Sea.

AdministrationBoundaries (feature class), Canal Area, Canal Line, Cliff, Contours (feature class), Flats (feature class), Island, Lake, Mainland, PondageAreas (feature class), Rapid Area, Rapid Line, Reservoir, Sea, Shoreline and Watercourse, Watercourse Area, WaterbodyBoundaries (feature class)

Section 2 chapter 2.2.3
Section 3 chapters 5.11, 5.15, 5.17 and 6.9

NTMS 250K

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

Flood Irrigation Storage

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.

FloodIrrigationStorage

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

The name of the Reservoir. ie the name of the water body not the dam wall. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

12

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.

New Flood Irrigation Storage reservoirs smaller than 22500 sq. m will not be captured as a Water tank or Dam feature.

1:100 000

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

New Flood Irrigation Storage reservoirs smaller than 22500 sq. m will not be captured as a Water tank or Dam feature.

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.

New Flood Irrigation Storage reservoirs smaller than 140625 sq. m will not be captured as a Water tank feature.

General - All Scales

In densely and moderately settled regions as defined by Appendix C where a Dam wall meets the minimum size criteria, the attached reservoir should be shown regardless of whether or not it is below the minimum size criteria for reservoirs. If a reservoir no longer exists (ie. Filled with sediment) then the dam wall will not be shown.

Flood Irrigation Storage typically occurs in low lying areas abutting large fields of intensive agricultural production of cotton and rice. Large Flood Irrigation Storage Reservoirs can generally be identified by related infrastructure, such as Cotton Gin facilities that require Flood Irrigation practices. Town Rural Storage Reservoirs may be differentiated from Flood Irrigation Storage by their proximity to populated places and it's surrounding landscape use.

Reservoirs of FloodIrrigationStorage classification are to have an accompanying textnote e.g.: flood irrigation farming.

1:250 000

Reservoirs (feature class) will be bounded by entities in the WaterbodyBoundaries (feature class).

General - All Scales

Reservoirs (feature class) cannot overlap ;
Waterpoints, other waterbody coverage polygons.

1:25 000

Reservoirs (feature class) cannot overlap ;
Mine Area, Road and Railway (except where they co-exist with bridges, tunnels or fords), SurveyMarks (feature dataset), Built Up Area, Streams of any sort (except connectors), Spot Elevations, Sea, Building Point, Building Area, Discontinuities (feature class), Cave, Pinnacle, MarineHazardPoints ( feature class), Lighthouse, AircraftFacilityPoints, AircraftFacilityArea, Airport Area and Cleared Lines.

1:100 000

Reservoirs (feature class) cannot overlap ;
Mine Area, Road and Railway (except where they co-exist with bridges, tunnels or fords), SurveyMarks (feature dataset), Built Up Area, Streams of any sort (except connectors), Spot Elevations, Sea, Building Point, Building Area, Discontinuities (feature class), Cave, Pinnacle, MarineHazardPoints ( feature class), Lighthouse, AircraftFacilityPoints, AircraftFacilityArea, Airport Area and Cleared Lines.

1:250 000

Reservoirs (feature class) cannot overlap ;
Mine Area, DeformationAreas (feature class), Sands (feature class), Sand Ridges, Road and Railway (except where they co-exist with bridges, tunnels or fords), SurveyMarks (feature dataset), Built Up Area, Streams of any sort (except connectors), Spot Elevations, Sea, Building Point, Building Area, NativeVegetationAreas (feature class), CultivatedAreas (feature class), Discontinuities (feature class), Cave, Pinnacle, MarineHazardPoints ( feature class), Lighthouse, AircraftFacilityPoints, AircraftFacilityArea, Airport Area and Cleared Lines.

General - All Scales

Dam Walls should be coincident with the high water mark of the reservoir
for the portion of the water boundary for which the dam wall creates a barrier. The dam wall may extend beyond the boundary of reservoir where imagery confirms this is the case.

Flood Irrigation Storage cannot overlap;
Water Tank, Dam

General - All Scales

Reservoirs will be named where named in the base material/digital data or reference material supplied.

Reservoirs of the FloodIrrigationStorage classification are to have an accompanying descriptive note e.g.: flood irrigation farming.

Reservoirs will mask Recreation Areas (feature class).

Connector, Dam Wall, Junction, Lake, Spillway, Limit of Data, Water tank, Watercourse, Watercourse Area , Shoreline, WaterbodyBoundaries (Feature Class), TownRuralStorage

Section 3 chapter 5.3, 5.17, 5.18, 6.9
Appendix U 2.3.3, 2.3.4

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.

Gnamma Hole

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.

GnammaHole

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

The name of the Gnamma Hole. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

82

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

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

1:25 000

All Gnamma Holes in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured, no filtering should occur. Gnamma Holes inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Gnamma Holes in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

This feature will be shown when it is less than 2500 sq m. Features larger than these dimensions will be shown as lakes.

1:100 000

All Gnamma Holes in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured; no filtering should occur. Gnamma Holes inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Gnamma Holes in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

All Gnamma Holes will be represented in the TOPO100K NTDB either as a Gnamma Hole or as a Lake. All features less than 2500 sq m will be shown as a Gnamma Hole. New features less than 10 000 sq m will be shown as a Gnamma Hole. New features greater than 10 000 sq m will be shown as a Lake. For existing features between 2500 sq m and 10 000 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Gnamma Hole or Lake).

1:250 000

In sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', 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.

This feature will not be captured/retained in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' regardless of whether it was shown on/in the base material/digital data. Refer to Appendix C for more information on when to capture this feature.

This feature will be shown when it does not exceed 62500 sq m. Features larger than these dimensions will be shown as lakes. (see Lakes and Waterholes)

General - All Scales

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Waterpoints are to have an accompanying textnote eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

General - All Scales

WaterPoints feature class cannot overlap;
Watercourse Area, Lake, Canal Areas, Flood Irrigation Storage, Town Rural Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or Building Area.

General - All Scales

Waterpoints are to have an accompanying descriptive note eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

Lake, Spring, Water Tank , Waterhole, Rock Hole, Pool, Native Well, Soak

Section 3 Chapter 5.3
Appendix C

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.

Junction

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.

Junction

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.

Junction

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

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

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

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

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

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

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

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

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

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

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

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

0

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

Junctions may also form a section of the boundary of Lake, Land Subject To inundation, Swamp, Marine Swamp, Flood Irrigation Storage, Town Rural Storage, Settling Pond, Aquaculture Area, Canal Area and Watercourse Area.

Junctions in the waterbodies feature dataset are generally 2 point lines except where the junctions are used to separate sea from inland waterbodies or more vertices are needed to close the polygon and maintain the correct polygon closing line shape. See Section 3 Chapter 6.9.

Junctions must be bordered by waterbodies in the Waterbodies coverage or by the sea on one side in the Framework coverage.

Junctions are only used to separate water polygons where there is no physical feature already doing so. They are most commonly used to separate water polygon features with different names.

General - All Scales

The WaterbodyBoundaries feature junction must be coincident with the FrameworkBoundaries feature junction if situated on shoreline.

AdministrationBoundaries (feature class), Canal Area, Canal Line, Cliff, Contours (feature class), Flats (feature class), Island, Lake, Mainland, PondageAreas (feature class), Rapid Area, Rapid Line, Flood Irrigation Storage, Town Rural Storage, Sea, Shoreline and Watercourse, Watercourse Area, WaterbodyBoundaries (feature class)

Section 3 chapters 5.11, 5.15, 5.17 and 6.9

NTMS 250K

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

Lake

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

10 - Perennial
11 - Non-perennial

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.

New features smaller than the minimum area and on a watercourse will be shown by the feature 'waterhole'.

New features smaller than the minimum area and not on a watercourse will be shown by the feature class 'Waterpoint'. This includes small lakes within the boundaries of a braided stream which are not on a watercourse.

The perenniality classification of lakes, existing in the base material, will be maintained. The perenniality of new lakes will be as per TOPO250K NTDB when provided as reference material or as a default of 'non perennial' when no reference material is supplied. The only exception to these two rules is where:
-The lake is shown as perennial on Appendix D. This indicates the lake is under tidal influence and therefore should be classified as perennial.
-A perennial lake which upon the review of two sets of imagery (which differ in age by at least a year) is dry on both as the result of drought conditions. If the lake is dry on both sets of imagery the classification will be downgraded to non perennial. However, where there is still evidence of the existence of at least a small portion of water in the basin of a feature on either image, the lake will be retained as perennial. The imagery does not need to be of the same resolution or sensor but the band combinations used should be the best for highlighting the presence of water.

In all cases, the high water mark will be retained as the delineation of the lake extent and should not be modified based on the reduced water capacity resulting from drought conditions.

1:100 000

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

All naturally occuring bodies of water will be represented in the TOPO100K NTDB either as a Waterhole, WaterPoints (feature class) or as a Lake. A feature will be represented as a 'waterhole' when it is a perennial entity situated on a non perennial watercourse or lake and is either a new feature smaller than the minimum size for data capture or an existing feature under the minimum size for inclusion. A feature will be represented by the feature class 'Waterpoint' when not situated on a watercourse and is either a new feature smaller than the minimum size for data capture or an existing feature smaller than the minimum size for inclusion. This includes small lakes within the boundaries of a braided stream which are not on a watercourse.
For existing features between 2500 sq m and 10 000 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Waterhole, Water Point (feature class) or Lake).

The perenniality classification of lakes, existing in the base material, will be maintained. The perenniality of new lakes will be as per TOPO250K NTDB when provided as reference material or as a default of 'non perennial' when no reference material is supplied. The only exception to these two rules is where:
-The lake is shown as perennial on Appendix D. This indicates the lake is under tidal influence and therefore should be classified as perennial.
-A perennial lake which upon the review of two sets of imagery (which differ in age by at least a year) is dry on both as the result of drought conditions. If the lake is dry on both sets of imagery the classification will be downgraded to non perennial. However, where there is still evidence of the existence of at least a small portion of water in the basin of a feature on either image, the lake will be retained as perennial. The imagery does not need to be of the same resolution or sensor but the band combinations used should be the best for highlighting the presence of water.

In all cases, the high water mark will be retained as the delineation of the lake extent and should not be modified based on the reduced water capacity resulting from drought conditions.

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.

New features smaller than the minimum area and on a watercourse will be shown by the feature 'waterhole'.

New features smaller than the minimum area and not on a watercourse will be shown by the feature class 'Waterpoint'. This includes small lakes within the boundaries of a braided stream which are not on a watercourse.

The perenniality classification of lakes, existing in the base material, will be maintained. The perenniality of new lakes will default to 'non perennial' when no reference material is supplied. The only exception to these two rules is where:
-The lake is shown as perennial on Appendix D. This indicates the lake is under tidal influence and therefore should be classified as perennial.
-A perennial lake which upon the review of two sets of imagery (which differ in age by at least a year) is dry on both as the result of drought conditions. If the lake is dry on both sets of imagery the classification will be downgraded to non perennial. However, where there is still evidence of the existence of at least a small portion of water in the basin of a feature on either image, the lake will be retained as perennial. The imagery does not need to be of the same resolution or sensor but the band combinations used should be the best for highlighting the presence of water.

In all cases, the high water mark will be retained as the delineation of the lake extent and should not be modified based on the reduced water capacity resulting from drought conditions.

General - All Scales

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Where a Open Cut Mine Area is no longer associated with any mining activity and has since filled with water to the extent that it is now a permanent 'lake type feature', then it should be captured as a Lake. This is in spite of the feature type definition saying it must be naturally occuring as it is now a key hydrological entity not held behind a dam structure. Minimum size criteria methodology is to be applied in the same manner as if it was a naturally occuring feature.

In areas containing numerous small lakes, sufficient will be shown to indicate the extent of the area and a suitable descriptive note added eg 'numerous small lakes'.

Claypans and saltpans will be TextNoted eg 'claypan'. Lakes will be labelled 'salt' where known to be saline.

General - All Scales

Lakes will be bounded by entities in the WaterbodyBoundaries feature class.

Lakes cannot overlap;
Other polygon features within the Waterbodies Dataset.

Lake Perennial cannot overlap;
Bores, Waterholes, Water Point (Feature Class)

A Lake edge must be coincident with the edge of other polygon features in the Waterbodies feature dataset where it abuts (where water flows between) them in reality. E.g. Water may flow directly from a Lake into a Watercourse Area.

1:25 000

Lakes cannot overlap;
Sea, Built Up Area, Mine Area.

Lakes (Non Perennial) cannnot overlap;
DeformationAreas (feature class), Sands (feature class), Crater, CultivatedAreas (feature class), Rainforest, Mangrove.

1:100 000

Lakes cannot overlap;
Sea, Built Up Area, Mine Area.

Lakes (Non Perennial) cannnot overlap;
DeformationAreas (feature class), Sands (feature class), Crater, CultivatedAreas (feature class), Rainforest, Mangrove.

1:250 000

Lakes cannot overlap;
Sea, Built Up Area, Mine Area, DeformationAreas (feature class), Sands (feature class), Crater, CultivatedAreas (feature class), Rainforest, Mangrove.

Perennial Lakes cannot overlap;
Forest Or Shrub.

General - All Scales

In areas containing numerous small lakes, sufficient will be shown to indicate the extent of the area and a suitable descriptive note added eg 'numerous small lakes'.

Claypans and saltpans will be labelled eg 'claypan'. Lakes will be labelled 'salt' where known to be saline.

Lakes will mask Recreation Areas (feature class).

Connector, Junction, Flood Irrigation Storage, Town Rural Storage, Limit of Data, Watercourse, Watercourse Area, Waterhole, Shoreline, WaterbodyBoundaries (Feature Class) , Gnamma Hole, Native Well, Pool, Rockhole, Soak, Built Up Area, Dam

Section 2 chapters 2.2.3
Section 3 chapters 5.3, 6.9, 5.11.2, 5.17, 5.18

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.

Lake Boundary Line

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.

LakeBdyLine

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

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

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

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

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

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

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

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

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

94

General - All Scales

When bounding sea and estuarine areas, the line is indicative of the position of mean high water. The exception is in Mangroves, where the line is indicative of the position of the seaward side of the mangroves.

The shoreline of lakes will be the line washed by the water when the feature is filled.

The shoreline of reservoirs formed by water impounded by dams or weirs will be shown at the top water level.

This feature is also used to depict the banks of a double line watercourse.

1:250 000

WaterbodyBoundaries (Feature Class) will bound all polygons within the Waterbodies Dataset, see Section 3 Chapter 5.17 for details on Feature Type hierarchy and when using Lake Boundary Line is applicable.

General - All Scales

WaterbodyBoundaries bounding Saline Coastal Flats will be coincident with the Shoreline in the framework layer where the Saline Costal Flat abuts the Sea.

AdministrationBoundaries (feature class), Built Up Area, Canal Area, Canal Line, Cliff, Contours (feature class), Plantation, Orchard, RecreationAreas, Cemetery Area, Landmark Area, Rubbish Tip, Flats (feature class), Island, Lake, Mainland, ForestOrShrub, Rainforest, Mangrove, PondageAreas (feature class), Rapid Area, Rapid Line, Flood Irrigation Storage, Town Rural Storage, Sea, Shoreline and Watercourse, Watercourse Area, WaterbodyBoundaries (feature class)

Section 2 chapter 2.2.3
Section 3 chapters 5.11, 5.15, 5.17 and 6.9

NTMS 250K

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

Land Subject To Inundation

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.

LandSubjectToInundation

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

The name of the feature. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

14

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

Land subject to inundation polygons that form clusters may be combined to form one or more larger polygons if the individual polygons which consitute the cluster are smaller than the minimum size for inclusion, provided this does not misrepresent the true extent/significance of the feature.

General - All Scales

Land subject to inundation will be bounded by entities in the WaterbodyBoundaries feature class.

Land subject to inundation cannot overlap;
Other polygon features in the Waterbodies Dataset

A Land Subject to Inundation edge must be coincident with the edge of other polygon features in the Waterbodies feature dataset where it abuts (where water flows between) them in reality. E.g. Water may flow directly from a Land Subject to Inundation into an area of Swamp.

1:25 000

Land subject to inundation cannot overlap:
Mangrove.

1:100 000

Land subject to inundation cannot overlap:
Mangrove.

1:250 000

Land subject to inundation cannot overlap:
Mangrove, Sea, Built Up Area.

General - All Scales

Connectors may be shown through this feature.

Connector, Junction, Limit of Data , Shoreline, WaterbodyBoundaries (Feature Class)

Section 3 chapter 6.9, 5.17 and 5.18

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.

Limit Of Data

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

9

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

LimitOfData

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

9

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

LimitOfData

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

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

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

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

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

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

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

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

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

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

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

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

0

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

WaterbodyBoundaries (Feature Class) will bound all polygons within the Waterbodies Dataset, see Section 3 Chapter 5.17 for details on Feature Type hierarchy and when using Reservoir Boundary Line is applicable.

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.

Canal Area, Lake, Land subject to inundation, Marine swamp, Rapid Area, Flood Irrigation Storage, Town Rural Storage, Saline coastal flat, Salt evaporator, Sand Area, Sand Dune, Aquaculture Area, Settling Pond, Swamp, Watercourse Area, WaterbodyBoundaries (feature class), SeriesIndex (feature dataset), Limit Of Data (framework)

Section 1 chapters 3.4 and 3.7
Section 3 chapters 5.11, 5.12, 5.15, 5.17 and 6.1

NTMS 250K

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

Marine Swamp

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.

MarineSwamp

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

The name of the marine swamp. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

908

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

Marine Swamp polygons that form clusters may be combined to form one or more larger polygons if the individual polygons which consitute the cluster are smaller than the minimum size for inclusion, provided this does not misrepresent the true extent/significance of the feature.

Watercourses entering swampy areas will be shown only to the limits of eroded channels.

Marine Swamps having distinctive vegetation will be textnoted appropriately e.g. lignum, marsh, wetlands, cane grass unless a description is included in the name.

Marine Swamps will have a TextNote 'marine swamp'. Where clutter occurs this note will take precedence to the distinctive vegetation label, otherwise where applicable both shall be shown.

General - All Scales

Marine swamps will be bounded by entities in the WaterbodyBoundaries (feature class)

Marine Swamps cannot overlap;
Other polygon features in the Waterbodies Dataset.

A Marine Swamp edge must be coincident with the edge of other polygon features in the Waterbodies feature dataset where it abuts (where water flows between) them in reality. E.g. Water may flow directly from a marine swamp into an area of saline coastal flat.

1:250 000

Marine Swamps cannot overlap;
Sea, Mine Area.

General - All Scales

Marine Swamps cannot overlap;
Mangrove.

General - All Scales

Watercourses entering swampy areas will be shown only to the limits of eroded channels.

Marine Swamps having distinctive vegetation will be labelled appropriately e.g. lignum, marsh, wetlands, cane grass unless a description is included in the name.

Marine Swamps will have a descriptive note 'marine swamp'. Where clutter occurs this note will take precedence to the distinctive vegetation label, otherwise where applicable both shall be shown.

Connector, Swamp, Limit of Data , Shoreline, WaterbodyBoundaries (Feature Class)

Section 3 chapter 6.9, 5.17 and 5.18

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.

Native Well

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.

NativeWell

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

The name of the Native Well. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

82

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

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

1:25 000

All Native Wells in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured, no filtering should occur. Native Wells inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Native Wells in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

This feature will be shown when it is less than 2500 sq m. Features larger than these dimensions will be shown as lakes.

1:100 000

All Native Wells in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured; no filtering should occur. Native Wells inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Native Wells in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

All Native Wells will be represented in the TOPO100K NTDB either as a Native Well or as a Lake. All features less than 2500 sq m will be shown as a Native Well. New features less than 10 000 sq m will be shown as a Native Well. New features greater than 10 000 sq m will be shown as a Lake. For existing features between 2500 sq m and 10 000 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Native Well or Lake).

1:250 000

In sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', 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.

This feature will not be captured/retained in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' regardless of whether it was shown on/in the base material/digital data. Refer to Appendix C for more information on when to capture this feature.

This feature will be shown when it does not exceed 62500 sq m. Features larger than these dimensions will be shown as lakes. (see Lakes and Waterholes)

General - All Scales

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Waterpoints are to have an accompanying textnote eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

General - All Scales

WaterPoints feature class cannot overlap;
Watercourse Area, Lake, Canal Areas, Flood Irrigation Storage, Town Rural Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or Building Area.

General - All Scales

Waterpoints are to have an accompanying descriptive note eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

Lake, Spring, Water Tank , Waterhole, Rock Hole, Pool, Gnamma Hole, Soak

Section 3 Chapter 5.3
Appendix C

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.

Pondage Boundary Line

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.

PondageBdyLine

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

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

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

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

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

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

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

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

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

114

General - All Scales

WaterbodyBoundaries (Feature Class) will bound all polygons within the Waterbodies Dataset, see Section 3 Chapter 5.17 for details on Feature Type hierarchy and when using Pondage Boundary Line is applicable.

General - All Scales

The WaterbodyBoundaries feature junction must be coincident with the FrameworkBoundaries feature junction if situated on shoreline.

AdministrationBoundaries (feature class), Built Up Area, Canal Area, Canal Line, Cliff, Contours (feature class), Plantation, Orchard, RecreationAreas(feature class), Cemetery Area, Rubbish Tip, Flats (feature class), Island, Lake, Mainland, Rainforest, Forest Or Shrub, Mangrove, PondageAreas (feature class), Rapid Area, Rapid Line, Flood Irrigation Storage, Town Rural Storage, Sea, Shoreline and Watercourse, Watercourse Area, WaterbodyBoundaries (feature class)

Section 2 chapter 2.2.3
Section 3 chapters 5.11, 5.15, 5.17 and 6.9

NTMS 250K

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

Pool

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.

Pool

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

The name of the pool. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

82

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

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

1:25 000

All Pools in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured, no filtering should occur. Pools inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Pools in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

This feature will be shown when it is less than 2500 sq m. Features larger than these dimensions will be shown as lakes.

1:100 000

All Pools in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured; no filtering should occur. Pools inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Pools in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

All Pools will be represented in the TOPO100K NTDB either as a Pool or as a Lake. All features less than 2500 sq m will be shown as a Pool. New features less than 10 000 sq m will be shown as a Pool. New features greater than 10 000 sq m will be shown as a Lake. For existing features between 2500 sq m and 10 000 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Pool or Lake).

1:250 000

In sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', 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.

This feature will not be captured/retained in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' regardless of whether it was shown on/in the base material/digital data. Refer to Appendix C for more information on when to capture this feature.

This feature will be shown when it does not exceed 62500 sq m. Features larger than these dimensions will be shown as lakes. (see Lakes and Waterholes)

General - All Scales

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Waterpoints are to have an accompanying textnote eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

General - All Scales

WaterPoints feature class cannot overlap;
Watercourse Area, Lake, Canal Areas, Flood Irrigation Storage, Town Rural Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or Building Area.

General - All Scales

Waterpoints are to have an accompanying descriptive note eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

Lake, Spring, Water Tank , Waterhole, Rock Hole, Gnamma Hole, Native Well, Soak

Section 3 Chapter 5.3
Appendix C

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.

Rapid Area

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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

881

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 or they are on a non-perennial stream.

General - All Scales

Rapids are only to be shown in perennial streams.

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 Area will be bounded by entities in the WaterbodyBoundaries feature class.

Rapid Area must overlap;
Watercourse Area

Where the Rapid Area edge (feature type polygon) is associated with the river bank it must be coincident with the associated boundary of the watercourse area.

1:25 000

Rapids cannot overlap;
Building Area (Ruin).

1:100 000

Rapids cannot overlap;
Building Area (Ruin).

1:250 000

Rapids cannot overlap;
Sea or Building Area.

General - All Scales

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

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

Section 3 chapters 5.17, 5.18 and 6.9

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 Boundary Line

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.

RapidBdyLine

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

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

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

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

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

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

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

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

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

0

General - All Scales

See Rapid Area

General - All Scales

WaterbodyBoundaries (Feature Class) will bound all polygons within the Waterbodies Dataset, see Section 3 Chapter 5.17 for details on Feature Type hierarchy and when using Rapid Boundary Line is applicable.

Rapid Area, Rapid Line, WaterbodyBoundaries (feature class)

Section 3 chapters 5.11, 5.15, 5.17 and 6.9

NTMS 250K

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

Reservoir Boundary Line

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.

ReservoirBdyLine

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

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

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

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

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

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

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

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

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

94

General - All Scales

The shoreline of reservoirs formed by water impounded by dams or weirs will be shown at the top water level.

General - All Scales

WaterbodyBoundaries (Feature Class) will bound all polygons within the Waterbodies Dataset, see Section 3 Chapter 5.17 for details on Feature Type hierarchy and when using Reservoir Boundary Line is applicable.

General - All Scales

WaterbodyBoundaries bounding Saline Coastal Flats will be coincident with the Shoreline in the framework layer where the Saline Costal Flat abuts the Sea.

AdministrationBoundaries (feature class), Built Up Area, Canal Area, Canal Line, Cliff, Contours (feature class), Plantation, Orchard, RecreationAreas (Feature Class), Cemetery Area, Rubbish Tip, Flats (feature class), Island, Lake, Mainland, Rainforest, Forest Or Shrub, Mangrove, PondageAreas (feature class), Rapid Area, Rapid Line, Flood Irrigation Storage, Town Rural Storage, Sea, Shoreline and Watercourse, Watercourse Area, WaterbodyBoundaries (feature class)

Section 2 chapter 2.2.3
Section 3 chapters 5.11, 5.15, 5.17 and 6.9

NTMS 250K

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

Rockhole

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.

Rockhole

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

The name of the Rockhole. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

82

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

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

1:25 000

All Rockholes in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured, no filtering should occur. Rockholes inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Rockholes in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

This feature will be shown when it is less than 2500 sq m. Features larger than these dimensions will be shown as lakes.

1:100 000

All Rockholes in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured; no filtering should occur. Rockholes inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Rockholes in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

All Rockholes will be represented in the TOPO100K NTDB either as a Rockhole or as a Lake. All features less than 2500 sq m will be shown as a Rockhole. New features less than 10 000 sq m will be shown as a Rockhole. New features greater than 10 000 sq m will be shown as a Lake. For existing features between 2500 sq m and 10 000 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Rockhole or Lake).

1:250 000

In sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', 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.

This feature will not be captured/retained in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' regardless of whether it was shown on/in the base material/digital data. Refer to Appendix C for more information on when to capture this feature.

This feature will be shown when it does not exceed 62500 sq m. Features larger than these dimensions will be shown as lakes. (see Lakes and Waterholes)

General - All Scales

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Waterpoints are to have an accompanying textnote eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

General - All Scales

WaterPoints feature class cannot overlap;
Watercourse Area, Lake, Canal Areas, Flood Irrigation Storage, Town Rural Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or Building Area.

General - All Scales

Waterpoints are to have an accompanying descriptive note eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

Lake, Spring, Water Tank , Waterhole, Pool, Gnamma Hole, Native Well, Soak

Section 3 Chapter 5.3
Appendix C

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.

Saline Coastal Flat

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.

SalineCoastalFlat

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

This field is not applicable to this subtype and therefore is currently not to be populated;

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

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

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

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

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

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

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

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

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

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

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

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

23

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

Saline Coastal Flat polygons that form clusters may be combined to form one or more larger polygons if the individual polygons which consitute the cluster are smaller than the minimum size for inclusion, provided this does not misrepresent the true extent/significance of the feature.

A TextNote is only required when the previous edition map, reference material or a special instruction from Geoscience Australia indicates precise characteristics of the Saline Coastal flat e.g. mud.

General - All Scales

Saline coastal flats will be bounded by entities in the WaterbodyBoundaries feature class.

Saline coastal flat cannot overlap;
Other polygon features within the Waterbodies Dataset.

A Saline Coastal Flat edge must be coincident with the edge of other polygon features in the Waterbodies feature dataset where it abuts (where water flows between) them in reality. E.g. Water may flow directly from a Saline Coastal Flat into an area of Swamp.

1:250 000

Saline coastal flat cannot overlap;
Sea

General - All Scales

Saline coastal flat cannot overlap;
Mangrove

General - All Scales

A descriptive note is only required when the previous edition map, revision source material or a special instruction from Geoscience Australia indicates precise characteristics of the Saline Coastal flat e.g. mud.

Junction, Limit of Data , Shoreline, WaterbodyBoundaries (Feature Class)

Section 3 chapter 6.9, 5.17 and 5.18

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.

Salt Evaporator

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.

SaltEvaporator

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

23

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

Individual adjacent ponds separated only by either artificial barriers or access paths will be captured as one polygon. The separations caused by artificial barrirers or access paths will be represented by Salt Evaporator Internal Lines.

General - All Scales

Salt evaporators will be bounded by entities in the WaterbodyBoundaries feature class.

Salt evaporators cannot overlap;
Other polygon features within the Waterbodies Dataset.

General - All Scales

Salt Evaporators cannot overlap ;
Mine Area, DeformationAreas (feature class), Crater, Sands (feature class), Building Area, RecreationAreas (feature class), Cemetery Area, Built Up Area, AircraftFacilityArea (feature class), Airport Area, Sea, NativeVegetationAreas (feature class), CultivatedAreas (feature class).

General - All Scales

Salt evaporators will be labelled 'salt evaporator'.

Canal Area, Canal Line, Levee, Salt evaporator internal line, Limit of Data , Shoreline, WaterbodyBoundaries (Feature Class)

Section 3 chapters 5.3, 5.17, 5.18 and 6.9
Appendix U chapter 2.3.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.

Settling Pond

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.

SettlingPond

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

23

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

Individual adjacent ponds separated only by either artificial barriers or access paths will be captured as one polygon. The separations caused by artificial barrirers or access paths will be represented by Settling pond internal lines.

Settling ponds are to have an accompanying textnote eg 'settling ponds', 'tailings pond', 'sewage treatment plant' unless the words 'settling pond', 'tailings pond', 'sewage treatment plant' etc are included in the name.

1:250 000

Settling ponds will be bounded by entities in the WaterbodyBoundaries feature class.

General - All Scales

Settling Ponds cannot overlap;
Other polygon features within the Waterbodies Dataset.

General - All Scales

Settling ponds cannot overlap;
AircraftFacilityAreas (feature class), Airport Area, Sea, NativeVegetationAreas (feature class), CultivatedAreas (feature class),

General - All Scales

Settling ponds are to have an accompanying descriptive note eg 'settling ponds', 'tailings pond', 'sewage treatment plant' unless the words 'settling pond', 'tailings pond', 'sewage treatment plant' etc are included in the name.

Mine Point, Mine Area, Settling pond internal line, Limit of Data , Shoreline, WaterbodyBoundaries (Feature Class)

Section 3 chapters 5.3, 5.17, 5.18 and 6.9
Appendix U chapter 2.3.3, 2.4.4

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.

Soak

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.

Soak

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

The name of the Soak. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

82

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

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

1:25 000

All Soaks in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured, no filtering should occur. Soaks inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Soaks in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

This feature will be shown when it is less than 2500 sq m. Features larger than these dimensions will be shown as lakes.

1:100 000

All Soaks in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured; no filtering should occur. Soaks inside densely settled regions will be captured upon direction from Geoscience Australia.

Only Soaks in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

All Soaks will be represented in the TOPO100K NTDB either as a Soak or as a Lake. All features less than 2500 sq m will be shown as a Soak. New features less than 10 000 sq m will be shown as a Soak. New features greater than 10 000 sq m will be shown as a Lake. For existing features between 2500 sq m and 10 000 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Soak or Lake).

1:250 000

In sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', 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.

This feature will not be captured/retained in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' regardless of whether it was shown on/in the base material/digital data. Refer to Appendix C for more information on when to capture this feature

This feature will be shown when it does not exceed 62500 sq m. Features larger than these dimensions will be shown as lakes. (see Lakes and Waterholes)

General - All Scales

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Waterpoints are to have an accompanying textnote eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

General - All Scales

WaterPoints feature class cannot overlap;
Watercourse Area, Lake, Canal Areas, Flood Irrigation Storage, Town Rural Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or Building Area.

General - All Scales

Waterpoints are to have an accompanying descriptive note eg 'pool','soak', 'gnamma hole','native well','rock hole' unless the words 'pool','soak', 'gnamma hole','native well','rock hole' etc are included in the name.

Lake, Spring, Water Tank , Waterhole, Rock Hole, Pool, Gnamma Hole, Native Well

Section 3 Chapter 5.3
Appendix C

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.

Spring

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

The name of the Spring. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

73

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

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

1:25 000

All Springs in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured, no filtering should occur. Springs inside densely settled regions will be captured upon direction from Geoscience Australia.

1:100 000

All Springs in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured; no filtering should occur. Springs inside densely settled regions will be captured upon direction from Geoscience Australia.

1:250 000

In sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', 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.

This feature will not be captured/retained in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' regardless of whether it was shown on/in the base material/digital data. Refer to Appendix C for more information on when to capture this feature.

General - All Scales

Springs cannot overlap;
Lake perennial, Flood Irrigation Storage, Town Rural Storage, Watercourse Area, Canal Area.

1:250 000

Springs cannot overlap;
Sea.

Bore , Gnamma Hole, Native Well, Pool, Rockhole, Soak

Appendix C

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.

Swamp

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.

Swamp

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

The name of the Swamp. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

908

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

Swamp polygons that form clusters may be combined to form one or more larger polygons if the individual polygons which consitute the cluster are smaller than the minimum size for inclusion, provided this does not misrepresent the true extent/significance of the feature.

Swamps having distinctive vegetation will be textnoted appropriately e.g. lignum, marsh, wetlands, cane grass unless a description is included in the name

General - All Scales

Swamps will be bounded entities in the WaterbodyBoundaries feature class

Swamps cannot overlap;
Other polygon features in the Waterbodies Dataset.

A Swamp edge must be coincident with the edge of other polygon features in the Waterbodies feature dataset where it abuts (where water flows between) them in reality. E.g. Water may flow directly from a Swamp into an area of Saline Coastal Flat.

1:250 000

Swamps cannot overlap;
Sea

General - All Scales

No flow direction arrow will be added when a watercourse stops in a swamp. (see Watercourse)

Watercourses entering swampy areas will be shown only to the limits of the eroded channels.

Swamps cannot overlap;
Mangrove

General - All Scales

Swamps having distinctive vegetation will be labelled appropriately e.g. lignum, marsh, wetlands, cane grass unless a description is included in the name

Connector, Junction, Marine swamp, Limit of Data , Shoreline, WaterbodyBoundaries (Feature Class)

Section 3 chapter 5.3, 5.17, 5.18, 6.9

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.

Town Rural Storage

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.

TownRuralStorage

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

The name of the Reservoir. ie the name of the water body not the dam wall. 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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

10

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.

All TownRuralStorage reservoirs will be represented in the data as either a Town Rural Storage Reservoir or a Dam. TownRuralStorage reservoirs smaller than 6400 sq. m will be captured as a Dam feature.

1:100 000

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

In sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide, all TownRuralStorage reservoirs will be represented in the data as either a Town Rural Storage Reservoir or a Dam. New TownRuralStorage reservoirs smaller than 22500 sq. m will be captured as a Dam feature subject to Appendix C. For existing features between 6400 sq m and 22500 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Dam, TownRuralStorage).

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.

New TownRuralStorage reservoirs smaller than 140625 sq. m will be captured as a Water Tank feature.

General - All Scales

In densely and moderately settled regions as defined by Appendix C where a Dam wall meets the minimum size criteria, the attached reservoir should be shown regardless of whether or not it is below the minimum size criteria for reservoirs. If a reservoir no longer exists (ie. Filled with sediment) then the dam wall will not be shown.

Town Rural Storage Reservoirs may be differentiated from Flood Irrigation Storage by their proximity to populated places and it's surrounding landscape use.Flood Irrigation Storage typically occurs in low lying areas abutting large fields of intensive agricultural production of cotton and rice. Large Flood Irrigation Storage Reservoirs can generally be identified by related infrastructure, such as Cotton Gin facilities that require Flood Irrigation practices.

Reservoirs of the TownRuralStorage classification are to have an accompanying textnote e.g: 'aquarium' for features not being used directly for human or livestock consumption.

General - All Scales

Reservoirs (feature class) will be bounded by the WaterbodyBoundaries (feature class).

Reservoirs (feature class) cannot overlap ;
Waterpoints, other waterbody coverage polygons.

1:25 000

Reservoirs (feature class) cannot overlap ;
Mine Area, DeformationAreas (feature class), Sands (feature class), Sand Ridges, Road and Railway (except where they co-exist with bridges, tunnels or fords), SurveyMarks (feature dataset), Built Up Area, Streams of any sort (except connectors), Spot Elevations, Sea, Building Point, Building Area, NativeVegetationAreas (feature class), CultivatedAreas (feature class), Discontinuities (feature class), Cave, Pinnacle, MarineHazardPoints ( feature class), Lighthouse, AircraftFacilityPoints, AircraftFacilityArea, Airport Area and Cleared Lines, Dam, Water Tank.

1:100 000

Reservoirs (feature class) cannot overlap ;
Mine Area, DeformationAreas (feature class), Sands (feature class), Sand Ridges, Road and Railway (except where they co-exist with bridges, tunnels or fords), SurveyMarks (feature dataset), Built Up Area, Streams of any sort (except connectors), Spot Elevations, Sea, Building Point, Building Area, NativeVegetationAreas (feature class), CultivatedAreas (feature class), Discontinuities (feature class), Cave, Pinnacle, MarineHazardPoints ( feature class), Lighthouse, AircraftFacilityPoints, AircraftFacilityArea, Airport Area and Cleared Lines, Dam, Water Tank.

1:250 000

Reservoirs (feature class) cannot overlap ;
Mine Area, DeformationAreas (feature class), Sands (feature class), Sand Ridges, Road and Railway (except where they co-exist with bridges, tunnels or fords), SurveyMarks (feature dataset), Built Up Area, Streams of any sort (except connectors), Spot Elevations, Sea, Building Point, Building Area, NativeVegetationAreas (feature class), CultivatedAreas (feature class), Discontinuities (feature class), Cave, Pinnacle, MarineHazardPoints ( feature class), Lighthouse, AircraftFacilityPoints, AircraftFacilityArea, Airport Area and Cleared Lines, Water Tank.

General - All Scales

Dam Walls should be coincident with the high water mark of the reservoir
for the portion of the water boundary for which the dam wall creates a barrier. The dam wall may extend beyond the boundary of reservoir where imagery confirms this is the case.

Reservoirs (feature class) cannot overlap ;
Mine Area, DeformationAreas (feature class), Sands (feature class), Sand Ridges, Road and Railway (except where they co-exist with bridges, tunnels or fords), SurveyMarks (feature dataset), Built Up Area, Streams of any sort (except connectors), Spot Elevations, Sea, Building Point, Building Area, NativeVegetationAreas (feature class), CultivatedAreas (feature class), Discontinuities (feature class), Cave, Pinnacle, MarineHazardPoints ( feature class), Lighthouse, AircraftFacilityPoints, AircraftFacilityArea, Airport Area and Cleared Lines.

General - All Scales

Reservoirs will be named where named in the base material/digital data or revision source material supplied.

Reservoirs of the TownRuralStorage classification are to have an accompanying descriptive note e.g: 'aquarium' for features not being used directly for human or livestock consumption.

Reservoirs will mask Recreation Areas.

Connector, Dam Wall, Junction, Lake, Spillway, Limit of Data, Water tank, Watercourse, Watercourse Area , Shoreline, WaterbodyBoundaries (Feature Class), FloodIrrigationStorage

Section 3 chapter 5.3, 5.17, 5.18, 6.9
Appendix U 2.3.3, 2.3.4, 2.3.5

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 WaterbodiesAnno;
Arial18ptItalicCenter
Arial6ptItalicCenter
ArialNarrow10ptItalicCenter
ArialNarrow12ptItalicCenter
ArialNarrow14ptItalicCenter
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow7ptItalicCenter
ArialNarrow7ptItalicLeft
ArialNarrow7ptItalicRight
ArialNarrow8ptItalicCenter

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_WaterbodiesFCs;
Bores
CanalAreas
Flats
Lakes
PondageAreas
RapidAreas
Reservoirs
Springs
WaterbodyBoundaries
WatercourseAreas
Waterholes
WaterPoints

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 specifcation documentation for ease of reference.

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

Waterbody Boundary Line

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

10

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

WaterbodyBdyLine

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

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

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

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

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

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

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;

94 - See Geodatabase Rules
114 - See Geodatabase Rules
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.

General - All Scales

When bounding sea and estuarine areas, the line is indicative of the position of mean high water. The exception is in Mangroves, where the line is indicative of the position of the seaward side of the mangroves.

The shoreline of lakes will be the line washed by the water when the feature is filled.

The shoreline of reservoirs formed by water impounded by dams or weirs will be shown at the top water level.

This feature is also used to depict the banks of a double line watercourse.

General - All Scales

WaterbodyBoundaries (Feature Class) will bound all polygons within the Waterbodies Dataset, see Section 3 Chapter 5.17 for details on Feature Type hierarchy.

General - All Scales

WaterbodyBoundaries bounding waterbodies will be coincident with the Shoreline in the framework layer where the waterbody abuts the Sea.

AdministrationBoundaries (feature class),Canal Area, Canal Line, Cliff, Contours (feature class), Flats (feature class), Island, Lake, Mainland, PondageAreas (feature class), Rapid Area, Rapid Line, Reservoir, Sea, Shoreline and Watercourse, Watercourse Area, WaterbodyBoundaries (feature class)

Section 2 chapter 2.2.3
Section 3 chapters 5.11, 5.15, 5.17 and 6.9

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

Watercourse Area

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/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

10 - Perennial
11 - Non perennial
0 - Containing linear braided watercourses.

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

Watercourses shown as double line streams on the latest previous edition map or compilation material at the comparable scale will be shown as polygons. Other watercourses will be shown as 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 coastline.

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

The hierarchy of double line Watercourses will not be shown.

Braided streams with a hierarchy of major will have only the channel coded as major shown with symbol 92 (major watercourse).

General - All Scales

Watercourse Area will be bounded by entitites in the WaterbodyBoundaries feature class.

Watercourse Area cannot overlap;
Other polygon features within the Waterbodies Dataset.

1:25 000

Where a Dam Wall crosses a Watercourse Area, the upstream portion should be treated as a Reservoir feature. The reservoir will be from the dam wall upstream encompassing the static water extent of the waterbody at its full holding capacity.

1:100 000

Where a Dam Wall crosses a Watercourse Area, the upstream portion should be treated as a Reservoir feature. The reservoir will be from the dam wall upstream encompassing the static water extent of the waterbody at its full holding capacity.

1:250 000

Where a Dam Wall crosses a Watercourse Area, the upstream portion should be treated as a Reservoir feature. The reservoir will be from the dam wall upstream encompassing the static water extent of the waterbody at its full holding capacity.This means a Junction will be placed across the watercourse area polygon, coincident with the Dam Wall. Depending on the situation an additional junction further upstream may be needed to complete Reservoir feature.

Watercourse Area - perennial cannot overlap;
NativeVegetationAreas (feature class), CultivatedAreas (feature class).

General - All Scales

Watercourse Area - perennial cannot overlap;
Sea, Built Up Areas.

Non-perennial watercourse polygons cannot overlap Sea, Built-up area,CultivatedAreas (feature class), Mangrove.

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.17, 5.18 and 6.9

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.

Watercourse Boundary Line

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

8

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

WatercourseBdyLine

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

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

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

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

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

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

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

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

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

94

General - All Scales

When bounding estuarine areas, the line is indicative of the position of mean high water. The exception is in Mangroves, where the line is indicative of the position of the seaward side of the mangroves.

The shoreline of lakes will be the line washed by the water when the feature is filled.

The shoreline of reservoirs formed by water impounded by dams or weirs will be shown at the top water level.

General - All Scales

WaterbodyBoundaries (Feature Class) will bound all polygons within the Waterbodies Dataset, see Section 3 Chapter 5.17 for details on Feature Type hierarchy and when using Watercourse Boundary Line is applicable.

General - All Scales

WaterbodyBoundaries bounding Saline Coastal Flats will be coincident with the Shoreline in the framework layer where the Saline Costal Flat abuts the Sea.

AdministrationBoundaries (feature class), Built Up Area, Canal Area, Canal Line, Cliff, Contours (feature class), Orchard, Plantation, RecreationAreas (Feature Class), Cemetery Area, Rubbish Tip, Flats (feature class), Island, Lake, Mainland, Foreshore Flat, Reef, Shoal, Rainforest, Forest Or Shrub, Mangrove, PondageAreas (feature class), Rapid Area, Rapid Line, Reservoir, Sea, Shoreline and Watercourse, Watercourse Area, WaterbodyBoundaries (feature class)

Section 2 chapter 2.2.3
Section 3 chapters 5.11, 5.15, 5.17 and 6.9

NTMS 250K

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

Waterhole

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

81

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

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

1:25 000

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

Features greater than 2500 sq m will be captured as a lake.

1:100 000

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

All Waterholes will be represented in the TOPO100K NTDB either as a waterhole or as a Lake. All features less than 2500 sq m will be shown as a waterholes. New features less than 10 000 sq m will be shown as a waterholes. New features greater than 10 000 sq m will be shown as a lakes (perennial). For existing features between 2500 sq m and 10 000 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. waterhole or Lake(perennial)).

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.

This feature will be shown when it does not exceed 62500 sq m, features larger than these dimensions will be shown as lakes.

General - All Scales

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Waterholes which are distinctive may have an accompanying textnote e.g: 'salt', 'billabong' unless the words 'salt','billabong' etc are included in the name.

General - All Scales

Waterholes must be coincident with a vertex on a Watercourse chain or fall within a Watercourse Area.

Waterholes cannot overlap;
Lake (Perennial), Watercourse Area (Perennial) or Reservoir (feature class).

General - All Scales

Waterholes must be coincident with a vertex on a Watercourse chain or fall within a Watercourse Area.

Waterholes cannot overlap;
Sea.

General - All Scales

Waterholes which are distinctive may have an accompanying descriptive note e.g: 'salt', 'billabong' unless the words 'salt','billabong' etc are included in the name.

Connector, Lake, Watercourse, Watercourse Area , Gnamma Hole, Native Well, Pool, Rockhole, Soak,

Section 3 chapters 5.3, 5.11.2, 6.9

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