Geoscience Australia: Appendix A -Feature Type Dictionary
Updated:   5 December 2006

Scales 1:250 000 & 1:100 000

Production Index

ProductionIndexes

Production

Polygon

An area defining the production precedence source information used to form the NTDBs.

Minimum Size for Inclusion

Criterion 1:25 000 1:100 000 1:250 000
Area (sq m)      
Length (m)      

Data Attributes

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

Production Index

GEODATA TILE NUMBER (TILENUMBER) [String; No; 8; Pop_Req] The geodata tile number assigned to the extent defined e.g. E5515, S9445;

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

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

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

Geodatabase Rules

Revision of Production Indexes will only be conducted when specifically directed by GEOSCIENCE AUSTRALIA.

Inter-Feature Relationship Rules - Internal to Associated Dataset

 

Inter-Feature Relationship Rules - External to Associated Dataset

 

Map Rules

 

Related Features

 

Related Chapters

 

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.

[an error occurred while processing this directive]



Geoscience Australia: Appendix A -Feature Type Dictionary
Updated:   5 December 2006

Scales 1:250 000 & 1:100 000

Production Note

ProductionNotePoints

Production

Point

An informative notation pertaining to the background of a decision on the representation or non-representation of a real world feature within the database.

Minimum Size for Inclusion

Criterion 1:25 000 1:100 000 1:250 000
Area (sq m)      
Length (m)      

Data Attributes

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

Production Note

PRODUCTION FEATURE TYPE (PRODUCTIONFEATURETYPE) [String; Yes; 32; Pop_Req] The feature type of the production feature in question.

PRODUCTION PID (PRODUCTIONPID) [Long Integer; Yes; 8; Pop_Dep] The pid value of the production feature in question. If a PID value has been assigned to the production feature it must be populated in this field. If no PID value has been assigned to the production feature this item may be left blank.

PRODUCTION OID (PRODUCTIONOID) [Long Integer; Yes; 8; Pop_Req] The oid value of the production feature in question.

PRODUCTION NUMBER (PRODUCTIONNUMBER) [Long Integer; Yes; 8; Pop_Dep] A unique production assigned number assigned for cross reference purposes. Population of this item should only be conducted on direction by GEOSCIENCE AUSTRALIA.

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

PRODUCER (PRODUCER) [String; Yes; 50; Pop_Req] The name of the company who is supplying information on production activities

PRODUCTION COMMENTS (PRODUCTIONCOMMENTS) [String; Yes; 1000; Pop_Req] A single/series of comments included to explain the reasoning behind a production activity.

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

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

Geodatabase Rules

These should exist whenever either a justification or explanation is needed regarding why an action was conducted that is inconsistent with relevant Project Instructions, or Specifications during the creation and/or revision of data within the NTDBs.

An explanation is not required when what has been done is just standard procedure that should be obvious to all eg attributing a feature from its primary source. However if the source is obscure or non standard, or a subjective decision made which is in a grey area, then a note will be needed.

If reference is made to a large scale map or other source that VAT will not have ready access to, then an attachment showing the source needs to be included on the project file and referred to in the production note. The attachment should be clearly labelled in the top right corner with the attachment number, map (or other) name and edition. If the feature that is the subject of the production note is named it is beneficial to quote the name in the note to aid quick identification.

It is permissible to write a general production note covering many features, unless each feature needs for some reason to be specifically identified. When a production note refers to one feature that is composed of more than one arc, it is generally only necessary to write one note. Its can be placed centrally on the feature.

The note should contain all the necessary information, reasons and justifications to enable the reader to come to the same decision.

All Action Requests relevant to your work package should be referred to in the production notes.

Refer to Action Requests in production notes by just the NMD number (eg A/R C7710) unless there is no NMD number. In these cases obviously the producer number would be then quoted as such - A/R RFD2751.

An Action Request listing should be included in the project file and this listing should highlight both numbers for cross reference purposes.

Reference to attachments shown as such:- 'A landing ground was placed as per Mobilong 25k map Edn 2 (see attachment 21).

Inter-Feature Relationship Rules - Internal to Associated Dataset

 

Inter-Feature Relationship Rules - External to Associated Dataset

 

Map Rules

 

Related Features

 

Related Chapters

 

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.


[back to top]





Unless otherwise noted, all Geoscience Australia material on this website is licensed under the Creative Commons Attribution 3.0 Australia Licence.