TEST - Field Descriptors
dataset
Dataset: TEST - Field Descriptors
Assembly: Not Entered
|
Citation proposal Citation proposal
TEST - Field Descriptors https://uat-metashare.maps.vic.gov.au/geonetwork/srv/eng/catalog.search#/metadata/e96c6930-14fa-5466-94f7-33756ce46c3d |
- Description
- Temporal
- Spatial
- Maintenance
- Format
- Contacts
- Keywords
- Resource Constraints
- Lineage
- Metadata Constraints
- Quality
Description
- Title
- TEST - Field Descriptors
- Resource Type
- Dataset
Temporal
Spatial
- Spatial representation type
- Grid
- Horizontal Accuracy
- 9999m
- Code
- MGA Zone 54 GDA94
Maintenance
Format
- Title
- ECW
Contacts
Point of contact
Keywords
- Topic category
-
- not Entered
Resource Constraints
- Use limitation
- Departmental
- Classification
- Limited Distribution
Lineage
- Description
- Product Description Heading: LINEAGE / HISTORY Metashare Heading: HISTORY -> PROCESSING STEPS Content Description From ANZLIC /ISO STANDARDS >>>>>>>>>>>>>>>>>>>>>>>>>>>> Information aboutn the events or source data used in construction the data specified by the scope or lack of knowledge about lineage Content Description From PRODUCT DESCRIPTION TEMPLATE >>>>>>>>>>>>>>>>>>>>>>>>>>>> The sources used to construct the data set and what steps were taken in the processing of the data, including: ¿ When created; ¿ Who created; ¿ Source/material/s; ¿ How captured/created ¿ methodology, and significant issues encountered in development and ¿ How/when revised.
Metadata Constraints
- Classification
- Unclassified
Quality
Attribute Quality
Positional Accuracy
Conceptual Consistency
- Comments
- Treat as Logical Consistency Conformance to the Specification: -------------------------------------------------------------------- Product Description Heading: LOGICAL CONSISTENCY Metashare Heading: QUALITY -> ACCURACY -> LOGICAL CONSISTENCY Content Description From ANZLIC /ISO STANDARDS >>>>>>>>>>>>>>>>>>>>>>>>>>>> Degree of adherence to logical rules of data structure, attribution and relationships (data structure can be conceptually, logical or physical) Comments: How it conforms to the data model codelists (ie feature type code) and relationships. Example: That all feature type codes are complete and valid
Missing Data
- Comments
- Product Description Heading: COMPLETENESS Metashare Heading: QUALITY -> COMPLETENESS -> COVERAGE Content Description From ANZLIC /ISO STANDARDS >>>>>>>>>>>>>>>>>>>>>>>>>>>> Data which is absent from the dataset as described from the scope Example: Scope is rivers but the feature River Murray is missing, Scope is water bodies but water bodies smaller than 1ha are missing.
Excess Data
Overviews
Provided by
Views Views
e96c6930-14fa-5466-94f7-33756ce46c3d
Access to the portal Access to the portal
Read here the full details and access to the data. Read here the full details and access to the data.
Associated resources
Not available