duckdb / duckdb/duckdb-spatial
DuckDB Spatial extension in 1.5.1 not able to read GPX files anymore: "Too much data inside one element. File probably corrupted"
- Dominant language
- C
- Stars
- 708
- Forks
- 96
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 5
Description
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](https://github.com/user-attachments/files/26562118/New.file.1.gpx.zip)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.