Metadata Name Descriptions
Resource Name: BATHYMETRY_GIPPSLAND_LAKES_ARC
Title: Gippsland Lakes Depth Contours at 1:25,000
Anzlic ID: ANZVI0803004014
Custodian:
Abstract:
This layer contains line features which represent depth contours (bathymetry) in the Gippsland Lakes.
Search Words: Oceans
Publication Date: 23 January 2018
Dataset Status: Layer has been completed for Gippsland Lakes, not including Lake Wellington which is a relatively shallow waterbody with little variation in depth.
Progress: Completed
Access Constraint:
Creative Commons Attribution 4.0 (CC-BY) ( License Text )
http://www.data.vic.gov.au/ The depth information contained within this layer should not be used for navigational purposes.
Data Existence:
Metadata Name Descriptions
Resource Name: BATHYMETRY_GIPPSLAND_LAKES_ARC
Title: Gippsland Lakes Depth Contours at 1:25,000
Anzlic ID: ANZVI0803004014
Custodian:
Owner:
Jurisdiction: Victoria
Abstract:
This layer contains line features which represent depth contours (bathymetry) in the Gippsland Lakes.
Search Words: Oceans
Purpose:
BATHYMETRY_GIPPSLAND_LAKES_ARC is a 1:25,000 layer used for depth analysis.
A specific use for depth zone information include comparative analysis with fisheries catch data and representing the movement of commercial species in three dimensions.  
The depth information within this layer should not be used for navigation purposes.
Geographic Extent Polygon:

Geographic Bounding Box:
Beginning to Ending Date: 1981-06-01 - 1999-11-30
Maintainence and Update Frequency: As needed
Stored Data Format:
Available Format(s) Types: DIGITAL All major formats available on request.
Positional Accuracy:
Not determined.
The depth information within this layer should not be used for navigation purposes.
Attribute Accuracy:
All attributes have been checked by DPI Queenscliff
Logical Consistency:
Not available.
Data Source:
Dataset Source: Data was digitised from Victorian Channels Authority charts (formerly Ports and Harbours).  Two types of data were digitised.  Firstly, depth contours that had been manually interpreted and drafted on the charts by Ports and Harbours were digitised as arcs.  For the area between Flannagan Island and Lakes Entrance, contours were created automatically in ARCINFO by digitising depth points.  The depth charts used to create the layer are listed below.

Depth Contours
GL166-2752.  Lake King scale 1:25,000.  Surveyed June 1981-1982: Composite chart derived from 1:10,000 series, Ports and Harbours. Shore detail derived from 1:25,000 series , Lands Department. Contours show depths below A.H.D..
GL165-2751.  Lake Victoria scale 1:25,000.  Surveyed June 1981-1982: Composite derived from 1:10,000 series, Ports and Harbours. Shore detail derived from 1:25,000 series, Lands Department. Contours show depths below A.H.D..
Depth Points
GL159-2596.  Flannagan Island to Lakes Entrance.  Scale 1:10,000.  Surveyed July-Aug, 1981.   Soundings are in decimetres. Datum for soundings is 1.313 metres below the P.S.M. plaque in the concrete wall at the base ot the new works jetty and is 0.537 metres below A.H.D.
GL158-2590.  Tambo Bluff to Flannagan Island.  Scale 1:10,000.  Surveyed June-Oct, 1981: Soundings are in decimetres. Datum for soundings is A.H.D. which is 1.858 metres below the level of the permanent mark 397, situated at the eastern end of Fort King Road.


Dataset Originality: Primary & Derived
Contact Organisation:
Contact Position:
Address:
Telephone:
Facsimile:
Email Address:
Metadata Date: 2014-11-13
Additional Metadata:
                            
                              History: This layer replaced GL_BATHYM in March 2010

Current Design Issues: Bathymetric information is initially collected as point features or spot depths.  Isobaths are interpreted either by visual manual methods or by automated techniques.  As more data becomes available the positional accuracy of isobaths should be revised.  Each acquisition of depth information needs to be documented and assessed before it is incorporated in the layer.

Future Design Issues: This layer is a base line data set and future design considerations will be limited.

Related Documents: None
                            
                          
Column Name Obligation Unique Data Type Reference Table Comments
FEATURE O N VARCHAR2
LENGTH_M O N NUMBER
DEPTH O N NUMBER
SOURCE O N VARCHAR2
GL_BATH_G1 O N NUMBER
GL_BATH_G_ O N NUMBER
VERSION O N NUMBER