Fix ParquetProvider geometry handling and add configurable geometry column support #2150
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.
Overview
This PR enhances the ParquetProvider with critical geometry handling fixes and adds support for configurable geometry columns, including WKT format support.
Key improvements:
nullin individual item requests (/collections/.../items/[id])geometry_columnparameter in provider configurationcrs_transformBug fixes:
'list' object attribute 'index' is read-onlyerror inget()methodquery()andget()methodsRelated Issue / discussion
This PR addresses multiple issues reported by users:
nullgeometry despite having valid geometry dataThese improvements make the ParquetProvider more robust and compatible with real-world geospatial parquet files that contain geometry in various formats.
Additional information
Testing performed:
Configuration examples:
Breaking changes: None - all changes are backward compatible.
Dependency policy (RFC2)
Updates to public demo
Note: No breaking changes were introduced, so no demo updates are required.
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)