H. Thomson Comer

Hey Ken, do you have an update on your progress here? I've had some ideas I'd like to chat about.

So, right now there's a workaround for getting the polygons into cuspatial format: `geodataframe.write_file('tempfile.shp'); cuspatial_polygons = cuspatial.read_polygon_shapefile('tempfile.shp')`. You'll need to do a similar workaround for the points, but I'm not...

I may move this post into a different or multiple separate issues. This documents my ideas involving accelerated I/O, leveraging geoPandas for loading many existing file formats and moving their...

Hey @achapkowski spatial references are very high in the next priority list. I'm inclined to include a coordinate reference system object with every GeoSeries, or two.

Hey @jorisvandenbossche I've been meaning to chime in and let you know I'm working on a similar problem, and geoPandas is going to be my foundation on the Python side....

Thanks for the quick response! Judging from your answer and opinions internally, I'm going to leave it open and undefined in my mind despite what the "accepted answer" in [the...

Hey @kylebarron ! Thanks for the super quick response. So, we did decide to go with a nested array, and the nested array is implemented in http://www.github.com/rapidsai/cuspatial/pull/585 . My original...

I'm willing to include it in the core spec because it allows us to represent and transmit a singular object as a GeoArrow datasource. However, I understand the concern about...

We'd definitely like to leave WKB behind since it has fundamental I/O limitations. `DenseUnion` is working really well in cuspatial now, with a `GeoSeries` ala GeoPandas allowing arbitrary geometry collections....

Originally we wanted each point coordinate column to have an optional `z` that could be specified. We could just as easily allow any number of "extra dimensions" to be specified...