Kyle Barron

you should be able to use the glob crate: https://docs.rs/glob/latest/glob/struct.Pattern.html

Successful prototype was merged in https://github.com/geoarrow/geoarrow-rs/pull/1093

This is taken directly from `geo`: See [`chamberlain_duquette_signed_area`](https://docs.rs/geo/latest/geo/algorithm/chamberlain_duquette_area/trait.ChamberlainDuquetteArea.html#tymethod.chamberlain_duquette_signed_area) and [`geodesic_area_signed`](https://docs.rs/geo/latest/geo/algorithm/geodesic_area/trait.GeodesicArea.html#tymethod.geodesic_area_signed). I'm inclined to keep the API as similar to `geo` as possible. What do you think.

Maybe it would be best to mimic the `geoarrow` crate layout?

Are we using aiopmtiles in prod anywhere?

GeoPolars is not currently functional, regardless. We need Polars to enable additional APIs to make GeoPolars possible. See https://github.com/pola-rs/polars/issues/1830#issuecomment-2218102856

Can you test on latest main? (Or on 0.3.0-beta.2, which I released yesterday) Also, is there a reason why rust nightly would have different behavior here? I haven't seen this...

> consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`geoarrow`) I mean that's a very reasonable thing to do. we mostly need this...

Ah, it does look similar to that compiler bug. I'll hold off on adding `#![recursion_limit = "256"]`, but hopefully never has that much geometry - geometry collection - geometry recursions...

> Inspired by the broader, but GDAL dependent, work above GDAL is not a necessary dependency of the above stac-geoparquet implementation. GeoPandas is included as a dependency because it's the...