Horsham - DEM
dataset
Dataset: Horsham - DEM
Assembly: Single
|
Citation proposal Citation proposal
Horsham - DEM Department of Transport and Planning https://metashare.maps.vic.gov.au/geonetwork/srv/eng/catalog.search#/metadata/c2267c5c-4025-5d1c-a81a-c3f0f9ca4cf0 |
- Description
- Temporal
- Spatial
- Maintenance
- Format
- Contacts
- Keywords
- Resource Constraints
- Lineage
- Metadata Constraints
- Quality
Description
- Title
- Horsham - DEM
- Resource Type
- Dataset
Temporal
Spatial
- Spatial representation type
- Grid
- Horizontal Accuracy
- 0.3m
- Code
- MGA Zone 54 GDA94
Maintenance
Format
- Title
- ESRI Ascii
Contacts
Point of contact
Department of Transport and Planning
-
Coordinated Imagery Program
PO Box 500
East Melbourne
Victoria
3002
Australia
Keywords
- Topic category
-
- Elevation
Resource Constraints
- Use limitation
- General
- Classification
- Unclassified
Lineage
- Description
- ArcGIS 9.2 Terrain Grids were derived using the Natural Neighbor interpolation from points representing Classes 2. This method uses the closest triangles and applies weights to the proportionate areas from the grid cell centroid to interpolate the value. It uses known elevation data, it does not make any predictions regarding the surface and accurately depicts existing troughs and peaks in the data and supports irregular point spacing, which suits the nature LiDAR data. Hydro Flattening process was undertaken on the data, during editing of the LiDAR point cloud 2D hydro boundaries of water bodies were manually digitized. The hydro boundary polygons were digitized from the LiDAR intensity imagery and the LiDAR surface model, these results were verified against aerial imagery. The hydro boundaries were then draped onto LASD dataset and the minimum Z for each hydro polygon extracted. Heighted hydro polygons then incorporated into LASD dataset. LASD to DEM grid process generation using hydro flattened polygons. The Horsham project are was mereged with the 2011-12 Flood Plains LiDAR Stage 2- Wimmera CMA project. The a point cloud was used in the DEM merge process, a minimum of 50m overlap was used between the projects, cut lines were derived to avoid areas of change in the overlap area. The Ground and non ground data was reclassified in the overlap area to avoid any `noise¿ between merged datasets. The merged DEM's were created using the new merged point cloud data. Breaklines such as the water polygons digitized during the LiDAR editing stages of the Hydro Flattening were used.
Metadata Constraints
- Classification
- Unclassified
Quality
Attribute Quality
Positional Accuracy
Conceptual Consistency
- Comments
- The DEMs are consistent with respect to their visual representation of the ground features, continuity at the tile boundaries and representation of elevation values.
Missing Data
- Comments
- The DEM tiles supplied are complete for the defined project extents. No Data has a alue of -9999.
Excess Data
Overviews
Provided by
Views Views
c2267c5c-4025-5d1c-a81a-c3f0f9ca4cf0
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