[gdal-dev] ogr2ogr explanations for error XML parsing of GML file failed?
Jeroen Hovens
jeroen at groenebij.nl
Mon Jan 12 08:06:11 PST 2026
Hi,
I use QGIS on Windows10 which comes with GDAL. The latest QGIS LTR (3.40.14)
uses GDAL 3.12.1
In QGIS I can open a terminal (browser panel, rightclick a folder and select
Open in Terminal) and immediately use ogr2ogr to convert a WFS to a
geopackage, because QGIS has altered the path to include the GDAL directory
However, with some WFS services ogr2ogr throws an error. I have no trouble
using those WFS services in QGIS.
For instance, this one I can't convert:
ogr2ogr -f gpkg test.gpkg
WFS:"https://service.pdok.nl/kadaster/bestuurlijkegebieden/wfs/v1_0?"
Provinciegebied -overwrite -nln provincie_kadaster
But this one I can:
ogr2ogr -f gpkg test2.gpkg WFS:"https://map.data.amsterdam.nl/maps/gebieden"
wijk -overwrite -nln amsterdam_wijk
The first WFS is part of a large Dutch open data organization and depending
on which WFS I choose from them I see two different errors:
ERROR 1: XML parsing of GML file failed : no element found at line 27,
column 31065 (or different numbers)
Or
ERROR 1: XML parsing of GML file failed : unclosed token at line 555, column
9
I was able to compare a debug on with someone who was able to convert the
WFS to a gpkg and this part was surely different
VSICURL: Read attempt beyond end of file
VSICURL: Read attempt beyond end of file
After this, the error appeared.
To make things more complicated:
When I open a Windows Prompt (terminal) and set a path to the GDAL directory
in QGIS using set PATH=%PATH%;C:\Program Files\QGIS 3.40.14\bin
I can also use ogr2ogr.
Interestingly, now I can convert both WFS datasets to gpkg.
What could be different with the QGIS Terminal setting from a Windows Prompt
setting with the path set that would explain the errors?
What might be different in both WFS services that triggers these errors?
Kind regards,
Jeroen Hovens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20260112/99572021/attachment.htm>
More information about the gdal-dev
mailing list