DuckDB Spatial extension in 1.5.1 not able to read GPX files anymore: "Too much data inside one element. File probably corrupted"

[michael-simons]

See title, reproducer is easy:

-- Loading resources from /Users/msimons/.duckdbrc
Catalog Error:
unrecognized configuration parameter "geometry_always_xy"

Did you mean: "threads"
DuckDB v1.4.4 (Andium) 6ddac802ff
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
●◗ load spatial;
●◗ SELECT count(*) FROM st_read('New file 1.gpx', layer = 'track_points');
┌──────────────┐
│ count_star() │
│    int64     │
├──────────────┤
│      76      │
└──────────────┘
●◗ 

And on 1.5.0 and 1.5.1

-- Loading resources from /Users/msimons/.duckdbrc
DuckDB v1.5.1 (Variegata)
Enter ".help" for usage hints.
●◗ SELECT count(*) FROM st_read('New file 1.gpx', layer = 'track_points');
IO Error:
Too much data inside one element. File probably corrupted

My resources:

 more ~/.duckdbrc 
.prompt "●◗ "
INSTALL spatial;
LOAD spatial;
SET geometry_always_xy = true;

demo file attached as zip: New file 1.gpx.zip

[michael-simons]

Interesting, seems to come from GDAL https://trac.osgeo.org/gdal/ticket/2818

[defuneste]

To confirm https://mastodon.social/@EvenRouault/116368579657657994

 docker run --rm -v $(pwd):/data ghcr.io/osgeo/gdal:ubuntu-small-latest gdal vector info data/bob.gpx

(bob.gpx is just how in unzipped it)

Give me your 76 track_points

I also tested with QGIS with an older GDAL no issue.

[michael-simons]

Does not occur in DuckDB 1.5.2 anymore.