Greater Melbourne LiDAR - DTM
dataset
Dataset: Greater Melbourne LiDAR - DTM
Assembly: Mosaic
|
Citation proposal Citation proposal
Greater Melbourne LiDAR - DTM Department of Environment, Land, Water and Planning (DELWP) https://dev-metashare.maps.vic.gov.au/geonetwork/srv/eng/catalog.search#/metadata/a8bee60a-30c6-50da-86ab-4a189ba9f14f |
- Description
- Temporal
- Spatial
- Maintenance
- Format
- Contacts
- Keywords
- Resource Constraints
- Lineage
- Metadata Constraints
- Quality
- Acquisition Info
- Raster Data Details
- Raster Type Details
- Point Cloud Data Details
- Contour Data Details
- Survey Details
Simple
Description
- Title
- Greater Melbourne LiDAR - DTM
Temporal
- Time period
- 2017-11-282018-10-27
Spatial
- Horizontal Accuracy
- 0.2m
- Vertical Accuracy
- 0.1m
- Code
- MGA Zone 55 GDA2020
Maintenance
Format
- Title
- ESRI Ascii
Contacts
Point of contact
Department of Environment, Land, Water and Planning (DELWP)
PO Box 500
East Melbourne
Victoria
3002
Australia
Keywords
- Topic category
-
- Elevation
Resource Constraints
- Use limitation
- General
- Classification
- Unclassified
Lineage
- Description
- A DTM with a ground pixel spacing of one metre was generated from the LiDAR ground points. The method of deriving the height for each grid point is by triangulation between the three nearest LiDAR ground points using a nearest neighbor interpolation method. The DEM was exported to ESRI floating Point ASCII grid as 2km by 2km tiles. During classification of the LiDAR point cloud, polygons were drawn around areas of water in order to select points classified as ground and reassign these to water. These were then saved, converted to ESRI feature classes and cleaned to produce boundaries for all the water bodies greater than 625 square metres and break lines for all watercourses with a nominal width greater than 30 metres. The water boundaries were provided as shape files, as per the Statement of Requirement. For water bodies, including disconnected pools within channels, the DEM was set to the height of the lowest interpolated pixel within each polygon. For watercourses the algorithms were more complex and performed the following basic functions; creating pairs of points across river channels, determining the flow direction, interpolating downstream so that there were no humps or rises. The complexity of the algorithms was necessary to deal with confluences, connected lacustrine features and irregular banks, all of which were distinguished and dealt with differently.
Metadata Constraints
- Classification
- Unclassified
Quality
Attribute Quality
Positional Accuracy
Conceptual Consistency
- Comments
- The data adheres to the logical rules of data structure, attribution and relationships as per project specifications.
Missing Data
- Comments
- Dataset is complete for the defined project extent.
Excess Data
Acquisition Info
- Platform Type
- Aerial
- Assembly
- Mosaic
- Tile Size
- 1 km
Raster Data Details
- Raster Type
- DEM
- X Pixel Resolution (cm)
- 1cm
- Y Pixel Resolution (cm)
- 1cm
- Seamlessness
- Full
- Number of Bands
- 1
- Band List
- 1
- Resampling Kernel
- Nearest Neighbour
- Rectification Type
- Not Rectified
- Platform Name
- Fixed Wing Aircraft
Raster Type Details
- DEM Creator
- Supplier
Point Cloud Data Details
Contour Data Details
Survey Details
Sensor
- Title
- Trimble AX60
- Identifier
- Aerial
- Type
- LIDAR
- Cloud Cover Percentage
- 0
Aerial Survey Details
- Runs
- 4567
- Run Orientation
- E-W and N-S
- Swath Width
- 520
- Side Overlap
- 30
- Flying Height Unit
- agl metre
- Flight Height
- 450
Overviews
Provided by
Views Views
a8bee60a-30c6-50da-86ab-4a189ba9f14f
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