Wetlands Extent for Victoria Prior to European Settlement - Deduced
Anzlic ID:
ANZVI0803001065
Custodian:
Abstract:
Polygons showing the extent of wetlands in Victoria prior to European settlement. Wetlands are classified into primary categories based on water regimes.
The polygon boundaries were derived from digitizing marked up aerial photography interpretation.
Search Words:
Inland waters
Publication Date:
01 February 2018
Dataset Status:
All wetlands with an area of 1 hectare or more should be present.
All wetlands with an area of 1 hectare or more should be present.
Progress:
Completed
Access Constraint:
Creative Commons Attribution 4.0 (CC-BY)
(
License Text
)
Data is available under licence.
Access subject to custodial approval.
Data Existence:
Metadata Name
Descriptions
Resource Name:
WETLAND_1788
Title:
Wetlands Extent for Victoria Prior to European Settlement - Deduced
Anzlic ID:
ANZVI0803001065
Custodian:
Owner:
Jurisdiction:
Victoria
Abstract:
Polygons showing the extent of wetlands in Victoria prior to European settlement. Wetlands are classified into primary categories based on water regimes.
The polygon boundaries were derived from digitizing marked up aerial photography interpretation.
Search Words:
Inland waters
Purpose:
WETLAND_1788 is one of two layers designed to document changes over time in the nature and extent of wetland environments in Victoria. This layer is directly related to WETLAND_1994 via the use of a common wetland identification system. It is a simpler layer than WETLAND_1994 in that there is no delineation of sub areas within wetlands.
Geographic Extent Polygon:
Geographic Bounding Box:
-34
141
150
-39
Beginning to Ending Date:
1949-01-01 - 1992-01-01
Maintainence and Update Frequency:
Not planned
Stored Data Format:
Available Format(s) Types:
DIGITAL - All major formats available
Positional Accuracy:
Precision: 10m to 100m
Determination: Deductive estimate. Ad-hoc comparisons with 1:25,000 layer data and various sorts of imagery indicated good correlation in terms of shape and size but with errors of the order indicated above in terms of position and/or rotation. When resources permit, the 1:25,000 library hydrology and roads layers should be used to identify layer inconsistencies which may indicate specific wetlands which require translation, rotation or boundary modifications.
Attribute Accuracy:
The classification scheme used is based on photo interpretation and ground surveys carried out by Departmental research staff under the direction of research scientist Andrew Corrick.
Logical Consistency:
The Wetland Mapping System includes processes for checking: *node, label and intersect errors. *validation of category codes prior to insertion in the library.
Data Source:
Dataset Source: The data has been prepared primarily from standard Survey and Mapping Victoria photo runs with some local revisions based on other historical sources.
Dataset Originality: Primary
Contact Organisation:
Contact Position:
Address:
Telephone:
Facsimile:
Email Address:
Metadata Date:
2019-02-06
Additional Metadata:
Relationship to other Datasets: As stated above, this layer is closely related to WETLAND_1994 and should be maintained in a way which ensures consistency between them in the use of identifiers and classification codes. Comparisons of this layer with HYDRO100 and HYDROP100 should be made with caution as the definitions used in delineating and classifying wetlands are likely to be significantly different in some cases.
Current Design Issues: Although the only attributes held within this layer are an identifier and a wetland category, there are several external tables in existence keyed on the same identifier. These include tables documenting RAMSAR wetlands, High Value wetlands, named wetlands and wetlands supporting breeding colonies of waterbirds.
Future Design Issues: It is envisaged that additional external tables will be defined which group wetlands in additional ways according to specific attributes (eg: membership of large scale wetland systems). Further attributes may also be added to existing tables, but none of this work should require any change to the structure of the library layer.
Related Documents: None
))