Data Attributes

The name of Aerial Cableway. This item should be populated where name is known.

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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:100 000

Size and any other selection criteria apply to all feature occurrences.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

General - All Scales

A TextNote is to be added to the data e.g. 'chairlift'.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

End-points of this feature cannot overlap; Sea or Perennial Waterbodies.

Map Rules

General - All Scales

A descriptive note is to be added e.g. 'chairlift'.

Related Features

Conveyor

Related Chapters

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

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

DESCRIPTION (DESCRIPTION) [String;Yes;30;0;0;Pop_Req]

Expanded description of the type of Landmark area feature, see Geodatabase Rules for further information.

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/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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

1:100 000

Size and any other selection criteria apply to only feature occurrences which can not be derived from the larger scale data capture programs.

General - All Scales

Landmark area features will only be used for man made entities or areas defined by man for a specific use which are clearly identifiable either through signage or infrastructure.

Landmark area features will not be used to duplicate or clone entities covered by another feature class, for example recreation area, prohibited areas, but may be used to provide a spatial link between numerous feature classes comprising a cohesive complex. They represent the area extent of a feature or complex not just its component parts, e.g. The 'Agricultural Production' feature type will represent the boundary of the agricultural activities, not just the farm buildings (also represented in building points/area), fencing complexes and storage facilities (also represented as silos, storage tanks and water tanks).

The 'Agricultural Production' feature type includes the following (or any other feature specified by Geoscience Australia through a special instruction or action request):

cotton gin, seasonal agricultural facilities

The above list should be used as the acceptable description field entries, additional entries may be provided by Geoscience Australia.

Only seasonal Cotton Gins should be represented as Landmark Areas and will be attributed with a Text Note of 'seasonal'.

Greenhouses should be represented as Landmark Areas with the description of 'seasonal agricultural facilities' and Text Note of 'greenhouses seasonal'

Landmark area features are to have an accompanying textnote where it expands on the description and/or name field eg 'historical'.

Inter-Feature Relationship Rules - Internal to Associated Dataset

A LandmarkAreas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another LandmarkAreas (feature class polygon)Cemetery Area edge (feature class polygon)Rubbish Tip edge (feature type polygon)RecreationAreas (feature class polygon)

Related Chapters

Related Products

GEODATA LITE TOPO100K, NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

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

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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

All cemeteries will be represented either as a Cemetery Area or as a Cemetery Point.

Features whose area is less than the minimum size for inclusion shall be shown as Cemetery Point feature.

1:100 000

All cemeteries will be represented in the TOPO100K NTDB either as a Cemetery Area or as a Cemetery Point. All features less than 1406 sq m will be shown as a Cemetery Point. New features less than 22 500 sq m will be shown as a Cemetery Point. New features greater than 22 500 sq m will be shown as a Cemetery Area. For existing features between 1406 sq m and 22 500 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Cemetery Area or Cemetery Point).

1:250 000

All cemeteries will be represented either as a Cemetery Area or as a Cemetery Point.

Features whose area is less than the minimum size for inclusion shall be shown as Cemetery Point feature.

General - All Scales

Cemetery Areas can be surrounded by Built Up Areas or can be isolated polygons.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Cemetery Area edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another Cemetery Area edge (feature class polygon)Rubbish Tip edge (feature type polygon)RecreationAreas (feature class polygon)LandmarkAreas (feature class polygon)

1:100 000

A Cemetery Area edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another Cemetery Area edge (feature class polygon)Rubbish Tip edge (feature type polygon)RecreationAreas (feature class polygon)LandmarkAreas (feature class polygon)

1:250 000

Where a Cemetery Area edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another Cemetery Area edge (feature class polygon)Rubbish Tip edge (feature type polygon)RecreationAreas (feature class polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

A Cemetery Area edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

A Cemetery Area edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a Cemetery Area edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

All cemeteries are to have an accompanying descriptive note 'cemetery' unless the word 'cemetery' is included in the name.

Built Up Area will mask Cemetery Areas

Related Features

Cemetery Point

Related Chapters

Section 3 chapter 5.11.2, 5.18 and 5.19Appendix U chapter 2.1.9

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

The cemetery's name. This item should be populated where name is known.

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/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.

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;

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.

Geodatabase Rules

1:25 000

All cemeteries will be represented either as a Cemetery Area or as a Cemetery Point.

1:100 000

All cemeteries will be represented in the TOPO100K NTDB either as a Cemetery Area or as a Cemetery Point. All features less than 1406 sq m will be shown as a Cemetery Point. New features less than 22 500 sq m will be shown as a Cemetery Point. New features greater than 22 500 sq m will be shown as a Cemetery Area. For existing features between 1406 sq m and 22 500 sq m the information will be retained in the same geometry as captured in the base material/digital data (e.g. Cemetery Area or Cemetery Point).

1:250 000

All cemeteries will be represented either as a Cemetery Area or as a Cemetery Point.

The point representing the feature is to be placed within the bounds of the cemetery.

General - All Scales

Used for cemeteries smaller than the size criteria for the Cemetery Area feature.

The point representing the feature is to be placed within the bounds of the cemetery.

Where inclusion of a cemetery point would result in clutter they are to be symbolised to 0 non-printing.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Cemetery Points must not overlap;Cemetery Areas

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

General - All Scales

All cemeteries are to have an accompanying descriptive note 'cemetery' unless the word 'cemetery' is included in the name.

Related Chapters

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the Civic Square (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies feature dataset.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Recreation Areas are to have an accompanying textnote eg 'civic square' unless the words 'civic square' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:250 000

Civic Squares cannot overlap;Sea.

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance Rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Nature Conservation Reserve, Landmark Area

Related Chapters

Section 3 chapters 5.11.2, 5.18, 5.19 and 6.9

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

IDENTIFICATION CODE (IDCODE) [String;Yes;30;0;0;Pop_Wk] The code used to identify a communication device (or provide contact with) an emergency facility point

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/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.

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;

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.

Geodatabase Rules

General - All Scales

This feature will only be captured as directed in the project instructions supplied. It includes such features as emergency radio beacons, remote solar powered telephones, etc.

All available attribution will be supplied with the project instructions.

This feature should be captured in correct spatial relationship to its surrounding topology.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

This feature should be captured in correct spatial relationship to its surrounding topology.

Map Rules

General - All Scales

This feature will only be included on Non-Standard NTMS maps, specially created for Emergency Mapping Purposes. A descriptive note should appear on the map derived from the description & textnote fields of the NTDB.

Related Features

Related Chapters

Section 3 Chapter 5.3

Related Products

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

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.

Geodatabase Rules

General - All Scales

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

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

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

Related Features

Related Chapters

Section 2 Chapter 5, 9, 10

Related Products

NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Dam

WaterStoragePoints

Culture

Point

An open body of water collected and stored behind a constructed barrier consisting of earth, rock, concrete and/or masonry. Generally designed to capture run-off from the surrounding landscape or rainfall. The storage of water may occur on or below ground level.

The name of the Dam (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/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.

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;

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.

Geodatabase Rules

1:25 000

All dams in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured, no filtering should occur. Dams inside densely settled regions will be captured upon direction from Geoscience Australia.

Only dams in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Dams within Built Up Areas will not be classified with an upperscale equal to, or greater than, '100000'. 'Greater than' refers to smaller scales such as '250000','1000000'.

Names will be captured, where known.

Dams larger than 6400 sq. m will be shown as a TownRuralStorage reservoir feature.

Dams larger than 22500 sq. m will be shown as a TownRuralStorage reservoir feature.

New feature should only be captured in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', size and any other selection criteria apply to all feature occurrences.

In sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide, all TownRuralStorage reservoirs will be represented in the data as either a Town Rural Storage Reservoir or a Dam.For existing features in these regions between 6400 sq m and 22500 sq m the representation will be retained in the same geometry as captured in the base material/digital data (e.g. Dam, TownRuralStorage).

Only dams in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Dams within Built Up Areas will not be classified with an upperscale equal to, or greater than, '100000'. 'Greater than' refers to smaller scales such as '250000','1000000'.

Names will be captured, where known.

General - All Scales

This feature can be used to represent both farm dams or an undersized Town Rural Storage Reservoir. This feature will not be used to capture FloodIrrigationStorage Reservoirs smaller than their minimum size criteria.

Dams to have an accompanying textnote for features not being used directly for human or livestock consumption.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

Dams cannot overlap;Building Area (Ruin).

1:100 000

Dams cannot overlap;Building Area (Ruin).

General - All Scales

Where a Bore and a Dam are situated together, both will be included in the data but only the Dam will be shown as it usually has the greater landmark value. Bore should be symbolised to 0 (non - printing).

Dams plotted within 2.5 mm at map scale of a Built Up Area will be symbolised to 0 (non-printing).

Dams cannot overlap;Reservoirs (feature class)

Map Rules

General - All Scales

Names will be shown in sparsely settled areas.

As the density of the cultural detail increases, names will be progressively omitted.

Dam to have an accompanying descriptive note for features not being used directly for human or livestock consumption.

Where a Dam and Windpump are situated together, only the Windpump, which has the greater landmark value, will be shown. (Refer feature Windpump).

Related Chapters

Related Products

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

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

The name of the dam wall. This item should be populated where name is known.

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/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.

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;

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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

For dam walls coincident with roads, the feature width should only be populated where the known road classifications are consistent with those documented within these specifications, otherwise the feature width will remain as 'NULL' .

1:100 000

Size and any other selection criteria apply to all feature occurrences.

For dam walls coincident with roads, the feature width should only be populated where the known road classifications are consistent with those documented within these specifications, otherwise the feature width will remain as 'NULL' .

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

General - All Scales

Dams Walls will not be shown where the associated water storage is shown as a Water tank or Dam feature.

Dam Walls not shown to scale on the latest previous edition map will be captured as a chain 1mm long at map scale.

Dam Wall features will be associated with a spillway feature where the spillway is behind the wall or separated from it and meets other selection criteria for spillways. Where excess water overtops the dam wall along all or most of its length a spillway will not be shown e.g. Hume Dam or Scrivener Dam (see Spillway).

In densely and moderately settled regions as defined by Appendix C where a 'Dam Wall' meets the minimum size criteria, the attached reservoir should be shown regardless of whether or not it is below the minimum size criteria for reservoirs. If a reservoir no longer exists (ie. Filled with sediment) then the dam wall will not be shown.Where a spillway feature is not included (see Spillway), the reservoir connector and watercourse or watercourse connector will meet node to node at the dam.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

Where a Dam Wall crosses a Watercourse Area, the upstream portion should be treated as a Reservoir feature.The reservoir will be from the dam wall upstream encompassing the static water extent of the waterbody at its full holding capacity.

1:100 000

Where a Dam Wall crosses a Watercourse Area, the upstream portion should be treated as a Reservoir feature. The reservoir will be from the dam wall upstream encompassing the static water extent of the waterbody at its full holding capacity.

1:250 000

Where a Dam Wall crosses a Watercourse Area, the upstream portion should be treated as a Reservoir feature. The reservoir will be from the dam wall upstream encompassing the static water extent of the waterbody at its full holding capacity.This means a Junction will be placed across the watercourse area polygon, coincident with the Dam Wall. Depending on the situation an additional junction further upstream may be needed to complete Reservoir feature.

General - All Scales

Dam Walls that carry roads across them will be a clone of the equivalent section of the associated Road. There must be a vertex in the Road feature at the exact location of the start and end points of the Dam Wall. The road must continue outwards from both endpoints of the Dam Wall.

Dam Walls should be coincident with the high water mark of the reservoir for the portion of the water boundary for which the dam wall creates a barrier. The dam wall may extend beyond the boundary of reservoir where imagery confirms this is the case.

Dam Walls cannot cross any feature in the Drainage feature dataset (except Spillway, Watercourse and connectors) or Roads and Railways.

Dams cannot appear in the following; Sea, Lake, Canal Area, Watercourse Area and Building Area.

Map Rules

General - All Scales

If a dam wall and its associated reservoir have the same name, then : - where the name of the reservoir can be placed on the map face in a cartographically acceptable manner the associated dam wall name will not be included but a descriptive note e.g. 'dam','weir' will be added where space permits. - where the reservoir name can not be placed on the map face in a cartographically acceptable manner then the waterbody feature will remain unnamed but its associated dam wall would be named, where the name is known. It should also have an accompanying descriptive note e.g. 'dam', 'weir' unless the word 'dam','weir' is included in the name.

Related Features

Reservoir (Feature Class), Spillway , Water tank, Dam

Related Chapters

Section 3 chapters 5.3, 5.8 and 5.11.1 Appendix U chapter 2.3.4

Related Products

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

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

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

DESCRIPTION (DESCRIPTION) [String;Yes;30;0;0;Pop_Req]

Expanded description of the type of Landmark area feature, see Geodatabase Rules for further information.

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/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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:100 000

Size and any other selection criteria apply to all feature occurrences.

General - All Scales

Landmark area features will only be used for man made entities or areas defined by man for a specific use which are clearly identifiable either through signage or infrastructure.

Landmark area features will not be used to duplicate or clone entities covered by another feature class, for example recreation area, prohibited areas, but may be used to provide a spatial link between numerous feature classes comprising a cohesive complex. They represent the area extent of a feature or complex not just its component parts, e.g. Education Facility will represent the boundary of the school lands, not just the school buildings (also represented in building points/area), ovals and tennis courts (also represented as recreation areas) and the miscellaneous land not designated for any specific purpose but still owned by the school.

Landmark area features include the following (or any other feature specified by Geoscience Australia through a special instruction or action request):

The above list should be used as the acceptable description field entries however additional entries may be provided by Geoscience Australia.

When an Educational Institution comprises of multiple campuses, each campus will be captured separately (ie not as a multi-part polygon) and the size criteria will apply to each separate campus. However, each campus will be given the name of the primary Educational Institution only (eg 'The University of Melbourne' as opposed to 'The University of Melbourne Shepparton Campus').

For further information on Landmark Area - Educational Institution see Section 3 Chapter 6.14 Schools

Landmark area features are to have an accompanying textnote where it expands on the description and/or name field eg 'historical'.

Related Chapters

Related Products

GEODATA LITE TOPO100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

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/digital data for initial 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/digital data for initial capture) used for Attribute Verification.

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.

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.

Geodatabase Rules

General - All Scales

This feature will only be captured/retained in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide', regardless of whether it previously existed in the base material/digital data. The exception is that major vermin proof fences will be captured in all locations. Size and any other selection criteria apply to new feature occurrences. All vermin proof fences and feature occurrences in sparsely settled regions existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Fences around small paddocks adjacent to farm houses and homesteads will be omitted.

Fence features less than the minimum size for inclusion may be used to depict yards greater than 390625 sq m, refer feature 'Yard'.

Where a vermin proof fence follows a state border or a road (excluding Vehicle Tracks), the fence feature should be symbolised to 0 (non-printing) and the text_note 'vermin proof fence follows state border' or 'vermin proof fence follows road' should be applied.Where a vermin proof fence and a vehicle track are adjacent, an assessment must be made as to whether: The vehicle track is considered important in terms of road network connectivity; and/or The vehicle track is servicing a natural or cultural feature, excluding the fence, represented within the new topographic map and data product eg. Tower, mine, spring, etc.

If the track is deemed important, show the track, add the text_note 'vermin proof fence follows track' and symbolise vermin proof fence to 0. If not, the track should not be included in the data and a text_note 'track follows vermin proof fence' should be added to the fence feature shown on the map.

All of the above text_notes should be applied to the features in the Fence feature class.

Where a fence follows a road (excluding vehicle tracks) the fence should not be included in the data. Where a fence and a vehicle track are adjacent, an assessment must be made as to whether:The vehicle track is considered important in terms of road network connectivity ; and/orThe vehicle track is servicing a natural or cultural feature, excluding the fence, represented within the new topographic map and data product eg. Tower, mine, spring, etc.

If the vehicle track meets either of the above criteria then the vehicle track should be shown on the map, in accordance with the specifications. Alternatively, if the vehicle track does not meet either of the above criteria then the fence should be shown, provided it adds a meaningful connection to the existing fence network. These guidelines apply to both features existing on the previous edition maps and new features and are subject to Appendix C rules regarding fence selection.

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

Fences will be masked by gate stock grid and yard symbols and by roads.

Fences will be masked where black type unavoidably overprints the feature. The break measurement will be 0.2 mm on either side of the type where it crosses the feature. (Note: the feature will be masked only on the map and will be complete in the data.)

Related Features

Gate, Grid , Yard

Related Chapters

Section 3 chapter 5.11.2Appendix C Appendix U chapters 2.2.2, 2.4.1

Related Products

GEODATA TOPO250K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

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/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.

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;

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.

Geodatabase Rules

1:25 000

Fence features less than the minimum size for inclusion may be used to depict yards greater than 3906 sq m at 1:25 000 - refer feature 'Yard'.

1:100 000

Fence features less than the minimum size for inclusion may be used to depict yards greater than 62500 sq m - refer feature 'Yard'.

General - All Scales

This feature will only be captured in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide'. Size and any other selection criteria apply to all feature occurrences.

Fences around small paddocks adjacent to farm houses and homesteads will be omitted.

Where a fence follows a road (excluding vehicle tracks) the fence should not be included in the data. Where a fence and a vehicle track are adjacent, an assessment must be made as to whether:The vehicle track is considered important in terms of road network connectivity ; and/orThe vehicle track is servicing a natural or cultural feature, excluding the fence, represented within the new topographic map and data product eg. Tower, mine, spring, etc.

If the vehicle track meets either of the above criteria then the vehicle track should be shown on the map, in accordance with the specifications. Alternatively, if the vehicle track does not meet either of the above criteria then the fence should be shown, provided it adds a meaningful connection to the existing fence network. These guidelines apply to both features existing on the previous edition maps and new features and are subject to Appendix C rules regarding fence selection.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Fences cannot overlap;Sea and Building Area features.

Map Rules

General - All Scales

Fences will be masked by gate stock grid and yard symbols and by roads.

Fences will be masked where black type unavoidably overprints the feature. The break measurement will be 0.2 mm on either side of the type where it crosses the feature. (Note: the feature will be masked only on the map and will be complete in the data.)

Related Features

Gate, Grid , Yard, Vermin Proof Fence

Related Chapters

Related Products

NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Fence Vermin Proof

Fences

Culture

Polyline

A freestanding structure designed to enclose, bound or divide a property or a part thereof, preventing movement across the boundary. Intended to restrict the movement of species considered to be vermin that potentially carry disease or cause unwanted damage to the environment or property.

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/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.

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;

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.

Geodatabase Rules

1:25 000

Fence features less than the minimum size for inclusion may be used to depict yards greater than 3906 sq m at 1:25 000 - refer feature 'Yard'.

1:100 000

Fence features less than the minimum size for inclusion may be used to depict yards greater than 62500 sq m - refer feature 'Yard'.

General - All Scales

Size and any other selection criteria apply to all feature occurrences.

Fences around small paddocks adjacent to farm houses and homesteads will be omitted.

Where a vermin proof fence follows a state border or a road (excluding Vehicle Tracks), the fence feature should be symbolised to 0 (non-printing) and the text_note 'vermin proof fence follows state border' or 'vermin proof fence follows road' should be applied.Where a vermin proof fence and a vehicle track are adjacent, an assessment must be made as to whether: The vehicle track is considered important in terms of road network connectivity; and/or The vehicle track is servicing a natural or cultural feature, excluding the fence, represented within the new topographic map and data product eg. Tower, mine, spring, etc.

If the track is deemed important, show the track, add the text_note 'vermin proof fence follows track' and symbolise vermin proof fence to 0. If not, the track should not be included in the data and a text_note 'track follows vermin proof fence' should be added to the fence feature shown on the map.

The appropriate text_notes as indicated above should be applied to the features in the Fence feature class.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Fences cannot overlap;Sea and Building Area features.

Map Rules

Fences will be masked by gate stock grid and yard symbols and by roads.

Fences will be masked where black type unavoidably overprints the feature. The break measurement will be 0.2 mm on either side of the type where it crosses the feature. (Note: the feature will be masked only on the map and will be complete in the data.)

Related Features

Gate, Grid , Yard , Standard Fence

Related Chapters

Related Products

NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the Garden. (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies layer.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Recreation Areas are to have an accompanying textnote eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Related Chapters

Section 3 chapters 5.11.2, 5.18, 5.19 and 6.9

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the Golf Course (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies layer.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Recreation Areas are to have an accompanying textnote eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Related Chapters

Section 3 chapters 5.11.2, 5.18, 5.19 and 6.9Appendix U chapter 2.1.5

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Hospital

LandmarkAreas

Culture

Polygon

An institution on a designated area of land upon which buildings and other associated infrastructure has been constructed for the purposes of supplying medical facilities, surgical treatment and nursing support to surrounding communities.

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

DESCRIPTION (DESCRIPTION) [String;Yes;30;0;0;Pop_Req]

Expanded description of the type of Landmark area feature, see Geodatabase Rules for further information.

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/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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:100 000

Size and any other selection criteria apply to all feature occurrences.

General - All Scales

Landmark area features will only be used for man made entities or areas defined by man for a specific use which are clearly identifiable either through signage or infrastructure.

Landmark area features will not be used to duplicate or clone entities covered by another feature class, for example recreation area, prohibited areas, but may be used to provide a spatial link between numerous feature classes comprising a cohesive complex. They represent the area extent of a feature or complex not just its component parts, e.g. The 'Hospital' feature type will represent the boundary of the hospital lands, not just the hospital buildings (also represented in building points/area), car parks and heliports (also represented as aircraft facility points) and the miscellaneous land not designated for any specific purpose but still owned by the hospital.

The 'Hospital' feature type includes the following (or any other feature specified by Geoscience Australia through a special instruction or action request):

Inter-Feature Relationship Rules - Internal to Associated Dataset

A LandmarkAreas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another LandmarkAreas (feature class polygon)Cemetery Area edge (feature class polygon)Rubbish Tip edge (feature type polygon)RecreationAreas (feature class polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

Building Point/Areas with a building function of 'Hospital' must be contained within a Landmark Area (Hospital) polygon

1:100 000

Building Point/Areas with a building function of 'Hospital' must be contained within a Landmark Area (Hospital) polygon

Related Chapters

Related Products

GEODATA LITE TOPO100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Intensive Animal Production

LandmarkAreas

Culture

Polygon

An area of land or water developed for the intensive industrialised production of a variety of animals for commercial purposes, generally associated with man-made structures such as yards, buildings and other farming infrastructure

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

DESCRIPTION (DESCRIPTION) [String;Yes;30;0;0;Pop_Req]

Expanded description of the type of Landmark area feature, see Geodatabase Rules for further information.

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/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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:100 000

Size and any other selection criteria apply to all feature occurrences.

General - All Scales

Landmark area features will only be used for man made entities or areas defined by man for a specific use which are clearly identifiable either through signage or infrastructure.

Landmark area features will not be used to duplicate or clone entities covered by another feature class, for example recreation area, prohibited areas, but may be used to provide a spatial link between numerous feature classes comprising a cohesive complex. They represent the area extent of a feature or complex not just its component parts, e.g. Education Facility will represent the boundary of the school lands, not just the school buildings (also represented in building points/area), ovals and tennis courts (also represented as recreation areas) and the miscellaneous land not designated for any specific purpose but still owned by the school.

The Intensive Animal Production feature type includes the following (or any other feature specified by Geoscience Australia through a special instruction or action request):

Inter-Feature Relationship Rules - Internal to Associated Dataset

A LandmarkAreas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another LandmarkAreas (feature class polygon)Cemetery Area edge (feature class polygon)Rubbish Tip edge (feature type polygon)RecreationAreas (feature class polygon)

Related Chapters

Related Products

GEODATA LITE TOPO100K, NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Landmark Area General

LandmarkAreas

Culture

Polygon

A geographic area which has a landmark value or is useful for navigation, and includes areas comprising developed or specialised man-made infrastructure or concentrated areas of permanent natural physical features.

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

DESCRIPTION (DESCRIPTION) [String;Yes;30;0;0;Pop_Req]

Expanded description of the type of Landmark area feature, see Geodatabase Rules for further information.

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/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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:100 000

Size and any other selection criteria apply to all feature occurrences.

General - All Scales

Landmark area features will only be used for man made entities or areas defined by man for a specific use which are clearly identifiable either through signage or infrastructure.

Landmark area features will not be used to duplicate or clone entities covered by another feature class, for example recreation area, prohibited areas, but may be used to provide a spatial link between numerous feature classes comprising a cohesive complex. They represent the area extent of a feature or complex not just its component parts, e.g. Education Facility will represent the boundary of the school lands, not just the school buildings (also represented in building points/area), ovals and tennis courts (also represented as recreation areas) and the miscellaneous land not designated for any specific purpose but still owned by the school.

The 'Landmark Area General' feature type includes the following (or any other feature specified by Geoscience Australia through a special instruction or action request):

The above list should be used as the acceptable description field entries, additional entries may be provided by Geoscience Australia.

When representing a Windfarm as a landmark area individual Wind generators should still be captured in landmark points but not symbolised. Similar situations where landmark points have a direct relationship with a landmark area may be treated in the same manner.

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Landmark area features are to have an accompanying textnote where it expands on the description and/or name field eg 'historical'.

Related Chapters

Related Products

GEODATA LITE TOPO100K, NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

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

DESCRIPTION (DESCRIPTION) [String;Yes;30;0;0;Pop_Req]

Description of the type of Landmark feature, see Geodatabase Rules for a list of generic terms and more information.

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/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.

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;

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.

Geodatabase Rules

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Landmark Points whose area is larger than 40 000 sq. m will be shown as a landmark area feature.

When representing an observatory complex as a landmark area individual telescopes should still be captured in landmark points but not symbolised. Similar situations where landmark points have a direct relationship with a landmark area may be treated in the same manner.

General - All Scales

Landmark Point features are not shown in or in close proximity to Built Up Areas, unless the feature is of significant landmark value.

Landmark Point features will only be used for entities which cover a small area on the ground.

The following are typical examples of Landmark Points.Note: This listing does not represent all features that may be considered for inclusion in this Feature Type. Other features meeting the definition and criteria for this feature type (and not represented by any other entity i.e building, recreation area) may be included where sourced from authorised Revision Information, Special Instructions or Action Requests supplied by Geoscience Australia. Refer to the Feature Type Cross Reference listing in Appendix A for commonly used terms that default to the Landmark Point feature type. These terms will be attributed with the following generic description on entry to the NTDB:

Where a lookout can be confirmed as having an associated tower structure in the base material/digital data or revision material it will be represented as a 'Vertical Obstruction'. Otherwise where the lookout is named or has man made features such as brickwork,paving or wooden structure it will be represented as a landmark point.

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Radio Repeator Station will be captured only when there is no evidence of the presence of buildings, otherwise they will be represented as a building with a textnote of 'radio repeator station'.

Kilns will only be captured when not associated with a chimney represented in the vertical obstructions feature type.

Ventilation shafts should be represented as mine points with a textnote 'ventilation shaft' and not as a landmark point.

Drive-in should be represented in the 'Recreation Areas' (feature class) not as a landmark point.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

General - All Scales

Landmark Point features are to have an accompanying descriptive note eg 'kiln', 'monument' unless the words 'kiln', 'monument' etc are included in the name.

Related Features

Related Chapters

Section 3 chapters 5.3, 6.6Appendix U chapter 2.4.2

Related Products

GEODATA LITE TOPO100K, NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the park (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies layer.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Recreation Areas are to have an accompanying textnote eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Training Tracks should be classified as feature type 'Miscellaneous Area' in the Recreation Areas feature class but only included when their existence can be confirmed through reference material and/or imagery.

Caravan Parks are to be captured as feature type 'Miscellaneous Area' in the Recreation Areas feature class. Caravan Park are to have an accompanying textnote eg 'caravan park' unless the words 'caravan park' etc are included in the name

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Related Chapters

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the park (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies layer.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Recreation Areas are to have an accompanying textnote eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Related Chapters

Section 3 chapters 5.11.2, 5.18, 5.19 and 6.9

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the Oval (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies layer.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Rectangular shaped areas of land for sports such as rugby, soccer, lawn bowls, hockey will not be represented as an Oval feature type but rather as a Recreation Area feature type.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Recreation Areas are to have an accompanying textnote eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 and 20 metres at 1:100 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Related Chapters

Section 3 chapters 5.11.2, 5.18, 5.19 and 6.9Appendix U chapter 2.1.3

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

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

DESCRIPTION (DESCRIPTION) [String;Yes;30;0;0;Pop_Req]

Expanded description of the type of Landmark area feature, see Geodatabase Rules for further information.

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/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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:100 000

Size and any other selection criteria apply to all feature occurrences.

General - All Scales

Landmark area features will only be used for man made entities or areas defined by man for a specific use which are clearly identifiable either through signage or infrastructure.

Landmark area features will not be used to duplicate or clone entities covered by another feature class, for example recreation area, prohibited areas, but may be used to provide a spatial link between numerous feature classes comprising a cohesive complex. They represent the area extent of a feature or complex not just its component parts, e.g. Education Facility will represent the boundary of the school lands, not just the school buildings (also represented in building points/area), ovals and tennis courts (also represented as recreation areas) and the miscellaneous land not designated for any specific purpose but still owned by the school.

The 'Power Generation Facilities' feature type includes the following (or any other feature specified by Geoscience Australia through a special instruction or action request):

The above list should be used as the acceptable description field entries, additional entries may be provided by Geoscience Australia.

When representing a Windfarm as a landmark area individual Wind generators should still be captured in landmark points but not symbolised. Similar situations where landmark points have a direct relationship with a landmark area may be treated in the same manner.

Landmark area features are to have an accompanying textnote where it expands on the description and/or name field eg 'historical'.

Related Chapters

Related Products

GEODATA LITE TOPO100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the Racecourse (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies layer.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Training Tracks should be classified as feature type 'Miscellaneous Area' in the Recreation Areas feature class but only included when their existence can be confirmed through reference material and/or imagery.

Recreation Areas are to have an accompanying textnote eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Related Chapters

Section 3 chapters 5.11.2, 5.18, 5.19 and 6.9Appendix U chapter 2.1.8

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the Recreation Area (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies layer.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Rectangular shaped areas of land for sports such as rugby, soccer, lawn bowls, hockey will not be represented as an Oval feature type but rather as a Recreation Area feature type.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Recreation Areas are to have an accompanying textnote eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Related Chapters

Section 3 chapters 5.11.2, 5.18, 5.19 and 6.9

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

IDENTIFICATION CODE (IDCODE) [String;Yes;30;0;0;Pop_Wk] The code used to identify a communication device (or provide contact with) an emergency facility point

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/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.

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;

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.

Geodatabase Rules

General - All Scales

This feature will only be captured as directed in the project instructions supplied.

This feature should be captured in correct spatial relationship to its surrounding topology.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

This feature should be captured in correct spatial relationship to its surrounding topology.

Map Rules

General - All Scales

This feature will only be included on Non-Standard NTMS maps, specially created for Emergency Mapping Purposes. A descriptive note should appear on the map derived from the description & textnote fields of the NTDB.

Related Features

Related Chapters

Section 3 Chapter 5.3

Related Products

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the Rifle Range (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies layer.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Recreation Areas are to have an accompanying textnote eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Related Chapters

Section 3 chapters 5.11.2, 5.18, 5.19 and 6.9Appendix U chapter 2.1.7

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

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/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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

A Rubbish Tip (feature type) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another Rubbish Tip edge (feature type polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)RecreationAreas (feature class polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

A Rubbish Tip (feature type) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Sea edge (feature type polygon)Waterbodies edge (feature class polygon)Built Up Area edge (feature type polygon)

Map Rules

General - All Scales

Features should be labelled 'rubbish tip'.

Related Features

Built Up Area, Cemetery Area, RecreationAreas (Feature Class)

Related Chapters

Section 3 chapters 5.18, 5.19 and 6.9

Related Products

NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

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

DESCRIPTION (DESCRIPTION) [String;Yes;30;0;0;Pop_Req]

Expanded description of the type of Landmark area feature, see Geodatabase Rules for further information.

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/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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:100 000

Size and any other selection criteria apply to all feature occurrences.

General - All Scales

Landmark area features will only be used for man made entities or areas defined by man for a specific use which are clearly identifiable either through signage or infrastructure.

Landmark area features will not be used to duplicate or clone entities covered by another feature class, for example recreation area, prohibited areas, but may be used to provide a spatial link between numerous feature classes comprising a cohesive complex. They represent the area extent of a feature or complex not just its component parts, e.g. Education Facility will represent the boundary of the school lands, not just the school buildings (also represented in building points/area), ovals and tennis courts (also represented as recreation areas) and the miscellaneous land not designated for any specific purpose but still owned by the school.

Scientific Facilities include the following (or any other feature specified by Geoscience Australia through a special instruction or action request):

The above list should be used as the acceptable description field entries, additional entries may be provided by Geoscience Australia.

When representing a Windfarm as a landmark area individual Wind generators should still be captured in landmark points but not symbolised. Similar situations where landmark points have a direct relationship with a landmark area may be treated in the same manner.

Landmark area features are to have an accompanying textnote where it expands on the description and/or name field eg 'historical'.

Related Chapters

Related Products

GEODATA LITE TOPO100K, NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the Show Ground (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/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.

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.

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.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Recreation Areas will be named, when known, in the base or reference material.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

General - All Scales

Recreation Areas will usually occur surrounded by built-up areas. They may also be isolated polygons outside the built up area.

Recreation Areas should not be confused with the Nature Conservation Reserve feature.

Recreation Areas may overlap polygons in the Waterbodies feature dataset. Waterbodies fully included in recreation areas will be considered part of the recreation area. These waterbodies will also be shown in the waterbodies layer.

Where different types of RecreationAreas existing within base material adjoin one another, each area which meets or exceeds the minimum size for inclusion will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum 'inclusion' criteria to show separately but which together create an area at or above the minimum size for inclusion will be shown as a single polygon.

When capturing a new feature from reference material, each area which meets or exceeds the minimum size for data capture will be shown as a separate polygon and attributed accordingly. Adjoining areas not meeting the minimum data capture criteria to show separately but which together create an area at or above the minimum size for data capture will be shown as a single polygon.

Recreation Areas (Feature Class) adjacent, or within, school grounds will still be captured as long as they meet the definition of the applicable Recreation feature type and associated size criteria (e.g. oval, miscellaneous area (tennis courts).

Recreation Areas are to have an accompanying textnote eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:25 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:100 000

A Recreation Areas (feature class) edge must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;another RecreationAreas (feature class polygon)Cemetery Area edge (feature class polygon)LandmarkAreas (feature class polygon)Rubbish Tip edge (feature type polygon)

1:250 000

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:another RecreationAreas edge (feature class polygon)Cemetery Area edge (feature type polygon)Rubbish Tip edge (feature type polygon)

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

1:100 000

A RecreationAreas edge (feature class polygon) must be coincident with the following features where it abuts (shares a cadastral boundary with) them in reality;Built Up Area edge (feature type polygon)Landmark Area edge (feature type polygon)Waterbodies edge (feature dataset polygon)Sea edge (feature type polygon)

Where a RecreationAreas edge (feature class polygon) is within 50 metres at 1:250 000 of and runs alongside the following features it will be coincident with the other feature:RoadRailwaySea wallShorelineWaterbodyBoundaries (except junction and Limit Of Data)Building Area edge (feature type polygon)Built Up Area edge (feature type polygon)Foreshore Flat edge (feature type polygon)Landmark Area edge (feature type polygon)Prohibited Area edge (feature type polygon)MarineHazardAreas edge (feature class polygon)Reserves edge (feature class polygon)Vegetation edge (feature dataset polygon)

Map Rules

General - All Scales

Recreation Areas will be named where they are considered to be of national cultural or historical significance. E.g. Melbourne Botanical Gardens, Taronga Zoo.

Recreation Areas are to have an accompanying descriptive note eg 'golf course', 'showgrounds' unless the words 'golf course', 'showgrounds' etc are included in the name. 'Miscellaneous Area', 'Multiple use' and 'other' will not be used as descriptive labels.

In areas where there are a number of recreation areas and other detail the labels may be dropped to avoid clutter. In such cases preference will be given to showing labels on the following types of recreation area in descending order.

Recreation Areas of national cultural or historical significance rifle rangeshowgroundracecoursegolf courseovalAll other categories

Related Features

Related Chapters

Section 3 chapters 5.11.2, 5.18, 5.19 and 6.9

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

IDENTIFICATION CODE (IDCODE) [String;Yes;30;0;0;Pop_Wk] The code used to identify a communication device (or provide contact with) an emergency facility point

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/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.

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;

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.

Geodatabase Rules

General - All Scales

This feature will only be captured as directed in the project instructions supplied.

This feature should be captured in correct spatial relationship to its surrounding topology.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

This feature should be captured in correct spatial relationship to its surrounding topology.

Map Rules

General - All Scales

This feature will only be included on Non-Standard NTMS maps, specially created for Emergency Mapping Purposes. A descriptive note should appear on the map derived from the description & textnote fields of the NTDB.

Related Features

Related Chapters

Section 3 Chapter 5.3

Related Products

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

The name of the Swimming Pool (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/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.

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;

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.

Geodatabase Rules

General - All Scales

All swimming pools outside the defined Built Up Area will be captured.

Inside the defined Built Up Area, only publicly operated swimming pools that are not fully contained within a building will be captured.

Only Public Community Swimming Pools should be named, where name is known.

Related Features

Related Chapters

Section 3 Chapter 5.3Appendix C Appendix U chapter 2.3.1, 2.3.2

Related Products

GEODATA LITE TOPO100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Vertical Obstruction

VerticalObstructions

Culture

Point

Prominent man-made features of a permanent nature that either have landmark value, are useful for navigation or may constitute a danger to aircraft. Such features will have a height above the local terrain.

Data Attributes

The name of the vertical obstruction. This item should be populated where name is known.

DESCRIPTION (DESCRIPTION) [String;Yes;30;0;0;Pop_Req]

Description of the type of Vertical Obstruction feature, for example 'aerial', 'wind turbine generator', 'chimney'. The description field will be all lower case. See Geodatabase Rules for a list of generic terms.

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/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.

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;

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.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Offshore marine lights and beacons will be included only when they are represented on the associated 1:1 000 000 World Aeronautical Chart.

At 1:100 000 Vertical Obstruction features whose area is larger than 40 000 sq. m will be shown as a Landmark Area (feature class) feature.

At 1:100 000 when representing a Windfarm as a landmark area individual Wind generators should still be captured in Vertical Obstructions but not symbolised. Similar situations where Vertical Obstructions have a direct relationship with a landmark area may be treated in the same manner.

The following are typical examples of man-made features that are to be included as Vertical Obstructions.Note: This listing does not represent all features that may be considered for inclusion in this Feature Type. Other man-made features meeting the definition and criteria for this feature type (and not represented by any other entity i.e building, recreation area) may be included where sourced from authorised Revision Information, Special Instructions or Action Requests supplied by Geoscience Australia. Refer to the Feature Type Cross Reference listing in Appendix A for commonly used terms that default to the Vertical Obstruction feature type. These terms will be attributed with the following generic description on entry to the NTDB:

Where a lookout can be confirmed as having an associated tower structure in the base material/digital data or revision material it will be represented as a 'Vertical Obstruction'. Otherwise where the lookout is named or has man made features such as brickwork,paving or wooden structure it will be represented as a landmark point.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Offshore marine lights and beacons will be included only when they are represented on the associated 1:1 000 000 World Aeronautical Chart.

At 1:100 000 Vertical Obstruction features whose area is larger than 40 000 sq. m will be shown as a Landmark Area (feature class) feature.

At 1:100 000 when representing a Windfarm as a landmark area individual Wind generators should still be captured in Vertical Obstructions but not symbolised. Similar situations where Vertical Obstructions have a direct relationship with a landmark area may be treated in the same manner.

The following are typical examples of man-made features that are to be included as Vertical Obstructions.Note: This listing does not represent all features that may be considered for inclusion in this Feature Type. Other man-made features meeting the definition and criteria for this feature type (and not represented by any other entity i.e building, recreation area) may be included where sourced from authorised Revision Information, Special Instructions or Action Requests supplied by Geoscience Australia. Refer to the Feature Type Cross Reference listing in Appendix A for commonly used terms that default to the Vertical Obstruction feature type. These terms will be attributed with the following generic description on entry to the NTDB:

Where a lookout can be confirmed as having an associated tower structure in the base material/digital data or revision material it will be represented as a 'Vertical Obstruction'. Otherwise where the lookout is named or has man made features such as brickwork,paving or wooden structure it will be represented as a landmark point.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Offshore marine lights and beacons will not be included as vertical obstruction features at 1:250 000.

The following are typical examples of man-made features that are to be included as Vertical Obstructions.Note: This listing does not represent all features that may be considered for inclusion in this Feature Type. Other man-made features meeting the definition and criteria for this feature type (and not represented by any other entity i.e building, recreation area) may be included where sourced from authorised Revision Information, Special Instructions or Action Requests supplied by Geoscience Australia. Refer to the Feature Type Cross Reference listing in Appendix A for commonly used terms that default to the Vertical Obstruction feature type. These terms will be attributed with the following generic description on entry to the NTDB:

Where a lookout can be confirmed as having an associated tower structure in the base material/digital data or revision material it will be represented as a 'Vertical Obstruction'. Otherwise where the lookout is named, it will be represented as a Place name (small feature with an identifiable location).

General - All Scales

New towers and other obstructions will be added from the towers reference material. Where the position of new towers can not be verified on the imagery or other reference or supporting material they will be labelled '(position approximate)'. If the feature is in a closely settled area, the exact location should be sought via an Action Request.

Vertical Obstruction features will only be used for man made entities.

Vertical Obstruction features are not shown in or in close proximity to Built Up Areas, unless the feature is of significant landmark value.

Vertical Obstruction features will only be used for entities which cover a small area on the ground and which are usually prominent from a distance.

Indigenous sacred sites will not be named as sacred sites on the map even if named on a previous edition map, but the feature may be a lake, pool or waterhole in which case the appropriate map symbol and hydrological name will be used.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

General - All Scales

Vertical Obstruction features are to have an accompanying descriptive note eg 'communications tower', 'wind turbine generator' unless the words 'communications tower', 'wind turbine generator' etc are included in the name. The generic descriptions (only) of 'chimney', 'silo' and 'tower' will not be included on map face as they are represented in the legend.

Height above ground level of features will be shown as part of the descriptive note where it equals or exceeds 44.50 metres rounded to the nearest metre and when that information is available.

Related Features

Related Chapters

Section 3 chapters 5.3, 5.20, 6.6Appendix U chapter 2.4.2

Related Products

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

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Description of the type of water access (e.g. fire hydrant, overhead stand pipe)

IDENTIFICATION CODE (IDCODE) [String;Yes;30;0;0;Pop_Wk] The code used to identify a communication device (or provide contact with) an emergency facility point

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/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.

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;

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.

Geodatabase Rules

General - All Scales

This feature will only be captured as directed in the project instructions supplied. It includes such features as fire hydrants, overhead standpipes, etc

This feature should be captured in correct spatial relationship to its surrounding topology.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

This feature should be captured in correct spatial relationship to its surrounding topology.

Map Rules

General - All Scales

This feature will only be included on Non-Standard NTMS maps, specially created for Emergency Mapping Purposes. A descriptive note should appear on the map derived from the description & textnote fields of the NTDB.

Related Features

Related Chapters

Section 3 Chapter 5.3

Related Products

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Water Tank

WaterStoragePoints

Culture

Point

Water Tanks are storage containers for water, usually used for human consumption and other purposes such as irrigation, agriculture, fire suppression, agricultural farming and livestock, chemical manufacturing and food preparation. Water Tanks are constructed of various materials including plastic (polyethylene or polypropylene), fibreglass, reinforced concrete, steel (welded or bolted, carbon or stainless), and are generally fully enclosed.

The name of the Water Tank (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/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.

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;

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.

Geodatabase Rules

1:25 000

All water tanks in sparsely and moderately settled regions as defined by Appendix C ' Fence and Water Facilities Guide' should be captured, no filtering should occur. Water Tanks inside densely settled regions will be captured upon direction from Geoscience Australia.

Only water tanks in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Water Tanks within Built Up Areas will not be classified with an upperscale equal to, or greater than, '100000'. 'Greater than' refers to smaller scales such as '250000','1000000'.

Names will be captured, where known.

1:100 000

Water Tanks existing in approved Geoscience Australia base material will be included unfiltered regardless of location within Australia (e.g. data derived through the 1:25 000 data capture program).

New feature should only be captured in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', size and any other selection criteria apply to all feature occurrences.

Only Water Tanks in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', will be acceptable to be classified as an upperscale equal to, or greater (smaller scale) than, '100000'. Additional filtering criteria based on surrounding topography and cartographic generalisation principles as listed in Appendix C should be used to refine the upperscale tagging.

Water Tanks within Built Up Areas will not be classified with an upperscale equal to, or greater than, '100000'. 'Greater than' refers to smaller scales such as '250000','1000000'.

Names will be captured, where known.

General - All Scales

This feature can be used to represent water tanks (ie a physical tank structure) however it will not be used to capture Town Rural Storage Reservoirs or FloodIrrigationStorage Reservoirs smaller then their minimum size criteria.

This feature will be used to represent the location of an individual water tank as well as groups of tanks. A group of tanks that cannot be shown individually may also be shown by a representative pattern.

Water Tanks to have an accompanying textnote e.g: 'aquarium' for features not being used directly for human or livestock consumption.

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

Water tanks cannot overlap;Building Area (Ruin).

1:100 000

Water tanks cannot overlap;Building Area (Ruin).

General - All Scales

Where a Bore and a Water Tank are situated together, both will be included in the data but only the Water Tank will be shown as it usually has the greater landmark value. Bore should be symbolised to 0 (non - printing).

Water Tanks plotted within 2.5 mm at map scale of a Built Up Area will be symbolised to 0 (non-printing).

Water tanks cannot overlap;Flood Irrigation Storage.

Map Rules

General - All Scales

Names will be shown in sparsely settled areas.

As the density of the cultural detail increases, names will be progressively omitted.

Water Tanks to have an accompanying descriptive note e.g: 'aquarium' for features not being used directly for human or livestock consumption.

Where a Water Tank and Windpump are situated together, only the Windpump, which has the greater landmark value, will be shown. (Refer feature Windpump).

Related Features

Related Chapters

Section 3 Chapter 5.3Appendix C Appendix U chapter 2.3.1, 2.3.2

Related Products

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

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Water Tank

WaterTanks

Culture

Point

A feature constructed for the storage of water, including both enclosed man-made containers or open bodies of water behind constructed barriers in the natural landscape. The storage of water may occur on or below ground level.

Data Attributes

The name of the Water Tank (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/digital data for initial 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/digital data for initial capture) used for Attribute Verification.

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.

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.

Geodatabase Rules

General - All Scales

All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. Size and any other selection criteria apply to new feature occurrences. New features will only be captured in sparsely and moderately settled regions as defined by Appendix C ‘Fence and Water Facilities Guide’.

Water tanks larger than 140625 sq. m at 1:250 000 will be shown as a TownRuralStorage reservoir feature.

This feature can be used to represent both water tanks (ie a physical tank structure) or an undersized Town Rural Storage Reservoir. This feature will not be used to capture FloodIrrigationStorage Reservoirs smaller then their minimum size criteria.

This feature will not be shown in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' regardless of whether it was shown on/in the base material/digital data. Refer to Appendix C for more information on when to capture this feature.

This feature will be used to represent the location of an individual water tank as well as groups of tanks. A group of tanks that cannot be shown individually may also be shown by a representative pattern.

Names will be shown in sparsely settled areas.

Water Tanks to have an accompanying textnote e.g: 'aquarium' for features not being used directly for human or livestock consumption.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Where a Water Tank and Windpump are situated together, only the Windpump, which has the greater landmark value, will be shown. (Refer feature Windpump).

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Where a Bore and a Water Tank are situated together, both will be included in the data but only the Water Tank will be shown as it usually has the greater landmark value. Bore should be symbolised to 0 (non - printing).

Water Tanks plotted within 2.5 mm at map scale of a Built Up Area will be symbolised to 0 (non-printing).

Related Features

Related Chapters

Appendix C Appendix U chapter 2.3.1, 2.3.2

Related Products

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

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

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

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/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.

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;

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.

Geodatabase Rules

1:25 000

New features will only be captured in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', size and any other selection criteria apply to all feature occurrences.

1:100 000

New features will only be captured in sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', size and any other selection criteria apply to all feature occurrences.

1:250 000

In sparsely and moderately settled regions as defined by Appendix C 'Fence and Water Facilities Guide', size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

General - All Scales

This feature will not be captured/retained in densely settled regions as defined by Appendix C 'Fence and Water Facilities Guide' regardless of whether it was shown on/in the base material/digital data. Refer to Appendix C for more information on when to capture this feature.

Windpumps will be shown when the features are sufficiently prominent to serve as landmarks.

This feature will be used to represent the location of an individual windpump as well as groups of windpumps. A group of windpumps that cannot be shown individually may also be shown by a representative pattern.

Inter-Feature Relationship Rules - Internal to Associated Dataset

1:250 000

Where a Water Tank and Windpump are situated together, only the Windpump, which has the greater landmark value, will be shown. (Refer feature Windpump).

Inter-Feature Relationship Rules - External to Associated Dataset

Map Rules

Windpumps will be named where named on the base material/digital data or revision source material supplied.

Where a Water Tank/Dam and Windpump are situated together, only the Windpump, which has the greater landmark value, will be shown. (Refer feature Windpump).

Related Features

Bore , Water Tank, Dam

Related Chapters

Section 3 Chapter 5.3Appendix C

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.

Data Attributes

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

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/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.

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;

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.

Geodatabase Rules

1:25 000

This feature will only be captured in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide', size and any other selection criteria apply to all feature occurrences.

Features greater than 3906 sq m will be depicted using the feature class Fence.

1:100 000

This feature will only be captured/retained in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide', size and any other selection criteria apply to all feature occurrences.

Features greater than 62500 will be depicted using the feature class Fence.

1:250 000

This feature will only be captured in sparsely settled regions as defined by Appendix C 'Fence and Water Facilities Guide', regardless of whether it previously existed in the TOPO250K NTDB. Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB in sparsely settled regions will be retained unless there is clear evidence they no longer exist.

Features greater than 390625 sq m will be depicted using the feature Fence (see Fence).

Inter-Feature Relationship Rules - Internal to Associated Dataset

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Yards that are within 2mm at map scale of a bore or homestead will be symbolised to 0 (non-printing).

Map Rules

Related Features

Fence, Standard Fence, Vermin Proof Fence

Related Chapters

Section 3 Chapter 5.3Appendix C

Related Products

GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.