(sedona) branch master updated: [DOCS] Add example to use zstd compression when storing GeoParquet (#3117)

[ji...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jiayuasu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sedona.git


The following commit(s) were added to refs/heads/master by this push:
     new 0ba9baa6ae [DOCS] Add example to use zstd compression when storing GeoParquet (#3117)
0ba9baa6ae is described below

commit 0ba9baa6aea537f3b76a8572d6f99da7e27ea96c
Author: Jakob Miksch <in...@jakobmiksch.eu>
AuthorDate: Fri Jul 17 16:45:57 2026 +0200

    [DOCS] Add example to use zstd compression when storing GeoParquet (#3117)
    
    Co-authored-by: Jia Yu <ji...@apache.org>
---
 docs/tutorial/files/geoparquet-sedona-spark.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/tutorial/files/geoparquet-sedona-spark.md b/docs/tutorial/files/geoparquet-sedona-spark.md
index 8ba5e36c39..5310cccfad 100644
--- a/docs/tutorial/files/geoparquet-sedona-spark.md
+++ b/docs/tutorial/files/geoparquet-sedona-spark.md
@@ -269,6 +269,16 @@ ORDER BY geohash
 
 Let's look closer at how Sedona uses the GeoParquet bbox metadata to optimize queries.
 
+## Compression of GeoParquet file
+
+There are different options to compress Parquet and GeoParquet files. Using `zstd` is a good choice if you want to distribute your GeoParquet file, see [Best Practices for Distributing GeoParquet](https://github.com/opengeospatial/geoparquet/blob/main/format-specs/distributing-geoparquet.md) and [discussion thread](https://github.com/apache/sedona/discussions/3109#discussioncomment-17666620) for details. Example:
+
+```python
+df.write.format("geoparquet").option("compression", "zstd").mode("overwrite").save(
+    "path/to/output"
+)
+```
+
 ## How Sedona uses GeoParquet bounding box (bbox) metadata with Spark
 
 The bounding box metadata specifies the area covered by geometric shapes in a given file.  Suppose you query points in a region not covered by the bounding box for a given file.  The engine can skip that entire file when executing the query because it’s known that it does not cover any relevant data.