Kyle Barron

That warning is shown whenever the input data contains a CRS that is not EPSG:4326. I added that warning because I believed it was useful to be explicit about reprojecting...

👋 I've vaguely followed rerun for a while and it's really cool to see you adding spatial support! The general structure of your data does indeed match the structure of...

> > Separately, technically GeoArrow currently requires float64 coordinates, and you use float32. > > This is not accurate. Ah, apologies; I must've been looking at the wrong place in...

https://github.com/vincentsarago/color-operations from @vincentsarago is an updated fork

All layers already have bounding box and weighted centroid attributes that are inferred from the input data. https://github.com/developmentseed/lonboard/blob/5560ead37e4bf02b8a39ef08b631c5b2f7108754/lonboard/_layer.py#L75-L76 Currently it's on the `Map` class to compute a default view state...

I don't consider `NaN` a hack. As long as we only permit floating-point values, using `NaN` to represent missing isn't much different than an external bitmask. And other libraries also...

The `EPSG:4326` definition defines axis order as latitude, longitude. So the "correct" way of transforming that uses the prescribed axis order, which is your first example. But in practice, many...

I agree that there's scope for multiple TIFF readers. tifffile has been around longer, is in much wider use, and seems to be very stable, so it's probably the better...

Hmm perhaps this is an issue with the synchronous executor around the async writer. But I would've expected the string path to use the synchronous writer regardless

In case you ever come across this again and are able to reproduce it, please add it here! I'm not able to reproduce this myself.