CRS /schema error on read for geospatial data #375

Activity

1. knaaptime

   added

   needs triage

   on Mar 11, 2026
2. knaaptime

   changed the title [-]CRS /schema error on read[/-] [+]CRS /schema error on read for geospatial data[/+] on Mar 11, 2026
3. evertlammerts commented on Mar 19, 2026

   

   evertlammerts

   on Mar 19, 2026

   Member

   More actions

   Thanks for reporting. This is a known regression caused by the new CRS support added to GEOMETRY types in DuckDB 1.5 (duckdb/duckdb#20143). The Python client's type conversion doesn't have a handler for GEOMETRY types, so they fall through to an "Unsupported type" error.

   This is a duplicate of duckdb/duckdb-spatial#766. BTW: the verbose type string you're seeing (the full PROJJSON blob) is also discussed in duckdb/duckdb-spatial#765.

   A workaround while we work on adding support for these types in Python is to convert the geometry column to text or WKB before fetching:

   import duckdb
   
   # Use ST_AsWKT to get Well-Known Text
   df = duckdb.sql("""
       SELECT *, ST_AsWKT(geometry) as geometry_wkt
       FROM read_parquet('s3://spatial-ucr/census/administrative/counties.parquet')
   """).df()
   
   # Or cast to VARCHAR
   df = duckdb.sql("""
       SELECT geometry::VARCHAR as geometry
       FROM read_parquet('s3://spatial-ucr/census/administrative/counties.parquet')
   """).df()
4. evertlammerts

   added

   reproduced

   and removed

   needs triage

   on Mar 19, 2026
5. knaaptime commented on Mar 19, 2026

   

   knaaptime

   on Mar 19, 2026

   Last edited by knaaptime

   Author

   More actions

   cool, thanks for the update! (I forgot about the spatial repo, otherwise would've opened over there). Should I go ahead and close in favor of duckdb/duckdb-spatial#766?

   also, thanks for the workaround!
6. evertlammerts commented on Mar 20, 2026

   

   evertlammerts

   on Mar 20, 2026

   Member

   More actions

   cool, thanks for the update! (I forgot about the spatial repo, otherwise would've opened over there). Should I go ahead and close in favor of duckdb/duckdb-spatial#766?

   Yes, let's track this in duckdb/duckdb-spatial#766.

   I've also added basic support for the GEOMETRY type back into the v1.5-variegata branch, so that you can do at least things like:

   import duckdb
   from shapely import from_wkb
   conn = duckdb.connect()
   
   # Using a dataframe
   df = conn.sql("select 'POINT(0 1)'::GEOMETRY as geom;").df()
   wkb_data = bytes(df['geom'].iloc[0])
   shape = from_wkb(wkb_data)
   print(shape.wkt)
   
   # Or just plain python types
   res = conn.execute("SELECT 'POINT(0 2)'::GEOMETRY as geom;").fetchall()
   shape2 = from_wkb(res[0][0])
   print(shape2.wkt)

       POINT (0 1)
       POINT (0 2)
   

   This will be available in 1.5.1, which is scheduled for next week.
7. evertlammerts

   closed this as completedon Mar 20, 2026