You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sedona.apache.org by ji...@apache.org on 2026/07/31 14:44:21 UTC

(sedona) branch branch-1.9.0 updated: [DOCS] Refine the Waligora pine description in the spatial stats post (#3222)

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

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


The following commit(s) were added to refs/heads/branch-1.9.0 by this push:
     new d94296ae536 [DOCS] Refine the Waligora pine description in the spatial stats post (#3222)
d94296ae536 is described below

commit d94296ae5363213ce64a25d5651dc081998422b3
Author: Jia Yu <ji...@apache.org>
AuthorDate: Fri Jul 31 07:32:26 2026 -0700

    [DOCS] Refine the Waligora pine description in the spatial stats post (#3222)
---
 docs/blog/posts/spatial-stats-outliers.png | Bin 173018 -> 173941 bytes
 docs/blog/posts/spatial-stats.md           |   6 +++---
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/blog/posts/spatial-stats-outliers.png b/docs/blog/posts/spatial-stats-outliers.png
index 0cd051446c4..d7d4416bba9 100644
Binary files a/docs/blog/posts/spatial-stats-outliers.png and b/docs/blog/posts/spatial-stats-outliers.png differ
diff --git a/docs/blog/posts/spatial-stats.md b/docs/blog/posts/spatial-stats.md
index 646fcaa1cfc..9125fc13c32 100644
--- a/docs/blog/posts/spatial-stats.md
+++ b/docs/blog/posts/spatial-stats.md
@@ -19,7 +19,7 @@ Anyone can look at a map and see clumps. The interesting questions are the ones
 
 Sedona ships a spatial statistics module — `sedona.stats` — that answers those questions as DataFrame operations: **Moran's I** for global autocorrelation, **Getis-Ord Gi\*** for hotspot significance, **DBSCAN** for density clustering, and **Local Outlier Factor** for spatial anomalies. The classic exploratory-spatial-analysis toolkit, running distributed.
 
-This post works through all four as one investigation, on a dataset that ships in the Sedona repo: **12,873 OpenStreetMap points of interest** from western Poland (the Lubusz region), loaded straight from the bundled shapefile:
+This post works through all four as one investigation, on a dataset that ships in the Sedona repo: **12,873 OpenStreetMap points of interest** from western Poland's Lubusz region. (Poland is the home country of Sedona PMC member Pawel — which is how a slice of it became the project's sample data.) Loaded straight from the bundled shapefile:
 
 ```python
 from sedona.spark import SedonaContext
@@ -129,9 +129,9 @@ lof.orderBy("lof", ascending=False).select("fclass", "name", "lof").show(5)
 +-------------+----------------+-----+
 ```
 
-![The ten highest-LOF points highlighted against the dimmed dataset — isolated ruins, hunting stands, and one famous lone pine tree](spatial-stats-outliers.png)
+![The ten highest-LOF points highlighted against the dimmed dataset — isolated ruins, hunting stands, and one celebrity pine](spatial-stats-outliers.png)
 
-The algorithm has no idea what these features are — and it independently surfaced ruins in the forest, hunting stands, a roadside motel, and **„Sosna Waligóra", a monumental pine tree famous precisely for standing alone**. When your outlier detector rediscovers a landmark whose claim to fame is isolation, it's working.
+The algorithm has no idea what these features are — and it independently surfaced ruins in the forest, hunting stands, a roadside motel, and **Sosna Waligóra**: a celebrity pine near Sulechów with a six-metre waistline, long billed as the thickest in Poland, holding court entirely alone beside a country road. The detector's verdict, in effect: *this tree has no neighbors*. Correct — and when your outlier detector independently rediscovers a beloved national monument whose whole scene is  [...]
 
 ## The same code at any scale