Re: [PR] [SEDONA-615] Add ST_MaximumInscribedCircle [sedona]
jiayuasu merged PR #1488: URL: https://github.com/apache/sedona/pull/1488 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] sedona's docker image can not run successfully on k8s [sedona]
hong-yangzhao opened a new issue, #1492: URL: https://github.com/apache/sedona/issues/1492 ## Expected behavior run spark-pi example successfully ## Actual behavior ```sh Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "driver": executable file not found in $PATH: unknown ``` ## Steps to reproduce the problem I plan to run a Sedona cluster on Kubernetes. Prior to this, I have successfully used the spark-operator to run a Spark cluster and obtained results from the spark-pi example: ```yaml apiVersion: "sparkoperator.k8s.io/v1beta2" kind: SparkApplication metadata: name: spark-pi-test namespace: spark-tasks spec: type: Scala mode: cluster image: docker.io/spark:3.5.1 imagePullPolicy: IfNotPresent mainClass: org.apache.spark.examples.SparkPi mainApplicationFile: "local:///opt/spark/examples/jars/spark-examples_2.12-3.5.1.jar" sparkVersion: "3.5.1" restartPolicy: type: Never driver: cores: 4 memory: "4G" labels: version: 3.5.1 serviceAccount: spark-task-account env: - name: SPARK_MODE value: "driver" executor: cores: 4 instances: 2 memory: "4G" labels: version: 3.5.1 arguments: - "1000" ``` However, when I change the image to Sedona's image: ```yaml apiVersion: "sparkoperator.k8s.io/v1beta2" kind: SparkApplication metadata: name: sedona-test namespace: spark-tasks spec: type: Scala mode: cluster image: docker.io/apache/sedona:1.6.0 imagePullPolicy: IfNotPresent mainClass: org.apache.spark.examples.SparkPi mainApplicationFile: "local:///opt/spark/examples/jars/spark-examples_2.12-3.4.1.jar" sparkVersion: "3.4.1" restartPolicy: type: Never driver: cores: 4 memory: "4G" labels: version: 3.4.1 serviceAccount: spark-task-account env: - name: SPARK_MODE value: "driver" executor: cores: 4 instances: 2 memory: "4G" labels: version: 3.4.1 arguments: - "1000" ``` Submitting this YAML file results in an error:  The configMap (spark-drv-fba0809048193c11-conf-map) mentioned in the error message does exist: ```sh kubectl get configmap -n spark-tasks NAME DATA AGE kube-root-ca.crt 1 11d spark-drv-fba0809048193c11-conf-map 2 25m ``` My question is: Does the Sedona image not support running on Kubernetes? Or is there a problem with my configuration? Thank you. ## Settings Sedona version = 1.6.0 Apache Spark version = 3.4.1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-610] Add ST_IsValidTrajectory [sedona]
furqaankhan opened a new pull request, #1481: URL: https://github.com/apache/sedona/pull/1481 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-610. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? - Add ST_IsValidTrajectory ## How was this patch tested? - add new unit tests ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] There was garbled code when reading Chinese from shp file [sedona]
hong-yangzhao closed issue #1480: There was garbled code when reading Chinese from shp file URL: https://github.com/apache/sedona/issues/1480 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] There was garbled code when reading Chinese from shp file [sedona]
hong-yangzhao opened a new issue, #1480:
URL: https://github.com/apache/sedona/issues/1480
## Expected behavior
Successfully read Chinese
## Actual behavior
Garbled code
## Steps to reproduce the problem
Partial code(Java):
```java
public static void main(String[] args) {
SparkSession sedona = SedonaContext.builder()
.master("local")
.appName("test")
.config("spark.serializer",
"org.apache.spark.serializer.KryoSerializer")
.config("spark.kryo.registrator",
SedonaVizKryoRegistrator.class.getName())
.config("spark.driver.extraJavaOptions",
"-Dsedona.global.charset=utf8")
.config("spark.executor.extraJavaOptions",
"-Dsedona.global.charset=utf8")
.getOrCreate();
SedonaContext.create(sedona);
SpatialRDD rdd =
ShapefileReader.readToGeometryRDD(JavaSparkContext.fromSparkContext(sedona.sparkContext()),
"F:\\test_file\\test_shp");
Dataset df = Adapter.toDf(rdd , sedona);
df.show(1);
}
```
I followed the example from the official website 'API Docs -> Sedona with
Apache Spark -> Vector data -> Constructor -> Read ESRI Shapefile -> SparkSQL
example' to read a shp file. This shp file is able to display Chinese
characters properly in GIS software, but when sedona reads the data, whether
it's printed to the console or written to a file, the Chinese part is displayed
as garbled text. Additionally, when I use 'printSchema()', I noticed that all
the 'Column' types are shown as string, whereas my shp file contains data types
other than just string.
Since all the 'Column' types are displayed as string, I found that the
decimal numbers have been transformed into numbers in scientific notation. Is
it because I performed the operation incorrectly, or is there another reason?
Please advise, thank you!
## Settings
Sedona version = ?
1.5.1
Apache Spark version = ?
3.5.0
Apache Flink version = ?
API type = Scala, Java, Python?
Java
Scala version = 2.11, 2.12, 2.13?
2.13
JRE version = 1.8, 1.11?
1.8
Python version = ?
Environment = Standalone, AWS EC2, EMR, Azure, Databricks?
Standalone,local
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [I] AWS Glue official tutorial [sedona]
jiayuasu closed issue #1399: AWS Glue official tutorial URL: https://github.com/apache/sedona/issues/1399 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump urllib3 from 2.2.1 to 2.2.2 in /binder [sedona]
dependabot[bot] opened a new pull request, #1479: URL: https://github.com/apache/sedona/pull/1479 Bumps [urllib3](https://github.com/urllib3/urllib3) from 2.2.1 to 2.2.2. Release notes Sourced from https://github.com/urllib3/urllib3/releases;>urllib3's releases. 2.2.2 urllib3 is fundraising for HTTP/2 support https://sethmlarson.dev/urllib3-is-fundraising-for-http2-support;>urllib3 is raising ~$40,000 USD to release HTTP/2 support and ensure long-term sustainable maintenance of the project after a sharp decline in financial support for 2023. If your company or organization uses Python and would benefit from HTTP/2 support in Requests, pip, cloud SDKs, and thousands of other projects https://opencollective.com/urllib3;>please consider contributing financially to ensure HTTP/2 support is developed sustainably and maintained for the long-haul. Thank you for your support. Changes Added the Proxy-Authorization header to the list of headers to strip from requests when redirecting to a different host. As before, different headers can be set via Retry.remove_headers_on_redirect. Allowed passing negative integers as amt to read methods of http.client.HTTPResponse as an alternative to None. (https://redirect.github.com/urllib3/urllib3/issues/3122;>#3122) Fixed return types representing copying actions to use typing.Self. (https://redirect.github.com/urllib3/urllib3/issues/3363;>#3363) Full Changelog: https://github.com/urllib3/urllib3/compare/2.2.1...2.2.2;>https://github.com/urllib3/urllib3/compare/2.2.1...2.2.2 Changelog Sourced from https://github.com/urllib3/urllib3/blob/main/CHANGES.rst;>urllib3's changelog. 2.2.2 (2024-06-17) Added the Proxy-Authorization header to the list of headers to strip from requests when redirecting to a different host. As before, different headers can be set via Retry.remove_headers_on_redirect. Allowed passing negative integers as amt to read methods of http.client.HTTPResponse as an alternative to None. ([#3122](https://github.com/urllib3/urllib3/issues/3122) https://github.com/urllib3/urllib3/issues/3122;__) Fixed return types representing copying actions to use typing.Self. ([#3363](https://github.com/urllib3/urllib3/issues/3363) https://github.com/urllib3/urllib3/issues/3363;__) Commits https://github.com/urllib3/urllib3/commit/27e2a5c5a7ab6a517252cc8dcef3ffa6ffb8f61a;>27e2a5c Release 2.2.2 (https://redirect.github.com/urllib3/urllib3/issues/3406;>#3406) https://github.com/urllib3/urllib3/commit/accff72ecc2f6cf5a76d9570198a93ac7c90270e;>accff72 Merge pull request from GHSA-34jh-p97f-mpxf https://github.com/urllib3/urllib3/commit/34be4a57e59eb7365bcc37d52e9f8271b5b8d0d3;>34be4a5 Pin CFFI to a new release candidate instead of a Git commit (https://redirect.github.com/urllib3/urllib3/issues/3398;>#3398) https://github.com/urllib3/urllib3/commit/da410581b6b3df73da976b5ce5eb20a4bd030437;>da41058 Bump browser-actions/setup-chrome from 1.6.0 to 1.7.1 (https://redirect.github.com/urllib3/urllib3/issues/3399;>#3399) https://github.com/urllib3/urllib3/commit/b07a669bd970d69847801148286b726f0570b625;>b07a669 Bump github/codeql-action from 2.13.4 to 3.25.6 (https://redirect.github.com/urllib3/urllib3/issues/3396;>#3396) https://github.com/urllib3/urllib3/commit/b8589ec9f8c4da91511e601b632ac06af7e7c10e;>b8589ec Measure coverage with v4 of artifact actions (https://redirect.github.com/urllib3/urllib3/issues/3394;>#3394) https://github.com/urllib3/urllib3/commit/f3bdc5585111429e22c81b5fb26c3ec164d98b81;>f3bdc55 Allow triggering CI manually (https://redirect.github.com/urllib3/urllib3/issues/3391;>#3391) https://github.com/urllib3/urllib3/commit/52392654b30183129cf3ec06010306f517d9c146;>5239265 Fix HTTP version in debug log (https://redirect.github.com/urllib3/urllib3/issues/3316;>#3316) https://github.com/urllib3/urllib3/commit/b34619f94ece0c40e691a5aaf1304953d88089de;>b34619f Bump actions/checkout to 4.1.4 (https://redirect.github.com/urllib3/urllib3/issues/3387;>#3387) https://github.com/urllib3/urllib3/commit/9961d14de7c920091d42d42ed76d5d479b80064d;>9961d14 Bump browser-actions/setup-chrome from 1.5.0 to 1.6.0 (https://redirect.github.com/urllib3/urllib3/issues/3386;>#3386) Additional commits viewable in https://github.com/urllib3/urllib3/compare/2.2.1...2.2.2;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: #
Re: [PR] [SEDONA-609] Fix python 3.12 build issue caused by binary compatibility issues with numpy 2.0.0 [sedona]
jiayuasu merged PR #1478: URL: https://github.com/apache/sedona/pull/1478 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-609] Fix python 3.12 build issue caused by binary compatibility issues with numpy 2.0.0 [sedona]
zhangfengcdt opened a new pull request, #1478: URL: https://github.com/apache/sedona/pull/1478 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-609. The PR name follows the format `[SEDONA-609] my subject`. ## What changes were proposed in this PR? Numpy 2.0.0 is released as the major release of numpy on June 16, 2024. As of right now, the pandas version still has compatible with numpy 2.0. So, to avoid issues when installing pandas with pip, you should pin numpy < 2. ## How was this patch tested? All builds should be fixed and run successfully. ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Sedona fails to write Delta Lake on Databricks 15.3 Beta: ClassCastException [sedona]
jacob-talroo closed issue #1454: Sedona fails to write Delta Lake on Databricks 15.3 Beta: ClassCastException URL: https://github.com/apache/sedona/issues/1454 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] Breaking change between 1.5.3 and 1.6.0 affecting RASTER functions java.lang.NoSuchMethodError: void org.geotools.coverage.grid.GridGeometry2D [sedona]
golfalot closed issue #1477: Breaking change between 1.5.3 and 1.6.0 affecting RASTER functions java.lang.NoSuchMethodError: void org.geotools.coverage.grid.GridGeometry2D URL: https://github.com/apache/sedona/issues/1477 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Breaking change between 1.5.3 and 1.6.0 affecting RASTER functions java.lang.NoSuchMethodError: void org.geotools.coverage.grid.GridGeometry2D [sedona]
golfalot opened a new issue, #1477:
URL: https://github.com/apache/sedona/issues/1477
## Expected behavior
return result rows/table
## Actual behavior
crash with stack trace
java.lang.NoSuchMethodError: 'void
org.geotools.coverage.grid.GridGeometry2D.(org.opengis.coverage.grid.GridEnvelope,
org.opengis.referencing.datum.PixelInCell,
org.opengis.referencing.operation.MathTransform,
org.opengis.referencing.crs.CoordinateReferenceSystem,
org.geotools.util.factory.Hints)
## Steps to reproduce the problem
```python
from sedona.spark import SedonaContext
config = SedonaContext.builder() .\
config('spark.jars.packages',
'org.apache.sedona:sedona-spark-shaded-3.4_2.12-1.6.0,'
'org.datasyslab:geotools-wrapper:1.6.0-28.2'). \
getOrCreate()
```
```python
from pyspark.sql import functions as f
df =
sedona.read.format("binaryFile").load("/raw/GIS_Raster_Data/samples/test.nc")
df2 = df.withColumn("raster", f.expr("RS_FromNetCDF(content, 'O3')"))
df2.createOrReplaceTempView("raster_table")
# this command throws the error
sedona.sql("SELECT RS_Value(raster, 3, 4, 1) FROM raster_table").show()
```
Raster sources from:
https://github.com/apache/sedona/blob/master/spark/common/src/test/resources/raster/netcdf/test.nc
sedona = SedonaContext.create(config)
## Settings
Sedona version = 1.6.0
Apache Spark version = 3.4
API type =Python
Scala version = 2.12.17
Java version = 11
Python version = 3.10
Environment = Azure Synapse Spark Pool
# Additional background
We're using Azure Synapse with DEP (data exfiltration protection enabled)
which means no outbound internet access, so all packages must be obtained
manually before being uploaded as "Workspace packages" which can then enabled
on the spark pools.
## A configuration that works (no error)
### Spark pool
- Apache Spark version = 3.4
- Scala version = 2.12.17
- Java version = 11
- Python version = 3.10
Java
- sedona-spark-shaded-3.4_2.12-1.5.3.jar
- geotools-wrapper-1.5.3-28.2.jar
Python
-
apache_sedona-1.5.3-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
- shapely-2.0.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
## A configuration that causes the error
### Spark pool (identical to above)
- Apache Spark version = 3.4
- Scala version = 2.12.17
- Java version = 11
- Python version = 3.10
### Packages
Java
- sedona-spark-shaded-3.4_2.12-1.6.0.jar
- geotools-wrapper-1.6.0-28.2.jar
Python
- click_plugins-1.1.1-py2.py3-none-any.whl
- affine-2.4.0-py3-none-any.whl
-
apache_sedona-1.6.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
- cligj-0.7.2-py3-none-any.whl
- rasterio-1.3.10-cp310-cp310-manylinux2014_x86_64.whl
- shapely-2.0.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
- snuggs-1.4.7-py3-none-any.whl
**stating the obvious:** There are many packages listed in the failing
scenario. See below the convaluted steps need to establish what packages are
required for a baseline Synapse Spark pool.
# How to establish Python package dependencies for Synsapse Spark pool
## Identify Operating System
https://learn.microsoft.com/en-us/azure/synapse-analytics/spark/apache-spark-34-runtime
=> Mariner 2.0
## Create a VM and apply baseline configuration
https://github.com/microsoft/azurelinux/blob/2.0/toolkit/docs/quick_start/quickstart.md
### Get conda
```bash
wget
https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-x86_64.sh
sudo bash Miniforge3-Linux-x86_64.sh -b -p /usr/lib/miniforge3
export PATH="/usr/lib/miniforge3/bin:$PATH"
```
### Apply baseline Synapse configuration
```bash
sudo tdnf -y install gcc g++
wget
https://raw.githubusercontent.com/Azure-Samples/Synapse/main/Spark/Python/Synapse-Python310-CPU.yml
conda env create -n synapse-env -f Synapse-Python310-CPU.yml
source activate synapse-env
```
### Install pip packages and determine which packages are Downloaded above
and beyond the baseline packages
requirements.txt
```bash
# echo "apache-sedona==1.5.3" > input-user-req.txt
echo "apache-sedona==1.6.0" > input-user-req.txt
```
install apache-sedona and dependencies
```bash
pip install -r input-user-req.txt > pip_output.txt
```
install apache-sedona and dependencies
```bash
cat pip_output.txt | grep Downloading
```
Use the above output to identify the `.whl` files to download add to Synapse.
# Full stack trace of error
```python
---
Py4JJavaError
Re: [PR] [SEDONA-608] Fix ST_IsPolygonCW, ST_IsPolygonCCW, ST_ForcePolygonCW and ST_ForcePolygonCCW [sedona]
jiayuasu merged PR #1476: URL: https://github.com/apache/sedona/pull/1476 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] ST_IsPolygonCW, ST_IsPolygonCCW, ST_ForcePolygonCW and ST_ForcePolygonCCW fails on Polygons without interior ring [sedona]
jiayuasu closed issue #1475: ST_IsPolygonCW, ST_IsPolygonCCW, ST_ForcePolygonCW and ST_ForcePolygonCCW fails on Polygons without interior ring URL: https://github.com/apache/sedona/issues/1475 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-608] Fix ST_IsPolygonCW, ST_IsPolygonCCW, ST_ForcePolygonCW and ST_ForcePolygonCCW [sedona]
furqaankhan opened a new pull request, #1476: URL: https://github.com/apache/sedona/pull/1476 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-608. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? - add a check to see if the interior ring exists or not to fix #1475. ## How was this patch tested? - passed new tests ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-102] Use spotless as Java and Scala code formatter [sedona]
jiayuasu merged PR #1428: URL: https://github.com/apache/sedona/pull/1428 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-606] Add ST_IsValidDetail [sedona]
jiayuasu merged PR #1474: URL: https://github.com/apache/sedona/pull/1474 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-606] Add ST_IsValidDetail [sedona]
furqaankhan opened a new pull request, #1474: URL: https://github.com/apache/sedona/pull/1474 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-606. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? - Add ST_IsValidDetail ## How was this patch tested? - Add new unit tests ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-605] Fix rasterization when useGeometryExtent=false [sedona]
jiayuasu merged PR #1473: URL: https://github.com/apache/sedona/pull/1473 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-605] Fix rasterization when useGeometryExtent=false [sedona]
Kontinuation opened a new pull request, #1473: URL: https://github.com/apache/sedona/pull/1473 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-605. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Fix the code to compute the width and height of the rasterization result. Please refer to the JIRA ticket for a detailed explanation of this problem. This patch fixes `RS_AsRaster`, `RS_ZonalStats` and `RS_ZonalStatsAll`. ## How was this patch tested? Add new tests for RS_AsRaster. ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-602] Add ST_LocateAlong [sedona]
jiayuasu merged PR #1471: URL: https://github.com/apache/sedona/pull/1471 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-604] Add ST_AddMeasure [sedona]
jiayuasu merged PR #1472: URL: https://github.com/apache/sedona/pull/1472 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-601] Add ST_DelaunayTriangles [sedona]
jiayuasu merged PR #1470: URL: https://github.com/apache/sedona/pull/1470 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-599] [SEDONA-600] Add ST_MinimumClearance, ST_MinimumClearanceLine [sedona]
jiayuasu merged PR #1469: URL: https://github.com/apache/sedona/pull/1469 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-598] Add ST_UnaryUnion [sedona]
jiayuasu merged PR #1468: URL: https://github.com/apache/sedona/pull/1468 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-604] Add ST_AddMeasure [sedona]
jiayuasu opened a new pull request, #1472: URL: https://github.com/apache/sedona/pull/1472 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Add ST_AddMeasure ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-602] Add ST_LocateAlong [sedona]
jiayuasu opened a new pull request, #1471: URL: https://github.com/apache/sedona/pull/1471 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-602. The PR name follows the format `[SEDONA-602] my subject`. ## What changes were proposed in this PR? Add ST_LocateAlong ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-601] Add ST_DelaunayTriangles [sedona]
jiayuasu opened a new pull request, #1470: URL: https://github.com/apache/sedona/pull/1470 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Passed local tests ## How was this patch tested? Add ST_DelaunyTriangles ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-599] [SEDONA-600] Add ST_MinimumClearance, ST_MinimumClearanceLine [sedona]
jiayuasu opened a new pull request, #1469: URL: https://github.com/apache/sedona/pull/1469 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Add ST_MinimumClearance Add ST_MinimumClearanceLine ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-598] Add ST_UnaryUnion [sedona]
jiayuasu opened a new pull request, #1468: URL: https://github.com/apache/sedona/pull/1468 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-598. The PR name follows the format `[SEDONA-598] my subject`. ## What changes were proposed in this PR? Add ST_UnaryUnion ## How was this patch tested? Passed local test ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-596] [SEDONA-597] Add ST_SimplifyVW, ST_SimplifyPolygonHull [sedona]
jiayuasu merged PR #1467: URL: https://github.com/apache/sedona/pull/1467 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-595] [SEDONA-603] Add ST_LinestringFromWKB, ST_MakePointM [sedona]
jiayuasu merged PR #1466: URL: https://github.com/apache/sedona/pull/1466 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-596] [SEDONA-597] Add ST_SimplifyVW, ST_SimplifyPolygonHull [sedona]
jiayuasu opened a new pull request, #1467: URL: https://github.com/apache/sedona/pull/1467 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Add ST_SimplifyVW Add ST_SimplifyPolygonHull ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-595] [SEDONA-603] Add ST_LinestringFromWKB, ST_MakePointM [sedona]
jiayuasu opened a new pull request, #1466: URL: https://github.com/apache/sedona/pull/1466 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-595. The PR name follows the format `[SEDONA-595] my subject`. ## What changes were proposed in this PR? Add ST_LinestringFromWKB Add ST_MakePointM ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-593] [SEDONA-594] Add ST_Relate, ST_RelateMatch [sedona]
jiayuasu merged PR #1465: URL: https://github.com/apache/sedona/pull/1465 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-591] Add ST_MaxDistance [sedona]
jiayuasu merged PR #1464: URL: https://github.com/apache/sedona/pull/1464 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-590] [SEDONA-592] Add ST_GeomCollFromText, ST_MPointFromText [sedona]
jiayuasu merged PR #1463: URL: https://github.com/apache/sedona/pull/1463 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-593] [SEDONA-594] Add ST_Relate, ST_RelateMatch [sedona]
jiayuasu opened a new pull request, #1465: URL: https://github.com/apache/sedona/pull/1465 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-593. The PR name follows the format `[SEDONA-593] my subject`. ## What changes were proposed in this PR? Add ST_Relate Add ST_RelateMatch ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-591] Add ST_MaxDistance [sedona]
jiayuasu opened a new pull request, #1464: URL: https://github.com/apache/sedona/pull/1464 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-591. The PR name follows the format `[SEDONA-591] my subject`. ## What changes were proposed in this PR? Add ST_MaxDistance ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-590] [SEDONA-592] Add ST_GeomCollFromText, ST_MPointFromText [sedona]
jiayuasu opened a new pull request, #1463: URL: https://github.com/apache/sedona/pull/1463 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Add ST_GeomCollFromText Add ST_MPointFromText ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-589] Add ST_LongestLine [sedona]
jiayuasu merged PR #1462: URL: https://github.com/apache/sedona/pull/1462 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-587] Add ST_Force3DM, ST_Force4D [sedona]
jiayuasu merged PR #1461: URL: https://github.com/apache/sedona/pull/1461 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-589] Add ST_LongestLine [sedona]
jiayuasu opened a new pull request, #1462: URL: https://github.com/apache/sedona/pull/1462 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-589. The PR name follows the format `[SEDONA-589] my subject`. ## What changes were proposed in this PR? Add ST_LongestLine ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-587] Add ST_Force3DM, ST_Force4D [sedona]
jiayuasu opened a new pull request, #1461: URL: https://github.com/apache/sedona/pull/1461 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-587. The PR name follows the format `[SEDONA-587] my subject`. ## What changes were proposed in this PR? Add ST_Force3DM Add ST_Force4D ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-585] [SEDONA-586] Add ST_ForceCollection, ST_Force3DZ [sedona]
jiayuasu merged PR #1460: URL: https://github.com/apache/sedona/pull/1460 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-583] Add ST_Length2D [sedona]
jiayuasu merged PR #1458: URL: https://github.com/apache/sedona/pull/1458 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-584] Add ST_Zmflag [sedona]
jiayuasu merged PR #1459: URL: https://github.com/apache/sedona/pull/1459 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-585] [SEDONA-586] Add ST_ForceCollection, ST_Force3DZ [sedona]
jiayuasu opened a new pull request, #1460: URL: https://github.com/apache/sedona/pull/1460 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-585. The PR name follows the format `[SEDONA-585] my subject`. ## What changes were proposed in this PR? Add ST_ForceCollection Add ST_Force3DZ ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-582] Add ST_PointFromGeoHash [sedona]
jiayuasu merged PR #1457: URL: https://github.com/apache/sedona/pull/1457 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-584] Add ST_Zmflag [sedona]
jiayuasu opened a new pull request, #1459: URL: https://github.com/apache/sedona/pull/1459 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? Add ST_Zmflag ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-583] Add ST_Length2D [sedona]
jiayuasu opened a new pull request, #1458: URL: https://github.com/apache/sedona/pull/1458 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-583. The PR name follows the format `[SEDONA-583] my subject`. ## What changes were proposed in this PR? Add ST_Length2D ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-582] Add ST_PointFromGeoHash [sedona]
jiayuasu opened a new pull request, #1457: URL: https://github.com/apache/sedona/pull/1457 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-582. The PR name follows the format `[SEDONA-582] my subject`. ## What changes were proposed in this PR? Add ST_PointFromGeoHash ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-568] Refactor TestBaseScala to allow customizable Spark configurations [sedona]
jiayuasu merged PR #1455: URL: https://github.com/apache/sedona/pull/1455 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump tornado from 6.4 to 6.4.1 in /binder [sedona]
jiayuasu merged PR #1456: URL: https://github.com/apache/sedona/pull/1456 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump tornado from 6.4 to 6.4.1 in /binder [sedona]
dependabot[bot] opened a new pull request, #1456: URL: https://github.com/apache/sedona/pull/1456 Bumps [tornado](https://github.com/tornadoweb/tornado) from 6.4 to 6.4.1. Changelog Sourced from https://github.com/tornadoweb/tornado/blob/master/docs/releases.rst;>tornado's changelog. Release notes .. toctree:: :maxdepth: 2 releases/v6.4.1 releases/v6.4.0 releases/v6.3.3 releases/v6.3.2 releases/v6.3.1 releases/v6.3.0 releases/v6.2.0 releases/v6.1.0 releases/v6.0.4 releases/v6.0.3 releases/v6.0.2 releases/v6.0.1 releases/v6.0.0 releases/v5.1.1 releases/v5.1.0 releases/v5.0.2 releases/v5.0.1 releases/v5.0.0 releases/v4.5.3 releases/v4.5.2 releases/v4.5.1 releases/v4.5.0 releases/v4.4.3 releases/v4.4.2 releases/v4.4.1 releases/v4.4.0 releases/v4.3.0 releases/v4.2.1 releases/v4.2.0 releases/v4.1.0 releases/v4.0.2 releases/v4.0.1 releases/v4.0.0 releases/v3.2.2 releases/v3.2.1 releases/v3.2.0 releases/v3.1.1 releases/v3.1.0 releases/v3.0.2 releases/v3.0.1 releases/v3.0.0 releases/v2.4.1 releases/v2.4.0 releases/v2.3.0 ... (truncated) Commits https://github.com/tornadoweb/tornado/commit/2a0e1d13b5222dca4388c0ec8a4bb74ea6fa4af2;>2a0e1d1 Merge pull request https://redirect.github.com/tornadoweb/tornado/issues/3388;>#3388 from bdarnell/release-641 https://github.com/tornadoweb/tornado/commit/b7af4e8f5ee578b78e1be5ade43fdb1103659a0e;>b7af4e8 Release notes and version bump for version 6.4.1 https://github.com/tornadoweb/tornado/commit/d65f6e71a77f53a1ff0a0dc55704be13f04eb572;>d65f6e7 Merge pull request https://redirect.github.com/tornadoweb/tornado/issues/3387;>#3387 from bdarnell/chunked-parsing https://github.com/tornadoweb/tornado/commit/8d721a877dd5c2bc0693d9c4d3954eb11fbd404b;>8d721a8 httputil: Only strip tabs and spaces from header values https://github.com/tornadoweb/tornado/commit/7786f09f84c9f3f2012c4cf3878417cb9f053669;>7786f09 Merge pull request https://redirect.github.com/tornadoweb/tornado/issues/3386;>#3386 from bdarnell/curl-crlf https://github.com/tornadoweb/tornado/commit/fb119c767e9c43e71ea823311b0d53f566d86b73;>fb119c7 http1connection: Stricter handling of transfer-encoding https://github.com/tornadoweb/tornado/commit/b0ffc58e02f33f6aa480f008b74495601d988ce1;>b0ffc58 curl_httpclient,http1connection: Prohibit CR and LF in headers https://github.com/tornadoweb/tornado/commit/0efa9a42b4c94ee98549d86992c68227f83efd4e;>0efa9a4 Merge pull request https://redirect.github.com/tornadoweb/tornado/issues/3385;>#3385 from bdarnell/update-black https://github.com/tornadoweb/tornado/commit/2757c6e4874968dd2f74a4d08b450da795de5b6c;>2757c6e Merge pull request https://redirect.github.com/tornadoweb/tornado/issues/3384;>#3384 from tornadoweb/dependabot/pip/requests-2.32.2 https://github.com/tornadoweb/tornado/commit/291d1b661be273b86792e965ac65f9bced8d4ebe;>291d1b6 *: Update black Additional commits viewable in https://github.com/tornadoweb/tornado/compare/v6.4.0...v6.4.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop
[PR] [SEDONA-568] Refactor TestBaseScala to allow customizable Spark configurations [sedona]
zhangfengcdt opened a new pull request, #1455:
URL: https://github.com/apache/sedona/pull/1455
- Added default Spark configurations in `TestBaseScala` trait.
- Provided a method `defaultSparkConfig` for default configurations.
- Allowed subclasses to override `sparkConfig` to add or modify Spark
configurations.
- Updated initialization of Spark session and Spark context to use the
provided configurations.
- Included comments to explain how to override configurations in subclasses.
- Ensured that default configurations are preserved if not overridden by
subclasses.
## Did you read the Contributor Guide?
- Yes, I have read the [Contributor
Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and
[Contributor Development
Guide](https://sedona.apache.org/latest-snapshot/community/develop/)
## Is this PR related to a JIRA ticket?
- Yes, the URL of the associated JIRA ticket is
https://issues.apache.org/jira/browse/SEDONA-568. The PR name follows the
format `[SEDONA-XXX] my subject`.
## What changes were proposed in this PR?
- Added default Spark configurations in `TestBaseScala` trait.
- Provided a method `defaultSparkConfig` for default configurations.
- Allowed subclasses to override `sparkConfig` to add or modify Spark
configurations.
- Updated initialization of Spark session and Spark context to use the
provided configurations.
- Included comments to explain how to override configurations in subclasses.
- Ensured that default configurations are preserved if not overridden by
subclasses.
After this change, user can either use
- Default Configurations: Provided in defaultSparkConfig.
- Overriding Configurations: Subclasses can override sparkConfig and merge
additional configurations with the default ones using the ++ operator, for
example:
```
class CustomTest extends TestBaseScala {
// Override sparkConfig to provide additional configurations
override def sparkConfig: Map[String, String] = defaultSparkConfig ++ Map(
"spark.sql.warehouse.dir" -> "/custom/warehouse/location",
"spark.some.config.option" -> "some-value"
)
describe("CustomTest") {
it("should use custom Spark configuration") {
assert(sparkSession.conf.get("spark.some.config.option") ==
"some-value")
}
it("should access Spark context") {
assert(sc != null)
}
}
}
```
## How was this patch tested?
All existing unit tests should all pass without any impact.
## Did this PR include necessary documentation updates?
- No, this PR does not affect any public API so no need to change the
documentation.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [DOCS] add glue tutorial [sedona]
jiayuasu merged PR #1453: URL: https://github.com/apache/sedona/pull/1453 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[I] Sedona 1.5.3 and 1.6.0 fails to write Delta Lake on Databricks 15: ClassCastException [sedona]
jacob-talroo opened a new issue, #1454: URL: https://github.com/apache/sedona/issues/1454 ## Expected behavior Writing out a delta lake should work. ## Actual behavior Fails with: ```scala ClassCastException: class scala.collection.immutable.Map$Map1 cannot be cast to class com.databricks.sql.transaction.tahoe.actions.ParsedAddFileTags (scala.collection.immutable.Map$Map1 and com.databricks.sql.transaction.tahoe.actions.ParsedAddFileTags are in unnamed module of loader 'app') at scala.Option.flatMap(Option.scala:271) at com.databricks.sql.transaction.tahoe.actions.AddFile.longTag(actions.scala:938) at com.databricks.sql.transaction.tahoe.actions.AddFile.insertionTime(actions.scala:917) at com.databricks.sql.transaction.tahoe.files.DelayedCommitProtocolEdge.$anonfun$updateInsertionTime$1(DelayedCommitProtocolEdge.scala:116) at com.databricks.sql.transaction.tahoe.files.DelayedCommitProtocolEdge.$anonfun$updateInsertionTime$1$adapted(DelayedCommitProtocolEdge.scala:116) at scala.collection.TraversableLike.$anonfun$map$1(TraversableLike.scala:286) at scala.collection.Iterator.foreach(Iterator.scala:943) at scala.collection.Iterator.foreach$(Iterator.scala:943) at scala.collection.AbstractIterator.foreach(Iterator.scala:1431) at scala.collection.IterableLike.foreach(IterableLike.scala:74) at scala.collection.IterableLike.foreach$(IterableLike.scala:73) at scala.collection.AbstractIterable.foreach(Iterable.scala:56) at scala.collection.TraversableLike.map(TraversableLike.scala:286) at scala.collection.TraversableLike.map$(TraversableLike.scala:279) at scala.collection.AbstractTraversable.map(Traversable.scala:108) at com.databricks.sql.transaction.tahoe.files.DelayedCommitProtocolEdge.updateInsertionTime(DelayedCommitProtocolEdge.scala:116) at com.databricks.sql.transaction.tahoe.files.DelayedCommitProtocolEdge.commitJob(DelayedCommitProtocolEdge.scala:80) at org.apache.spark.sql.execution.datasources.FileFormatWriter$.$anonfun$writeAndCommit$3(FileFormatWriter.scala:400) at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23) at org.apache.spark.util.Utils$.timeTakenMs(Utils.scala:532) at org.apache.spark.sql.execution.datasources.FileFormatWriter$.writeAndCommit(FileFormatWriter.scala:400) at org.apache.spark.sql.execution.datasources.FileFormatWriter$.executeWrite(FileFormatWriter.scala:430) at org.apache.spark.sql.execution.datasources.FileFormatWriter$.$anonfun$write$1(FileFormatWriter.scala:300) at com.databricks.spark.util.FrameProfiler$.record(FrameProfiler.scala:94) at org.apache.spark.sql.execution.datasources.FileFormatWriter$.write(FileFormatWriter.scala:121) at com.databricks.sql.transaction.tahoe.commands.WriteIntoDeltaCommand.run(WriteIntoDeltaCommand.scala:121) at org.apache.spark.sql.execution.command.DataWritingCommandExec.$anonfun$sideEffectResult$5(commands.scala:137) at org.apache.spark.sql.execution.SparkPlan.runCommandWithAetherOff(SparkPlan.scala:180) at org.apache.spark.sql.execution.SparkPlan.runCommandInAetherOrSpark(SparkPlan.scala:191) at org.apache.spark.sql.execution.command.DataWritingCommandExec.$anonfun$sideEffectResult$4(commands.scala:137) at com.databricks.spark.util.FrameProfiler$.record(FrameProfiler.scala:94) at org.apache.spark.sql.execution.command.DataWritingCommandExec.sideEffectResult$lzycompute(commands.scala:133) at org.apache.spark.sql.execution.command.DataWritingCommandExec.sideEffectResult(commands.scala:132) at org.apache.spark.sql.execution.command.DataWritingCommandExec.$anonfun$doExecute$4(commands.scala:161) at com.databricks.spark.util.FrameProfiler$.record(FrameProfiler.scala:94) at org.apache.spark.sql.execution.command.DataWritingCommandExec.doExecute(commands.scala:161) at org.apache.spark.sql.execution.SparkPlan.$anonfun$execute$2(SparkPlan.scala:329) at com.databricks.spark.util.FrameProfiler$.record(FrameProfiler.scala:94) at org.apache.spark.sql.execution.SparkPlan.$anonfun$execute$1(SparkPlan.scala:329) at org.apache.spark.sql.execution.SparkPlan$.org$apache$spark$sql$execution$SparkPlan$$withExecuteQueryLogging(SparkPlan.scala:132) at org.apache.spark.sql.execution.SparkPlan.$anonfun$executeQuery$1(SparkPlan.scala:387) at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:165) at org.apache.spark.sql.execution.SparkPlan.executeQuery(SparkPlan.scala:383) at org.apache.spark.sql.execution.SparkPlan.execute(SparkPlan.scala:324) at org.apache.spark.sql.execution.adaptive.AdaptiveSparkPlanExec.$anonfun$doExecute$1(AdaptiveSparkPlanExec.scala:864) at
Re: [PR] Bump notebook from 6.0.0 to 6.4.12 in /python [sedona]
jiayuasu merged PR #634: URL: https://github.com/apache/sedona/pull/634 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [DOCS] add glue tutorial [sedona]
james-willis opened a new pull request, #1453: URL: https://github.com/apache/sedona/pull/1453 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. I am addressing this github issue: https://github.com/apache/sedona/issues/1399 ## What changes were proposed in this PR? This PR proposes adding an AWS Glue setup tutorial to the Sedona documentation website ## How was this patch tested? * built and ran the docs site locally.  * followed the tutorial using the wherobots jars in an account other than the one hosting the jars bucket. ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump notebook from 6.0.0 to 6.4.12 in /python [sedona]
dependabot[bot] opened a new pull request, #634: URL: https://github.com/apache/sedona/pull/634 Bumps [notebook](http://jupyter.org) from 6.0.0 to 6.4.12. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/incubator-sedona/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump jupyterlab from 3.6.4 to 3.6.7 in /binder [sedona]
jiayuasu merged PR #1424: URL: https://github.com/apache/sedona/pull/1424 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-579] Add ST_AsHEXEWKB [sedona]
jiayuasu merged PR #1452: URL: https://github.com/apache/sedona/pull/1452 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump pypa/cibuildwheel from 2.16.5 to 2.18.1 [sedona]
jiayuasu merged PR #1447: URL: https://github.com/apache/sedona/pull/1447 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-578] Add ST_Points [sedona]
jiayuasu merged PR #1451: URL: https://github.com/apache/sedona/pull/1451 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-576] Add ST_HasZ [sedona]
jiayuasu merged PR #1450: URL: https://github.com/apache/sedona/pull/1450 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-579] Add ST_AsHEXEWKB [sedona]
jiayuasu opened a new pull request, #1452: URL: https://github.com/apache/sedona/pull/1452 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-579. The PR name follows the format `[SEDONA-579] my subject`. - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? Add ST_AsHEXEWKB ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-578] Add ST_Points [sedona]
jiayuasu opened a new pull request, #1451: URL: https://github.com/apache/sedona/pull/1451 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-578. The PR name follows the format `[SEDONA-578] my subject`. ## What changes were proposed in this PR? Add ST_Points ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-576] Add ST_HasZ [sedona]
jiayuasu opened a new pull request, #1450: URL: https://github.com/apache/sedona/pull/1450 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-576. The PR name follows the format `[SEDONA-576] my subject`. ## What changes were proposed in this PR? Add ST_HasZ ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump pandas from 1.5.3 to 2.2.2 in /docker/sedona-spark-jupyterlab [sedona]
jiayuasu closed pull request #1449: Bump pandas from 1.5.3 to 2.2.2 in /docker/sedona-spark-jupyterlab URL: https://github.com/apache/sedona/pull/1449 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump jupyterlab-widgets from 1.1.7 to 3.0.11 in /docker/sedona-spark-jupyterlab [sedona]
jiayuasu closed pull request #1448: Bump jupyterlab-widgets from 1.1.7 to 3.0.11 in /docker/sedona-spark-jupyterlab URL: https://github.com/apache/sedona/pull/1448 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump pandas from 1.5.3 to 2.2.2 in /docker/sedona-spark-jupyterlab [sedona]
dependabot[bot] opened a new pull request, #1449: URL: https://github.com/apache/sedona/pull/1449 Bumps [pandas](https://github.com/pandas-dev/pandas) from 1.5.3 to 2.2.2. Release notes Sourced from https://github.com/pandas-dev/pandas/releases;>pandas's releases. Pandas 2.2.2 We are pleased to announce the release of pandas 2.2.2. This release includes some new features, bug fixes, and performance improvements. We recommend that all users upgrade to this version. See the https://pandas.pydata.org/pandas-docs/version/2.2.2/whatsnew/v2.2.2.html;>full whatsnew for a list of all the changes. Pandas 2.2.2 supports Python 3.9 and higher. The release will be available on the defaults and conda-forge channels: conda install pandas Or via PyPI: python3 -m pip install --upgrade pandas Please report any issues with the release on the https://github.com/pandas-dev/pandas/issues;>pandas issue tracker. Thanks to all the contributors who made this release possible. Pandas 2.2.1 We are pleased to announce the release of pandas 2.2.1. This release includes some new features, bug fixes, and performance improvements. We recommend that all users upgrade to this version. See the https://pandas.pydata.org/pandas-docs/version/2.2.1/whatsnew/v2.2.1.html;>full whatsnew for a list of all the changes. Pandas 2.2.1 supports Python 3.9 and higher. The release will be available on the defaults and conda-forge channels: conda install pandas Or via PyPI: python3 -m pip install --upgrade pandas Please report any issues with the release on the https://github.com/pandas-dev/pandas/issues;>pandas issue tracker. Thanks to all the contributors who made this release possible. Pandas 2.2.0 We are pleased to announce the release of pandas 2.2.0. This release includes some new features, bug fixes, and performance improvements. We recommend that all users upgrade to this version. See the https://pandas.pydata.org/pandas-docs/version/2.2.0/whatsnew/v2.2.0.html;>full whatsnew for a list of all the changes. Pandas 2.2.0 supports Python 3.9 and higher. The release will be available on the defaults and conda-forge channels: conda install pandas Or via PyPI: ... (truncated) Commits https://github.com/pandas-dev/pandas/commit/d9cdd2ee5a58015ef6f4d15c7226110c9aab8140;>d9cdd2e RLS: 2.2.2 https://github.com/pandas-dev/pandas/commit/98aeac9b1b559178ef4f6a0a112a09b1741d11d1;>98aeac9 Backport PR https://redirect.github.com/pandas-dev/pandas/issues/58209;>#58209: CI: Pin blosc to fix pytables (https://redirect.github.com/pandas-dev/pandas/issues/58211;>#58211) https://github.com/pandas-dev/pandas/commit/5466f15462784eaa26e7ac43fc382f3802ab3ed1;>5466f15 Backport PR https://redirect.github.com/pandas-dev/pandas/issues/58202;>#58202: DOC/TST: Document numpy 2.0 support and add tests… (https://redirect.github.com/pandas-dev/pandas/issues/58208;>#58208) https://github.com/pandas-dev/pandas/commit/45b0b32af03e65f8d9547c127f8694fb7c3e994f;>45b0b32 Backport PR https://redirect.github.com/pandas-dev/pandas/issues/58203;>#58203 on branch 2.2.x (DOC: Add release date/contributors for 2 https://github.com/pandas-dev/pandas/commit/c7ec5663b3a5f041d7e8c93fa3d75a1314477e27;>c7ec566 Backport PR https://redirect.github.com/pandas-dev/pandas/issues/58087;>#58087 on branch 2.2.x (BLD: Build wheels using numpy 2.0rc1) (https://redirect.github.com/pandas-dev/pandas/issues/5;>#5... https://github.com/pandas-dev/pandas/commit/691fc88fbd7b570017bbc05fa77754b24c1fa997;>691fc88 Backport PR https://redirect.github.com/pandas-dev/pandas/issues/58181;>#58181 on branch 2.2.x (CI: correct error msg in test_view_index)... https://github.com/pandas-dev/pandas/commit/a947587c8ad419e9cf8f6cce1fd5ad80c32d759f;>a947587 Backport PR https://redirect.github.com/pandas-dev/pandas/issues/58138;>#58138 on branch 2.2.x (BLD: Fix nightlies not building) (https://redirect.github.com/pandas-dev/pandas/issues/58140;>#58140) https://github.com/pandas-dev/pandas/commit/b56842d93dc76dc2a83b7ab640af6a419697decb;>b56842d Backport PR https://redirect.github.com/pandas-dev/pandas/issues/58100;>#58100 on branch 2.2.x (MNT: fix compatibility with beautifulsoup... https://github.com/pandas-dev/pandas/commit/0f83d50c477f8aafb61a3db1d310d0b5fd261adc;>0f83d50 Revert BLD: Pin numpy on 2.2.x (https://redirect.github.com/pandas-dev/pandas/issues/58093;>#58093) https://github.com/pandas-dev/pandas/commit/e9b81ee3ecca2720f59e21091528e1e1e7eafe9a;>e9b81ee Backport PR https://redirect.github.com/pandas-dev/pandas/issues/58126;>#58126: BLD: Build wheels with numpy 2.0rc1 (https://redirect.github.com/pandas-dev/pandas/issues/58127;>#58127) Additional commits viewable in https://github.com/pandas-dev/pandas/compare/v1.5.3...v2.2.2;>compare view [![Dependabot compatibility
[PR] Bump jupyterlab-widgets from 1.1.7 to 3.0.11 in /docker/sedona-spark-jupyterlab [sedona]
dependabot[bot] opened a new pull request, #1448: URL: https://github.com/apache/sedona/pull/1448 Bumps [jupyterlab-widgets](https://github.com/jupyter-widgets/ipywidgets) from 1.1.7 to 3.0.11. Commits https://github.com/jupyter-widgets/ipywidgets/commit/8f909606fc5e5875a2ab27ec8c4b48ac5c0a77f9;>8f90960 Publish npm packages https://github.com/jupyter-widgets/ipywidgets/commit/d6171602a42a8381f749de1dcd49a00d9a4a83a7;>d617160 Merge pull request https://redirect.github.com/jupyter-widgets/ipywidgets/issues/1813;>#1813 from jasongrout/update4 https://github.com/jupyter-widgets/ipywidgets/commit/6fd2b573c9bf11f5df67fbf7470ba9be5cad2819;>6fd2b57 Update to jlab 0.29. https://github.com/jupyter-widgets/ipywidgets/commit/6d610065a4a7e74c3a0571b99e10ced3c02205c2;>6d61006 Merge pull request https://redirect.github.com/jupyter-widgets/ipywidgets/issues/1807;>#1807 from orpheus92/patch-1 https://github.com/jupyter-widgets/ipywidgets/commit/5b71b39c1476f54d69f7f782424831eb0f4619f8;>5b71b39 Add Di Wang to mailmap https://github.com/jupyter-widgets/ipywidgets/commit/653327ef6defd3e2b9dcaef490855198500c8491;>653327e Update README.md https://github.com/jupyter-widgets/ipywidgets/commit/1eee3c60418c834df06f87c0e2290088d2cc4cfd;>1eee3c6 Publish npm packages https://github.com/jupyter-widgets/ipywidgets/commit/f4a61ad2e45a588383a97a61799e789b5e8c349f;>f4a61ad Merge pull request https://redirect.github.com/jupyter-widgets/ipywidgets/issues/1805;>#1805 from jasongrout/slim https://github.com/jupyter-widgets/ipywidgets/commit/683166b8db4fb8f49809ff4a4df3d865a7da1767;>683166b Simplify the controls utils module by reusing functions from the base utils m... https://github.com/jupyter-widgets/ipywidgets/commit/8fa2eec676f7b69c41b9a085332f1603e992dba1;>8fa2eec Use phosphorjs to generate the UUID instead of our own code. Additional commits viewable in https://github.com/jupyter-widgets/ipywidgets/compare/@jupyter-widgets/base@1.1.7...@jupyter-widgets/notebook-manager@3.0.11;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump pypa/cibuildwheel from 2.16.5 to 2.18.1 [sedona]
dependabot[bot] opened a new pull request, #1447: URL: https://github.com/apache/sedona/pull/1447 Bumps [pypa/cibuildwheel](https://github.com/pypa/cibuildwheel) from 2.16.5 to 2.18.1. Release notes Sourced from https://github.com/pypa/cibuildwheel/releases;>pypa/cibuildwheel's releases. v2.18.1 Add free-threaded Linux and Windows builds for 3.13. New identifiers cp313t-*, new option CIBW_FREE_THREADED_SUPPORT/tool.cibuildwheel.free-threaded-support required to opt-in. https://cibuildwheel.pypa.io/en/stable/options/#free-threaded-support;>See the docs for more information. (https://redirect.github.com/pypa/cibuildwheel/issues/1831;>#1831) ✨ The container-engine is now a build (non-global) option. (https://redirect.github.com/pypa/cibuildwheel/issues/1792;>#1792) The build backend for cibuildwheel is now hatchling. (https://redirect.github.com/pypa/cibuildwheel/issues/1297;>#1297) Significant improvements and modernization to our noxfile. (https://redirect.github.com/pypa/cibuildwheel/issues/1823;>#1823) Use pylint's new GitHub Actions reporter instead of a custom matcher. (https://redirect.github.com/pypa/cibuildwheel/issues/1823;>#1823) Unpin virtualenv updates for Python 3.7+ (https://redirect.github.com/pypa/cibuildwheel/issues/1830;>#1830) Fix running linux tests from Windows or macOS ARM. (https://redirect.github.com/pypa/cibuildwheel/issues/1788;>#1788) Fix our documentation build. (https://redirect.github.com/pypa/cibuildwheel/issues/1821;>#1821) v2.18.0 ✨ Adds CPython 3.13 support, under the prerelease flag https://cibuildwheel.pypa.io/en/stable/options/#prerelease-pythons;>CIBW_PRERELEASE_PYTHONS. This version of cibuildwheel uses 3.13.0b1. Free-threading mode is not available yet (https://redirect.github.com/pypa/cibuildwheel/issues/1657;>#1657), waiting on official binaries (planned for beta 2) and pip support. While CPython is in beta, the ABI can change, so your wheels might not be compatible with the final release. For this reason, we don't recommend distributing wheels until RC1, at which point 3.13 will be available in cibuildwheel without the flag. (https://redirect.github.com/pypa/cibuildwheel/issues/1815;>#1815) ✨ Musllinux now defaults to musllinux_1_2. You can set the older musllinux_1_1 via config if needed. (https://redirect.github.com/pypa/cibuildwheel/issues/1817;>#1817) No longer pre-seed setuptools/wheel in virtual environments (https://redirect.github.com/pypa/cibuildwheel/issues/1819;>#1819) Respect the constraints file when building with pip, matching build (https://redirect.github.com/pypa/cibuildwheel/issues/1818;>#1818) Use uv to compile our pinned dependencies, 10x faster and doesn't require special setup (https://redirect.github.com/pypa/cibuildwheel/issues/1778;>#1778) Fix an issue with the schema (https://redirect.github.com/pypa/cibuildwheel/issues/1788;>#1788) Document the new delocate error checking macOS versions (https://redirect.github.com/pypa/cibuildwheel/issues/1766;>#1766) Document Rust builds (https://redirect.github.com/pypa/cibuildwheel/issues/1816;>#1816) Speed up our readthedocs builds with uv, 26 seconds - 6 seconds to install dependencies (https://redirect.github.com/pypa/cibuildwheel/issues/1816;>#1816) v2.17.0 Adds the ability to inherit configuration in TOML overrides. This makes certain configurations much simpler. If you're overriding an option like before-build or environment, and you just want to add an extra command or environment variable, you can just append (or prepend) to the previous config. See https://cibuildwheel.pypa.io/en/stable/options/#inherit;>the docs for more information. (https://redirect.github.com/pypa/cibuildwheel/issues/1730;>#1730) Adds official support for native arm64 macOS GitHub runners. To use them, just specify macos-14 as an os of your job in your workflow file. You can also keep macos-13 in your build matrix to build x86_64. Check out the new https://cibuildwheel.pypa.io/en/stable/setup/#github-actions;>GitHub Actions example config. ✨ You no longer need to specify --platform to run cibuildwheel locally! Instead it will detect your platform automatically. This was a safety feature, no longer necessary. (https://redirect.github.com/pypa/cibuildwheel/issues/1727;>#1727) Removed setuptools and wheel pinned versions. This only affects old-style projects without a pyproject.toml, projects with pyproject.toml are already getting fresh versions of their build-system.requires installed into an isolated environment. (https://redirect.github.com/pypa/cibuildwheel/issues/1725;>#1725) Improve how the GitHub Action passes arguments (https://redirect.github.com/pypa/cibuildwheel/issues/1757;>#1757) Remove a system-wide install of pipx in the GitHub Action (https://redirect.github.com/pypa/cibuildwheel/issues/1745;>#1745) No longer will
[I] Flink Sedona,geomTbl.execute().print() happen error: [sedona]
Leopold-Xu opened a new issue, #1446:
URL: https://github.com/apache/sedona/issues/1446
## Expected behavior
i hope this proble solved,print result like this,Thanks!:
++++
| op | geom_polygon | name_polygon |
++++
| +I | POLYGON ((-0.5 -0.5, -0.5 0... | polygon0 |
| +I | POLYGON ((0.5 0.5, 0.5 1.5,... | polygon1 |
| +I | POLYGON ((1.5 1.5, 1.5 2.5,... | polygon2 |
| +I | POLYGON ((2.5 2.5, 2.5 3.5,... | polygon3 |
| +I | POLYGON ((3.5 3.5, 3.5 4.5,... | polygon4 |
| +I | POLYGON ((4.5 4.5, 4.5 5.5,... | polygon5 |
| +I | POLYGON ((5.5 5.5, 5.5 6.5,... | polygon6 |
| +I | POLYGON ((6.5 6.5, 6.5 7.5,... | polygon7 |
| +I | POLYGON ((7.5 7.5, 7.5 8.5,... | polygon8 |
| +I | POLYGON ((8.5 8.5, 8.5 9.5,... | polygon9 |
++++
10 rows in set
## Actual behavior
**this is java code:**
```
public void test() {
StreamExecutionEnvironment env =
StreamExecutionEnvironment.createRemoteEnvironment("192.168.0.102",8081,
"C:/Users/15218/Desktop/quickstart/jars/flink-connector-jdbc-3.1.2-1.18.jar",
"C:/Users/15218/Desktop/quickstart/jars/postgresql-42.7.3.jar"
);
EnvironmentSettings settings =
EnvironmentSettings.newInstance().inStreamingMode().build();
StreamTableEnvironment tableEnv = StreamTableEnvironment.create(env,
settings);
StreamTableEnvironment send = SedonaContext.create(env, tableEnv);
String sourceSql = "SELECT id,age,wkt FROM test";
String postgresSinkDDL = "CREATE TABLE source_table (\n" +
" id INT,\n" +
" age INT,\n" +
" wkt STRING,\n" +
" PRIMARY KEY (id) NOT ENFORCED\n" +
") WITH (\n" +
" 'connector' = 'jdbc',\n" +
" 'url' = 'jdbc:postgresql://192.168.0.102:5432/jjlbsdb',\n"+
" 'table-name' = 'test',\n" +
" 'driver' = 'org.postgresql.Driver',\n" +
" 'username' = 'postgres',\n" +
" 'password' ='postgres'\n" +
")";
tableEnv.executeSql(postgresSinkDDL);
Table result = tableEnv.sqlQuery("select id,age,wkt from
source_table");
result.execute().print();
send.createTemporaryView("myTable", result);
Table geomTbl = send.sqlQuery("SELECT id,age,ST_GeomFromWKT(wkt) as
point FROM myTable");
geomTbl.execute().print();
}
```
## Steps to reproduce the problem
**when program execute last line "geomTbl.execute().print() ' happened
ereor:`**
`Caused by: org.apache.flink.util.FlinkRuntimeException: java.io.EOFException
at
org.apache.flink.table.data.binary.BinaryRawValueData.toObject(BinaryRawValueData.java:66)
~[flink-table-common-1.19.0.jar:1.19.0]
at GeneratedCastExecutor$0.cast(Unknown Source) ~[na:na]
at
org.apache.flink.table.planner.functions.casting.RowDataToStringConverterImpl.lambda$init$0(RowDataToStringConverterImpl.java:81)
~[flink-table-planner_2.12-1.19.0.jar:1.19.0]
at
org.apache.flink.table.planner.functions.casting.RowDataToStringConverterImpl.convert(RowDataToStringConverterImpl.java:94)
~[flink-table-planner_2.12-1.19.0.jar:1.19.0]
at
org.apache.flink.table.utils.print.TableauStyle.rowFieldsToString(TableauStyle.java:174)
~[flink-table-common-1.19.0.jar:1.19.0]
at
org.apache.flink.table.utils.print.TableauStyle.print(TableauStyle.java:148)
~[flink-table-common-1.19.0.jar:1.19.0]
at
org.apache.flink.table.api.internal.TableResultImpl.print(TableResultImpl.java:163)
~[flink-table-api-java-1.19.0.jar:1.19.0]
at
com.jjgis.sedonaquickstart.demos.web.BasicController.test(BasicController.java:68)
~[classes/:na]
at
com.jjgis.sedonaquickstart.demos.web.BasicController.run(BasicController.java:75)
~[classes/:na]
at
org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:773)
[spring-boot-2.6.13.jar:2.6.13]
... 5 common frames omitted`
## Settings
Sedona version = 1.6.0
Apache Spark version = ?
Apache Flink version = 1.19
API type = Java
Scala version = 2.12,
JRE version = 1.8
Python version = ?
Environment = Standalone, AWS EC2, EMR, Azure, Databricks?
--
This is an automated message from the Apache Git Service.
To respond to the message,
Re: [PR] [SEDONA-581] SedonaKepler fails to reload if a raster column exists [sedona]
jiayuasu merged PR #1445: URL: https://github.com/apache/sedona/pull/1445 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-581] SedonaKepler fails to reload if a raster column exists [sedona]
furqaankhan opened a new pull request, #1445: URL: https://github.com/apache/sedona/pull/1445 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-581. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? - Drop the raster column if it exists to prevent serialization errors with Kepler. ## How was this patch tested? - Add unit tests ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-580] New instances of RasterUDT object should equal to the RasterUDT case object [sedona]
Kontinuation merged PR #1444: URL: https://github.com/apache/sedona/pull/1444 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-580] New instances of RasterUDT object should equal to the RasterUDT case object [sedona]
Kontinuation opened a new pull request, #1444: URL: https://github.com/apache/sedona/pull/1444 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-580. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? * Implement `equals` and `hashCode` for RasterUDT to ensure that newly created instances of RasterUDT class are equal to the RasterUDT case class. * Fix `hashCode` for GeometryUDT ## How was this patch tested? Add new tests and manually test on external systems. ## Did this PR include necessary documentation updates? - No, this PR does not affect any public API so no need to change the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-575] [SEDONA-577] Add ST_LineFromWKB, ST_GeometryFromText [sedona]
jiayuasu merged PR #1443: URL: https://github.com/apache/sedona/pull/1443 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-575] [SEDONA-577] Add ST_LineFromWKB, ST_GeometryFromText [sedona]
jiayuasu opened a new pull request, #1443: URL: https://github.com/apache/sedona/pull/1443 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-575. The PR name follows the format `[SEDONA-575] my subject`. ## What changes were proposed in this PR? * Add ST_LineFromWKB * Add ST_GeometryFromText ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-571][SEDONA-574] Add ST_MMin, ST_MMax [sedona]
jiayuasu merged PR #1442: URL: https://github.com/apache/sedona/pull/1442 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-571][SEDONA-574] Add ST_MMin, ST_MMax [sedona]
jiayuasu opened a new pull request, #1442: URL: https://github.com/apache/sedona/pull/1442 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? * Add ST_MMin * Add ST_MMax ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-573] Add ST_HasM [sedona]
jiayuasu merged PR #1441: URL: https://github.com/apache/sedona/pull/1441 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-569][SEDONA-570][SEDONA-572] Add ST_PointZM, ST_PointM, ST_PointFromWKB [sedona]
jiayuasu merged PR #1440: URL: https://github.com/apache/sedona/pull/1440 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-573] Add ST_HasM [sedona]
jiayuasu opened a new pull request, #1441: URL: https://github.com/apache/sedona/pull/1441 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-573. The PR name follows the format `[SEDONA-573] my subject`. ## What changes were proposed in this PR? Add ST_HasM ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-569][SEDONA-570][SEDONA-572] Add ST_PointZM, ST_PointM, ST_PointFromWKB [sedona]
jiayuasu opened a new pull request, #1440: URL: https://github.com/apache/sedona/pull/1440 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-XXX. The PR name follows the format `[SEDONA-XXX] my subject`. ## What changes were proposed in this PR? * Added ST_PointZM * Added ST_PointM * Added ST_PointFromWKB ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-559] Make the flink example work [sedona]
jiayuasu merged PR #1420: URL: https://github.com/apache/sedona/pull/1420 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [I] ST_Snap example code does not work [sedona]
jiayuasu closed issue #1438: ST_Snap example code does not work URL: https://github.com/apache/sedona/issues/1438 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [DOCS] Fix ST_Snap Example [sedona]
jiayuasu merged PR #1439: URL: https://github.com/apache/sedona/pull/1439 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [DOCS] Fix ST_Snap Example [sedona]
furqaankhan opened a new pull request, #1439: URL: https://github.com/apache/sedona/pull/1439 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - No, this is a documentation update. The PR name follows the format `[DOCS] my subject`. ## What changes were proposed in this PR? - Fix ST_Snap example ## How was this patch tested? ## Did this PR include necessary documentation updates? - Yes, I have updated the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-566] Add ST_TriangulatePolygon [sedona]
jiayuasu merged PR #1436: URL: https://github.com/apache/sedona/pull/1436 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-567] Add ST_M [sedona]
jiayuasu merged PR #1437: URL: https://github.com/apache/sedona/pull/1437 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-565] Add ST_ForceRHR [sedona]
jiayuasu merged PR #1435: URL: https://github.com/apache/sedona/pull/1435 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-564] Add ST_NumInteriorRing [sedona]
jiayuasu merged PR #1434: URL: https://github.com/apache/sedona/pull/1434 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [SEDONA-563] Add ST_GeomFromEWKB [sedona]
jiayuasu merged PR #1433: URL: https://github.com/apache/sedona/pull/1433 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-567] Add ST_M [sedona]
jiayuasu opened a new pull request, #1437: URL: https://github.com/apache/sedona/pull/1437 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-567. The PR name follows the format `[SEDONA-567] my subject`. ## What changes were proposed in this PR? Add ST_M ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-566] Add ST_TriangulatePolygon [sedona]
jiayuasu opened a new pull request, #1436: URL: https://github.com/apache/sedona/pull/1436 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-566. The PR name follows the format `[SEDONA-566] my subject`. ## What changes were proposed in this PR? Add ST_TriangulatePolygon ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-565] Add ST_ForceRHR [sedona]
jiayuasu opened a new pull request, #1435: URL: https://github.com/apache/sedona/pull/1435 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-565. The PR name follows the format `[SEDONA-565] my subject`. ## What changes were proposed in this PR? Add ST_ForceRHR ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] [SEDONA-564] Add ST_NumInteriorRing [sedona]
jiayuasu opened a new pull request, #1434: URL: https://github.com/apache/sedona/pull/1434 ## Did you read the Contributor Guide? - Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest-snapshot/community/develop/) ## Is this PR related to a JIRA ticket? - Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-564. The PR name follows the format `[SEDONA-564] my subject`. ## What changes were proposed in this PR? Add ST_NumInteriorRing ## How was this patch tested? Passed local tests ## Did this PR include necessary documentation updates? - Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in `vX.Y.Z` format. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
