locationtech / locationtech/geomesa
Spark - geometry z and m dimensions are dropped
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Spark - geometry z and m dimensions are dropped
Per a user: You're internally encoding using WKB, which, apparently, does not encode the z (or m) of a coordinate.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2592
Key: GEOMESA-2592
Type: Bug
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Wed, 27 Mar 2019 08:04:56 -0400
Updated: Wed, 27 Mar 2019 08:07:34 -0400
Affects Version(s): 2.0.0, 2.1.0, 2.0.1, 2.0.2, 2.2.0, 2.1.1, 2.1.2, 2.2.1, 2.1.3
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 by locating the Spark geometry serialization path that uses WKB, then reproduce the loss of Z and M dimensions with a focused test. Done means preserving both dimensions through the affected Spark read/write flow and adding regression coverage; the issue names no files or existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala, spark
- Domain
- data, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100