Updated: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000 &
1:1 000 000

Field Inspection Index

FieldInspectionIndex

MetadataIndex

Polygon

An area which will be undergoing, or has undergone, field inspection for data and map compilation and revision activities by Geoscience Australia or Associated Agencies.

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.

Field Inspection Index

FIELD CHECK NAME (FIELDINSPECTIONNAME) [String;Yes;50;0;0;Pop_Dep] Designated Name of Field Check including month and year when field check occurred. E.g Beenleigh field check name occurred in March 2007 so name should be Beenleigh0307.

FIELD CHECK TYPE (FIELDINSPECTIONTYPE) [String;Yes;25;0;0;Pop_Req] Type of methodology used to conduct field check.

Acceptable Domain Entries from dm_FieldInspections;
Audit
Liaison
Liaison/PostProduction
Liaison/PreProduction
PostProduction
PreProduction

PROJECT FILE NAME AND LOCATION (PROJECTFILE) [String;Yes;255;0;0;Pop_Wk] Project files associated with a Field Check or Work Package ,as appropriate, which may be required to be referenced for future review. This will be stored as a hyperlink.

THEMES INSPECTED (THEMESINSPECTED) [String;Yes;255;0;0;Pop_Req] Themes reviewed during Field Check based around Geoscience Australia's topographic production schema design.

INSPECTION DATE (INSPECTIONDATE) [Date;Yes;36;0;0;Pop_Req] Date of first day of field inspection.

COMMENTS (COMMENTS) [String;Yes(No);1000;0;0;Pop_Req] Additional comments supplied by operator to describe the exact nature of the error or feature.

FIELD TEAM MEMBERS (FIELDTEAM) [String;Yes;255;0;0;Pop_Wk] First Name and Family Names of the field team members. e.g. James Brown, Jack Ripper

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.

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


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]



Updated: 31/01/2012

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

Work Package Index

WorkPackageIndex

MetadataIndex

Polygon

An area which has undergone, or which will in the near future, revision work on particular themes.

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.

Work Package Index

WORK PACKAGE CODE (WORKPACKAGECODE) [SmallInteger;Yes;0;4;0;Pop_Req] The 4 digit work package code determined via GeoOperations Project Leaders Project Management Database.

WORK UNIT CODE (WORKUNITCODE) [SmallInteger;Yes;0;4;0;Pop_Req] The 4 digit work unit code determined via GeoOperations Project Leaders Project Management Database.

ACCURACY SUBSET CODE (SUBSETCODE) [SmallInteger;Yes;0;2;0;Pop_Req] This code differentiates various subsets areas of a work unit, each of which have different accuracy definitions in the related Feature Classes Revised Table.

WORK PACKAGE/WORK UNIT MERGED CODE (WPWUCODE) [String;Yes;9;0;0;Pop_Req] The combined work package code_work unit code written in the following format 0405_0321.

WORK PACKAGE/WORK UNIT/SUBSET MERGED CODE (WPWUSSCODE) [String;Yes;12;0;0;Pop_Req] The combined work package code_work unit code_subset code written in the following format 0405_0321_00.

REVISION TYPE (REVISIONTYPE) [String;Yes;20;0;0;Pop_Req] Type of Work Package for example scale.

Acceptable Domain Entries from dm_RevisionType;
100K Revision
1Mil Revision
250K Revision
25K Revision
Targeted Revision
Theme Revision

WORK PACKAGE NAME (WORKPACKAGENAME) [String;Yes;50;0;0;Pop_Dep] Designated name of Work Package.

WORK UNIT NAME (WORKUNITNAME) [String;Yes;50;0;0;Pop_Wk] Designated name of Work Unit.

PROJECT FILE NAME AND LOCATION (PROJECTFILE) [String;Yes;255;0;0;Pop_Wk] Project files associated with a Field Check or Work Package ,as appropriate, which may be required to be referenced for future review. This will be stored as a hyperlink.

THEMES UPDATED (THEMESUPDATED) [String;Yes;255;0;0;Pop_Req] Themes updated during work package activities based around Geoscience Australia's topographic production schema design.

COMMENTS (COMMENTS) [String;Yes(No);1000;0;0;Pop_Req] Additional comments supplied by operator to describe the exact nature of the error or feature.

WORK PACKAGE CONTACTS (WPCONTACTS) [String;Yes;50;0;0;Pop_Wk] Names of Primary Contacts for Information about Work Package;

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.

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


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]



Topic contact: mapfeedback@ga.gov.au Last updated: January 20, 2012