Add GeoArrow test files for comprehensive parsing tests #36
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.
Summary
test/links.txtwith 127 small parquet files (<2MB) from geoarrow.org/data.htmlruntests.jlto download geoarrow test files todata/geoarrow/GeoParquet.read()can parse all files, check:geometrycolumn exists, and runGI.testgeometryon first geometryGeoParquet.readto warn instead of error when GeoParquet metadata is missing, returning the DataFrame without geometry parsingusing WellKnownGeometryin tests to enable proper WKB geometry handlingTest files included
Files cover various geometry types and encodings:
Each dataset has
_geo(GeoArrow encoding) and_native(native Arrow encoding) variants where applicable.Changes to GeoParquet.read behavior
Files without valid GeoParquet metadata now emit a warning and return the DataFrame as-is, rather than throwing an error. This allows reading plain parquet files that happen to have geometry columns but no geo metadata.
Test plan
🤖 Generated with Claude Code