This is an automated email from the ASF dual-hosted git repository.
jiayu 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 6df699f970 [CI] Add Editorconfig checker with pre-commit (#2634)
6df699f970 is described below
commit 6df699f97048f6c4f5014392a08db3b2068290f1
Author: John Bampton <[email protected]>
AuthorDate: Wed Feb 11 16:33:45 2026 +1000
[CI] Add Editorconfig checker with pre-commit (#2634)
---
.pre-commit-config.yaml | 8 ++++++++
docs/tutorial/concepts/spatial-joins.md | 14 +++++++-------
docs/tutorial/files/geojson-sedona-spark.md | 4 ++--
3 files changed, 17 insertions(+), 9 deletions(-)
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 494c9e27b1..3be967720e 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -497,3 +497,11 @@ repos:
name: run blacken-docs
description: run `black` on python code blocks in documentation files
additional_dependencies: [black==26.1.0]
+ - repo: https://github.com/editorconfig-checker/editorconfig-checker.python
+ rev: 3.6.0
+ hooks:
+ - id: editorconfig-checker
+ name: run editorconfig-checker
+ description: a tool to verify that your files are in harmony with your
.editorconfig
+ exclude:
^docs/image/.*$|^R/man/.*\.Rd$|^spark/common/src/test/resources/.*$
+ alias: ec
diff --git a/docs/tutorial/concepts/spatial-joins.md
b/docs/tutorial/concepts/spatial-joins.md
index 7ec0a010c2..05a86bd609 100644
--- a/docs/tutorial/concepts/spatial-joins.md
+++ b/docs/tutorial/concepts/spatial-joins.md
@@ -38,7 +38,7 @@ SELECT
points.id as point_id,
polygons.id as polygon_id
FROM points
-JOIN polygons ON ST_Within(points.geometry, polygons.geometry);
+JOIN polygons ON ST_Within(points.geometry, polygons.geometry);
```
Here’s the result:
@@ -61,7 +61,7 @@ SELECT
points.id as point_id,
polygons.id as polygon_id
FROM points
-LEFT JOIN polygons ON ST_Within(points.geometry, polygons.geometry);
+LEFT JOIN polygons ON ST_Within(points.geometry, polygons.geometry);
```
Here’s the output:
@@ -87,7 +87,7 @@ SELECT
points.id as point_id,
polygons.id as polygon_id
FROM points
-LEFT JOIN polygons ON ST_Contains(polygons.geometry, points.geometry);
+LEFT JOIN polygons ON ST_Contains(polygons.geometry, points.geometry);
```
Here’s the same result:
@@ -115,7 +115,7 @@ SELECT
lines.id as line_id,
polygons.id as polygon_id
FROM lines
-LEFT JOIN polygons ON ST_Crosses(lines.geometry, polygons.geometry);
+LEFT JOIN polygons ON ST_Crosses(lines.geometry, polygons.geometry);
```
Here is the result:
@@ -169,7 +169,7 @@ SELECT
lines.id as line_id,
polygons.id as polygon_id
FROM lines
-LEFT JOIN polygons ON ST_Touches(lines.geometry, polygons.geometry);
+LEFT JOIN polygons ON ST_Touches(lines.geometry, polygons.geometry);
""").show()
```
@@ -401,13 +401,13 @@ See this section on [additional query enhancements
here](https://sedona.apache.o
## Spatial broadcast joins
-Sedona can run on a single node or many nodes in a cluster.
+Sedona can run on a single node or many nodes in a cluster.
As you can imagine, joining two datasets can be slower when your data is on
different machines in a cluster. That requires data shuffling, which can be
slow.
If one of the tables is small, you can broadcast it, which copies it to all
the machines in the cluster. Broadcasting can make the join much faster.
-You should generally only broadcast DataFrames that are relatively small, see
[here for more
information](https://sedona.apache.org/latest/api/sql/Optimizer/?h=broadcast#broadcast-index-join).
+You should generally only broadcast DataFrames that are relatively small, see
[here for more
information](https://sedona.apache.org/latest/api/sql/Optimizer/?h=broadcast#broadcast-index-join).
Sedona will automatically broadcast tables smaller than the threshold; [see
here for more
details](https://sedona.apache.org/latest/api/sql/Optimizer/#automatic-broadcast-index-join).
diff --git a/docs/tutorial/files/geojson-sedona-spark.md
b/docs/tutorial/files/geojson-sedona-spark.md
index 9b60859a1f..f55c9b0438 100644
--- a/docs/tutorial/files/geojson-sedona-spark.md
+++ b/docs/tutorial/files/geojson-sedona-spark.md
@@ -19,7 +19,7 @@
# Apache Sedona GeoJSON with Spark
-This page shows how to read/write single-line GeoJSON files and multiline
GeoJSON files with Apache Sedona and Spark.
+This page shows how to read/write single-line GeoJSON files and multiline
GeoJSON files with Apache Sedona and Spark.
The post concludes with a summary of the benefits and drawbacks of the GeoJSON
file format for spatial analyses.
@@ -142,7 +142,7 @@ df.show(truncate=False)
Here’s the result:
```
-+---------------------------------------------+------+
++---------------------------------------------+------+
|geometry |prop0 |
+---------------------------------------------+------+
|POINT (102 0.5) |value0|
