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

Airport

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.

Airport

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

The name of the licenced, certified or registered civilian Airport (see Geodatabase Rules for population requirements.)

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;

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;

701

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

General - All Scales

Only operational Aircraft Facilities found in the reference material supplied for Aircraft Facilities and are clearly visible on imagery, will be included regardless of whether it was shown on/in the base material/digital data. Abandoned facilities will not be shown.

The classification of facilities will be done according to the Enroute Supplement Australia published by Airservices Australia and supplied as reference material. Only facilities shown as licensed, certified or registered in the Enroute Supplement will be represented using the Airport feature type. If the facility is not listed in the supplement or is listed as unlicensed, uncertified or unregistered it will be represented using the Landing Ground feature type.

Only civilian licensed, certified or registered facilities will be named. The name should be that of the airport as signposted. Military aircraft facilities will not be named nor given any other indication of their military nature.

For civilian licensed, certified or registered facilities, the suffix of 'Airport' or 'Aerodrome' will be included in the name. When unknown the form of suffix used will be that used on/in the base material/digital data (e.g. existing TOPO100K NTDB, previous edition map or state information). If not previously indicated on/in the base material/digital data the default suffix 'Aerodrome' will be used.

When supplied with a change guide for aviation the above specifications will be taken into account unless otherwise documented.

The Airport feature will be centred on the longest sealed runway. If no sealed runways exist the Airport feature will be centred over the main unsealed runway.

For Airports the position, length and orientation of sealed runways will be shown. If there are no sealed runways, only the length and orientation of the main unsealed runway will be shown. See Runway centreline feature.

General - All Scales

Helipads will be not be captured when associated with an airport or landing ground

General - All Scales

Runway centrelines for all licenced aircraft facilities will be captured.

Airports cannot overlap; Sea, Perennial Waterbodies,Aquaculture Area

General - All Scales

Airports will be named on the map where named in the NTDB.

Military aircraft facilities will be symbolised in the same way as civil facilities and will not be given any indication of their military nature.

Runway Edge, Airport Area, Runway centreline, Taxiway, Heliport, Landing Ground (AircraftFacilityPoints)

Section 1 chapter 3.8.1
Section 3 chapters 5.10, 6.6, 6.10

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.

Airport Area

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

Name of aircraft facility.

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;

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.

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

0

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

The classification of facilities will be done according to the Enroute Supplement Australia published by Airservices Australia and supplied as reference material. Only facilities shown as licensed, certified or registered in the Enroute Supplement will be represented using the Airport Area feature type.

Abandoned airports will not be shown.

General - All Scales

A Landing Ground must not overlap;
Airport Area

Runways, Aprons and Taxiways must be fully contained within the Airport Area feature type.

Airport, Heliport, Landing Ground (Aircraft Facility Area), Runway, Runway Edge, Apron, Taxiway

Section 1 chapter 3.8.1
Section 3 chapter 5.10, 5.18, 5.19, 6.6, 6.10

GEODATA LITE TOPO100K, NTMS 100K

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

Apron

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.

Apron

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

This field is not applicable to this subtype and therefore is currently not to be populated;

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

This field is not applicable to this subtype and therefore is currently not to be populated;

AIRPORT DESIGNATION (AIRPORTDESIGNATION) [String;Yes;25;0;0;Pop_Req] International or Domestic Designation for Airport;

This field is not applicable to this subtype and therefore is currently not to be populated;

ELEVATION IN FT (ELEVATIONFT) [Single;Yes;0;6;2;Pop_Wk] The elevation of the entity in feet above sea level.

This field is not applicable to this subtype and therefore is currently not to be populated;

ICAO DESIGNATION (ICAODESIGNATION) [String;Yes;4;0;0;Pop_Wk] The designation code provided by the International Civil Aviation Organization (ICAO);

This field is not applicable to this subtype and therefore is currently not to be populated;

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

This field is not applicable to this subtype and therefore is currently not to be populated;

SURFACE (SURFACE) [String;Yes;24;0;0;Pop_Req] The description of the landing surface of the Aircraft Facility;

This field is not applicable to this subtype and therefore is currently not to be populated;

USAGE (USAGES) [String;Yes;75;0;0;Pop_Wk] The description of the type of civil and/or military use of the Aircraft Facility;

This field is not applicable to this subtype and therefore is currently not to be populated;

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see 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;

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

VERIFICATION STATUS (VERIFICATIONSTATUS) [String;Yes;30;0;0;Pop_Req] The verification status of the confirmation of Aircraft Facility existence (and where available attribution);

This field is not applicable to this subtype and therefore is currently not to be populated;

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

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.

This field is not applicable to this subtype and therefore is currently not to be populated;

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

Runways, Aprons and Taxiways must be fully contained within the Airport Area feature type.

Aprons must not overlap Runways.

Where Aprons abut Runways and Taxiways in reality they should be made coincident along those portions of the features.

The end nodes of taxiways shall be coincident with a vertex on the perimeter of a Aircraft Facility Area (feature class) polygon, the end nodes of two or more intersecting taxiways or with a building representing its destination point.

General - All Scales

Aprons will not be represented on the map.

Runway Edge, Airport Area, Taxiway , Landing Ground (AircraftFacillityLines), Runway, Heliport, Building Point, Building Area

Section 3 Chapter 5.3

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 AviationAnno;
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptLeft
ArialNarrow7ptRight

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_AviationFCs;
AircraftFacilityAreas
AircraftFacilityLines
AircraftFacilityPoints
AirportAreas
NavigationAids
NavigationLights

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 Aviation feature dataset should exist within the AviationAnno 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 Chapter 5.3, 5.5, 5.6, 9, 10

NTMS 100K

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

Heliport

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.

Heliport

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

Name of aircraft facility (see Geodatabase Rules for population requirements.)

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

ELEVATION IN FT (ELEVATIONFT) [Single;Yes;0;6;2;Pop_Wk] The elevation of the entity in feet above sea level.

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_AviationStatus;
Decommissioned
Operational
Abandoned
Under Construction
Unknown

USAGE (USAGES) [String;Yes;75;0;0;Pop_Wk] The description of the type of civil and/or military use of the Aircraft Facility;

Acceptable Domain Entries from dm_Usages;
Civil
Civil/Military
Military
Customs
Civil Water

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;

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

VERIFICATION STATUS (VERIFICATIONSTATUS) [String;Yes;30;0;0;Pop_Req] The verification status of the confirmation of Aircraft Facility existence (and where available attribution);

Acceptable Domain Entries from dm_VerificationStatus;
Agency Confirmation
Field Verified
Private Contact Confirmation
Unverified

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

708
0 - see Geodatabase rules

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

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:100 000

Helipads will be included within the boundaries of another Aircraft facility, a Builtup Area or a Recreation Area Polygon, however it will only be symbolised if space and cartographic generalisation permits.

Only heliports with an status of 'Operational' will be symbolised. All other status categories will be assigned the symbol '0'.

1:250 000

Helipads will be not be captured when they exist within the boundaries of another Aircraft Facility, Builtup Area or Recreation Area polygon.

Only operational facilities will be retained or captured. Abandoned facilities will not be included in the database.

General - All Scales

Helipads will be named where named in revision material supplied. The exception is military helipads which will not be named nor given any other indication of their military nature.

1:25 000

Helipads associated with an Airport Area or Landing Ground will be given an upperscale entry reflective of its unacceptability at 1:250 000 (e.g within the range of 0 to 100 000).

1:100 000

Helipads associated with an Airport Area or Landing Ground will be captured but attributed with an upperscale entry reflective of its unacceptability at 1:250 000.(e.g within the range of 0 to 100 000).

1:250 000

Helipads will be not be captured when associated with an airport or landing ground

General - All Scales

Heliport cannot overlap; Pondage Area (Feature Class), Cemetery Area, Rubbish Tip, Rapid Area

1:25 000

Helipads within the boundaries of another Aircraft facility, Builtup Area or a Recreation Area Polygon will only be symbolised if space and cartographic generalisation permits.

1:100 000

Helipads within the boundaries of another Aircraft facility, Builtup Area or a Recreation Area Polygon will only be symbolised if space and cartographic generalisation permits.

General - All Scales

Helipads will not be named.

Only heliports with an status of 'Operational' will be represented on the map face.

Airport Area,Runway, Landing Ground, Taxiway

Section 1 chapter 3.8.1
Section 3 chapter 5.3, 6.6, 6.10

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

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

Landing Ground

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.

LandingGround

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

This field is not applicable to this subtype and therefore is currently not to be populated;

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

This field is not applicable to this subtype and therefore is currently not to be populated;

ELEVATION IN FT (ELEVATIONFT) [Single;Yes;0;6;2;Pop_Wk] The elevation of the entity in feet above sea level.

SEASONAL (LANDINGACCESS) [String;Yes;60;0;0;Pop_Wk] The description of the ability to access the landing facility by an aircraft caused by weather or seasonal consideration;

Acceptable Domain Entries from dm_LandingAccess;
Year Round
Weather Permitting
Seasonal
Unknown

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_AviationStatus;
Decommissioned
Operational
Abandoned
Under Construction
Unknown

SURFACE (SURFACE) [String;Yes;24;0;0;Pop_Req] The description of the landing surface of the Aircraft Facility;

Acceptable Domain Entries from dm_Surface;
Grass
Earthern
Bitumen
Concrete
Water
Unknown
Gravel

USAGE (USAGES) [String;Yes;75;0;0;Pop_Wk] The description of the type of civil and/or military use of the Aircraft Facility;

Acceptable Domain Entries from dm_Usages;
Civil
Civil/Military
Military
Customs
Civil Water

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;

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

VERIFICATION STATUS (VERIFICATIONSTATUS) [String;Yes;30;0;0;Pop_Req] The verification status of the confirmation of Aircraft Facility existence (and where available attribution);

Acceptable Domain Entries from dm_VerificationStatus;
Agency Confirmation
Field Verified
Private Contact Confirmation
Unverified

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

703

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.

General - All Scales

Aircraft Facilities must be confirmed using approved reference or supporting material. If a producer is unable to verify the status or existence of an Aircraft Facility currently held within the base material then an Action Request should be directed to Geoscience Australia requesting information on how to proceed.

The classification of facilities will be done according to the Enroute Supplement Australia published by Airservices Australia and supplied as reference material. Only facilities shown as licensed, certified or registered in the Enroute Supplement will be represented using the Runway feature type. If the facility is not listed in the supplement or is listed as unlicensed, uncertified or unregistered it will be represented using the Landing Ground feature type.

Landing Grounds will not be named. Military Landing Grounds will not be given any other indication of their military nature.

The name of Landing Grounds of historical significance will be held in the textnote field. These landing grounds will have textnote of 'historical' appended to the name. Geoscience Australia will supply information within project instructions if historical landing grounds exist within a work package supplied to producers.

The elevation in feet of landing grounds should be derived from the Enroute Supplement Australia in the first instance. If the information is unavailable then the National Airfield Directory should be used.

The feature and attribute reliabilities will be the date of either the Enroute Supplement Australia, Imagery or the base material/digital data as appropriate.

When supplied with a change guide for aviation the above specifications will be taken into account unless otherwise documented.

The alignment of landing grounds should be checked against imagery whenever possible as it can change over time.

General - All Scales

A Landing Ground must not overlap;
Airport Area

General - All Scales

Landing Grounds cannot overlap;
Pondage Area (Feature Class), Cemetery Area, Rubbish Tip, Rapid Area

General - All Scales

All Operational and Historic Landing Grounds will be represented on the map face.

Historical Landing Grounds will be named, where known, and labelled with the decriptive note 'historical'

Military aircraft facilities will be symbolised in the same way as civil facilities, but will not be named nor given any other indication of their military nature.

All landing grounds will be labelled with a descriptive note "landing ground", this will be derived from the feature type field.

All landing grounds that have a status other than 'Decommissioned' and 'Abandoned' will be shown on the map face unless historical in nature.

All landing grounds with a status of 'Under Construction' will be labelled with the descriptive note 'under construction'

Runway Edge, Airport Area, Runway centreline, Taxiway , Limit of Data

Section 1chapter 3.8.1
Section 3 chapters 5.3, 5.18, 5.19, 6.6, 6.10
Appendix U chapters 2.2.3

GEODATA LITE TOPO100K, NTMS 100K

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

Landing Ground

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.

LandingGround

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

This field is not applicable to this subtype and therefore is currently not to be populated;

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see 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;

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;

703
0 - non printing for landing grounds on very small islands or helipads at 1:100000 where symbolisation can not occur do to rules set out in general notes

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;

0 - 360

General - All Scales

Only Aircraft Facilities confirmed using approved reference or supporting material and are clearly visible on imagery, will be included regardless of whether it was shown on/in the base material/digital data. Abandoned facilities will not be shown.

The classification of facilities will be done according to the Enroute Supplement Australia published by Airservices Australia and supplied as reference material. Only facilities shown as licensed, certified or registered in the Enroute Supplement will be represented using the Airport feature type. If the facility is not listed in the supplement or is listed as unlicensed, uncertified or unregistered it will be represented using the Landing Ground feature type.

Landing Grounds will not be named. Military Landing Grounds will not be given any other indication of their military nature.

The feature and attribute reliabilities will be the date of either the Enroute Supplement Australia, Imagery or the base material/digital data as appropriate.

When supplied with a change guide for aviation the above specifications will be taken into account unless otherwise documented.

Orientation of landing grounds should be checked against imagery whenever possible as it can change over time.

Runway centrelines >457 metres (1500 feet) will be captured for Landing Grounds.

For Landing Grounds the orientation of the runway will be shown. If there is more than one runway the orientation of the main runway will be shown.

General - All Scales

Helipads will be not be captured when associated with an airport or landing ground

General - All Scales

Landing Grounds cannot overlap;
Pondage Area (Feature Class), Cemetery Area, Rapid Area

General - All Scales

Landing Grounds will not be named. Military Landing Grounds will not be given any other indication of their military nature.

For Landing grounds the orientation of the runway will be shown. If there is more than one runway the orientation of the main runway will be shown.

Runway centreline, Airport

Section 1 chapter 3.8.1
Section 3 chapters 5.9, 6.6, 6.10
Appendix U chapters 2.2.3

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.

Navigation Aid

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

The name of the navigation aid. This item should be populated where name is known.

HEIGHT (HEIGHT) [Single;Yes;0;6;2;Pop_Wk] Height of feature above ground level

RELATIONSHIP (RELATIONSHIP) [String;Yes;12;0;0;Pop_Req] Relationship to sea level for marine features or to ground level for land based features;

Acceptable Domain Entries from dm_AviationRelationship;
Above Ground
Elevated
Offshore

SYSTEM (SYSTEM) [String;Yes;75;0;0;Pop_Wk] The Navigation Systems Type;

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.

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

not yet assigned

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.

Vertical Obstruction, Navigation Light

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

Navigation Light

COLOUR (COLOUR) [String;Yes;12;0;0;Pop_Wk] The colour of the Light projected from the feature.

Colours will be concatenated when more than one colour is projected e.g. BuGW.
Valid entries will be as per the following, and the case will be as shown;
B - represents Blue
G - represents Green
R - represents Red
W - represents White
Y - represents Yellow, Amber or Orange

DURATION (DURATION) [String;Yes;12;0;0;Pop_Wk] Duration of the cycle in seconds.

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

FLASHES (FLASHES) [String;Yes;12;0;0;Pop_Wk] Number of Light Flashes;

LIGHT FUNCTION (LIGHTFUNCTION) [String;Yes;12;0;0;Pop_Wk] Function Method of Light Emittance;

Acceptable Domain Entries from dm_LightFunction;
Identification Beacon
Rotating Beacon
Strobe
Unknown

LIGHT TYPE (LIGHTTYPE) [String;Yes;15;0;0;Pop_Wk] The nature of the light action.

Light Types will be concatenated when more than one type of action e.g. ALTNMo.
Valid entries will be as per the following, and the case will be as shown;
ALTN - represents Alternating
F - represents Fixed
Fl - represents Flashing
I - represents Interrupted
Iso - represents Isophase
Mo - represents Morse Code
Occ - represents Occulating
Q - represents Quick

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.

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

not yet assigned

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.

General - All Scales

For Navigation Lights the elevation field will be populated with the elevation of the light above mean sea level.

Vertical Obstruction, Navigation Aid

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

Runway

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.

Runway

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

Name of aircraft facility (see Geodatabase Rules for population requirements.)

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

AIRPORT DESIGNATION (AIRPORTDESIGNATION) [String;Yes;25;0;0;Pop_Req] International or Domestic Designation for Airport;

Acceptable Domain Entries from dm_AirportDesignation;
International
Limited International
Domestic
Unknown

ELEVATION IN FT (ELEVATIONFT) [Single;Yes;0;6;2;Pop_Wk] The elevation of the entity in feet above sea level.

ICAO DESIGNATION (ICAODESIGNATION) [String;Yes;4;0;0;Pop_Wk] The designation code provided by the International Civil Aviation Organization (ICAO);

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_AviationStatus;
Decommissioned
Operational
Abandoned
Under Construction
Unknown

SURFACE (SURFACE) [String;Yes;24;0;0;Pop_Req] The description of the landing surface of the Aircraft Facility;

Acceptable Domain Entries from dm_Surface;
Grass
Earthern
Bitumen
Concrete
Water
Unknown
Gravel

USAGE (USAGES) [String;Yes;75;0;0;Pop_Wk] The description of the type of civil and/or military use of the Aircraft Facility;

Acceptable Domain Entries from dm_Usages;
Civil
Civil/Military
Military
Customs
Civil Water

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;

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

VERIFICATION STATUS (VERIFICATIONSTATUS) [String;Yes;30;0;0;Pop_Req] The verification status of the confirmation of Aircraft Facility existence (and where available attribution);

Acceptable Domain Entries from dm_VerificationStatus;
Agency Confirmation
Field Verified
Private Contact Confirmation
Unverified

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

700

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

The feature and attribute reliabilities will be the date of either the Enroute Supplement Australia, Imagery or the base material/digital data as appropriate.

General - All Scales

The classification of facilities will be done according to the Enroute Supplement Australia published by Airservices Australia and supplied as reference material. Only facilities shown as licensed, certified or registered in the Enroute Supplement will be represented using the Runway feature type. If the facility is not listed in the supplement or is listed as unlicensed, uncertified or unregistered it will be represented using the Landing Ground feature type.

Licensed, certified or registered facilities will be named. The name should be that of the airport as signposted. The suffix of 'Airport' or 'Aerodrome' will be included in the name. When unknown the form of suffix used will be that used on/in the base material/digital data (e.g. existing TOPO100K NTDB, previous edition map or state information). If not previously indicated on/in the base material/digital data the default suffix 'Aerodrome' will be used.

Alternate Names should be captured, where known.

The Airport Designation should be as defined by Department of Transport and Regional Services web site (Designated International Airports in Australia).

The ICAO Designation will be as documented in the Enroute Supplement Australia published by Airservices Australia.

The elevation in feet of landing grounds should be derived from the Enroute Supplement Australia in first instance. If the information is unavailable then the National Airfield Directory should be used.

When supplied with a change guide for aviation the above specifications will be taken into account unless otherwise documented.

Runways will be captured to scale and formed using parallel lines that should give the appearance of right angles at each end.

In the stituation where Runways of different SURFACE, STATUS and SEASONAL classifications coexist on the ground, they should be represented as separate polygons otherwise a single polygon will be used to represent the feature. See Section 3 6.10 Aircraft Facilities for more information.

General - All Scales

Runways, Aprons and Taxiways must be fully contained within the Airport Area feature type.

Aprons must not overlap Runways.

Where Aprons abut Runways and Taxiways in reality they should be made coincident along the those portions of the features.

The end nodes of taxiways shall be coincident with a vertex on the perimeter of a Aircraft Facility Area (feature class) polygon, the end nodes of two or more intersecting taxiways or with a building representing its destination point.

Taxiways can overlap Runways.

General - All Scales

Runways cannot overlap;
Pondage Area (Feature Class), Cemetery Area, Rubbish Tip, Rapid Area

General - All Scales

Only Operational Runways will be represented on the map.

For named Aircraft Facilities, 'Airport' or 'Aerodrome' will be included in the name. The form used will be that used on the latest previous edition map. If the Aircraft Facility was not previously named 'Aerodrome' will be used.

Military aircraft facilities will be symbolised in the same way as civil facilities, but will not be named nor given any other indication of their military nature.

All Runways of licenced aircraft facilities will be drawn to scale and correctly oriented. All Runways should have the appearance that they are formed using parallel lines and right angles at each end.

Runway Edge, Airport Area, Runway centreline, Taxiway , Limit of Data, Landing Ground (AircraftFacillityLines)

Section 1 chapter 3.8.1
Section 3 chapters 5.3, 5.10, 5.18, 5.19,6.6, 6.10

GEODATA LITE TOPO100K, NTMS 100K

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

Taxiway

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.

Taxiway

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

This field is not applicable to this subtype and therefore is currently not to be populated;

ALTERNATIVE NAME (ALTERNATENAME) [String;Yes;60;0;0;Pop_Dep] An Alternate Name given to the entity;

This field is not applicable to this subtype and therefore is currently not to be populated;

ELEVATION IN FT (ELEVATIONFT) [Single;Yes;0;6;2;Pop_Wk] The elevation of the entity in feet above sea level.

This field is not applicable to this subtype and therefore is currently not to be populated;

Currently not to be populated.

SEASONAL (LANDINGACCESS) [String;Yes;60;0;0;Pop_Wk] The description of the ability to access the landing facility by an aircraft caused by weather or seasonal consideration;

This field is not applicable to this subtype and therefore is currently not to be populated;

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

This field is not applicable to this subtype and therefore is currently not to be populated;

SURFACE (SURFACE) [String;Yes;24;0;0;Pop_Req] The description of the landing surface of the Aircraft Facility;

This field is not applicable to this subtype and therefore is currently not to be populated;

USAGE (USAGES) [String;Yes;75;0;0;Pop_Wk] The description of the type of civil and/or military use of the Aircraft Facility;

This field is not applicable to this subtype and therefore is currently not to be populated;

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see 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;

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

VERIFICATION STATUS (VERIFICATIONSTATUS) [String;Yes;30;0;0;Pop_Req] The verification status of the confirmation of Aircraft Facility existence (and where available attribution);

This field is not applicable to this subtype and therefore is currently not to be populated;

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

709

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.

This field is not applicable to this subtype and therefore is currently not to be populated;

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

Taxiways should be captured along their centreline.

Sufficient taxiways will be shown to reflect the movement pattern. Select the major through routes within the area whilst avoiding clutter. Where all taxiways can be shown without causing clutter then they shall be shown.

General - All Scales

The end nodes of taxiways shall be coincident with a vertex on the perimeter of a Aircraft Facility Area (feature class) polygon, the end nodes of two or more intersecting taxiways or with a building representing its destination point.

Taxiways can overlap Runways.

Where Aprons abut Runways and Taxiways in reality they should be made coincident along the those portions of the features.

Runways, Aprons and Taxiways must be fully contained within the Airport Area feature type.

General - All Scales

Taxiways cannot overlap;
Pondage Area (Feature Class), Cemetery Area, Rubbish Tip, Rapid Area

The end nodes of taxiways shall be coincident with a vertex on the perimeter of a Aircraft Facility Area (feature class) polygon, the end nodes of two or more intersecting taxiways or with a building representing its destination point.

1:25 000

Taxiways will be a minimum length of 75m before representated on the map.

1:100 000

Taxiways will be a minimum length of 300m before representated on the map.

Airport, Heliport, Landing Ground (Aircraft Facility Points), Landing Ground (Aircraft Facility Line), Runway, Airport Area, Apron

Section 1 chapter 3.8.1
Section 3 chapter 5.3, 6.6, 6.10

GEODATA LITE TOPO100K, NTMS 100K