locationtech / locationtech/geomesa
Dwithin - evaluate distanceDegrees to ensure accurate dwithin queries
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Dwithin - evaluate distanceDegrees to ensure accurate dwithin queries
In the trino datastore work, we came up with a different approach to generating dwithin bounding boxes for an initial filter pass - distanceDegrees may exhibit an error in that the longest part of the circle is actually polewards of due east. we should evaluate and consolidate the dwithin handling.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-3592
Key: GEOMESA-3592
Type: Bug
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Wed, 8 Jul 2026 10:01:30 -0400
Updated: Wed, 8 Jul 2026 10:01:32 -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 locating the Trino datastore work and the existing dwithin handling, then trace how distanceDegrees is used to generate bounding boxes for the initial filter pass. Compare the approaches and determine the expected behavior near the poles; done means dwithin bounding boxes are accurate and the handling is consolidated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100