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

Bench Mark

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

CODE (CODE) [String; Yes; 24; 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; 0; 0; 36; 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 (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
- / - / 100

ELEVATION ACCURACY (ELEVATIONACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the vertical positional accuracy. The default value, when not specified in project instructions, will be as follows;
- / - / 1

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; Pop_Req] (Link to Symbol Dictionary)Symbol number/s applicable;

50
0 - see section 3 chapter 6.6

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

Currently not used by symbology; 0

ORIENTATION (ORIENTATION) [Short Integer; Yes; 3; Pop_Dep] Orientation in whole degrees from East going anti-clockwise;
Currently not used by symbology; 0

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

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.  

Bench marks must fit logically with the Contours feature class.

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 

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

Horizontal Control Point

NAME (NAME) [String; Yes; 60; Pop_Dep] The name of the feature the Horizontal control point is located on (see Geodatabase Rules for population requirements).

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

CODE (CODE) [String; Yes; 24; 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.

HORIZONTAL ORDER (ORDEROFACCURACY) [String; Yes; 6; Pop_Req] The horizontal control point’s horizontal accuracy order  

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
This primary source used to determine the spatial location of a feature (For use in TOPO100K only;).

ATTRIBUTE RELIABILITY (ATTRIBUTERELIABILITY) [Date; Yes; 0; 0; 36; 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; Pop_Req]
The primary source used to populate the attribute fields of a feature (For use in TOPO100K only;).

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the horizontal positional accuracy.The default value, when not specified in project instructions, will be as follows;
10 / 10 / 10

ELEVATION ACCURACY (ELEVATIONACCURACY) [Short Integer; No; 4; Pop_Req] The standard deviation of the vertical positional accuracy. The default value, when not specified in project instructions, will be as follows;
1 / 1 / 1

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

UNIQUE FEATURE IDENTIFIER (UFI) [String; Yes; 10; Pop_Aut] Alphanumeric feature identifier defined for GEODATA SERIES 2 (For use in TOPO250K only;) (see Section 3 chapter 5.14)

FEATURE CREATION DATE (CREATIONDATE) [Date; Yes; 0; 0; 36; 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; 0; 0; 36; Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

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

SYMBOL (SYMBOL) [Short Integer; No; 4; 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; 8; 4; Pop_Dep]

Currently not used by symbology; 0

ORIENTATION (ORIENTATION) [Short Integer; Yes; 3; Pop_Dep] Orientation in whole degrees from East going anti-clockwise;
Currently not used by symbology; 0

TEXT NOTE (TEXTNOTE) [String; Yes; 50; 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.

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 double zero, zero, first, second and third order will be shown.

Horizontal Control Points should not be moved from the location in the revision source material.

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.

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.
 
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 horizontal control has no feature name. If a horizontal control point has a feature name, the alphanumeric designation will not be shown (See Section 2 chapter 5.13).  

Except for the application of the datum shift, Horizontal control points will not be moved from the coordinates supplied.  

Horizontal control points will not appear over;
Sea, Lake, Flood Irrigation Storage, Town Rural Storage, Canal Area, Watercourse Area,Building Area and Mine Area.

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

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 horizontal control has no feature name. If a horizontal control point has a feature name, the alphanumeric designation will not be shown (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 6.6