sedona
sedona copied to clipboard
apache
A cluster computing framework for processing large-scale geospatial data
## Expected behavior In the [RDD Distance Join Docs](https://sedona.apache.org/latest/tutorial/rdd/?h=rdd#write-a-distance-join-query) There is a link for the output format in the text "The output format of the distance join query is [here](https://sedona.apache.org/latest/tutorial/rdd/?h=rdd#output-format-2)."...
## Expected behavior I'd like to develop Apache Sedona from VSCode and it's a generally popular IDE that others might want to use too! ## Actual behavior The developer guide...
Hello. We are trying to use geometry data with Apache Spark Connect and Apache Sedona. We are able to convert binary geometry data to Sedona geometry types using `ST_GeomFromWKB` on...
In the Databricks Spark documentation here: https://sedona.apache.org/1.3.1-incubating/setup/databricks/ It says recommends the following Spark configuration: ``` spark.sql.extensions org.apache.sedona.viz.sql.SedonaVizExtensions,org.apache.sedona.sql.SedonaSqlExtensions spark.serializer org.apache.spark.serializer.KryoSerializer spark.kryo.registrator org.apache.sedona.core.serde.SedonaKryoRegistrator ``` However, after speaking with Carto support, they said...
Parameterized queries [were recently added to Spark](https://www.databricks.com/blog/parameterized-queries-pyspark) and allow for some really clean syntax when shifting from the Python API to the SQL API. We should consider adding this interface...
I think that all polygons in OSM and other datasets are supposed to be ordered in such a way that the points in the polygon are listed in counter clockwise...
Run seen here: https://github.com/apache/sedona/actions/runs/11573723748/job/32216483591?pr=1659 I see it failed on at least 2 PRs. https://github.com/actions/first-interaction
Postgis: ``` # select ST_Subdivide('LINESTRING (0 0, 99 99)'::geometry, 4); ERROR: lwgeom_subdivide_prec: cannot subdivide to fewer than 5 vertices per output ``` Sedona: ``` select ST_Subdivide(ST_GeomFromWKT('LINESTRING (0 0, 99 99)'),...
It would be nice to have something like https://postgis.net/docs/ST_Segmentize.html to break up large geometries for better partitioning and indexing. Unfortunately I'm swamped so I won't have time work on this...
https://github.com/textlint/textlint https://textlint.github.io/