Hi Stefan,

thanks for the link: That's also the latest information we found so far, except 
for several OSGeo conference recordings (e.g. https://doi.org/10.5446/40913 
https://doi.org/10.5446/40694).
My colleagues have ingested CityGML datasets into R, which caused issues with 
the vector-topology for individual buildings. Also, we have to cope with 
significant amounts of CityGML datasets, which would require very large amounts 
of RAM, if the processing is done in R. Since GRASS locations are 
storage-effective AND GRASS handles vector topologies well, I had hoped that 
someone already explored this approach further :-)

If this should be not the case (yet) we'll gladly report at one of next years 
FOSS4G events.

Best,
peter   

<[email protected]>


> Gesendet: Dienstag, 06. August 2019 um 11:13 Uhr
> Von: "Stefan Blumentrath" <[email protected]>
> An: "Peter Löwe" <[email protected]>, "[email protected]" 
> <[email protected]>
> Betreff: RE: [GRASS-user] Wrangling CityGML with GRASS ?
>
> Hi Peter,
> 
> Not personally...
> I would guess you would import CityGML through GDAL:
> https://3d.bk.tudelft.nl/svitalis/citygml/gdal/2017/07/24/messing-around-with-citygml-on-gdal-2.2.html
> There you can create subsets and the like...
> 
> What are you planning to do with it, roughly?
> 
> Cheers
> Stefan
> 
> 
> -----Original Message-----
> From: grass-user <[email protected]> On Behalf Of "Peter 
> Löwe"
> Sent: torsdag 1. august 2019 11:10
> To: [email protected]
> Subject: [GRASS-user] Wrangling CityGML with GRASS ?
> 
> Hi list,
> 
> I'm looking for information/howtos/etc. about how to deal with large CityGML 
> data sets using GRASS.
> 
> Has anybody already explored this ?
> 
> Best,
> Peter
> 
> <[email protected]>
> 
> _______________________________________________
> grass-user mailing list
> [email protected]
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
_______________________________________________
grass-user mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-user

Reply via email to