Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 000 |
---|
Production Index
ProductionIndexes
Production
Polygon
An area defining the production precedence source information used to form the NTDBs.
Minimum Size Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Production Index
TILE NUMBER (TILENUMBER) [String;Yes(No);8;0;0;Pop_Req] The geodata tile number assigned to the extent defined e.g. E5515, S9445;
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.
EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.
GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.
Geodatabase Rules
General - All Scales
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
Map Index 100K, Map Index 250K, Map Index WAC, Map Index 2_5MIL, Geodata Index (250K), Field Inspection Index, Work Package Index
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.
Scales | 1:25 000 1:100 000 1:250 000 1:1 000 000 1:2 500 000 1:5 000 000 & 1:10 000 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 Criterion:
Minimum Size for Inclusion: | Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features |
Minimum Size for Data Captured and Map Representation (per scale): |
Area (sq m) Criterion | Length (m) Criterion |
---|---|---|
All features Regardless of Scale |
Data Attributes
FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.
Production Note
PRODUCTION FEATURE TYPE (PRODUCTIONFEATURETYPE) [String;Yes;32;0;0;Pop_Req] The feature type of the production feature in question.
PRODUCTION PID (PRODUCTIONPID) [Integer;Yes;0;8;0;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) [Integer;Yes;0;8;0;Pop_Req] The oid value of the production feature in question.
LINK TO SOURCE FEATURE CLASS GLOBAL ID (SRCFEATURECLGIDLINK) [GUID;Yes(No);26;0;0;Pop_Req] The Global id value of the associated feature class entity to provide a relational link.
PRODUCTION NUMBER (PRODUCTIONNUMBER) [Integer;Yes;0;8;0;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.
PRODUCER (PRODUCER) [String;Yes;50;0;0;Pop_Req] The name of the company who is supplying information on production activities.
PRODUCTION COMMENTS (PRODUCTIONCOMMENTS) [String;Yes;1000;0;0;Pop_Req] A single/series of comments included to explain the reasoning behind a production activity.
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.
EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.
GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.
Geodatabase Rules
General - All Scales
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 NTDB.
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 reference material. 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 NGIG number (eg A/R C7710) unless there is no NGIG 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.
Topic contact: mapfeedback@ga.gov.au Last updated: January 20, 2012