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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences in the NTDB meeting the minimum size for inclusion should be retained unless there is clear evidence they no longer exist.

Individual adjacent ponds separated only by either artificial barriers or access paths will be captured as one polygon. The separations caused by artificial barriers 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.

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

The UPPERSCALE value will be applied based on an Aquaculture Area polygon meeting the applicable minimum size for map representation. For Upperscale Values of 1 000 000, where Aquaculture Area polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature. For Upperscale Values of 100 000 and 250 000 where Aquaculture Area polygons are under the minimum size for map representation but form clusters where the separation between polygons is equal to or less than ((Capture Scale/1000) * 0.075)) metres and each component part is above the minimum size for inclusion, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature.

General - All Scales

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.

Airport Area, Sea, Forest Or Shrub, Rainforest, Plantation, Orchard, Mangrove, Settling Pond Internal Line, Shoreline, Intensive Animal Production

Section 3 Chapters 5.3, 5.17, 5.18, 6.9
Appendix U Chapter 2.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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

General - All Scales

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

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. The only exception would be if data capture scale was specified at a scale greater than 25,000 and in this case the applicable previous edition map would be used as a guide for feature density capture.

Bores inside densely settled regions will only 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 100 000 or smaller scale (larger area). Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging. Upperscale tagging can also be assisted by reviewing the feature density represented on the previous edition NTMS and WACs for each applicable scale.

Bores within the NTDB with an Upperscale of 250,000 and 1,000,000 should be retained as such unless there is clear evidence they no longer exist.

Bores within Built Up Areas will not be eligible to be classified with Upperscale values equal to '100000' or smaller scales (larger areas).

In moderately and sparsely settled regions where a bore, windpump and/or water tank are interdependent, all three features should be given the equivalent Upperscale value. This value should be the smallest scale (largest area) to which at least one of the three features would be applicable.

When multiple bores are within ((Upperscale Value/1000m) * 85)m proximity, only one of those bores is eligible to be tagged with the applicable Upperscale Value. Preference will be given to named bores and bores associated with either windpumps, Water Tanks, Farm Dams, Town Water Storage or Rural Water Storage.

General - All Scales

Where a bore and a water tank/dam are situated together, both will be included in the data but only the water tank/dam will be symbolised as it usually has the greater landmark value. Bore should be symbolised to 2 PointNoDraw.

Bores must not overlap;
Aquaculture Area, Canal Area, Lake (Perennial), Salt Evaporator, Settling Pond, Town Water Storage, Rural Water 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. The Bore should be symbolised to 2 PointNoDraw.

Bores plotted within 2.5 mm at map scale of a populated place will not be shown (symbolised to 2 PointNoDraw).

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

General - All Scales

New features less than the 25m will be captured as Canal Lines only.

Existing features below the minimum data capture size or below the (Capture Scale/2000)m wide will be retained in the same geometry as captured in the base material/digital data.

New features greater than or equal to 25m wide but smaller than (Capture Scale/2000)m wide will be captured as Canal Lines only (eg for 1:100,000 data capture it must be (100,000/2000)m or 50m wide).

New features greater than or equal to 25m wide and at least (Capture Scale/2000)m wide will be captured as Canal Area (with a backbone of a canal line see Section 3 6.9.5 Connector Feature for more detail).


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.

• Small linear features that carry water away from point features such as water tanks or a bore/windpump to an animal watering device; or
• A natural watercourse which has had its banks re-contoured or normal path dredged to provide better water flow; or
• 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.

General - All Scales

Canal Areas cannot overlap;
Any feature in any feature class within the waterbodies feature dataset.

General - All Scales

Connectors & canal lines will be placed through Canal Areas to complete stream networking see Section 3 6.9.5 Connector Feature.

Canal Areas cannot overlap;
Built Up Area.

The following cannot overlap or fall within polygon canals;
BuildingPoints (feature class), BuildingAreas (feature class), 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, Salt Evaporator, Salt Evaporator Internal Line, Settling Pond Internal Line, Watercourse, Watercourse Area, Estuary, Shoreline, Junction

Section 2 Chapter 2.2.3
Section 3 Chapter 5.3, 5.17, 5.18, 6.9
Appendix U Chapter 2.2, 2.3, 2.5

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.

Dam

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.

Dam

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

The name of the Dam (see Geodatabase Rules for population requirements).

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

General - All Scales

When applicable for inclusion/data capture a Dam/Town Water Storage/Rural Water Storage will be depicted as either a Dam or Town Water Storage or Rural Water Storage dependant on size criteria.

Existing Dam/Town Water Storage/Rural Water Storage features below the minimum data capture size for a Town Water Storage/Rural Water Storage will be retained (unfiltered) in the same geometry as captured in the base material/digital data (eg Dam or Town Water Storage/Rural Water Storage). The only exception is all features below 625 sq m which will be shown as Dam.

New features in sparsely and moderately settled regions as defined by Appendix C ('Fence and Water Facilities Guide') and below the minimum data capture size for an Town Water Storage/Rural Water Storage will be captured as a Dam. New features in densely settled regions as defined by Appendix C ('Fence and Water Facilities Guide') and below the minimum data capture size for an Town Water Storage/Rural Water Storage will only be captured as a Dam upon direction from Geoscience Australia. New features which are equal to or above the minimum data capture size for a Town Water Storage/Rural Water Storage at the specified scale will be captured as a Town Water Storage or Rural Water Storage as appropriate.

This feature will not be used to capture FloodIrrigationStorage Reservoirs smaller than their minimum size criteria.

Dams to have an accompanying textnote for features not being used directly for human or livestock consumption.

Names will be captured, where known.

When assigning Upperscale, no two waterstoragepoints should be within 1.06mm at map representation scale (eg 265m at 1:250 000).

Dams within Built Up Areas will not be eligible for upperscale values of '100000' and smaller scales (larger areas eg '250000','1000000').

Only dams 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. The selection used on the previous edition map at the applicable scale should be used as a guide unless significant variations in land use have occurred. Newly captured features should have the significance compared to those currently represented. Preference will be given to named features and features where additional information is known eg 'salt'.

General - All Scales

Where a Bore and a Dam are situated together, both will be included in the data but only the Dam will be shown as it usually has the greater landmark value. The Bore should be symbolised to 2 Point No Draw.

Dams cannot overlap;
Reservoirs (feature class)

General - All Scales

Dams plotted within 2.5 mm at map scale of a Built Up Area will be symbolised to 2 Point No Draw.

Dams cannot overlap;
BuildingAreas feature class (Ruin)

General - All Scales

Names will be shown in sparsely settled areas.

As the density of the cultural detail increases, names will be progressively omitted.

Dams are to have an accompanying descriptive note for features not being used directly for human or livestock consumption.

Where a Dam and Windpump are situated together, only the Windpump, which has the greater landmark value, will be shown. (Refer feature Windpump).

Bore, Built Up Area, Dam Wall, Vertical Obstruction, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Storage Tank, Gnamma Hole, Native Well, Pool, Rockhole, Soak, Swimming Pool, Windpump, Water Tank

Section 3 Chapter 5.3 Cartographic Selection, Generalisation and Overlap
Appendix C
Appendix U Chapter 2.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.

Estuary

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.

Estuary

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;
Perennial
Non Perennial

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

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

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist. Where an Estuary is connecting a watercourse area to the sea or lake (under tidal influence), the size criteria will apply to the sum of the adjoining WatercourseAreas feature class polygons.

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.

Hierarchy of Estuary 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 Estuary will be 'perennial' as they are under daily tidal influence.

The hierarchy of double line Watercourses will not be represented by symbology.

General - All Scales

WatercourseAreas (Feature Class) cannot overlap;
Other polygon features within the Waterbodies Dataset with the exception of Rapid Areas.

General - All Scales

Where a Dam Wall crosses a Watercourse Area or Estuary, 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.

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

Estuary cannot overlap;
Sea, Built Up Areas.

Canal Area, Canal Line, Connector, Flow Direction Arrow, Ford Line, Ford Point, Junction, Lake, Gorge, Lock, Mangrove, Rapid Area, Rapid Line, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Waterfall Point, Waterhole, Shoreline

Section 1 Chapters 3.8.1
Section 2 Chapters 2.2.3, 5.3
Section 3 Chapters 5.3, 5.7, 5.11.2, 5.17, 5.18, 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.

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.

VOLUME IN MEGA LITRES (VOLUMEMEGAL) [Single;Yes(No);0;6;2;Pop_Wk] Volume through put of site or facility in mega litres per annum.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

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

General - All Scales

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

All existing Flood Irrigation Storage features in approved Geoscience Base Material/NTDB will be retained when it meets the minimum size for data inclusion regardless of if a data capture scale is specified. All existing features which meet the definition of a Flood Irrigation Storage but are below the minimum size for inclusion will not be retained nor will they be captured as a Water Tank or Dam.

New Flood Irrigation Storage reservoirs smaller than the minimum size criteria for data capture will not be captured as a Water tank or Dam feature.

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 Water Storage/Rural Water 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.

General - All Scales

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


Flood Irrigation Storage cannot overlap;
Water Tank, Dam

General - All Scales

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 or DEMConnectors), Spot Elevations, Sea, BuildingPoints (feature class), BuildingAreas (feature class), NativeVegetationAreas (feature class), CultivatedAreas (feature class), Discontinuities (feature class), Cave, Pinnacle, MarineHazardPoints ( feature class), Lighthouse, AircraftFacilityPoints, AircraftFacilityArea, Airport Area and Cleared Lines.

Dam Walls should be coincident with the high water mark of the reservoir for the portion of the waterbody 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.

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, Lake, Spillway, Water Tank, Watercourse, Watercourse Area, Shoreline, Town Water Storage, Rural Water Storage, Estuary

Section 3 Chapter 5.3, 5.17, 5.18, 6.9
Appendix U 2.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.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

General - All Scales

All feature occurrences existing in the NTDB will be retained unless there is clear evidence they no longer exist.

When applicable for inclusion/data capture a Gnamma Hole will be represented either as a Gnamma Hole or as a Lake, dependant on size criteria.

Existing Gnamma Hole features below the minimum data capture size for a lake will be retained in the same geometry as captured in the base material/digital data (eg Gnamma Hole or Lake). The only exception is all features less than 2500 sq m which will be shown as a Gnamma Hole.

New features which are below the minimum data capture size for a lake at the specified scale will be captured as a Gnamma Hole. New features which are equal to or above the minimum data capture size for a lake at the specified scale will be captured as a Lake.

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 only 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 eligible for Upperscale values of '100000' and smaller scales (larger areas eg '250000'). Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Features attributed with an Upperscale of 250,000 or smaller scale (larger areas eg '1 000 000') should be retained as such unless there is clear evidence they no longer exist.

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;
WatercourseAreas (feature class), Lake, Canal Areas, Flood Irrigation Storage, Town Water Storage, Rural Water Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or BuildingAreas (feature class).

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, Rockhole, Pool, Native Well, Soak

Section 3 Chapter 5.3 Cartographic Selection, Generalisation and Overlap
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.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

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

General - All Scales

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

All naturally occurring bodies of water will be represented in the 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 the minimum size for inclusion and the minimum size for data capture 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 existing base material/digital data, 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.
• The base material/digital data for revision is not the NTDB but the NTDB has been provided as reference material for perenniality, in this case the perenniality of the lake should default to that indicated in the NTDB unless one of the above two cases exist which take precedence.

General - All Scales

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.

General - All Scales

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

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

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 Water Storage, Rural Water Storage, Watercourse, Watercourse Area, Estuary, Waterhole, Shoreline, 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.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

General - All Scales

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

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

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

General - All Scales

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.

General - All Scales

Land subject to inundation cannot overlap:
Mangrove.

Connectors may be shown through this feature.

Connector, Junction, Shoreline

Section 3 Chapter 6.9, 5.17, 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.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

General - All Scales

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

Size criteria will not apply where Marine Swamp completely covers small islands i.e boundary of island is completely coincident with boundary of Marine Swamp.

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

The UPPERSCALE value will be applied based on an Marine Swamp polygon meeting the applicable minimum size for map representation. Where Marine Swamp polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature. Marine Swamp polygons completely covering islands which meet the equivalent 'UPPERSCALE' will be included in that 'UPPERSCALE' category regardless of scale.

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

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, Junction, Shoreline

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

General - All Scales

All feature occurrences existing in the NTDB will be retained unless there is clear evidence they no longer exist.

When applicable for inclusion/data capture a Native Well will be represented either as a Native Well or as a Lake, dependant on size criteria.

Existing Native Well features below the minimum data capture size for a lake will be retained in the same geometry as captured in the base material/digital data (eg Native Well or Lake). The only exception is all features less than 2500 sq m which will be shown as a Native Well.

New features which are below the minimum data capture size for a lake at the specified scale will be captured as a Native Well. New features which are equal to or above the minimum data capture size for a lake at the specified scale will be captured as a Lake.

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 only 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 eligible for Upperscale values of '100000' and smaller scales (larger areas eg '250000'). Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Features attributed with an Upperscale of 250,000 or smaller scale (larger areas eg '1 000 000') should be retained as such unless there is clear evidence they no longer exist.

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;
WatercourseAreas (feature class), Lake, Canal Areas, Flood Irrigation Storage, Town Water Storage, Rural Water Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or BuildingAreas (feature class).

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, Town Water Storage, Rural Water Storage, Spring, Water Tank, Dam, Waterhole, Rockhole, Gnamma Hole, Native Well, Soak, Pool

Section 3 Chapter 5.3 Cartographic Selection, Generalisation and Overlap
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.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

General - All Scales

All feature occurrences existing in the NTDB will be retained unless there is clear evidence they no longer exist.

When applicable for inclusion/data capture a Pool will be represented either as a Pool or as a Lake, dependant on size criteria.

Existing Pool features below the minimum data capture size for a lake will be retained in the same geometry as captured in the base material/digital data (eg Pool or Lake). The only exception is all features less than 2500 sq m which will be shown as a Pool.

New features which are below the minimum data capture size for a lake at the specified scale will be captured as a Pool. New features which are equal to or above the minimum data capture size for a lake at the specified scale will be captured as a Lake.

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 only 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 eligible for Upperscale values of '100000' and smaller scales (larger areas eg '250000'). Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Features attributed with an Upperscale of 250,000 or smaller scale (larger areas eg '1 000 000') should be retained as such unless there is clear evidence they no longer exist.

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;
WatercourseAreas (feature class), Lake, Canal Areas, Flood Irrigation Storage, Town Water Storage, Rural Water Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or BuildingAreas (feature class).

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, Town Water Storage, Rural Water Storage, Spring, Water Tank, Dam, Waterhole, Rockhole, Gnamma Hole, Native Well, Soak, Pool

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

General - All Scales

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

Rapids in double line streams will be shown as both a Rapid Area and Rapid Line feature. Rapids on watercourse (lines) will be captured as a Rapid Line only.

For a Rapid Area to be given either a SYMBOL100K or SYMBOL250K value of 880 it must meet both the minimum map representation length size criteria and be associated with a perennial WatercourseAreas (feature class polygon) with the equivalent Upperscale value or smaller scale (larger area).

General - All Scales

Rapid Area must overlap;
WatercourseAreas (feature class)

Rapid Area must not overlap;
Other polygon features within the Waterbodies Dataset with the exception of WatercourseAreas (feature class).

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

General - All Scales

Rapids cannot overlap;
BuildingAreas feature class (Ruin).

General - All Scales

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

Connector, Rapid Line, Watercourse, Watercourse Area, Shoreline, Estuary

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.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

General - All Scales

All feature occurrences existing in the NTDB will be retained unless there is clear evidence they no longer exist.

When applicable for inclusion/data capture a Rockhole will be represented either as a Rockhole or as a Lake, dependant on size criteria.

Existing Rockhole features below the minimum data capture size for a lake will be retained in the same geometry as captured in the base material/digital data (eg Rockhole or Lake). The only exception is all features less than 2500 sq m which will be shown as a Rockhole.

New features which are below the minimum data capture size for a lake at the specified scale will be captured as a Rockhole. New features which are equal to or above the minimum data capture size for a lake at the specified scale will be captured as a Lake.

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 only 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 eligible for Upperscale values of '100000' and smaller scales (larger areas eg '250000'). Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Features attributed with an Upperscale of 250,000 or smaller scale (larger areas eg '1 000 000') should be retained as such unless there is clear evidence they no longer exist.

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;
WatercourseAreas (feature class), Lake, Canal Areas, Flood Irrigation Storage, Town Water Storage, Rural Water Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or BuildingAreas (feature class).

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, Town Water Storage, Rural Water Storage, Dam

Section 3 Chapter 5.3 Cartographic Selection, Generalisation and Overlap
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.

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

RuralWaterStorage

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.

VOLUME IN MEGA LITRES (VOLUMEMEGAL) [Single;Yes(No);0;6;2;Pop_Wk] Volume through put of site or facility in mega litres per annum.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

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

General - All Scales

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

All Rural Water Storage reservoirs will be represented in the base material/digital data as either a Rural Water Storage Reservoir or a Dam.

All Rural Water Storage reservoirs less than the minimum size for inclusion will be shown as a Dam.

Existing features between minimum size for inclusion and the applicable Data Capture And Map Representation minimum size criteria will be retained in the same geometry as captured in the base material/digital data (e.g. Rural Water Storage Reservoir or a Dam).

New features less than the applicable Data Capture And Map Representation minimum size criteria will be captured as a Dam, unless otherwise directed. New or Revised features greater than the applicable Data Capture And Map Representation minimum size criteria will be captured as a Rural Water Storage.

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

In densely and moderately settled regions as defined by Appendix C where a Dam wall meets the minimum data capture & map representation size criteria for a specific scale , the attached reservoir should be assigned the upperscale of the dam wall and symbolised 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 represented at that scale unless it has significant historical/landmark value.

Town Water Storage/Rural Water 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 Rural Water Storage classification are to have an accompanying textnote e.g: 'aquarium' for features not being used directly for human or livestock consumption.

Man-made permanent ornamental lakes within parks and gardens which have been carved into the landscape (generally utilising and exaggerating a natural depression), which are left to fill and retain water naturally without the use of a defined dam wall will be captured/maintained as feature type 'Lake'. This is in spite of the 'Lake' feature type definition saying it must be naturally occurring 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 occurring feature.

General - All Scales

Reservoirs (feature class) cannot overlap;
Waterpoints, other waterbodies feature dataset polygons.

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 or DEMConnectors), Spot Elevations, Sea, BuildingPoints (feature class), BuildingAreas (feature class), 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, Lake, Spillway, Dam, Water Tank, Watercourse, Watercourse Area, Shoreline, Flood Irrigation Storage, Estuary

Section 3 Chapter 5.3, 5.17, 5.18, 6.9
Appendix U 2.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.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

General - All Scales

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

Size criteria will not apply where Saline Coastal Flat completely covers small islands i.e boundary of island is completely coincident with boundary of Saline Coastal Flat.

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

The UPPERSCALE value will be applied based on a Saline Coastal Flat polygon meeting the applicable minimum size for map representation. Where Saline Coastal Flat polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature. Saline Coastal Flat polygons completely covering islands which meet the equivalent 'UPPERSCALE' will be included in that 'UPPERSCALE' category regardless of scale.

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

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, Shoreline, Swamp, Marine Swamp, Land Subject To Inundation

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences in the NTDB meeting the minimum size for inclusion should be retained unless there is clear evidence they no longer exist.

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

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

The UPPERSCALE value will be applied based on an Salt Evaporator polygon meeting the applicable minimum size for map representation. For Upperscale Values of 1 000 000, where Salt Evaporator polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature. For Upperscale Values of 100 000 annd 250 000 where Salt Evaporator polygons are under the minimum size for map representation but form clusters where the separation between polygons is equal to or less than ((Capture Scale/1000) * 0.075)) metres and each component part is above the minimum size for inclusion, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature.

General - All Scales

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), BuildingAreas (feature class), 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, Shoreline

Section 3 Chapters 5.3, 5.17, 5.18, 6.9
Appendix U Chapter 2.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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences meeting the minimum size for inclusion in the NTDB should be retained unless there is clear evidence they no longer exist. New Settling Pond features below the minimum size for Data Capture will not be captured as any other feature type.

Individual adjacent ponds separated only by either artificial barriers or access paths will be captured as one polygon. The separations caused by artificial barriers 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.

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

The UPPERSCALE value will be applied based on a Settling Pond polygon meeting the applicable minimum size for map representation. For Upperscale Values of 1 000 000, where Settling Pond polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature. For Upperscale Values of 100 000 and 250 000 where Settling Pond polygons are under the minimum size for map representation but form clusters where the separation between polygons is equal to or less than ((Capture Scale/1000) * 0.075)) metres and each component part is above the minimum size for inclusion, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature.

General - All Scales

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

General - All Scales

Where settling ponds are associated with surrounding waste treatment infrastructure (e.g processing plants, etc), if the total area of the entire complex meets the appropriate size criteria it should be bounded by a feature type Landmark Area General with a description of treatment works.

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 Area, Mine Point, Settling Pond Internal Line, Shoreline, Landmark Area General , Salt Evaporator, Aquaculture Area, Intensive Animal Production, Power Generation Facility

Section 3 Chapters 5.3, 5.17, 5.18, 6.9
Appendix U Chapter 2.3, 2.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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial capture) used for Spatial Verification

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

General - All Scales

All feature occurrences existing in the NTDB will be retained unless there is clear evidence they no longer exist.

When applicable for inclusion/data capture a Soak will be represented either as a Soak or as a Lake, dependant on size criteria.

Existing Soak features below the minimum data capture size for a lake will be retained in the same geometry as captured in the base material/digital data (eg Soak or Lake). The only exception is all features less than 2500 sq m which will be shown as a Soak.

New Soak features in sparsely and moderately settled regions as defined by Appendix C ('Fence and Water Facilities Guide') which are below the minimum data capture size for a lake at the specified scale will be captured as a Soak. New Soak features in densely settled regions as defined by Appendix C ('Fence and Water Facilities Guide') which are below the minimum data capture size for a lake at the specified scale will be captured as a Soak only upon direction from Geoscience Australia. New Soak features which are equal to or above the minimum data capture size for a lake at the specified scale will be captured as a Lake.

Only Soaks in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide will be eligible for Upperscale values of '100000' and smaller scales (larger areas eg '250000'). Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Features attributed with an Upperscale of 250,000 or smaller scale (larger areas eg '1 000 000') should be retained as such unless there is clear evidence they no longer exist.

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;
WatercourseAreas (feature class), Lake, Canal Areas, Flood Irrigation Storage, Town Water Storage, Rural Water Storage.

General - All Scales

WaterPoints feature class cannot overlap;
Sea, Watercourse or BuildingAreas (feature class).

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, Rockhole, Pool, Gnamma Hole, Native Well, Town Water Storage, Rural Water Storage, Dam

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

General - All Scales

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.

The feature will not be symbolised 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.

General - All Scales

Springs cannot overlap;
Lake perennial, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, WatercourseAreas (feature class), Canal Area.

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

General - All Scales

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

Size criteria will not apply where Swamp completely covers small islands i.e boundary of island is completely coincident with boundary of Swamp.

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

The UPPERSCALE value will be applied based on an Swamp polygon meeting the applicable minimum size for map representation. Where Swamp polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature. Swamp polygons completely covering islands which meet the equivalent 'UPPERSCALE' will be included in that 'UPPERSCALE' category regardless of scale.

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

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

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, Shoreline, Marine Swamp, Land Subject To Inundation, Saline Coastal Flat

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.

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

SwimmingPool

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

The name of the Swimming Pool (see Geodatabase Rules for population requirements).

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

General - All Scales

All swimming pools outside the defined Built Up Area will be captured.

Inside the defined Built Up Area, only publicly operated swimming pools that are not fully contained within a building will be captured.

Only Public Community Swimming Pools should be named, where name is known.

When assigning Upperscale, no two waterstoragepoints should be within 1.06mm at map representation scale (eg 265m at 1:250 000).

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

Only Public Community Swimming Pools will be eligible to be classified with an upperscale equal to, or greater than, '100000'. 'Greater than' refers to smaller scales such as '250000','1000000'.

Bore, Built Up Area, Dam Wall, Vertical Obstruction, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Storage Tank, Gnamma Hole, Native Well, Pool, Rockhole, Soak, Windpump, Water Tank, Dam

Section 3 Chapter 5.3 Cartographic Selection, Generalisation and Overlap
Appendix C
Appendix U Chapter 2.3

GEODATA LITE TOPO100K

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

Town Water Storage

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.

TownWaterStorage

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.

VOLUME IN MEGA LITRES (VOLUMEMEGAL) [Single;Yes(No);0;6;2;Pop_Wk] Volume through put of site or facility in mega litres per annum.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

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

General - All Scales

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

All Town Water Storage reservoirs will be represented in the base material/digital data as either a Town Water Storage Reservoir or a Dam.

All Town Water Storage reservoirs less than the minimum size for inclusion will be shown as a Dam.

Existing features between minimum size for inclusion and the applicable Data Capture And Map Representation minimum size criteria will be retained in the same geometry as captured in the base material/digital data (e.g. Town Water Storage Reservoir or a Dam).

New features less than the applicable Data Capture And Map Representation minimum size criteria will be captured as a Dam, unless otherwise directed. New or Revised features greater than the applicable Data Capture And Map Representation minimum size criteria will be captured as a Town Water Storage.

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

In densely and moderately settled regions as defined by Appendix C where a Dam wall meets the minimum data capture & map representation size criteria for a specific scale, the attached reservoir should be assigned the upperscale of the dam wall and symbolised 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 represented at that scale unless it has significant historical/landmark value.

Town Water Storage/Rural Water 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 Town Water Storage/Rural Water Storage classification are to have an accompanying textnote e.g: 'aquarium' for features not being used directly for human or livestock consumption.

Man-made permanent ornamental lakes within parks and gardens which have been carved into the landscape (generally utilising and exaggerating a natural depression), which are left to fill and retain water naturally without the use of a defined dam wall will be captured/maintained as feature type 'Lake'. This is in spite of the 'Lake' feature type definition saying it must be naturally occurring 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 occurring feature.

General - All Scales

Reservoirs (feature class) cannot overlap;
Waterpoints, other waterbodies feature dataset polygons.

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 or DEMConnectors), Spot Elevations, Sea, BuildingPoints (feature class), BuildingAreas (feature class), 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, Lake, Spillway, Dam, Water Tank, Watercourse, Watercourse Area, Shoreline, Flood Irrigation Storage, Estuary

Section 3 Chapter 5.3, 5.17, 5.18, 6.9
Appendix U 2.3

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
Arial6ptItalicLeft
Arial8ptItalicCenter
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
WatercourseAreas
Waterholes
WaterPoints
WaterStoragePoints

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

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

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

General - All Scales

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

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

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

Section 2 Chapters 5, 9

NTMS 100K

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
Arial24ptItalicCenter
Arial6ptItalicCenter
ArialNarrow10ptItalicCenter
ArialNarrow12ptItalicCenter
ArialNarrow12ptItalicLeft
ArialNarrow14ptItalicCenter
ArialNarrow16ptItalicCenter
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow7ptItalicCenter
ArialNarrow7ptItalicLeft
ArialNarrow7ptItalicRight
ArialNarrow8ptItalicCenter
ArialNarrow8ptItalicLeft

FEATURE (FEATURE) [String;Yes;32;0;0;Pop_Req] The code which identifies the class of topographic feature represented by the annotation. This field must be a legitimate feature class name.

Acceptable Domain Entries from dm_WaterbodiesFCs;
Bores
CanalAreas
Flats
Lakes
PondageAreas
RapidAreas
Reservoirs
Springs
WatercourseAreas
Waterholes
WaterPoints
WaterStoragePoints

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

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

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

General - All Scales

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

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

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

Section 2 Chapters 5, 10

NTMS 100K

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;
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
Arial14ptItalicCentre
Arial16ptItalicCentre
Arial18ptItalicCentre
Arial20ptItalicCentre
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow10ptItalicCenter
ArialNarrow10ptItalicLeft
ArialNarrow12ptItalicCenter
ArialNarrow12ptItalicLeft
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow7ptItalicCenter
ArialNarrow7ptItalicLeft
ArialNarrow7ptItalicRight
ArialNarrow8ptItalicCenter
ArialNarrow8ptItalicLeft
ArialNarrow6ptItalic100C10M10KCenter
ArialNarrow6ptItalic100C10M10KLeft
ArialNarrow6ptItalic100C10M10KRight
ArialNarrow7ptItalic100C10M10KCenter
ArialNarrow7ptItalic100C10M10KLeft
ArialNarrow7ptItalic100C10M10KRight
ArialNarrow8ptItalic100C10M10KCenter
ArialNarrow8ptItalic100C10M10KLeft
ArialNarrow8ptItalic100C10M10KRight
ArialNarrow10ptItalic100C10M10KCenter
ArialNarrow10ptItalic100C10M10KLeft
ArialNarrow10ptItalic100C10M10KRight
ArialNarrow12ptItalic100C10M10KCenter
ArialNarrow14ptItalic100C10M10KCenter
ArialNarrow16ptItalic100C10M10KCenter
ArialNarrow18ptItalic100C10M10KCenter

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
Reservoirs
Springs
WatercourseAreas
Waterholes
WaterPoints
WaterStoragePoints

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

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

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

General - All Scales

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

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

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

Section 2 Chapters 5, 11

NTMS 100K

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;
ArialNarrow10ptItalic100C9MCenter
ArialNarrow10ptItalic100C9MLeft
ArialNarrow10ptItalic100C9MRight
ArialNarrow8ptItalic100C9MCenter
ArialNarrow8ptItalic100C9MLeft
ArialNarrow8ptItalic100C9MRight
ArialNarrow7ptItalic100C9MCenter
ArialNarrow7ptItalic100C9MLeft
ArialNarrow7ptItalic100C9MRight
ArialNarrow6ptItalic100C9MCenter
ArialNarrow6ptItalic100C9MLeft
ArialNarrow6ptItalic100C9MRight
ArialNarrow9ptItalic100C9MCenter
ArialNarrow9ptItalic100C9MLeft
ArialNarrow9ptItalic100C9MRight
ArialNarrow12ptItalic100C9MCenter
ArialNarrow12ptItalic100C9MLeft
ArialNarrow12ptItalic100C9MRight

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;
Flats
Lakes
Reservoirs
Springs
WatercourseAreas

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

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

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

General - All Scales

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

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

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

Section 2 Chapters 5, 12

NTMS 100K

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;
Arial5pt5Italic100C9MCenter
Arial5pt5Italic100C9MLeft
Arial5pt5Italic100C9MRight
Arial7ptItalic100C9MCenter
Arial7ptItalic100C9MLeft
Arial7ptItalic100C9MRight
Arial8ptItalic100C9MCenter
Arial8ptItalic100C9MLeft
Arial8ptItalic100C9MRight
Arial6pt5Italic100C9MCenter
Arial6pt5Italic100C9MLeft
Arial6pt5Italic100C9MRight
Arial7pt5Italic100C9MCenter
Arial7pt5Italic100C9MLeft
Arial7pt5Italic100C9MRight
ArialNarrow6pt5Italic100C9MCenter
ArialNarrow6pt5Italic100C9MLeft
ArialNarrow6pt5Italic100C9MRight
ArialNarrow8ptItalic100C9MCenter
ArialNarrow8ptItalic100C9MLeft
ArialNarrow8ptItalic100C9MRight
ArialNarrow10ptItalic100C9MCenter
ArialNarrow10ptItalic100C9MLeft
ArialNarrow10ptItalic100C9MRight

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;
Flats
Lakes
Reservoirs
WatercourseAreas

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

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

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

General - All Scales

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

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

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

Section 2 Chapters 5, 13

NTMS 100K

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;
Arial6ptItalic100C9MCenter
Arial6ptItalic100C9MLeft
Arial6ptItalic100C9MRight
Arial7ptItalic100C9MCenter
Arial7ptItalic100C9MLeft
Arial7ptItalic100C9MRight

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;
Lakes
Reservoirs
WatercourseAreas

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

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

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

General - All Scales

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

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

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

Section 2 Chapters 5, 14

NTMS 100K

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

Watercourse Area

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.

WatercourseArea

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;
Perennial
Non Perennial

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

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

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

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

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

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

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist. Where an Estuary is connecting a watercourse area to the sea or lake (under tidal influence), the size criteria will apply to the sum of the adjoining WatercourseAreas feature class polygons.

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 represented by symbology.

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

General - All Scales

WatercourseAreas (Feature Class) cannot overlap;
Other polygon features within the Waterbodies Dataset with the exception of Rapid Areas.

General - All Scales

Where a Dam Wall crosses a Watercourse Area or Estuary, 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.

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

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, Rapid Area, Rapid Line, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Waterfall Point, Waterhole, Shoreline, Estuary

Section 1 Chapters 3.8.1
Section 2 Chapters2.2.3, 5.3
Section 3 Chapters 5.3, 5.7, 5.11.2, 5.17, 5.18, 6.9
Appendix D

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.

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

General - All Scales

All feature occurrences existing in the NTDB will be retained unless there is clear evidence they no longer exist.

When applicable for inclusion/data capture a Waterhole will be represented either as a Waterhole or as a Lake (perennial), dependant on size criteria.

Existing Waterholes features below the minimum data capture size for a lake will be retained in the same geometry as captured in the base material/digital data (eg Waterhole or Lake (perennial)). The only exception is all features less than 2500 sq m which will be shown as a Waterhole.

New features which are below the minimum data capture size for a lake at the specified scale will be captured as a Waterhole. New features which are equal to or above the minimum data capture size for a lake at the specified scale will be captured as a Lake.

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 WatercourseAreas (feature class polygon).

Waterholes cannot overlap;
Lake (Perennial), WatercourseAreas feature class (Perennial) or Reservoirs (feature class).

General - All Scales

Waterholes must be coincident with a vertex on a Watercourse chain or fall within a WatercourseAreas (feature class polygon).

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

Section 3 Chapters 5.3, 5.11.2, 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.

Water Tank

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.

WaterTank

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

The name of the Water Tank (see Geodatabase Rules for population requirements).

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

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

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

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

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

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

General - All Scales

Water Tanks 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).

Water tanks in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured. At 1:25 000 data capture scale no filtering should occur, however when capturing at smaller scales (larger area eg 1:100 000) a representative selection may be captured based on the density showed on the previous edition map unless directed otherwise by Geoscience Australia.

Water Tanks inside densely settled regions will only be captured upon direction from Geoscience Australia.

This feature can be used to represent water tanks (ie a physical tank structure) however it will not be used to capture Town Water Storage, Rural Water Storage or FloodIrrigationStorage Reservoirs smaller then their minimum size criteria.

Water Tanks to have an accompanying textnote e.g: 'aquarium' for features not being used directly for human or livestock consumption.

When assigning upperscale values, the proximity between water tanks at the applicable scale should be considered. No two waterstoragepoints should be within 1.06mm at map representation scale (eg 265m at 1:250 000). Where all water tanks can not be shown at one location, a selection should be made to retain a representative pattern.

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

Only Water Tanks 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. The selection used on the previous edition map at the applicable scale should be used as a guide unless significant variations in land use has occurred. Newly captured features should have the significance compared to those currently represented. Preference will be given to named features and features where additional information is known eg 'aquarium'.

Names will be captured, where known.

General - All Scales

Where a Bore and a Water Tank are situated together, both will be included in the data but only the Water Tank will be shown as it usually has the greater landmark value. Bore should be symbolised to 2 - Point No Draw.

Water tanks cannot overlap;
Flood Irrigation Storage

General - All Scales

Where a Elevated Water Tank exists, it will be captured/maintained in Water Storage Point feature class as a Water Tank and cloned as a Vertical Obstruction with a description of 'water tower'.

Water Tanks plotted within 2.5 mm at map scale of a Built Up Area will be symbolised to 2 - Point No Draw.

Water tanks cannot overlap;
BuildingAreas feature class (Ruin).

General - All Scales

Names will be shown in sparsely settled areas.

As the density of the cultural detail increases, names will be progressively omitted.

Water Tanks to have an accompanying descriptive note e.g: 'aquarium' for features not being used directly for human or livestock consumption.

Where a Water Tank and Windpump are situated together, only the Windpump, which has the greater landmark value, will be shown. (Refer feature Windpump).

Bore, Built Up Area, Dam Wall, Vertical Obstruction, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Storage Tank, Gnamma Hole, Native Well, Pool, Rockhole, Soak, Windpump, Swimming Pool, Dam

Section 3 Chapter 5.3 Cartographic Selection, Generalisation and Overlap
Appendix C
Appendix U Chapter 2.3

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