locationtech / locationtech/geomesa
Better handling for anti-meridian crossing geometries
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Better handling for anti-meridian crossing geometries
We currently use an index based on the geometry envelope. However, this doesn't work well for geometries that cross the anti-meridian, as they envelope spans the whole world. Possibly we need to split the geometry up?
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2323
Key: GEOMESA-2323
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Tue, 17 Jul 2018 09:19:36 -0400
Updated: Tue, 31 Jul 2018 13:53:56 -0400
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 tracing the geometry-envelope index used for spatial data and examine how anti-meridian-crossing geometries are represented. Compare the current whole-world envelope behavior with the proposed option of splitting the geometry. Done should include a defined handling strategy and verification that crossing geometries are indexed without spanning the entire world.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100