Max Gabrielsson

I'm not very familiar with the geodatbase format but I can try to test it out myself later, there may be an option or something we can pass to make...

Interestingly after coming across [this thread](https://twitter.com/postholer/status/1691494402353721344) it seems like there might be options we could pass to make it faster. Just commenting here to look into later.

You should be able to already, are you sure the WKB actually contains a 2D polygon? If it is a multipolygon or contains z/m values it won't work however.

Yes! "WKT" and "Text" is the same thing. Use ST_GeomFromText(VARCHAR). You can pass an 'ignore_invalid := bool flag too to get nulls instead of error should the geom be invalid.

That is interesting, `ST_Within` for geometry is just a wrapper around the geos implementation. Are these just linestrings or multilinestrings/geometrycollections?

Could you try to check if they are valid with `ST_IsValid()`?

I suspect something is going wrong in geos but we are currently too lenient in responding to errors raised by geos. We need to do some changes so we more...

Now that #61 landed were more aggressive in responding to GEOS errors and perform predicates faster, so if you still have this data on standby I'd really appreciate giving it...

Uh oh, that sounds like a memory leak. I'll investigate too.

Thanks for finding these bugs and reporting this issue! Just curious, do you find these through normal duckdb usage or are these the result of some sort of automatic testing/fuzzing?