paleolimbot commented on issue #148: URL: https://github.com/apache/parquet-site/issues/148#issuecomment-3729272296
We clearly didn't get to that 😬 . I'm still willing to draft this (but I am also not offended if it's been way too long and somebody else would like to do so first!). Here is some content I happen to know about. This is all from the "hey geo people! Use Parquet!" angle (there is also an angle from a helping primarily non-spatial workflows/users/engines improve fidelity). I also agree it was amazing and should be highlighted how quickly we were able to implement and release support in so many implementations! - https://cloudnativegeo.org/blog/2025/02/geoparquet-2.0-going-native/ - https://wherobots.com/blog/apache-iceberg-and-parquet-now-support-geo/ - https://dewey.dunnington.ca/slides/coc2025/#/title-slide (slides from my Community over Code talk last year about this) - https://dewey.dunnington.ca/post/2025/lazy-geoparquet-reading-in-sedonadb-duckdb-geopandas-and-gdal/ (technical details of how pruning works with a section on why this can be better in -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
