-
Notifications
You must be signed in to change notification settings - Fork 441
GEOMESA-3308 Fix DWithin filter to compute distance between points across the antimeridian #3028
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -41,14 +41,24 @@ object FastDWithin { | |
|
|
||
| override def evaluate(obj: AnyRef): Boolean = { | ||
| val geom = exp1.evaluate(obj).asInstanceOf[Geometry] | ||
| if (geom == null || envelope.distance(geom.getEnvelopeInternal) > maxDegrees) { false } else { | ||
|
|
||
| if (geom == null) { | ||
| false | ||
| } else { | ||
| val op = new DistanceOp(geometry, geom) | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The variable names |
||
| op.distance <= minDegrees || { | ||
| val Array(p1, p2) = op.nearestPoints() | ||
| val calculator = calculators.get | ||
| calculator.setStartingGeographicPoint(p1.x, p1.y) | ||
|
|
||
| calculator.setStartingGeographicPoint(p1.x - 360, p1.y) | ||
| calculator.setDestinationGeographicPoint(p2.x, p2.y) | ||
| calculator.getOrthodromicDistance <= meters | ||
| val dist1 = calculator.getOrthodromicDistance | ||
|
|
||
| calculator.setStartingGeographicPoint(p1.x + 360, p1.y) | ||
| calculator.setDestinationGeographicPoint(p2.x, p2.y) | ||
| val dist2 = calculator.getOrthodromicDistance | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. as another optimization here, we could return early if dist1 <= meters and not calculate dist2. but we also need to calculate dist0, which would be the unmodified point. I'm a little surprised none of the existing unit tests failed with this change :( before changing anything, could you add a test for
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I added a unit test (db811e3), but it passes, which I'm not sure is the intended behavior. However, I think the calculator computes the shortest distance between two points on the Earth's surface, so it's likely that it already accounts for the anti-meridian wrapping. |
||
|
|
||
| Math.min(dist1, dist2) <= meters | ||
| } | ||
| } | ||
| } | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.