Feature #1573
open
3d geometries
Description
In the INDIGO projects we will receive additional 3d geometry data. So far we only map points, lines and polygons so we need another geometry type (with height).
We will also use this opportunity to merge all GIS data into one table and move into the model schema (instead using a dedicated GIS schema)
In the first version they will be shown on the map but without functionality to add or edit them manually.
To consider- Adapting database (see merge suggestion above)
- How do we import them (INDIGO workflow specific)
- How do we present them on the map, I guess it should be possible to "flatten" them
- How to prevent them being overridden when working with maps the "classic" way
Updated by Alexander Watzinger over 2 years ago
- Target version changed from 252 to Wishlist
Moving to wishlist for now until we know more details how and from where we would get 3d geometry data.
Updated by Alexander Watzinger over 2 years ago
- Target version changed from Wishlist to 7.4.0
- Description updated (diff)
Added Stefan's idea to merge all GIS data into one table.
Updated by Stefan Eichert about 2 years ago
- Related to Feature #1631: Join database GIS tables added
Updated by Stefan Eichert about 2 years ago
@Geert: Which geometries are you considering? 3D Polygons/Linestrings/Points? Point Clouds? Tins? or even Polyhedral Surfaces?
Updated by Geert Verhoeven about 2 years ago
From what I have in mind right now:
vector-based:- points (3D)
- lines (3D)
- polygons (2D, 3D)
- surface meshes (triangle- or quad-based, not sure yet; note that the polygons in quad based meshes do not have to be flat, so they are not strictly polyhedral surfaces)
- georeferenced images (since we work on vertical walls, image pixels will have 3D coordinates)
I do not foresee point clouds
Updated by Stefan Eichert about 2 years ago
Geert Verhoeven wrote:
From what I have in mind right now:
vector-based:
- points (3D)
- lines (3D)
- polygons (2D, 3D)
The above should work without any problems. However to get them into the database some kind of import feature needs to be implemented.
One possibility would be to import them as WKT text strings.
- surface meshes (triangle- or quad-based, not sure yet; note that the polygons in quad based meshes do not have to be flat, so they are not strictly polyhedral surfaces)
I have not yet worked with them before in PostGIS but I will look it up and figure out howto
Raster-based
- georeferenced images (since we work on vertical walls, image pixels will have 3D coordinates)
I think just uploading these will not be a problem, but dealing with the respective geometry and visualising them probably is for the presentation frontend.
I do not foresee point clouds
Updated by Alexander Watzinger about 2 years ago
- Related to deleted (Feature #1631: Join database GIS tables)
Updated by Alexander Watzinger about 2 years ago
- Start date changed from 2021-09-11 to 2022-01-21
- Follows Feature #1631: Join database GIS tables added
Updated by Alexander Watzinger almost 2 years ago
- Target version changed from 7.4.0 to Wishlist
We already solved the prerequisites (restructuring GIS tables) in OpenAtlas with the latest release. Once we receive test data, which is needed for implementation, we move this issue from the wishlist in the actual roadmap again.