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 c1cfbc351e [DOCS] Standardize filenames by removing spaces (#2638)
c1cfbc351e is described below

commit c1cfbc351e4a46bc04c92c945a661d49c46563f0
Author: John Bampton <[email protected]>
AuthorDate: Wed Feb 11 16:32:21 2026 +1000

    [DOCS] Standardize filenames by removing spaces (#2638)
---
 docs/blog/posts/spatial-query-benchmarking-databricks.md    |   6 +++---
 .../{SpatialBench @ SF100 .png => [email protected]}   | Bin
 .../{SpatialBench @ SF1000 .png => [email protected]} | Bin
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/blog/posts/spatial-query-benchmarking-databricks.md 
b/docs/blog/posts/spatial-query-benchmarking-databricks.md
index e5c8de29bb..90471e3dd1 100644
--- a/docs/blog/posts/spatial-query-benchmarking-databricks.md
+++ b/docs/blog/posts/spatial-query-benchmarking-databricks.md
@@ -40,7 +40,7 @@ We found that only one of the simpler SpatialBench queries 
(\#2) tested on Datab
 
 You can see these results in the graph below, which represents a 
price-performance measurement normalized to the Sedona configuration (1x) on 
Databricks Jobs clusters and compares this to Serverless SQL using SpatialBench 
at a scale factor of 1000. We’ll dive into how these results were produced and 
share other results as well. Some queries are missing data points because those 
queries didn’t finish or errored out given the configuration and guardrails we 
used.
 
-![SpatialBench @ 
SF1000](../../image/blog/query-benchmarking-dbx/SpatialBench%20@%20SF1000%20.png)
+![SpatialBench @ 
SF1000](../../image/blog/query-benchmarking-dbx/[email protected])
 
 ## What is SpatialBench?
 
@@ -104,9 +104,9 @@ Neither option finished all queries within the 10-hour 
timeout, and some queries
 
 The following shows query price-performance normalized against the results of 
Sedona (1x baseline) at both SF100 and SF1000. Missing data points match the 
capability matrices above, where only price-performance is shown for queries 
that finished. Lower is better.
 
-![SpatialBench @ 
SF100](../../image/blog/query-benchmarking-dbx/SpatialBench%20@%20SF100%20.png)
+![SpatialBench @ 
SF100](../../image/blog/query-benchmarking-dbx/[email protected])
 
-![SpatialBench @ 
SF1000](../../image/blog/query-benchmarking-dbx/SpatialBench%20@%20SF1000%20.png)
+![SpatialBench @ 
SF1000](../../image/blog/query-benchmarking-dbx/[email protected])
 
 ### SpatialBench @ SF100: Actual Cost per Query
 
diff --git a/docs/image/blog/query-benchmarking-dbx/SpatialBench @ SF100 .png 
b/docs/image/blog/query-benchmarking-dbx/[email protected]
similarity index 100%
rename from docs/image/blog/query-benchmarking-dbx/SpatialBench @ SF100 .png
rename to docs/image/blog/query-benchmarking-dbx/[email protected]
diff --git a/docs/image/blog/query-benchmarking-dbx/SpatialBench @ SF1000 .png 
b/docs/image/blog/query-benchmarking-dbx/[email protected]
similarity index 100%
rename from docs/image/blog/query-benchmarking-dbx/SpatialBench @ SF1000 .png
rename to docs/image/blog/query-benchmarking-dbx/[email protected]

Reply via email to