[SEDONA-226] Support reading and writing GeoParquet file metadata #740
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Honor the geo metadata when loading GeoParquet files, instead of letting the user explicitly specify the name of the geometry column.
Kontinuation
force-pushed
the
geoparquet-metadata
branch
from
4acf56a
to
eaed2c8
Compare
jiayuasu
approved these changes
Dec 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Did you read the Contributor Guide?
Is this PR related to a JIRA ticket?
[SEDONA-XXX] my subject.What changes were proposed in this PR?
This patch makes
GeoParquetFileFormataware of thegeometadata in GeoParquet files. We removed thefieldGeometryoption for loading GeoParquet files, and file metadata would be written when saving dataframes as GeoParquet files.This patch also resolves several bugs related to GeoParquet support:
How was this patch tested?
Unit tests were added to test this patch. We've also tested this patch manually on Spark standalone clusters running various versions of Spark.
Interoperability with the latest GeoPandas (0.11.1) was tested manually.
Did this PR include necessary documentation updates?