Repository navigation
GH-55598: [C++][Parquet] Align Parquet-to-GeoArrow conversions with Parquet, GeoParquet, and arrow-rs - #55599
Conversation
|
Thanks for opening a pull request! This pull request has been automatically converted to a draft because its title doesn't match Arrow's required format. If this is not a minor PR, could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename the pull request title in the following format? or After updating the title, you can mark the pull request as ready for review. See also: |
|
|
|
cc @wgtmac and @jorisvandenbossche |
|
@github-actions crossbow submit -g cpp |
|
Revision: 8948f00 Submitted crossbow builds: ursacomputing/crossbow @ actions-919d56f824 |
|
@github-actions crossbow submit -g cpp |
|
Revision: 2ed428f Submitted crossbow builds: ursacomputing/crossbow @ actions-e2747b8627 |
Rationale for this change
GeoArrow input to the Parquet reader with a "missing" CRS (
nullin GeoParquet,Nonein GeoPandas) are currently written with a Parquet CRS that denotes lon/lat and will roundtrip incorrectly when read back to GeoPandas/GeoArrow.What changes are included in this PR?
Adds a mapping between
srid:0and GeoArrow's "missing" CRS to match arrow-rs, GeoParquet, and the discussion aroundsrid:0in the Parquet format PR adding it as an example.Are these changes tested?
Yes, the parameterized geospatial logical type mapping tests in both directions were ported from arrow-rs and include srid:0.
Are there any user-facing changes?
Yes: under a very specific set of circumstances (GeoArrow extension types registered, Parquet
Was AI used for this PR?
In accordance to the AI generation guidelines, please disclose below whether and how AI was used in this PR.
PR code and description written by:
Reviewed before submission by:
Closes #55598.