[gdal-dev] ogrmerge running very slow on merging GML to GPGK
Even Rouault
even.rouault at spatialys.com
Sat Oct 19 15:06:17 PDT 2024
Vedran,
the issue is that your GML files reference a
http://cap115:8101/geoserver/oss/wfs?service=WFS&version=1.0.0&request=DescribeFeatureType&typeName=oss%3AKATASTARSKE_OPCINE
XML schema, and if the cap115:8101 server is not reachable, GDAL spends
some time waiting for it before giving up.
If all your .gml files share the same schema, you can actually use the
generated .gfs file (which is a OGR GML specific schema format) for all
of them, which will skip the step trying to download the XML schema
Just add " --config GML_GFS_TEMPLATE katastarske_opcine.gfs" (without
the double quotes) to your ogrmerge command line (cf
https://gdal.org/en/latest/drivers/vector/gml.html#configuration-options),
and this should run in one second total.
Even
Le 19/10/2024 à 22:58, Vedran Stojnović via gdal-dev a écrit :
> Hi all,
>
> not sure if this is a bug report so I want to check here if someone
> has experience with this.
> I need to merge 98 GML files, each having one MultiLineString feature
> into one layer so I'm using:
> ogrmerge -single -f GPKG -o merged.gpkg *.gml
>
> But it takes very long time (few seconds per file), and in the
> meantime gfs files are created every few seconds. I'm running ogrmerge
> from OSGeo4W Shell on Windows 11 PC, GDAL 3.9.2, released 2024/08/13.
>
> My dataset is available here (1 MB ZIP with all 98 files):
> https://we.tl/t-V8Azs8WokU
>
> --
> Kind regards,
> Vedran Stojnović.
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
--
http://www.spatialys.com
My software is free, but my time generally not.
Butcher of all kinds of standards, open or closed formats. At the end, this is just about bytes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20241020/41d21f78/attachment.htm>
More information about the gdal-dev
mailing list