search

ngageoint / hootenanny

Hootenanny conflates multiple maps into a single seamless map.
GNU General Public License v3.0
353 stars 74 forks source link

Handle Z Values #4808

Open MikeTho16 opened 3 years ago

MikeTho16 commented 3 years ago

Introduction Z values are not attributes, but are a special piece of data associated with every vertex in a dataset. They are typically used to hold the ground elevation (above some specified vertical datum) at the location of the vertex in question. Z values are supported by shapefiles, File Geodatabases, SDE, and many other formats.

Is your feature request related to a problem? Please describe. There is a need to represent 3D data (really 2.5D, or LOD0)

Describe the solution you'd like Import When importing data from a GIS format (e.g. shapefile, fgdb), z values should be translated to z tags on individual nodes and the nodes that are members of ways and relations. The system will need to handle the possibility that two coincident vertices might have different z values. Initially this could be handled by an error message, but eventually we may want to generate multiple different nodes (and still issue an error message).

Export When exporting data to a GIS format, z tags should be translated to z values in the resulting GIS data.

Schema Switcher Translation A z tag should simply be passed unchanged when translating between different schemas.

mattjdnv commented 3 years ago

I think this is doable. The OSM ele:wgs84 tag could work https://wiki.openstreetmap.org/wiki/Key:ele:wgs84