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

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

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

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;

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

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

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

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

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

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

50
0 - see section 3 chapter 6.6

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

General - All Scales

No new features will be added. Bench Marks currently existing in the TOPO250K 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 and Spot Elevation

GEODATA TOPO250K, NTMS 250K

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

Horizontal Control Point

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

The name of the feature the Horizontal control point is located on (see Geodatabase Rules for population requirements).

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

51
0 - see Section 3 chapter 6.6 Mountains, Spot Elevations and Horizontal Control Points

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

Currently not used by symbology; 0

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

Currently not used by symbology; 0

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

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

1:25 000

All features meeting the criteria set out in the general rules will be assigned a Upper Scale of 100 000 as a minumum.

1:100 000

All features meeting the criteria set out in the general rules will be assigned a Upper Scale of 100 000 as a minumum.


Features meeting 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 the working database exceeds fifty all lowest order stations will be dropped. This process will be repeated until the number is less than the maximum. This process will take precedence over the overlap rules in Section3 chapter 5.3'

1:250 000

No more than fifty points will be included on a standard 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 the working database exceeds fifty all lowest order stations will be dropped. This process will be repeated until the number is less than the maximum. This process will take precedence over the overlap rules in Section3 chapter 5.3


The NAME field will be populated with the name of a prominent feature upon which the horizontal control point is situated. This feature must have a defined position within a localised area and should be represented elsewhere in the database under a different feature class, such as a locality mountain or a locality place name of clear locality (symbolised with symbol 52). Large area features such as ranges are not appropriate. The National Geodetic Database items name 1, name 2 and name 3 will not be used to populate the horizontal control point name field.

General - All Scales

Horizontal control points will be selected from the Horizontal control points data file. 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.

General - All Scales

Horizontal control points cannot overlap;
Sea, Lake, Flood Irrigation Storage, Town Rural Storage, Canal Area, Watercourse Area, Building Area, 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).

Auxiliary Contour, Bench Mark, Connector Discontinuity, Connector Standard, Depression Contour, Interpolated Contour, Standard Contour, Vertical Obstruction, Mountain and 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;
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.

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

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

General - All Scales

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

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

Section 2 Chapters 5, 9, 10

NTMS 100K