Kyle Barron

> I'm thinking that the answer to my question is "`geojson` is the a higher-level library, and is probably what you want to use for simply iterating through features in...

> I never got that to work with `geozero`. You'd need to impl your own [GeozeroDatasource](https://docs.rs/geozero/latest/geozero/trait.GeozeroDatasource.html). It's a bit of work, which is why it's not done often; instead converting...

> Ran into this error when trying to open a NetCDF over https on `develop` `270a484`. > ``` > OSError: Generic HTTP error: Request error: Error performing GET https://data-dataref.ifremer.fr/ww3/GLOBMULTI_ERA5_GLOBCUR_01/GLOB-30M/2024/FIELD_NC/LOPS_WW3-GLOB-30M_202401.nc in...

Maybe we should first use this issue to resolve: where should we discuss this? And then we can start a discussion in that new place to resolve the implementation details?

To add my two cents: I'd argue that the `geoarrow` Github org is the right place with the right mixture of people across geo, Arrow, H3, and S2. Regardless of...

I agree rather strongly with @martinfleis. It's already difficult to explain the difference between serialized and native encodings in GeoArrow. "duckdb-spatial gives you GeoArrow, why can't I pass that straight...

I think it would be clearest for end users to have them as a separately-named spec from GeoArrow. Unless we're worried about another community making a competing spec, I think...

> I would assume that an `h3` prefixed type was maintained by Uber and that's definitely not the case. Is there any restriction to have only one `.` in an...

What are you trying to achieve here? Can you expand on what you mean by "compose maps"? Do you just mean a side-by-side view?

> side-by-side is the second use-case I think side-by-side might become in scope for handling on the JS side natively > the most important one is combining two maps such...