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

Cleared Line

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.

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

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

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_Vegetation.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_Vegetation.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

Cleared Lines shown on the latest previous edition map, base material/digital data or in the NTDB will be captured/retained, where there is clear evidence they exist. New Cleared lines may be added.

Cleared lines will be TextNoted e.g 'cleared line'. No reference to seismic lines should be made in the text_note field. If pre-existing features have been identified as seismic lines and are still visible on imagery, they will be redefined as 'cleared line' in the text_note field.

General - All Scales

Cleared Lines should not be captured/retained where the underlying reason for the clearing of vegetation is also captured/maintained as another feature type within the database. e.g. If vegetation has been cleared for fire prevention under powerlines and the powerline exists within the database then the cleared line should not be captured/retained.

General - All Scales

Cleared lines cannot overlap;
Sea, Lake, Reservoirs (feature class), WatercourseAreas (feature class) or Canal Area.

Cleared Lines should not be captured/retained where the underlying reason for the clearing of vegetation is also captured/maintained as another feature type within the database. e.g. If vegetation has been cleared for fire prevention under powerlines and the powerline exists within the database then the cleared line should not be captured/retained.

General - All Scales

Cleared lines will be labelled, for example 'cleared line'.

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

Appendix U Chapter 2.2, 2.5

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.

Forest Or Shrub

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.

ForestOrShrub

FOLIAGE COVER DENSITY (COVERDENSITY) [String;Yes;10;0;0;Pop_Dep] Density of foliage coverage;

Acceptable Domain Entries from dm_CoverDensity;
Sparse
Dense
Closed

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.

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

This classification excludes mangroves, orchards, plantations and rainforest.

Size criteria will not apply where 'Forest Or Shrub' completely covers small islands, i.e. such islands will have a matching 'Forest Or Shrub' polygon.

When capturing data at 1: 250 000 scale only, only 'Forest or Shrub' of 'Dense' and 'Closed' foliage coverage should be captured. Minimum Size for Data Capture at 1: 250 000 will apply to the sum of adjacent 'Forest Or Shrub' polygons.

Fire Scars will be considered as defined holes (areas on universe polygon) within vegetation polygon feature classes. Regrowth of vegetation in these areas will not be anticipated.

The classification of Foliage cover density have the following meanings:
Classification: Meaning
Sparse : Foliage coverage of 10 - 30%
Dense : Foliage coverage of 30 - 70%
Closed : Foliage coverage of 70%+

General - All Scales

Plantations and Rainforest which are under their minimum size criteria for inclusion, and are adjoined or surrounded by 'Forest Or Shrub' will be reclassified as 'Forest Or Shrub' and merged with its adjoining polygon.

Forest Or Shrub cannot overlap;
Other polygons in the Vegetation Dataset.

Upperscale, USCertainity and Symbol assignments for 'Forest Or Shrub' should consider the following:

• The minimum size for map representation.
• The minimum size for map representation will not apply when 'Forest Or Shrub' completely covers small islands which meet the equivalent map representation scale.
• Upperscale values of 250 000 will only be eligible for foliage coverage of 'Dense' or 'Closed'. The only exception is areas of 'Sparse' vegetation which are fully surrounded by other classifications of 'Forest Or Shrub' and under the size criteria for a defined hole. In this case the specific 'Sparse' vegetation areas will be symbolised to produce a continuous shading.
• For 1:250 000 Minimum Size for Map Representation will apply to the sum of adjacent 'Forest Or Shrub' polygons taking into account the previous criteria.
• Upperscale, USCertainity and Symbol assignments should be conducted with consideration of other feature types within the Vegetation feature dataset. For more detailed information on the attribution of these fields see 'Rainforest Upperscale and Symbol Representation Assignments' decision tree.

General - All Scales

Forest Or Shrub can overlap Built Up Area.

Forest Or Shrub cannot overlap;
BuildingAreas feature class (Ruin), Flood Irrigation Storage, Settling Pond, Aquaculture Area, Salt Evaporator.

General - All Scales

Forest Or Shrub will be masked for Built Up Areas on the map

Mangrove, Orchard, Plantation, Rainforest, Sand Area, Cleared Line and Windbreak

Section 2 Chapter 2.2.3
Section 3 Chapter 5.11.1, 5.11.2, 5.18, 5.19 and 6.3

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.

Mangrove

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.

Mangrove

FOLIAGE COVER DENSITY (COVERDENSITY) [String;Yes;10;0;0;Pop_Dep] Density of foliage coverage;

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.

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

Mangroves will be revised from the imagery, ortho photography or vegetation revision databases to be supplied.

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

New Mangrove polygons that are under the minimum size for data capture but form clusters with other new or existing Mangrove 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 Mangrove polygons should be captured as their individual components not as the cluster upon which its applicability is based. At Capture Scales of 2 500 000 and smaller scales (larger areas) the clusters can also be formed with Marine Swamp, Swamp and Saline Coastal Flat polygons.

The UPPERSCALE value will be applied based on a Mangrove polygon meeting the applicable minimum size for map representation. Where Mangrove 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. Mangroves polygons completely covering islands which meet the equivalent 'UPPERSCALE' will be included in that 'UPPERSCALE' category regardless of scale.

Fire Scars will be considered as defined holes (areas on universe polygon) within vegetation polygon feature classes. Regrowth of vegetation in these areas will not be anticipated.

General - All Scales

Mangrove cannot overlap;
Other polygons in the Vegetation Dataset.

General - All Scales

Mangrove cannot overlap;
AircraftFacilityArea polygons, Airport Area, BuildingAreas Ruin (Feature Class), Cemetery Area, Landmark Area, Waste Management Area, Flats (Feature Class), Lakes (Non Perennial), Pondage Areas (Feature Class), Flood Irrigation Storage, Watercourse Area (Non Perennial).

Connector, Forest Or Shrub, Plantation, Orchard, Rainforest, Watercourse, Watercourse Area, Estuary

Section 2 Chapter 2.2.3
Section 3 Chapter 5.11.2, 5.18, 5.19 and 6.3

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.

Orchard

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.

Orchard

PRODUCT CODE (PRODUCT) [String;Yes;35;0;0;Pop_Dep] Type of product produced or transported;

Acceptable Domain Entries from dm_OrchardProduct;
Apples
Bananas
Citrus
Coffee
Grapes
Olives
Tree Nuts
Other Orchard Type (Unspecified).

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_Vegetation.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_Vegetation.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.

New Orchard polygons that are under the minimum size for data capture but form clusters with other new or existing Orchard 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 Orchard 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 primarily on an Orchard polygon meeting the applicable minimum size for map representation. Where Orchard 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. See the Inter-Feature Relationship Rules for more details.

Fire Scars will be considered as defined holes (areas on universe polygon) within vegetation polygon feature classes. Regrowth of vegetation in these areas will not be anticipated.

General - All Scales

Orchard cannot overlap;
Other polygons in the Vegetation Dataset.

Upperscale, USCertainity and Symbol assignments should be conducted with consideration of other feature types within the Vegetation feature dataset. For more detailed information on the attribution of these fields see 'Cultivated Areas Upperscale and Symbol Representation Assignments'

General - All Scales

Orchard cannot overlap;
AircraftFacilityAreas, Airport Area, Building Area (Ruin), Waste Management Area, Flood Irrigation Storage, Lake (Non Perennial), Watercourse Area (Non Perennial), Salt Evaporators, Settling Pond, Aquaculture Area, Cemetery Area, Landmark Area.

1:25 000

Orchards are to have an accompanying descriptive note e.g. 'bananas',' tree nuts',' vineyard', etc if the horticultural type/product is known.

1:100 000

Orchards are to have an accompanying descriptive note e.g. 'bananas',' tree nuts',' vineyard', etc if the horticultural type/product is known.

Forest Or Shrub, Plantation, Rainforest, Mangrove

Section 3 Chapter 5.11.1, 5.11.2, 5.18 and 5.19
Appendix U Chapter 2.5

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.

Plantation

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.

Plantation

PRODUCT CODE (PRODUCT) [String;Yes;35;0;0;Pop_Dep] Type of product produced or transported;

Acceptable Domain Entries from dm_PlantationProduct;
Softwood
Hardwood

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

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_Vegetation.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_Vegetation.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.

Plantations are classified using the product field into two types; Softwood plantations which include features such as pine plantations and hardwood plantations which include the eucalyptus species.

New Plantation polygons that are under the minimum size for data capture but form clusters with other new or existing Plantation 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 100 000 and larger scales (smaller areas) the clusters can only be formed by polygons of the same Plantation Product. 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 Plantation 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 primarily on a Plantation polygon meeting the applicable minimum size for map representation. Where Plantation 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. See Inter- Feature relationship Rules for more details.

Fire Scars will be considered as defined holes (areas on universe polygon) within vegetation polygon feature classes. Regrowth of vegetation in these areas will not be anticipated.

When it is clear that a section of plantation has been harvested and no vegetation in that section now exists, that section will be considered as a defined hole (an area on universe polygon) within plantation feature class. Regrowth of the plantation in these areas will not be anticipated.

General - All Scales

Plantations cannot overlap;
Other polygons in the Vegetation Dataset.

Plantations and Rainforest which are under their minimum size criteria for inclusion/data capture, and are adjoined or surrounded by 'Forest Or Shrub' will be reclassified as 'Forest Or Shrub' and merged with its adjoining polygon.

Upperscale, USCertainity and Symbol assignments should be conducted with consideration of other feature types within the Vegetation feature dataset. For more detailed information on the attribution of these fields see 'Cultivated Areas Upperscale and Symbol Representation Assignments'

General - All Scales

Plantations cannot overlap;
Lake (Non Perennial), Flood Irrigation Storage, Watercourse Area (Non Perennial), BuildingAreas Ruin (feature class), AircraftFacilityArea, Airport Area, Salt Evaporators, Aquaculture Area and Settling Pond, Waste Management Area, Landmark Area, Cemetery Area.

Forest Or Shrub, Orchard, Rainforest, Mangrove

Section 3 Chapter 5.11.1, 5.11.2, 5.18 and 5.19
Appendix U Chapter 2.5

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.

Rainforest

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.

Rainforest

FOLIAGE COVER DENSITY (COVERDENSITY) [String;Yes;10;0;0;Pop_Dep] Density of foliage coverage;

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.

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

New Rainforest polygons that are under the minimum size for data capture but form clusters with other new or existing Rainforest 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 Rainforest polygons should be captured as their individual components not as the cluster upon which its applicability is based.

Rainforest should be named where named on base material/digital data or rainforest reference material, the name will be held in the textnote field.

General - All Scales

Rainforest cannot overlap;
Other polygons in the Vegetation Dataset.

Plantations and Rainforest which are under their minimum size criteria, and are adjoined or surrounded by 'Forest Or Shrub' will be reclassified as 'Forest Or Shrub' and merged with its adjoining polygon.

Upperscale, USCertainity and Symbol assignments should be conducted with consideration of other feature types within the Vegetation feature dataset. For more detailed information on the attribution of these fields see 'Rainforest Upperscale and Symbol Representation Assignments' decision tree.

General - All Scales

Rainforest cannot overlap;
BuildingAreas Ruin (feature class), AircraftFacilityArea, Airport Area, Flood Irrigation Storage, Settling Pond, Aquaculture Area, Salt Evaporator, Lake (Non Perennial), Waste Management Area, Landmark Area, Cemetery Area.

General - All Scales

Rainforest should be named where named on base material/digital data or rainforest revision source material. Type styles for named areas of rainforest will be those used for Vegetation features, see Section 2 chapter 8.4 (for 1:250 000) and 9.4 (for 1:100 000).

Forest Or Shrub, Plantation, Orchard, Mangrove, Cleared Line, Windbreak

Section 2 Chapter 2.2.3
Section 3 Chapter 5.11.1, 5.11.2, 5.18 and 5.19

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.

Seagrass

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.

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

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

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

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_Vegetation.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.

Seagrass will not be revised from the imagery or ortho photography only. Vegetation revision databases or material will be supplied by Geoscience Australia.

General - All Scales

Seagrass cannot overlap;
Other polygons in the Vegetation Dataset.

General - All Scales

Seagrass must appear in Lake (Perennial), WatercourseAreas (Perennial) feature class or Sea.

Seagrass must not overlap;
MarineHazardAreas (feature class), Foreshore Flat

General - All Scales

Seagrass will be labelled 'seagrass' on the map face.

Plantation, Orchard, Forest Or Shrub, Rainforest, Watercourse Area, Estuary, Lake, Sea, Shoal, Reef, Foreshore Flat

Section 2 Chapter 2.2.3
Section 3 Chapter 5.11.2, 5.18, 5.19 and 6.3

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 VegetationAnno;
Arial10ptItalicCenter
Arial12ptItalicCenter
Arial14ptItalicCenter
Arial18ptItalicCenter
Arial6ptItalicCenter
Arial8ptItalicCenter
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow8ptCenter
ArialNarrow8ptLeft
ArialNarrow8ptRight

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_VegetationFCs;
ClearedLines
CultivatedAreas
NativeVegetationAreas
Seagrass
Windbreaks

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 Vegetation feature dataset should exist within the VegetationAnno 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 VegetationAnno;
Arial10ptItalicCenter
Arial12ptItalicCenter
Arial14ptItalicCenter
Arial18ptItalicCenter
Arial6ptItalicCenter
Arial8ptItalicCenter
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow7ptCenter
ArialNarrow7ptLeft
ArialNarrow7ptRight
ArialNarrow8ptCenter

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_VegetationFCs;
ClearedLines
CultivatedAreas
NativeVegetationAreas
Windbreaks

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 Vegetation feature dataset should exist within the VegetationAnno 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 VegetationAnno;
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight

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_VegetationFCs;
NativeVegetationAreas

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 Vegetation feature dataset should exist within the VegetationAnno 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

NTMS 100K

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

Windbreak

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.

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

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

Windbreaks shown on the base material/digital data, within the NTDB and on the latest previous edition map as well as its related 'parent' 100K and 250K maps will be shown, unless there is clear evidence they no longer exist. Windbreaks will be added when they can be confirmed on imagery and on additional approved revision source material.

No distinction will be made between different types of trees. This feature does not include uncleared portions of road reserves or fauna protection corridors regardless of whether or not that feature is represented on the previous edition map or in the data.

When assigning Upperscale Values the windbreaks must meet the map representation size criteria and a sufficient selection must be made to show a suitable representative pattern at scale.

General - All Scales

Windbreaks cannot overlap;
Watercourse Area (Non Perennial), Lake (Non Perennial), BuildingAreas Ruin (feature class), Sand Area or Sand Dune.

General - All Scales

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

Forest Or Shrub, Rainforest, Cleared Line, Plantation

Section 3 Chapter 5.3
Appendix U Chapter 2.5

GEODATA TOPO250K, NTMS 100K, NTMS 250K