Re: [GRASS-user] Wrangling CityGML with GRASS ?
Hi Markus, I am not sure whether GMLAS is currently supported: ogr2ogr -f GeoJSON SMALL.json GMLAS:SMALL.gml -oo REMOVE_UNUSED_LAYERS=YES -oo REMOVE_UNUSED_FIELDS=YES -sql "SELECT * FROM groundsurface" throws "FAILURE: Unable to open datasource `GMLAS:SMALL.gml' with the following drivers. -> `OGR_GRASS' -> `PCIDSK' -> `PDF' [...] " -> with no mentioning of GMLAS as a driver option. Best, Peter You need to rebuild GDAL accordingly, but > override for the import-driver: > > ogr2ogr -f GeoJSON SMALL.json GMLAS:SMALL.gml -oo REMOVE_UNUSED_LAYERS=YES -oo REMOVE_UNUSED_FIELDS=YES -sql "SELECT * FROM groundsurface" apparently GMLAS is supported. What is the exact error message for " GDAL2.3.1 in GRASS refuses to accept the "GMLAS:""? Markus M ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Wrangling CityGML with GRASS ?
Hi Peter, On Thu, Aug 8, 2019 at 3:56 PM "Peter Löwe" wrote: > > Hi Markus, all, [...] > > For me, GDAL2.3.1 in GRASS refuses to accept the "GMLAS:" from https://gdal.org/drivers/vector/gmlas.html: The driver requires Xerces-C >= 3.1 You need to rebuild GDAL accordingly, but > override for the import-driver: > > ogr2ogr -f GeoJSON SMALL.json GMLAS:SMALL.gml -oo REMOVE_UNUSED_LAYERS=YES -oo REMOVE_UNUSED_FIELDS=YES -sql "SELECT * FROM groundsurface" apparently GMLAS is supported. What is the exact error message for " GDAL2.3.1 in GRASS refuses to accept the "GMLAS:""? Markus M > > --> if GDAL-4-GRASS is currently built without GMLAS-support, it would be wortwhile to include it soonish (-> benefits: https://inspire.ec.europa.eu/sites/default/files/presentations/gml_application_schema_made_easy_in_gdal_ogr_and_qgis_-_gmlas_driver_0.pdf) > > Otherwise, the standard GML-driver doesn't feature the REMOVE_xxx options: > ogr2ogr -f GeoJSON SMALL.json SMALL.gml -oo REMOVE_UNUSED_LAYERS=YES -oo REMOVE_UNUSED_FIELDS=YES -sql "SELECT * FROM groundsurface" > > Warning 6: driver GML does not support open option REMOVE_UNUSED_LAYERS > Warning 6: driver GML does not support open option REMOVE_UNUSED_FIELDS > ERROR 6: The GeoJSON driver does not overwrite existing files. > ERROR 1: GeoJSON driver failed to create SMALL.json > > Best, > peter > > > > > > > Gesendet: Donnerstag, 08. August 2019 um 15:15 Uhr > Von: "Markus Metz" > An: "Peter Löwe" > Cc: grass-user > Betreff: Re: [GRASS-user] Wrangling CityGML with GRASS ? > > > On Thu, Aug 8, 2019 at 2:59 PM "Peter Löwe" wrote: > > > > Hello Markus, Stefan, all, > > > > thanks for all your advice. New challenges have emerged, as the dataset is defined as a polyhedral surface: > > > > I upgraded to GRASS 7.6.1 which comes with GDAL 2.3.1. > > > > The data sources are official CityGML files provided by the German Federal Agency for Cartographyand Geodesy (Bundesamt für Kartographie), which have an ".xml"-extension. > > > > v.in.ogr -2 -o --o input=TEST.xml output=TEST01 > > throws several warnings and creates an empty vector without an points/lines in it: > > > > Warning 1: Unrecognized geometry type : 1015 [<=== note this!] > > No projection information available for layer > > Übersteuere die Überprüfung der Projektion. > > Check if OGR layer contains polygons... > > 100% > > WARNUNG: Vektorkarte existiert bereits und wird überschrieben. > > Creating attribute table for layer ... > > Importing 1 features (OGR layer )... > > WARNUNG: Skipping unsupported geometry type 'POLYHEDRALSURFACE' [<=== note this!] > > v.in.ogr could force-convert these polyhedral surfaces to multipolygons, at the risk of getting garbage. > > The required change to v.in.ogr would be small, but it would be safer to skip these unsupported feature types in order to avoid garbage output. > > Markus M > > ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Wrangling CityGML with GRASS ?
Hi Markus, all, one option to deal with this is in a structured way could be to use the GMLAS-driver of GDAL, prior to the import into GRASS via v.in.ogr, as Stelios Vitalis described it here: https://3d.bk.tudelft.nl/svitalis/citygml/gdal/2017/07/24/messing-around-with-citygml-on-gdal-2.2.html (last code example) For me, GDAL2.3.1 in GRASS refuses to accept the "GMLAS:" override for the import-driver: ogr2ogr -f GeoJSON SMALL.json GMLAS:SMALL.gml -oo REMOVE_UNUSED_LAYERS=YES -oo REMOVE_UNUSED_FIELDS=YES -sql "SELECT * FROM groundsurface" --> if GDAL-4-GRASS is currently built without GMLAS-support, it would be wortwhile to include it soonish (-> benefits: https://inspire.ec.europa.eu/sites/default/files/presentations/gml_application_schema_made_easy_in_gdal_ogr_and_qgis_-_gmlas_driver_0.pdf) Otherwise, the standard GML-driver doesn't feature the REMOVE_xxx options: ogr2ogr -f GeoJSON SMALL.json SMALL.gml -oo REMOVE_UNUSED_LAYERS=YES -oo REMOVE_UNUSED_FIELDS=YES -sql "SELECT * FROM groundsurface" Warning 6: driver GML does not support open option REMOVE_UNUSED_LAYERS Warning 6: driver GML does not support open option REMOVE_UNUSED_FIELDS ERROR 6: The GeoJSON driver does not overwrite existing files. ERROR 1: GeoJSON driver failed to create SMALL.json Best, peter Gesendet: Donnerstag, 08. August 2019 um 15:15 Uhr Von: "Markus Metz" An: "Peter Löwe" Cc: grass-user Betreff: Re: [GRASS-user] Wrangling CityGML with GRASS ? On Thu, Aug 8, 2019 at 2:59 PM "Peter Löwe" <peter.lo...@gmx.de> wrote: > > Hello Markus, Stefan, all, > > thanks for all your advice. New challenges have emerged, as the dataset is defined as a polyhedral surface: > > I upgraded to GRASS 7.6.1 which comes with GDAL 2.3.1. > > The data sources are official CityGML files provided by the German Federal Agency for Cartographyand Geodesy (Bundesamt für Kartographie), which have an ".xml"-extension. > > v.in.ogr -2 -o --o input=TEST.xml output=TEST01 > throws several warnings and creates an empty vector without an points/lines in it: > > Warning 1: Unrecognized geometry type : 1015 [<=== note this!] > No projection information available for layer > Übersteuere die Überprüfung der Projektion. > Check if OGR layer contains polygons... > 100% > WARNUNG: Vektorkarte existiert bereits und wird überschrieben. > Creating attribute table for layer ... > Importing 1 features (OGR layer )... > WARNUNG: Skipping unsupported geometry type 'POLYHEDRALSURFACE' [<=== note this!] v.in.ogr could force-convert these polyhedral surfaces to multipolygons, at the risk of getting garbage. The required change to v.in.ogr would be small, but it would be safer to skip these unsupported feature types in order to avoid garbage output. Markus M ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Wrangling CityGML with GRASS ?
line 39, in > > > > > 'locale')).ugettext > > > AttributeError: 'GNUTranslations' object has no attribute 'ugettext' > > > [MÁSCARA ráster presente] > > > GRASS 7.4.1 (EPSG5344):~/Documentos/grassdata > > > > > > > Can someone help with this issue? > > > > GNUTranslations has an attribute ugettext only in Python2, not in Python3. > > Make sure that the link "python" points to "python2", test with "python > > --version" > > > > Markus M > > -- next part -- > > An HTML attachment was scrubbed... > > URL: < http://lists.osgeo.org/pipermail/grass-user/attachments/20190805/c9190edf/attachment-0001.html > > > > > -- > > > > Message: 2 > > Date: Tue, 6 Aug 2019 09:19:31 +0300 > > From: Micha Silver > > To: Sebastián Dietrich > > Cc: Ken Mankoff , grass-user@lists.osgeo.org > > Subject: Re: [GRASS-user] wms google > > Message-ID: <73c1d605-3729-ab98-2f81-096d4a8d2...@gmail.com> > > Content-Type: text/plain; charset="utf-8" > > > > An HTML attachment was scrubbed... > > URL: < http://lists.osgeo.org/pipermail/grass-user/attachments/20190806/002e1069/attachment-0001.html > > > > > ------ > > > > Message: 3 > > Date: Tue, 6 Aug 2019 09:13:57 + > > From: Stefan Blumentrath > > To: "Peter Löwe" , "grass-user@lists.osgeo.org" > > > > Subject: Re: [GRASS-user] Wrangling CityGML with GRASS ? > > Message-ID: > > < he1pr0201mb21405732c039676e8a785d9c9e...@he1pr0201mb2140.eurprd02.prod.outlook.com > > > > > Content-Type: text/plain; charset="utf-8" > > > > 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 On Behalf Of "Peter Löwe" > > Sent: torsdag 1. august 2019 11:10 > > To: grass-user@lists.osgeo.org > > 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 > > > > > > > > ___ > > grass-user mailing list > > grass-user@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-user > > > > -- > > > > Message: 4 > > Date: Tue, 6 Aug 2019 12:23:29 +0200 > > From: "Peter Löwe" > > To: "Stefan Blumentrath" > > Cc: "grass-user@lists.osgeo.org" > > Subject: Re: [GRASS-user] Wrangling CityGML with GRASS ? > > Message-ID: > > > > > > Content-Type: text/plain; charset=UTF-8 > > > > 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 > > > > > > > > > > > Gesendet: Dienstag, 06. August 2019 um 11:13 Uhr > > > Von: "Stefan Blumentrath" > > > An: "Peter Löwe" , "grass-user@lists.osgeo.org" < grass-user@lists.osgeo.org> > > > 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 an
[GRASS-user] Wrangling CityGML with GRASS ?
rom: Micha Silver > To: Sebastián Dietrich > Cc: Ken Mankoff , grass-user@lists.osgeo.org > Subject: Re: [GRASS-user] wms google > Message-ID: <73c1d605-3729-ab98-2f81-096d4a8d2...@gmail.com> > Content-Type: text/plain; charset="utf-8" > > An HTML attachment was scrubbed... > URL: > <http://lists.osgeo.org/pipermail/grass-user/attachments/20190806/002e1069/attachment-0001.html> > > -- > > Message: 3 > Date: Tue, 6 Aug 2019 09:13:57 + > From: Stefan Blumentrath > To: "Peter Löwe" , "grass-user@lists.osgeo.org" > > Subject: Re: [GRASS-user] Wrangling CityGML with GRASS ? > Message-ID: > > > > Content-Type: text/plain; charset="utf-8" > > 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 On Behalf Of "Peter > Löwe" > Sent: torsdag 1. august 2019 11:10 > To: grass-user@lists.osgeo.org > 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 > > > > ___ > grass-user mailing list > grass-user@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-user > > -- > > Message: 4 > Date: Tue, 6 Aug 2019 12:23:29 +0200 > From: "Peter Löwe" > To: "Stefan Blumentrath" > Cc: "grass-user@lists.osgeo.org" > Subject: Re: [GRASS-user] Wrangling CityGML with GRASS ? > Message-ID: > > > > Content-Type: text/plain; charset=UTF-8 > > 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 > > > > > > Gesendet: Dienstag, 06. August 2019 um 11:13 Uhr > > Von: "Stefan Blumentrath" > > An: "Peter Löwe" , "grass-user@lists.osgeo.org" > > > > 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 On Behalf Of "Peter > > Löwe" > > Sent: torsdag 1. august 2019 11:10 > > To: grass-user@lists.osgeo.org > > 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 > > > > > > > > ___ > > grass-user mailing list > > grass-user@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-user > > > > > -- > > Message: 5 > Date: Tue, 6 Aug 2019 14:45:50 +0200 > From: Markus Metz > To: Peter Löwe > Cc: Stefan Blumentrath , > "grass-user@lists.osgeo.org" > Subject: Re: [GRASS-user] Wrangling CityGML with GRASS ? > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Hi Peter, > > On Tue, Aug 6, 2019 at 12:23 PM "Peter Löwe" wrote: &g
Re: [GRASS-user] Wrangling CityGML with GRASS ?
Hi Peter, On Tue, Aug 6, 2019 at 12:23 PM "Peter Löwe" wrote: > > 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). GML and GMLAS are supported by GDAL 2.2+. However, in order to import GMLAS properly, some tricks are needed (interleaved reading for non-sequential layers, see https://gdal.org/drivers/vector/gmlas.html#performance-issues-with-large-multi-layer-gml-files) which are built into GRASS 7.6+. > My colleagues have ingested CityGML datasets into R, which caused issues with the vector-topology for individual buildings. That's not related to the data format, but to the content: 3D polygons. These are not supported in GRASS, when importing you need to convert the data to 2D with v.in.ogr -2, otherwise you get corrupt topology. Maybe this is also needed for R. Markus M > 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 > > > > > > Gesendet: Dienstag, 06. August 2019 um 11:13 Uhr > > Von: "Stefan Blumentrath" > > An: "Peter Löwe" , "grass-user@lists.osgeo.org" < grass-user@lists.osgeo.org> > > 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 On Behalf Of "Peter Löwe" > > Sent: torsdag 1. august 2019 11:10 > > To: grass-user@lists.osgeo.org > > 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 > > > > > > > > ___ > > grass-user mailing list > > grass-user@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-user > > > ___ > grass-user mailing list > grass-user@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Wrangling CityGML with GRASS ?
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 > Gesendet: Dienstag, 06. August 2019 um 11:13 Uhr > Von: "Stefan Blumentrath" > An: "Peter Löwe" , "grass-user@lists.osgeo.org" > > 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 On Behalf Of "Peter > Löwe" > Sent: torsdag 1. august 2019 11:10 > To: grass-user@lists.osgeo.org > 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 > > > > ___ > grass-user mailing list > grass-user@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-user > ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
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 On Behalf Of "Peter Löwe" Sent: torsdag 1. august 2019 11:10 To: grass-user@lists.osgeo.org 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 ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
[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 ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
