ChHarding
commented
9 months ago Thomas,
Sadly I know next to nothing about City GML (or DSMs in general). I’m guessing you have building mesh models and want to combine them with a DEM? I assume the issue is to have both the DEM and the building model need to have the same coordinate system and the mm-based STLs you get from TouchTerrain won’t work unless you manually scale and position your building model?
Touchterrain has a way to create STLs where the coordinate are UTM coordinates (search for use_geo_coords) here: https://github.com/ChHarding/TouchTerrain_for_CAGEO#general-processing-parameters
I’ve also written a blogpost here: http://blog.touchterrain.org/2020/03/exporting-terrain-models-with-real.html
This was in the context of using Blender GIS as an alternative path draping method: https://drive.google.com/drive/folders/12b2Ne8O3aHSHB9Oo9_BB6AtgLm2pIzC9
TBH I’ve not had any feedback on any of this and have not used it beyond my examples. But maybe something in there can be used as a start for you.
Or if that’s not what you need, let’s talk …
Cheers
Chris
On Dec 19, 2023, at 12:38, Thomas Pentenrieder @.**@.>> wrote:
hey, really love your tool! Lately I was investigating on how to best combine terrain models (geotiff) with CityGML or CityJSON files. Since I'm new to Python I wanted to hear your thoughts on how to best approach this and perhaps contribute back to this codebase.
I tried combining seperately generated STLs (using cjio for the CityJSON modelhttps://cjio.readthedocs.io/en/latest/includeme.html#) afterwards with somewhat okayish results but that was a lot of work and error-prone.
I'm wondering if integrating the model generation into the TouchTerrain workflow would be the best approach (similar to how the GPX addition works), but I'm worried it might not be a simple as that as the addition of CityGML would potentially introduce holes to the model (thinking of bridges, for example).
The other approach would be to combine the STLs programatically later, however that would probably be also difficult to properly align all parts when the Geo-Data isn't there anymore.
Is there maybe something obivious I'm missing? Seems like there's a reason why not many tools (only found 1 tbh) can do this kind of merge already.
— Reply to this email directly, view it on GitHubhttps://github.com/ChHarding/TouchTerrain_for_CAGEO/issues/83, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEYDF5P6PYSVAK3FRCS55VTYKHNKDAVCNFSM6AAAAABA3T76ZCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2DSMRTGY4TGMI. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Chris Harding Associate Professor Department of Geological & Atmospheric Sciences Touchterrain.geol.iastate.eduhttp://Touchterrain.geol.iastate.edu
ThomasPe
hey, really love your tool! Lately I was investigating on how to best combine terrain models (geotiff) with CityGML or CityJSON files. Since I'm new to Python I wanted to hear your thoughts on how to best approach this and perhaps contribute back to this codebase.
I tried combining seperately generated STLs (using cjio for the CityJSON model) afterwards with somewhat okayish results but that was a lot of work and error-prone.
I'm wondering if integrating the model generation into the TouchTerrain workflow would be the best approach (similar to how the GPX addition works), but I'm worried it might not be a simple as that as the addition of CityGML would potentially introduce holes to the model (thinking of bridges, for example).
The other approach would be to combine the STLs programatically later, however that would probably be also difficult to properly align all parts when the Geo-Data isn't there anymore.
Is there maybe something obivious I'm missing? Seems like there's a reason why not many tools (only found 1 tbh) can do this kind of merge already.