Antoine Beyeler
Antoine Beyeler
> Separately, technically GeoArrow currently requires float64 coordinates, and you use float32. This is not accurate. Although we do use `float32` extensively throughout the rerun data model, the geospatial primitive...
Yeah, let's punt on it. I think it was a proposal to address my need to generate the URL column in the viewer, but I did that with basic DF...
I'm not 100% but walkers currently doesn't seem to have disk-based tile caching, so everything gets reloaded every launch of the app. It would be great to have that. **BIG...
I'll probably have to do something like that, though I might save the `(name, n)`, to refer to the `n`th device named `name`. edit: this workaround precludes using the system-defined...
Isn't that closed by https://github.com/rerun-io/rerun/pull/9535?
We extensively discussed the data model and the next steps with @grtlr this morning. Here is our proposal. **edit**: proposal heavily discussed, amended, and ✨ decided ✨ with @jleibs ####...
> @abey79 @jleibs Just a heads up: The only real deviation from our design that I had to do was storing the edges in a table rather than a struct....
Makes sense to me 👍🏻
> cc: [@abey79](https://github.com/abey79) having a "remove recording" endpoint on OSS server should be pretty easy if we don't have it already, right? 🤔 This points at one of the hurdles...
> Is there any documentation on the server I could read? Seems like something i would like to use! The documentation on this stuff if sadly very lacunary. The open...