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

Bench Mark

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

CODE (CODE) [String;Yes;24;0;0;Pop_Dep]

Code which identifies the benchmark (to be populated if information within revision source material supplied). Alpha characters in this field are to be in the case used on the revision source material.

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

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

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

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

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

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

General - All Scales

No new features will be added.

This feature class is for archival purposes only and is not to be altered/adjusted for any map/data products.

Bench Marks currently existing in the NTDB will be retained.

The elevation will not be duplicated in the TextNote field.

Bench marks will be TextNoted 'BM' in the data.

General - All Scales

Bench marks must fit logically with the Contours feature class.

General - All Scales

Bench marks will be labelled 'BM' followed by the elevation to the nearest metre eg BM1902.

Connector Discontinuity, Connector Standard, Depression Contour, Interpolated Contour, Standard Contour, Horizontal Control Point, Spot Elevation

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

Horizontal Control Point

BEACON (BEACON) [String;Yes;100;0;0;Pop_Wk] A description of the type of associated Navigation aid if it exists;

CODE (CODE) [String;Yes;24;0;0;Pop_Dep]

The code which identifies the Horizontal control point (to be populated if information within revision source material supplied). Alpha characters in this field are to be in upper case.

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

HORIZONTAL ORDER (ORDEROFACCURACY) [String;Yes;2;0;0;Pop_Req] The horizontal control point's horizontal accuracy order.

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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

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

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

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

General - All Scales

Horizontal control points will be selected from the Horizontal control points data file supplied by the Geodesy Group of Geoscience Australia.

The most recent record of each horizontal control point will be utilised for the NTDB, two or more points should not be used to indicate the same feature.

All features meeting the 3 criteria set out below will be assigned a Upper Scale of 100 000 as a minumum:

• Only permanently marked and monumented horizontal control points (ie those with a beacon, cairn or pole) that have elevations will be shown.
• Only points with a horizontal accuracy of zero, first, second and third order will be shown. Except for the application of the datum shift, Horizontal control points will not be moved from the coordinates supplied in the reference material.
• The CODE field will be populated with the alphanumeric designations from the National Geodetic Database. The alphanumeric designation will be found in the name 1, name 2 or name 3 field in the National Geodetic Database. Where there is no alphanumeric designation code this field will be left blank. Only alphanumeric designations containing letters and numerals will be included. Solely numeric designations will not be included nor will designations including words or place names such as 'Ravensthorpe 1' or 'log2'. Horizontal control point names from the name 1, name 2 or name 3 field will not be shown in the code field. Where more than one alphanumeric designation exists in the National Geodetic Database for a Horizontal control point an arbitrary choice will be made.

Features meeting the above criteria for Upperscale of 100 000 and the following sentence will be assigned a Upper Scale of 250 000 as a minumum:

'No more than fifty points will be included on a standard 1:250K map area. Where the land area of the map differs from the standard size, the maximum number will be in proportion. If the number of monumented stations in each defined map area exceeds fifty all lowest order stations will be downgraded to an Upperscale of 100 000. This process will be repeated until the number is less than the maximum. This process will take precedence over the overlap rules in Section 3 chapter 5.3'

For features to be assigned an Upperscale 1 000 000, they must be required to represent specific mountain elevations (which do not have corresponding spot elevation features) on either WAC or IMW charting, see previous hardcopy or digital map editions for more information.

General - All Scales

Horizontal control points cannot overlap;
Sea, Lake, Flood Irrigation Storage, Town Water Storage, Rural Water Storage, Canal Area, WatercourseAreas (feature class), BuildingAreas (feature class), Settling Ponds, Aquacultural Ponds, Salt Evaporator and Mine Area

The Contours feature class and Horizontal Control Points will not contradict each other.

General - All Scales

Where a horizontal control point and another cultural feature such as a Landmark Point feature are adjacent or coincident, precedence will be given to the other cultural feature (see Section 3 chapter 6.6).

Alphanumeric designations will be shown when the topographic feature on which the horizontal control is situated has no name; otherwise the feature name will take precedence (See Section 2 chapter 5.13).

Bench Mark, Vertical Obstruction, Mountain, Contours100K (feature class), Contours250K (feature class), ContoursWAC (feature class), Spot Elevation

Section 1 Chapter 3.7.5
Section 2 Chapter 5.13
Section 3 Chapters 5.3, 6.6

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

ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.

The following annotation classes exist in SurveyMarksAnno;
Arial6ptItalicLeft
Arial6ptItalicRight

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

Acceptable Domain Entries from dm_SurveyMarksFCs;
Benchmarks
HorizontalControlPoints

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

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

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

General - All Scales

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

Only Annotation associated with, or derived from, entities in feature classes grouped within the SurveyMarks feature dataset should exist within the SurveyMarksAnno feature class.

Wherever possible annotation should be stored using the subclasses indicated under AnnotationClassID. Annotation stored as inline text should be kept to a minimum.

Type for large polygons and long linear features may be held in an annotation feature for each word to allow for spacing and differences in orientation, see Section 2 chapter 4.

Annotation should not contain any HTML tags within the blob element, nor should it contain any special characters.

Editing and placement of Annotation should be conducted in the appropriate MGA 1994 zone to ensure the spatial position of type on the map face can be correctly represented.

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

Section 2 Chapters 5, 9

NTMS 100K

ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.

The following annotation classes exist in SurveyMarksAnno;
Arial5ptItalicLeft
Arial5ptItalicRight
Arial8ptItalicLeft
Arial8ptItalicRight

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_SurveyMarksFCs;
Benchmarks
HorizontalControlPoints

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

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

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

General - All Scales

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

Only Annotation associated with, or derived from, entities in feature classes grouped within the SurveyMarks feature dataset should exist within the SurveyMarksAnno feature class.

Wherever possible annotation should be stored using the subclasses indicated under AnnotationClassID. Annotation stored as inline text should be kept to a minimum.

Type for large polygons and long linear features may be held in an annotation feature for each word to allow for spacing and differences in orientation, see Section 2 chapter 4.

Annotation should not contain any HTML tags within the blob element, nor should it contain any special characters.

Editing and placement of Annotation should be conducted in the appropriate MGA 1994 zone to ensure the spatial position of type on the map face can be correctly represented.

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

Section 2 Chapters 5, 10

NTMS 100K

ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.

The following annotation classes exist in SurveyMarksAnno;
Arial6ptItalic47M100Y25KCenter
Arial6ptItalic47M100Y25KLeft
Arial6ptItalic47M100Y25KRight

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_SurveyMarksFCs;
Benchmarks
HorizontalControlPoints

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

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

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

General - All Scales

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

Only Annotation associated with, or derived from, entities in feature classes grouped within the SurveyMarks feature dataset should exist within the SurveyMarksAnno feature class.

Wherever possible annotation should be stored using the subclasses indicated under AnnotationClassID. Annotation stored as inline text should be kept to a minimum.

Type for large polygons and long linear features may be held in an annotation feature for each word to allow for spacing and differences in orientation, see Section 2 chapter 4.

Annotation should not contain any HTML tags within the blob element, nor should it contain any special characters.

Editing and placement of Annotation should be conducted in the appropriate Simple Conic Projection with two standard parallels of 18 degrees south and 36 degrees south to ensure the spatial position of type on the map face can be correctly represented.

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

Section 2 Chapters 5, 12

NTMS 100K