ENH: support reading GeoParquet with native geoarrow-based encodings #3278
Conversation
| return coords | ||
| else: | ||
| # fixed size list | ||
| return np.asarray(arr.values).reshape(len(arr), -1) |
There was a problem hiding this comment.
Is it easy to generate an input file to read so our tests cover the interleaved coordinates case? (we also miss coverage above for the 2D/3D case, but the logical is identical so I don't think that matters.
There was a problem hiding this comment.
So officially GeoParquet doesn't support interleaved coordinates, only separated. That's why it is not included here in the tests. In a follow-up PR, I however want to add support for converting from (Geo)Arrow (in-memory) to geopandas (#3219 is already doing the export from geopandas to geoarrow), and those code paths will be covered.
Not ideal that for now it's not covered (and I could also have just included the separated code path here), but will do that follow-up shortly.
Broken off from #3275 with just the read support.
Implementing the reading part of #3253