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 0b9dd43c6 [DOCS] Enable markdownlint rule MD038 (#1629)
0b9dd43c6 is described below
commit 0b9dd43c6e9a61b926418d9ca9c0b205d238a42b
Author: John Bampton <[email protected]>
AuthorDate: Sun Oct 13 12:00:50 2024 +1000
[DOCS] Enable markdownlint rule MD038 (#1629)
https://github.com/DavidAnson/markdownlint/blob/main/doc/md038.md
---
.github/linters/.markdown-lint.yml | 3 ---
docs/api/sql/Optimizer.md | 2 +-
docs/tutorial/rdd.md | 2 +-
docs/tutorial/snowflake/sql.md | 2 +-
4 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/.github/linters/.markdown-lint.yml
b/.github/linters/.markdown-lint.yml
index ddbf76e67..0fc00475e 100644
--- a/.github/linters/.markdown-lint.yml
+++ b/.github/linters/.markdown-lint.yml
@@ -30,9 +30,6 @@ MD034: false
# no-emphasis-as-heading - Emphasis used instead of a heading
MD036: false
-# no-space-in-code - Spaces inside code span elements
-MD038: false
-
# fenced-code-language - Fenced code blocks should have a language specified
MD040: false
diff --git a/docs/api/sql/Optimizer.md b/docs/api/sql/Optimizer.md
index 63e485ee3..f48227080 100644
--- a/docs/api/sql/Optimizer.md
+++ b/docs/api/sql/Optimizer.md
@@ -130,7 +130,7 @@ WHERE
ST_DistanceSpheroid(pointdf1.pointshape1,pointdf2.pointshape2) <= 2
```
!!!warning
- If you use `ST_DistanceSpheroid ` or `ST_DistanceSphere` as the
predicate, the unit of the distance is meter. Currently, distance join with
geodesic distance calculators work best for point data. For non-point data, it
only considers their centroids.
+ If you use `ST_DistanceSpheroid` or `ST_DistanceSphere` as the
predicate, the unit of the distance is meter. Currently, distance join with
geodesic distance calculators work best for point data. For non-point data, it
only considers their centroids.
## Broadcast index join
diff --git a/docs/tutorial/rdd.md b/docs/tutorial/rdd.md
index 65fe0c859..d2880388f 100644
--- a/docs/tutorial/rdd.md
+++ b/docs/tutorial/rdd.md
@@ -28,7 +28,7 @@ A generic SpatialRDD is not typed to a certain geometry type
and open to more sc
#### From WKT/WKB
-Geometries in a WKT and WKB file always occupy a single column no matter how
many coordinates they have. Sedona provides `WktReader ` and `WkbReader` to
create generic SpatialRDD.
+Geometries in a WKT and WKB file always occupy a single column no matter how
many coordinates they have. Sedona provides `WktReader` and `WkbReader` to
create generic SpatialRDD.
Suppose we have a `checkin.tsv` WKT TSV file at Path `/Download/checkin.tsv`
as follows:
diff --git a/docs/tutorial/snowflake/sql.md b/docs/tutorial/snowflake/sql.md
index 20824e094..6cdacb133 100644
--- a/docs/tutorial/snowflake/sql.md
+++ b/docs/tutorial/snowflake/sql.md
@@ -38,7 +38,7 @@ SELECT Sedona.ST_GeomFromWKT(wkt) AS geom, city_name
FROM city_tbl
```
-The `geom` column Table `city_tbl_geom ` is now in a `Binary` type and data in
this column is in a format that can be understood by Sedona. The output of this
query will show geometries in WKB binary format like this:
+The `geom` column Table `city_tbl_geom` is now in a `Binary` type and data in
this column is in a format that can be understood by Sedona. The output of this
query will show geometries in WKB binary format like this:
```
GEOM CITY_NAME
