duckdb_spatial icon indicating copy to clipboard operation
duckdb_spatial copied to clipboard

`Geoparquet column 'geometry' does not have geometry types` error after updating duckdb to 1.3

Open vojtatom opened this issue 4 months ago • 3 comments

Similarly to https://github.com/duckdb/duckdb-spatial/issues/423, after updating duckdb to 1.3.2, we are again getting

Invalid Input Error: Geoparquet column 'geometry' does not have geometry types

for files that used to cause the same error in the past without the flag enable_geoparquet_conversion. ~~Enabling~~ Disabling the flag resolved the issue until recently, when we updated to 1.3, it is as if the ~~SET enable_geoparquet_conversion = true~~ SET enable_geoparquet_conversion = falsewas ignored. Is there something we can do about it to avoid the error?

vojtatom avatar Sep 02 '25 15:09 vojtatom

Hello!

enable_geoparquet_conversion is always set to true by default, so I don't think it has anything to do with anything (and I don't understand how it solved your problem before). This error occurs when trying to read a GeoParquet file that is missing some required fields in the metadata (e.g. geometry_types). What program was used to write this file? Can you share the file? If not, can you run select * from parquet_kv_metadata('<your_geoparquet_file>.parquet'); and share the output?

Maxxen avatar Sep 02 '25 15:09 Maxxen

@Maxxen Apologies, of course we were setting it to false, not true - an oversight on my part when I was writing the issue - to avoid the conversion, but after updating to 1.3, it is as if the flag was ignored. I'll try to get you a snippet of the geoparquet, it was created with an older version of geopandas, using an outdated schema version.

vojtatom avatar Sep 03 '25 08:09 vojtatom

@Maxxen apologies for the delay, here is the full metadata dump from the file:

full.txt

vojtatom avatar Sep 15 '25 14:09 vojtatom