locationtech / locationtech/geomesa
Allow for use of JTS functions in GeoMesa PySpark without needing a GeoMesa DataStore
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Allow for use of JTS functions in GeoMesa PySpark without needing a GeoMesa DataStore
To address this, we either need to document a correct approach or add the capability to GeoMesa's PySpark support.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2452
Key: GEOMESA-2452
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: James Hughes
Created: Thu, 1 Nov 2018 14:01:52 -0400
Updated: Thu, 8 Nov 2018 17:51:33 -0500
Comments:
557058:48912df4-0004-4f90-9915-db26684ec006 (Mon, 5 Nov 2018 11:21:52 -0500):
In Scala, this would be done with SparkSession.withJts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with GeoMesa's PySpark support and compare it with the Scala SparkSession.withJts approach mentioned in the comment. Determine whether a correct documented approach already exists or whether capability must be added; done means PySpark users can use JTS functions without a GeoMesa DataStore.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, scala, spark
- Domain
- data-engineering, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100