`ST_Distance` returning incorrect result with DuckDB 1.3.1

[cpcloud]

Setup code

# the URL is public
curl -OLsS 'https://storage.googleapis.com/ibis-pins/zones/20240322T150549Z-b1ed0/zones.geojson'

install spatial;
load spatial;
set variable penn_station = ST_Point(986345.399, 211974.446);

DuckDB 1.2.2

D select ST_Distance(geom, getvariable('penn_station')) as dist from st_read('./zones.geojson') where lower(zone) = 'flushing';
┌───────────────────┐
│       dist        │
│      double       │
├───────────────────┤
│ 42715.16463868837 │
└───────────────────┘

DuckDB 1.3.0

D select ST_Distance(geom, getvariable('penn_station')) as dist from st_read('./zones.geojson') where lower(zone) = 'flushing';
┌───────────────────┐
│       dist        │
│      double       │
├───────────────────┤
│ 42715.16463868837 │
└───────────────────┘

DuckDB 1.3.1

D select ST_Distance(geom, getvariable('penn_station')) as dist from st_read('./zones.geojson') where lower(zone) = 'flushing';
┌────────┐
│  dist  │
│ double │
├────────┤
│  0.0   │
└────────┘

[Maxxen]

Hello! Thanks a lot for reporting this issue! This turned out to be caused by a pretty precise edge-case I hadn't considered, but I'm very happy to have fixed. I've pushed a fix + test in #617, it should be available to get by FORCE INSTALL spatial FROM core_nightly an hour or so after it gets merged.