Pieter Roggemans

I suppose this is the same case as also posted in https://github.com/shapely/shapely/issues/2029? In that case the same remark from my side applies: > I cannot reproduce the problem using geos...

Shapefile cannot make the distinction between NULL/None values versus POINT EMPTY, and the choice was made to return NULL/None when reading. E.g. Geopackage does support the distinction between both, so...

I think this can be closed as there is nothing actionable, or ?

There have been some fixes regarding this type of things in GDAL in the past, e.g. https://github.com/OSGeo/gdal/pull/11420, first released in GDAL 3.10.1, sounds like a good match... However, even with...

XLSX gave UTF-8 decoding errors when reading a file written after the change. GDAL does say that XLSX needs UTF-8 (via the OLCStringsAsUTF8 capability), but this only worked for existing...

> Thanks for working on this! Still a bit unsure of the correct behavior for shapefiles when `encoding` is not provided by the user, but otherwise this looks reasonable. I'm...

> However, I would then maybe do that for all platforms, including Windows? I agree. If we would go for "UTF-8", I would also vote to do it for all...

UTF-8 is now the default for Shapefile on all platforms...

Reference to the identical question on stackoverflow (with a similar but slightly different attempt to answer): https://gis.stackexchange.com/questions/483678/buffer-without-overlaps-in-python @poroc300

I had a deeper and broader look... and it's a bit complicated, as typically with datetimes and timezones :-). Based on this, it looks like there some issues when reading...