Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Bay
Locations
Framework
Point
A named wide, open and curving indentation into the land formed by the sea or inland waterbody.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Bay
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.
Bay
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the Bay. This item must 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
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.
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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
Includes features such as bays, inlets and coves. This feature type will be used for an indentation of the sea into the land and for the equivalent features in inland waterbodies.
The bay location will be positioned at a point in the sea or waterbody in the middle of the indentation (or centre of the bay).
For Upperscale assignment, selection of locations should be based on the equivalent scale previous edition hardcopy or digital topographic map taking into account any significant changes in a regions population growth or decline, underlying infrastructure or industry change which may impact the importance of an entities potential for recognition or landmark value (including history of area). In general, all localities of regional importance should be included at 1:25000, all localities of a state/territory importance should be included at 1:100000 and only localities of national importance should be assigned values of 1:250000 and greater (eg 1:5000000).
When a Bay is legitimate for map representation at a specified scale, it will be assigned symbol 2 (Point No Draw) and will be visually denoted by text only.
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
In general, for each locality bay name, the associated location entity should only be captured once and positioned central to the feature. Large bays (eg 'Port Phillip Bay') which overlap 2 or more MapIndex250K sheets, will have the location entity placed in the bleed area of the overlapping sheets and only where this can not properly represent the whole bay may a duplicate be made.
A locality of the same code and name should not be repeated within the same MapIndex250K sheet unless it relates to a number of entities sharing the same name.
Map Rules
Related Features
Place Name, Sea, Lake, Watercourse Area, Estuary, Town Water Storage, Rural Water Storage, Map Index 100K, Map Index 250K, Map Index WAC, Map Index 2_5MIL, Beach, Cape, Island, Large Area Feature, Waterbody Island
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Beach
Locations
Framework
Point
A named strip of land or terrace bordering the sea, usually lying between high and low tides.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Beach
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.
Beach
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the Beach. This item must 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
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.
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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
Only named beaches on the base material/digital data and authorised revision source material are to be included.
The beach location will be coincident with the Shoreline or Waterbodies (feature dataset polygon edge) at the approximate centre of the beach.
For Upperscale assignment, selection of locations should be based on the equivalent scale previous edition hardcopy or digital topographic map taking into account any significant changes in a regions population growth or decline, underlying infrastructure or industry change which may impact the importance of an entities potential for recognition or landmark value (including history of area). In general, all localities of regional importance should be included at 1:25000, all localities of a state/territory importance should be included at 1:100000 and only localities of national importance should be assigned values of 1:250000 and greater (eg 1:5000000).
When a Beach is legitimate for map representation at a specified scale, it will be assigned symbol 2 (Point No Draw) and will be visually denoted by text only.
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
Where a locality beach name refers to an extensive area the associated Location entity should only be captured once and positioned central to the feature.
A locality of the same code and name should not be repeated within the same MapIndex250K sheet unless it relates to a number of entities sharing the same name.
Map Rules
General - All Scales
The names of all beaches on the previous edition map are to be included except where they are adjacent to a populated place with the same root-name. ie. 'Bondi Beach' would not appear if there is an adjacent populated place named 'Bondi' on the map.
Related Features
Place Name, Sea, Lake, Watercourse Area ,Estuary, Town Water Storage, Rural Water Storage, Map Index 100K, Map Index 250K, Map Index WAC, Map Index 2_5MIL , Bay, Cape, Island, Large Area Feature, Waterbody Island, Shoreline, Mainland, Sand Area, Sand Dune, Built Up Area, Populated Place
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Cape
Locations
Framework
Point
A named prominent headland projecting into the sea or inland waterbody.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Cape
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.
Cape
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the Cape. This item must 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
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.
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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
Includes features such as capes, headlands, heads and points. This code will be used for a section of land protruding into the sea and for the equivalent features in inland waterbodies.
Cape features will be positioned at a point on the land representative of the location of the cape.
For Upperscale assignment, selection of locations should be based on the equivalent scale previous edition hardcopy or digital topographic map taking into account any significant changes in a regions population growth or decline, underlying infrastructure or industry change which may impact the importance of an entities potential for recognition or landmark value (including history of area). In general, all localities of regional importance should be included at 1:25000, all localities of a state/territory importance should be included at 1:100000 and only localities of national importance should be assigned values of 1:250000 and greater (eg 1:5000000).
When a Cape is legitimate for map representation at a specified scale, it will be assigned symbol 2 (Point No Draw) and will be visually denoted by text only.
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
Capes must not overlap;
Sea.
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
In general, for each locality cape name, the associated location entity should only be captured once and positioned central to the feature. Large capes (eg 'Cape York Peninsula') which overlap 2 or more MapIndex250K sheets, will have the location entity placed in the bleed area of the overlapping sheets and only where this can not properly represent the whole cape may duplicates be made.
A locality of the same code and name should not be repeated within the same MapIndex250K sheet unless it relates to a number of entities sharing the same name.
Capes must not overlap;
Lake (Perennial), WatercourseAreas feature class (Perennial).
Map Rules
Related Features
Place Name, Sea, Lake, Watercourse Area, Estuary, Town Water Storage, Rural Water Storage, Map Index 100K, Map Index 250K, Map Index WAC, Map Index 2_5MIL , Island, Large Area Feature, Waterbody Island, Mainland
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:100 000 |
---|
Framework Anno 100K
FrameworkAnno100K
Framework
Annotation
Type associated with the Framework Feature Dataset for 1:100 000 scale
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.
The following annotation classes exist in FrameworkAnno;
Arial10ptCenter
Arial10ptItalicCenter
Arial12ptCenter
Arial12ptItalicCenter
Arial14ptCenter
Arial14ptItalicCenter
Arial18ptCenter
Arial18ptItalicCenter
Arial20ptItalicCenter
Arial24ptCenter
Arial24ptItalicCenter
Arial6ptCenter
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
Arial6ptLeft
Arial7ptCenter
Arial7ptLeft
Arial8ptCenter
Arial8ptItalicCenter
Arial8ptItalicLeft
Arial8ptItalicRight
Arial9ptBoldCenter
Arial9ptBoldLeft
ArialNarrow10ptCenter
ArialNarrow10ptItalicCenter
ArialNarrow12ptItalicCenter
ArialNarrow14ptItalicCenter
ArialNarrow16ptItalicCenter
ArialNarrow5ptCenter
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow7ptCenter
ArialNarrow7ptLeft
ArialNarrow7ptRight
ArialNarrow7ptItalicCenter
ArialNarrow7ptItalicLeft
ArialNarrow7ptItalicRight
ArialNarrow8ptCenter
ArialNarrow8ptItalicCenter
ArialNarrow8ptLeft
ArialNarrow8ptRight
PalatinoLinotype6ptLeft
PalatinoLinotype6ptRight
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_FrameworkFCs;
FrameworkBoundaries
Islands
LargeAreaFeatures
Locations
Mainlands
Seas
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.
Geodatabase Rules
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 Framework feature dataset should exist within the FrameworkAnno 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)
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
Related Features
Related Chapters
Related Products
NTMS 100K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:250 000 |
---|
Framework Anno 250K
FrameworkAnno250K
Framework
Annotation
Type associated with the Framework Feature Dataset for 1:250 000 scale
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.
The following annotation classes exist in FrameworkAnno;
Arial10ptCenter
Arial10ptItalicCenter
Arial12ptCenter
Arial12ptItalicCenter
Arial14ptCenter
Arial14ptItalicCenter
Arial18ptCenter
Arial18ptItalicCenter
Arial20ptItalicCenter
Arial24ptCenter
Arial24ptItalicCenter
Arial30ptItalicCenter
Arial5ptItalicCenter
Arial5ptItalicLeft
Arial5ptItalicRight
Arial6ptCenter
Arial6ptLeft
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
Arial7ptCenter
Arial7ptLeft
Arial7ptitalicCenter
Arial7ptItalicLeft
Arial8ptCenter
Arial8ptItalicCenter
Arial8ptItalicLeft
Arial8ptItalicRight
Arial9ptBoldCenter
Arial9ptBoldLeft
ArialNarrow10ptCenter
ArialNarrow10ptItalicCenter
ArialNarrow12ptItalicCenter
ArialNarrow14ptItalicCenter
ArialNarrow16ptItalicCenter
ArialNarrow5ptCenter
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow7ptCenter
ArialNarrow7ptLeft
ArialNarrow7ptItalicCenter
ArialNarrow7ptItalicLeft
ArialNarrow7ptItalicRight
ArialNarrow8ptCenter
ArialNarrow8ptItalicCenter
ArialNarrow8ptLeft
ArialNarrow8ptRight
PalatinoLinotype6ptLeft
PalatinoLinotype6ptRight
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_FrameworkFCs;
FrameworkBoundaries
Islands
LargeAreaFeatures
Locations
Mainlands
Seas
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.
Geodatabase Rules
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 Framework feature dataset should exist within the FrameworkAnno 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)
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
Related Features
Related Chapters
Related Products
NTMS 100K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:1 000 000 |
---|
Framework Anno WAC
FrameworkAnnoWAC
Framework
Annotation
Type associated with the Framework Feature Dataset for 1:1 000 000 scale
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.
The following annotation classes exist in FrameworkAnno;
Arial6ptCenter
Arial6ptLeft
Arial6ptRight
Arial7ptCenter
Arial7ptLeft
Arial7ptRight
Arial8ptCenter
Arial8ptLeft
Arial8ptRight
Arial10ptCenter
Arial12ptCenter
Arial14ptCenter
Arial16ptCenter
Arial18ptCenter
Arial20ptCenter
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
Arial7ptItalicCenter
Arial7ptItalicLeft
Arial8ptItalicCenter
Arial8ptItalicLeft
Arial8ptItalicRight
Arial10ptItalicCenter
Arial12ptItalicCenter
Arial14ptItalicCenter
Arial16ptItalicCenter
Arial18ptItalicCenter
Arial20ptItalicCenter
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptCenter
ArialNarrow7ptLeft
ArialNarrow7ptRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow7ptItalicCenter
ArialNarrow7ptItalicLeft
ArialNarrow7ptItalicRight
ArialNarrow8ptItalicCenter
ArialNarrow8ptItalicLeft
ArialNarrow10ptItalicCenter
ArialNarrow10ptItalicLeft
ArialNarrow12ptItalicCenter
ArialNarrow12ptItalicLeft
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_FrameworkFCs;
FrameworkBoundaries
Islands
LargeAreaFeatures
Locations
Mainlands
Seas
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.
Geodatabase Rules
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 Framework feature dataset should exist within the FrameworkAnno 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)
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
Related Features
Related Chapters
Related Products
NTMS 100K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:2 500 000 |
---|
Framework Anno 2_5MIL
FrameworkAnno2_5MIL
Framework
Annotation
Type associated with the Framework Feature Dataset for 1:2 500 000 scale
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.
The following annotation classes exist in FrameworkAnno;
Arial6ptCenter
Arial6ptLeft
Arial6ptRight
Arial24ptBoldCenter
Arial24ptBoldLeft
Arial24ptBoldRight
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
Arial7ptItalicCenter
Arial7ptItalicLeft
Arial8ptItalicCenter
Arial8ptItalicLeft
Arial8ptItalicRight
Arial10ptItalicCenter
Arial10ptItalicLeft
Arial10ptItalicRight
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow10ptItalicCenter
ArialNarrow10ptItalicLeft
ArialNarrow6ptItalic100C9MCenter
ArialNarrow6ptItalic100C9MLeft
ArialNarrow6ptItalic100C9MRight
ArialNarrow7ptItalic100C9MCenter
ArialNarrow7ptItalic100C9MLeft
ArialNarrow7ptItalic100C9MRight
ArialNarrow8ptItalic100C9MCenter
ArialNarrow8ptItalic100C9MLeft
ArialNarrow8ptItalic100C9MRight
ArialNarrow9ptItalic100C9MCenter
ArialNarrow9ptItalic100C9MLeft
ArialNarrow9ptItalic100C9MRight
ArialNarrow12ptItalic100C9MCenter
ArialNarrow12ptItalic100C9MLeft
ArialNarrow12ptItalic100C9MRight
ArialNarrow18ptItalic100C9MRight
Arial14ptItalic100C9MCenter
Arial14ptItalic100C9MLeft
Arial14ptItalic100C9MRight
Arial18ptItalic100C9MCenter
Arial18ptItalic100C9MLeft
Arial6ptItalic47M100Y25KCenter
Arial6ptItalic47M100Y25KLeft
Arial6ptItalic47M100Y25KRight
Arial7ptItalic47M100Y25KCenter
Arial7ptItalic47M100Y25KLeft
Arial7ptItalic47M100Y25KRight
Arial8ptItalic47M100Y25KCenter
Arial8ptItalic47M100Y25KLeft
Arial8ptItalic47M100Y25KRight
Arial12ptItalic47M100Y25KCenter
Arial12ptItalic47M100Y25KLeft
Arial12ptItalic47M100Y25KRight
Arial24ptBold100Y30KCenter
Arial24ptBold100Y30KLeft
Arial24ptBold100Y30KRight
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_FrameworkFCs;
FrameworkBoundaries
Islands
LargeAreaFeatures
Locations
Mainlands
Seas
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.
Geodatabase Rules
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 Framework feature dataset should exist within the FrameworkAnno 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)
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
Related Features
Related Chapters
Related Products
NTMS 100K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:5 000 000 |
---|
Framework Anno 5MIL
FrameworkAnno5MIL
Framework
Annotation
Type associated with the Framework Feature Dataset for 1:5 000 000 scale
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.
The following annotation classes exist in FrameworkAnno;
ArialNarrow6pt5Center
ArialNarrow6pt5Left
ArialNarrow6pt5Right
Arial14ptBold100Y30KCenter
Arial14ptBold100Y30KLeft
Arial14ptBold100Y30KRight
Arial10ptItalicCenter
Arial10ptItalicLeft
Arial10ptItalicRight
Arial14ptBold75KCenter
Arial14ptBold75KLeft
Arial14ptBold75KRight
Arial5pt5Italic47M100Y25KCenter
Arial5pt5Italic47M100Y25KLeft
Arial5pt5Italic47M100Y25KRight
Arial8ptItalic47M100Y25KCenter
Arial8ptItalic47M100Y25KLeft
Arial8ptItalic47M100Y25KRight
Arial10ptItalic47M100Y25KCenter
Arial10ptItalic47M100Y25KLeft
Arial10ptItalic47M100Y25KRight
ArialNarrow6pt5Italic47M100Y25KCenter
ArialNarrow6pt5Italic47M100Y25KLeft
ArialNarrow6pt5Italic47M100Y25KRight
Arial7pt5ItalicCenter
Arial7pt5ItalicLeft
Arial7pt5ItalicRight
Arial6pt5ItalicCenter
Arial6pt5ItalicLeft
Arial6pt5ItalicRight
Arial8pt5ItalicCenter
Arial8pt5ItalicLeft
Arial8pt5ItalicRight
ArialNarrow6pt5Italic100C9MCenter
ArialNarrow6pt5Italic100C9MLeft
ArialNarrow6pt5Italic100C9MRight
ArialNarrow8ptItalic100C9MCenter
ArialNarrow8ptItalic100C9MLeft
ArialNarrow8ptItalic100C9MRight
ArialNarrow10ptItalic100C9MCenter
ArialNarrow10ptItalic100C9MLeft
ArialNarrow10ptItalic100C9MRight
Arial14ptItalic100C9MCenter
Arial14ptItalic100C9MLeft
Arial14ptItalic100C9MRight
Arial18ptItalic100C9MCenter
Arial18ptItalic100C9MLeft
Arial18ptItalic100C9MRight
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_FrameworkFCs;
FrameworkBoundaries
Islands
LargeAreaFeatures
Locations
Mainlands
Seas
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.
Geodatabase Rules
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 Framework feature dataset should exist within the FrameworkAnno 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)
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
Related Features
Related Chapters
Related Products
NTMS 100K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:10 000 000 |
---|
Framework Anno 10MIL
FrameworkAnno10MIL
Framework
Annotation
Type associated with the Framework Feature Dataset for 1:10 000 000 scale
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.
The following annotation classes exist in FrameworkAnno;
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight
Arial12ptBold100Y30KCenter
Arial12ptBold100Y30KLeft
Arial12ptBold100Y30KRight
Arial5ptItalic47M100Y25KCenter
Arial5ptItalic47M100Y25KLeft
Arial5ptItalic47M100Y25KRight
Arial6ptItalic47M100Y25KCenter
Arial6ptItalic47M100Y25KLeft
Arial6ptItalic47M100Y25KRight
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
Arial6pt5ItalicCenter
Arial6pt5ItalicLeft
Arial6pt5ItalicRight
Arial10ptItalic100C9MCenter
Arial10ptItalic100C9MLeft
Arial10ptItalic100C9MRight
Arial8ptItalic100C9MCenter
Arial8ptItalic100C9MLeft
Arial8ptItalic100C9MRight
Arial7ptItalic100C9MCenter
Arial7ptItalic100C9MLeft
Arial7ptItalic100C9MRight
Arial6ptItalic100C9MCenter
Arial6ptItalic100C9MLeft
Arial6ptItalic100C9MRight
Arial12ptBoldCenter
Arial8ptBoldCenter
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_FrameworkFCs;
FrameworkBoundaries
Islands
LargeAreaFeatures
Locations
Mainlands
Seas
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.
Geodatabase Rules
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 Framework feature dataset should exist within the FrameworkAnno 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.
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
Related Features
Related Chapters
Related Products
NTMS 100K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Gorge
Locations
Framework
Point
A named deep and narrow, steep-sided, usually rocky river valley.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Gorge
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.
Gorge
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the Gorge. This item must 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
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.
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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
The locality point will be placed approximately half way along the length of the gorge. The locality point will be coincident with a vertex on the main watercourse in the gorge, where there is a watercourse. Where there is no watercourse the locality point will be placed central to the gorge.
For Upperscale assignment, selection of locations should be based on the equivalent scale previous edition hardcopy or digital topographic map taking into account any significant changes in a regions population growth or decline, underlying infrastructure or industry change which may impact the importance of an entities potential for recognition or landmark value (including history of area). In general, all localities of regional importance should be included at 1:25000, all localities of a state/territory importance should be included at 1:100000 and only localities of national importance should be assigned values of 1:250000 and greater (eg 1:5000000).
When a Gorge is legitimate for map representation at a specified scale, it will be assigned symbol 2 (Point No Draw) and will be visually denoted by text only.
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
Where a locality gorge name refers to an extensive area the associated Location entity should only be captured once and positioned central to the feature.
A locality of the same code and name should not be repeated within the same MapIndex250K sheet unless it relates to a number of entities sharing the same name.
Map Rules
Related Features
Contours250K (feature class) and Contours 100K (feature class), Horizontal Control Point, Spot Elevation, Watercourse, Watercourse Area, Estuary
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 & 1:250 000 |
---|
Island
Islands
Framework
Polygon
An area of land fully surrounded by the sea.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features | 39 |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
1:25 000 | 39 | |
1:100 000 | 625 | |
1:250 000 | 3906 | |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Island
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the island. This item should be populated where name is known.
STATE/TERRITORY (STATE) [String;Yes(No);30;0;0;Pop_Req] Australian/Foreign State or Territory identifier code;
Acceptable Domain Entries from dm_IslandState;
AUSTRALIAN CAPITAL TERRITORY
EAST TIMOR
INDONESIA
JERVIS BAY TERRITORY
NEW SOUTH WALES
NORTHERN TERRITORY
NOT APPLICABLE
PAPUA NEW GUINEA
QUEENSLAND
SOUTH AUSTRALIA
TASMANIA
VICTORIA
WESTERN AUSTRALIA
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.
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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
This feature refers to offshore islands only.
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 features smaller than the minimum size for data capture will be captured as Offshore Rocks with a RELATIONSHIP of Bare.
For Island feature type SYMBOL100K and SYMBOL250K must not be NULL.
For SYMBOL 100K and SYMBOL250K, islands above the respective minimum size for map representation should be shown with a symbol polygon no draw (thereby being shown as clear space within the ocean). For Islands below the respective minimum size for map representation they should initially be given 'Island to Offshore Rock' symbology. Then these Islands below the respective minimum size for map representation should be reviewed for cartographic clutter (eg overlapping symbols, conflict with other marine information of higher cartographic importance such as lighthouses) and if required have their symbology altered to 'Perennial Water' to mask the existence of a rock at the assigned scale. When reviewing conflict of 'Island to Offshore Rock' symbology against Offshore Rock symbology from the marinehazardpoints feature class, 'Island to Offshore Rock' symbology should be given precedence due to its representation of a bigger land mass above the tidal line.
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
Islands are bounded by Junction, Shoreline and Limit of Data
Islands cannot overlap each other or other polygons in the Framework Dataset.
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
Islands may also be bounded by Sea wall features.
Map Rules
General - All Scales
The island name will appear on the map, where known.
Related Features
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 & 1:250 000 |
---|
Junction
FrameworkBoundaries
Framework
Polyline
An artificial line used to separate adjacent hydrographic areas which have differing attributes and across which flow can occur.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Junction
SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature.
1
DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
Junction
FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (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.
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_Framework.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_Framework.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.
Geodatabase Rules
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
FrameworkBoundaries (feature class) bound all polygons in the Framework Dataset except Large Area Features. For more information on the use of Junction See Section 3 Chapter 5.17.
Junctions will be included in the Framework Dataset where they form part of the coastline, and will replace the equivalent section of Shoreline. They will also appear in the Framework Dataset where they separate two Sea feature types.
Junctions within the framework dataset are generally 3 point lines except where their separate two sea polygons or where more vertices are needed to close the polygon and maintain the correct polygon closing line shape. See Section 3 Chapter 6.9.
Junctions are only used to separate water polygons where there is no physical feature already doing so. They are most commonly used to separate water polygon features with different names.
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
Junctions must be bordered by waterbodies in the Waterbodies Dataset or by the sea on one side in the Framework Dataset.
Map Rules
Related Features
Canal Area, Canal Line, Connector, Island, Lake, Mainland, Town Water Storage, Rural Water Storage, Sea, Shoreline, Watercourse, Watercourse Area, Contours250K (feature class) and Contours 100K (feature class), Estuary
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Large Area Feature
LargeAreaFeatures
Framework
Polygon
A representation that is indicative of the extent of nationally recognized significant regions.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Large Area Feature
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the significant region. This item must 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.
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.
Geodatabase Rules
General - All Scales
Revision of Large Area Features will only be conducted when specifically directed by GEOSCIENCE AUSTRALIA. The only exception to this rule is when the shoreline is spatially adjusted, in which case Large Areas Features will be also be adjusted to maintain consistency.
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
Large Area Features cannot overlap;
Sea
Where a Large Area Feature edge (feature class polygon) is within 50 metres of and runs alongside the Shoreline they must be coincident with each other.
A Place Name (feature type) should not duplicate the representation of features already defined in the Large Area Features feature class.
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
General - All Scales
When a Large Area Feature occupies a spatial extent greater than or equal to 5% of the applicable map index (including the bleed edges), it will be labelled with its name. Annotation representing a Large Area Features will be placed within its polygon boundary.
Related Features
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 & 1:250 000 |
---|
Limit Of Data
FrameworkBoundaries
Framework
Polyline
The line bounding the limits of known source material or the edge of the defined NTDB.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Limit Of Data
SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature.
4
DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
LimitOfData
FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see (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.
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_Framework.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_Framework.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.
Geodatabase Rules
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
The limit of Data feature will bound or complete all polygon features whose extent can not be fully determined by source material or where the associated polygon feature is adjacent to the edge of the database. For more information on the use of Limit Of Data Line See Section 3 Chapter 5.17.
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
Related Features
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 & 1:250 000 |
---|
Mainland
Mainlands
Framework
Polygon
The area of continental Australia including Tasmania.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Mainland
STATE/TERRITORY (STATE) [String;Yes(No);30;0;0;Pop_Req] Australian/Foreign State or Territory identifier code;
Acceptable Domain Entries from dm_MainlandState are;
AUSTRALIAN CAPITAL TERRITORY
JERVIS BAY TERRITORY
NEW SOUTH WALES
NORTHERN TERRITORY
QUEENSLAND
SOUTH AUSTRALIA
TASMANIA
VICTORIA
WESTERN AUSTRALIA
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.
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.
Geodatabase Rules
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
The Mainland feature will be bounded by a combination of Shoreline, State border and Junction features.
Mainland excludes Sea areas, and Islands surrounded by the Sea.
No gaps should exist between the mainland and sea polygons.
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
Mainland cannot overlap marine areas except Foreshore Flats in estuarine areas (see Foreshore Flat).
Map Rules
Related Features
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Mountain
Locations
Framework
Point
A named markedly elevated landform bounded by steep slopes and rising to prominent ridges and individual peaks.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Mountain
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.
Mountain
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the Mountain. This item must 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
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.
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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
Includes features such as mountains, peaks and hills. The locality point will be positioned exactly as shown on the base material/digital data. If a positioning point is not shown on the map then other compilations or large scale maps may be used to position the locality feature at its true planimetric position.
Mountains will be named. See Section 2 chapter 5.10 for naming conventions.
If multiple peaks are confirmed to be associated with the same name, then each individual peak should be captured as a Mountain and attributed accordingly.
For Upperscale assignment, selection of locations should be based on the equivalent scale previous edition hardcopy or digital topographic map taking into account any significant changes in a regions population growth or decline, underlying infrastructure or industry change which may impact the importance of an entities potential for recognition or landmark value (including history of area). In general, all localities of regional importance should be included at 1:25000, all localities of a state/territory importance should be included at 1:100000 and only localities of national importance should be assigned values of 1:250000 and greater (eg 1:5000000).
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
If a Mountain feature appears on the latest previous edition map with a name and spot identifier only and a matching spot elevation does not exist then the Mountain feature type will have a symbol code of 52 ( Spot Elevation or Mountain) , otherwise a symbol code of symbol 2 (Point No Draw).
Where there is a known elevation for the Mountain feature it will be cloned as a Spot elevation (see Spot elevation). Should the spot elevation need to be moved (see Section 3 chapter 6.6) the Mountain will be moved with it.
A locality of the same code and name should not be repeated within the same MapIndex250K sheet unless it relates to a number of entities sharing the same name eg 'The Three Brothers'.
Map Rules
General - All Scales
Mountains, peaks & hills will be named. See Section 2 chapter 5.10 for naming conventions.
Related Features
Horizontal Control Point, Spot Elevation, Contours250K (feature class) and Contours 100K (feature class)
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Pass
Locations
Framework
Point
A named low and passable gap through a mountain range.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Pass
SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature.
6
DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
Pass
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the pass. This item must 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
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.
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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
Named passes on the road network will be included. Any other named passes included on the latest previous edition map or base material/digital data will be included. The locality point will be at the highest point on the pass. Where a pass is transversed by a road feature, the point will be coincident with a vertex on the road. If necessary, a vertex will be created on the road coincident with the highest point on the road.
For Upperscale assignment, selection of locations should be based on the equivalent scale previous edition hardcopy or digital topographic map taking into account any significant changes in a regions population growth or decline, underlying infrastructure or industry change which may impact the importance of an entities potential for recognition or landmark value (including history of area). In general, all localities of regional importance should be included at 1:25000, all localities of a state/territory importance should be included at 1:100000 and only localities of national importance should be assigned values of 1:250000 and greater (eg 1:5000000).
When a Pass is legitimate for map representation at a specified scale, it will be assigned symbol 2 (Point No Draw) and will be visually denoted by text only.
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
Where a locality pass name refers to an extensive area the associated Location entity should only be captured once and positioned central to the feature.
Map Rules
Related Features
Horizontal Control Point, Dual Carriageway, Standard Road, Vehicular Track, Spot Elevation, Contours250K (feature class) and Contours 100K (feature class)
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Place Name
Locations
Framework
Point
A named place or area.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Place Name
SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature.
9
DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
PlaceName
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name given to the place. This item must 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
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.
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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
This category will be used to show localities that do not fall into any other category.
Where a Place Name point has previously been captured to represent a Large Area Feature (in the Framework Feature Dataset), it should not be retained within the NTDB.
The Locality point for area features, not associated with a Large Area Feature (Feature Type) in the Framework Dataset, will be located where the name was located in the base material/digital data or where text was placed on the latest previous edition map.
Text & the locality point for Indigenous Lands shown on Appendix O will be placed within the limits of the area. If the area on Appendix O occupies less than 20% of the area of the map (defined by the applicable Map Index) it will not be shown.
Suburb names included on the latest previous edition map and confirmed on the authorised revision source material for suburb names will be included as place names.
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.
For Upperscale assignment, selection of locations should be based on the equivalent scale previous edition hardcopy or digital topographic map taking into account any significant changes in a regions population growth or decline, underlying infrastructure or industry change which may impact the importance of an entities potential for recognition or landmark value (including history of area). In general, all localities of regional importance should be included at 1:25000, all localities of a state/territory importance should be included at 1:100000 and only localities of national importance should be assigned values of 1:250000 and greater (eg 1:5000000).
In general, Place Names will use the Symbol 2 (Point No Draw). Two other symbols are legitimate in specific situations indicated in the paragraph below and in the Inter Feature Relationship Rules External to the Database.
Small features with an identifiable location that are not represented by another feature class will be represented using symbol 53 (e.g. historical markers, rocks, etc).
'Other Waters' indicated on Appendix E will not be shown as Place Names.
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
A Place Name (feature type) should not duplicate the representation of features already defined in the Large Area Features feature class.
For every unique Built Up Area name a corresponding feature must exist in either the Populated Place or Place Name feature types (dependant on population) of the same name. Only one Populated Place or Place Name feature type entity should exist to correlate to a Built Up Area which is broken into disconnected sections each with identical attributes.
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
Places with a population of less than 200 and a Built-up area not large enough to be shown as a polygon will be positioned coincident with a vertex or node on the road network. These places will have a symbol of 420. Note: symbol 420 will only be used where the place name is associated with a small built up area.
In general, for each locality place name, the associated location entity should only be captured once and positioned central to the feature. For place names which extend over a vast area (eg 'GREAT DIVIDING RANGE') overlapping 2 or more MapIndex250K sheets, will have the location entity placed in the bleed area of the overlapping sheets and only where this can not properly represent the whole area name may duplicates be made. (eg for the 'GREAT DIVIDING RANGE' a duplicate may need to occur in the northern bleed of every second MapIndex250K sheet.)
A locality of the same code and name should not be repeated within the same MapIndex250K sheet unless it relates to a number of entities sharing the same name.
For every unique Built Up Area name a corresponding feature must exist in either the Populated Place or Place Name feature types (dependant on population) of the same name. Only one Populated Place or Place Name feature type entity should exist to correlate to a Built Up Area which is broken into disconnected sections each with identical attributes.
Map Rules
General - All Scales
Where symbol 420 is used, the symbol will mask all other detail.
Related Features
Building Area (feature class) and Building Point (feature class), Built Up Area, Distance Indicator, Large Area Feature, Populated Place, Railway Station, Sea
Related Chapters
Section 1 Chapters 3.8.1
Section 2 Chapter 5.3
Section 3 Chapters 5.3, 5.11.1, 5.11.2 and 6.5
Appendix E
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Road Junction
Locations
Framework
Point
A named intersection of two or more roads.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Road Junction
SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature.
7
DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
RoadJunction
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the Road Junction. This item must 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
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.
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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
Only named road junctions are included.
For Upperscale assignment, selection of locations should be based on the equivalent scale previous edition hardcopy or digital topographic map taking into account any significant changes in a regions population growth or decline, underlying infrastructure or industry change which may impact the importance of an entities potential for recognition or landmark value (including history of area). In general, all localities of regional importance should be included at 1:25000, all localities of a state/territory importance should be included at 1:100000 and only localities of national importance should be assigned values of 1:250000 and greater (eg 1:5000000).
When a Road Junction is legitimate for map representation at a specified scale, it will be assigned symbol 2 (Point No Draw) and will be visually denoted by text only.
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
The position of the location will be coincident with the node of the road intersection.
Map Rules
Related Features
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 & 1:250 000 |
---|
Sea
Seas
Framework
Polygon
The water area surrounding the Australian continent and its offshore islands.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Sea
OCEAN NAME (OCEANNAME) [String;Yes;20;0;0;Pop_Req] Ocean Name of represented area. (See Appendix E.)
Acceptable Domain Entries from dm_OceanNames;
INDIAN OCEAN
SOUTH PACIFIC OCEAN
SOUTHERN OCEAN
SEA NAME (SEANAME) [String;Yes;12;0;0;Pop_Wk] Sea Name of represented area. (See Appendix E.)
Acceptable Domain Entries from dm_SeaNames;
ARAFURA SEA
CORAL SEA
TASMAN SEA
TIMOR SEA
OTHER WATER NAME (OTHERWATERNAME) [String;Yes;22;0;0;Pop_Wk] Other Waters Name of represented area. (See Appendix E)
Acceptable Domain Entries from dm_OtherWaterNames;
BASS STRAIT
GREAT AUSTRALIAN BIGHT
GREAT BARRIER REEF
GULF OF CARPENTARIA
GULF OF PAPUA
JOSEPH BONAPARTE GULF
TORRES STRAIT
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.
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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
The boundaries and names of Seas will be as defined by Appendix E - 'Limits of Oceans and Seas'.
The sea feature type will be used for seas, oceans and other waters as defined on Appendix E.
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
The boundary between two seas/oceans/other waters will be shown by a junction feature.
Seas will be bounded by Junction, Shoreline and Limit of Data features.
Sea cannot overlap other polygons in the Framework Dataset .
No gaps should exist between the sea and either the Mainland or Island polygons as appropriate.
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
Sea may also be partially bounded by Sea wall features.
Map Rules
1:100 000
Where space permits, areas of sea will include the note:
'CAUTION: THIS MAP IS NOT TO BE USED
FOR MARITIME NAVIGATION PURPOSES
Refer to the appropriate hydrographic chart for depth information'
The note will be in black, on three lines broken as above and centre justified. The first two lines will be AN 10 point all caps and the third line will be AN 5 point caps and lower case.
1:250 000
Where space permits, areas of sea will include the note:
'CAUTION: THIS MAP IS NOT TO BE USED
FOR MARITIME NAVIGATION PURPOSES
Refer to the appropriate hydrographic chart for depth information'
The note will be in black, on three lines broken as above and centre justified. The first two lines will be ZC 10 point all caps and the third line will be ZC 5 point caps and lower case.
General - All Scales
The names of seas and oceans and other waters will be shown.
Related Features
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 & 1:250 000 |
---|
Shoreline
FrameworkBoundaries
Framework
Polyline
A line depicting the boundary of a mainland, island or sea.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Shoreline
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.
Shoreline
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.
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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
When bounding sea and estuarine areas, the line is indicative of the position of mean high water. The exception is in Mangroves, where the line is indicative of the position of the seaward side of the mangroves.
The coastline of both the mainland and islands is defined by a combination of shoreline and junction. For more information on when junction should be used in precedence to shoreline, see the junction feature type for the framework dataset.
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
FrameworkBoundaries (feature class) bound all polygons in the Framework Dataset except Large Area Features. For more information on the use of Shoreline See Section 3 Chapter 5.17.
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
Related Features
Built Up Area, Culture (feature dataset, polygon feature classes), Junction, Contours250K (feature class) and Contours 100K (feature class), Watercourse, Waterbodies (feature dataset, polygon feature classes), Canal Line, Connector, Island, Mainland, Sea, Foreshore Flat, Reef, Shoal, Large Area Feature, AdministrationAreas (feature class), NativeVegetationAreas (feature class) and CultivatedAreas (feature class), Cliff
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 & 1:250 000 |
---|
State Border
FrameworkBoundaries
Framework
Polyline
The boundary defining the division of the Commonwealth of Australia into State/Territory administrations.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
State Border
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.
StateBorder
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.
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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
State Borders which do not follow physical features will be imported from the Geoscience Australia GEODATA 100K Coast Product. State borders which follow physical features will be coincident with those features.
Where a state border coincides with a lock symbol it is logical that the border symbol should be broken and the lock symbol shown. In such circumstances, the state border symbol may be symbolised to symbol number '1' LineNoDraw.
Inter-Feature Relationship Rules - Internal to Associated Dataset
General - All Scales
FrameworkBoundaries (feature class) bound all polygons in the Framework Dataset except Large Area Features. For more information on the use of State Border See Section 3 Chapter 5.17.
State borders cannot overlap Sea.
Inter-Feature Relationship Rules - External to Associated Dataset
Map Rules
General - All Scales
State borders will be labelled with State names (See Section 2, 4.6)
State borders 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.)
Related Features
Fisheries Jurisdiction Boundary, International Boundary General, International Boundary Land, International Boundary Water, Limit Of Territorial Sea, Protection Zone, Seabed and Fisheries Jurisdctn, Seabed Jurisdiction Line, Mainland
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Waterbody Island
Locations
Framework
Point
A named island within an inland waterbody or forming part of the shoreline.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Waterbody Island
SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature.
8
DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.
WaterbodyIsland
NAME (NAME) [String;Yes;60;0;0;Pop_Dep]
The name of the Waterbody Island. This item must 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
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.
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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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_Framework.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.
Geodatabase Rules
General - All Scales
Only named inland islands and named islands which form part of the shoreline will be depicted. (See Section 3 6.9.7). The locality point will be placed on land at the approximate centre of the island. Offshore islands will be named as an attribute of the polygon, see Island.
For Upperscale assignment, selection of locations should be based on the equivalent scale previous edition hardcopy or digital topographic map taking into account any significant changes in a regions population growth or decline, underlying infrastructure or industry change which may impact the importance of an entities potential for recognition or landmark value (including history of area). In general, all localities of regional importance should be included at 1:25000, all localities of a state/territory importance should be included at 1:100000 and only localities of national importance should be assigned values of 1:250000 and greater (eg 1:5000000).
When a Waterbody Island is legitimate for map representation at a specified scale, it will be assigned symbol 2 (Point No Draw) and will be visually denoted by text only.
Inter-Feature Relationship Rules - Internal to Associated Dataset
Inter-Feature Relationship Rules - External to Associated Dataset
General - All Scales
Where a locality waterbody island name refers to an extensive area the associated Location entity should only be captured once and positioned central to the feature.
Map Rules
Related Features
Related Chapters
Related Products
GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K
Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.
Topic contact: mapfeedback@ga.gov.au Last updated: January 20, 2012