Kyle Barron
Kyle Barron
> unless we would just do away with this keyword altogether, given it's only one line extra that users have to write to get the pyarrow object I'm personally OK...
Thanks @jorisvandenbossche !
That link describes Carto's API documentation. We don't use any Carto APIs, we only use the Carto tile service. Why do you want to use a Google basemap? In the...
Also I think this is a duplicate of https://github.com/developmentseed/lonboard/issues/454 ?
Is it possible to use Google basemaps without using the Google maps sdk?
This is still a desired piece of functionality I believe
> With the GIL lock, that pretty much only applies at buffer protocol import time, yeah? In theory, I think you're supposed to hold the GIL for the entire lifetime...
I think I tried to generalize too soon and it became more work than I expected 😢 . Probably not worth trying to support non-float box types yet
Also I was thinking of trying to support both numpy and arrow input, but that seems a little hard. In general I'm trying to move towards arrow-first, but it seems...
It would probably be simplest to separate out the constructors for numpy and arrow. The consumer can deal with that. So we'd have ``` RTree.from_interleaved RTree.from_separated RTree.from_arrow ``` where the...