Murray Basin - Depth To Basement (1:1,000,000)
dataset:
DEPTH_TO_BASEMENT_MURRAY_BASIN
The polygons represent the depth from the surface to the Palaeozoic bedrock. The polygon data was constructed using the depth to basement contours at 50m interval generated from both drill hole data, and depth to magnetic source estimates. For detailed methodology refer to Gold Undercover report 21 - Depth to Palaeozoic basement of the Gold Undercover region using borehole and magnetic data.
|
Citation proposal Citation proposal
(2018) Murray Basin - Depth To Basement (1:1,000,000) Department of Energy, Environment and Climate Action https://metashare.maps.vic.gov.au/geonetwork/srv/eng/catalog.search#/metadata/5e869d7a-a149-5aa7-8f63-1d7a431fd1c1 |
- Description
- Temporal
- Spatial
- Maintenance
- Format
- Contacts
- Keywords
- Resource Constraints
- Lineage
- Metadata Constraints
- Quality
Description
- Title
- Murray Basin - Depth To Basement (1:1,000,000)
- Alternate title
- DEPTH_TO_BASEMENT_MURRAY_BASIN
- Resource Type
- Dataset
- Purpose
- To provide a 2D representation of the depth to Palaeozoic bedrock in the Victorian portion of the Murray Basin
- Supplemental Information
- History: Added to VSDLLD 13/03/2018 Related Documents: GSV Geoscience GIS Data Dictionary.doc - Maintained by Graham Callaway
- Status
- Completed
Temporal
- Time period
- 2013-03-232013-03-23
Spatial
- Spatial representation type
- Vector
- Horizontal Accuracy
- 250m
- Code
- 4283
N
S
E
W
Maintenance
- Maintenance and update frequency
- Irregular
Format
Contacts
Point of contact
Department of Energy, Environment and Climate Action
-
Geological Survey of Victoria
()
GPO Box 4509
Melbourne
Vic
3001
Australia
Cited responsible party
No information provided.
Cited responsible party
No information provided.
Cited responsible party
No information provided.
Cited responsible party
No information provided.
Cited responsible party
No information provided.
Keywords
- Topic category
-
- Geoscientific information
Resource Constraints
- Use limitation
- Creative Commons Attribution Version 4.0 (international licence).
- Classification
- Unclassified
Lineage
- Statement
- Dataset Source: Derived from published 3D modelling inhouse at Dept. of Primary Industries Dataset Originality: Derived
- Description
- 1. Shapefile for 50m contours generated by Mark McLean using 3d modelling in MGA54 2. Create working GDB at \\p00401\p_gsv\projects\\Solid Geology of Victoria\Depth_to_basement.gdb with 2 feature classes + topology 3. Load contours into \\p00401\p_gsv\projects\Solid Geology of Victoria\Depth_to_basement.gdb\DepthToBasement50m\Basement_contour from supplied shapefile (copy at \\p00401\p_gsv\projects\Solid Geology of Victoria\2013_02_20_murray_bsmt_contour_50.shp) 4. Select all Basement_contour arcs in arcmap and generalise (tolerance 0.001 dd) 5. Select Basement_contour arcs < 0.008dd and delete 6. Clean up arcs that look ugly (see below) and extend/ clip arcs to VMINDEX.FR_FRAMEWORK_AREA_LINE along Victorian border. 7. Check for dangles using the topology 8. Select all arcs + border arcs and construct polygons into \\p00401\p_gsv\projects\Solid Geology of Victoria\Depth_to_basement.gdb\DepthToBasement50m\Basement_depth 9. Manually populate DEPTH_TO_BASEMENT field in Basement_depth or use a spatial location selection starting with the smallest value (ie select all polygons that are touched by the selected arcs = 50m. You then have to recalculate the polygons that don't match as you will have selected both the 0-50m polygons as well as the 50-100m polygons). Watch out for depression contours! If you colour the polygons you will be able to see the wrong ones graphically. 10. Calculate the other fields for minimum and maximum depth to basement (numeric fields created to select from in Geovic - the DEPTH_TO_BASEMENT field is a text data type so can't be used for arithmetic selections) 11. When you are happy that you have coded all the polygons correctly load the shapes into a feature class you created at Database Connections\spivpro_gsv.sde\GSV.DEPTH_TO_BASEMENT (make sure it's SDO_GEOMETRY when you create it) 12. Create an sld file to symbolise the feature class in Geoserver. If you have symbolised polygons in arcmap you can convert the colours to hexadecimal values for input into your sld file. 13. Get someone with oracle rights to enable permissions and synonyms on the polygon feature class GSV.DEPTH_TO_BASEMENT to WXS_VIEWER
Metadata Constraints
- Classification
- Unclassified
Quality
Attribute Quality
- Comments
- Good
Positional Accuracy
- Comments
- Generally accurate to 1:1,000,000
Conceptual Consistency
- Comments
- Good
Missing Data
- Comments
- 1:1,000,000 complete Completeness Verification: Metadata Custodian Review Frequency: yearly Metadata Last Reviewed by Custodian: March 2013
Excess Data
- Comments
- 1:1,000,000 fair
Overviews
Provided by
Views Views
5e869d7a-a149-5aa7-8f63-1d7a431fd1c1
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