[geomesa-dev] [JIRA] (GEOMESA-2315) Map JTS to Shapely types for use wit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[geomesa-dev] [JIRA] (GEOMESA-2315) Map JTS to Shapely types for use with PySpark

From: "Tom Kunicki (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 9 Jul 2018 16:21:07 +0000 (UTC)
Auto-submitted: auto-generated
Delivered-to: geomesa-dev@xxxxxxxxxxxxxxxx
List-archive: <https://dev.locationtech.org/mhonarc/lists/geomesa-dev>
List-help: <mailto:geomesa-dev-request@locationtech.org?subject=help>
List-subscribe: <https://dev.locationtech.org/mailman/listinfo/geomesa-dev>, <mailto:geomesa-dev-request@locationtech.org?subject=subscribe>
List-unsubscribe: <https://dev.locationtech.org/mailman/options/geomesa-dev>, <mailto:geomesa-dev-request@locationtech.org?subject=unsubscribe>

Title: Message Title

Tom Kunicki created an issue

Issue Type:	Improvement
Assignee:	Unassigned
Created:	09/Jul/18 12:21 PM
Priority:	Major
Reporter:	Tom Kunicki

The current use of JTS JVM objects in PySpark via the Py4J bridge is problematic as the Py4J bridge is only available in the PySpark driver (and not executors). A more complete solution would be to map JTS (JVM) <-> Shapely (Python).

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS

This message was sent by Atlassian Jira

Prev by Date: [geomesa-dev] [JIRA] (GEOMESA-2314) Serialization - base geometry serialization on TWKB
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-2316) Kafka - Support non-points
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-2314) Serialization - base geometry serialization on TWKB
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-2316) Kafka - Support non-points
Index(es):
- Date
- Thread

Breadcrumbs