Hello
I am fairly new to 3D data handling and stumbled over the problem, that I can write 3D data to PostGIS but texture information seems to get lost.
Is it generally possible ? If yes, what do I need to do ?
Thanks for any hint
Michael
Question
PostGIS 3D Texture writing
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+52- Celebrity
Hi @mhab,
Could you share us more details? Workspace template ( FMWT ), print Database PostGis, etc...
Thanks,
Danilo
+10- Contributor
I have a textured 3D building (read from CityGML). If I write it to a FileGDB as Multipatch and read it afterwards I see the 3D object and the texturing is there.
If I do the same with PostGIS writer and read it afterwards I get the 3D objects without the texture.
I dont have more info and the very general question if texture handling is supported in PostGIS or not.
Michael
- Safer
This is expected behavior. The PostGIS reader/writer in FME does not preserve textures. This is because, to the best of my knowledge, PostGIS does not directly support textures.
That said, PostGIS (and FME) support rasters in PostGIS, and depending on your use case, there may be workarounds.
References:
- PostGIS 2.3 documentation on its supported geometry types: http://postgis.net/docs/manual-2.3/using_postgis_dbmanagement.html#RefObject http://postgis.net/docs/manual-2.3/ST_GeomFromWKB.html (and others, these are the main ones)
- A nice slide-deck talking about PostGID 3D from 2011 (so useful for context, not really useful for confirming the latest state of things) https://www.slideshare.net/SimeonNedkov/postgis-3d-implementation
Regards,
Paul
+10- Contributor
This is expected behavior. The PostGIS reader/writer in FME does not preserve textures. This is because, to the best of my knowledge, PostGIS does not directly support textures.
That said, PostGIS (and FME) support rasters in PostGIS, and depending on your use case, there may be workarounds.
References:
- PostGIS 2.3 documentation on its supported geometry types: http://postgis.net/docs/manual-2.3/using_postgis_dbmanagement.html#RefObject http://postgis.net/docs/manual-2.3/ST_GeomFromWKB.html (and others, these are the main ones)
- A nice slide-deck talking about PostGID 3D from 2011 (so useful for context, not really useful for confirming the latest state of things) https://www.slideshare.net/SimeonNedkov/postgis-3d-implementation
Regards,
Paul
It confirms what I thought maybe the state of art for now.
Now I'm pretty sure