GeofenceBreachAvoidance: Fixed vertical geofence #17566
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LorenzMeier
previously approved these changes
May 12, 2021
LorenzMeier
force-pushed
the
pr-fix_vertial_geofence
branch
from
1a0c30b to
b602a1d
Compare
|
Rebased |
sfuhrer
previously approved these changes
Jun 4, 2021
|
@LorenzMeier @dagar Could one of you please approve so that I can merge? |
LorenzMeier
previously approved these changes
Jun 4, 2021
… to fence not to be calculated Signed-off-by: RomanBapst <bapstroman@gmail.com>
RomanBapst
force-pushed
the
pr-fix_vertial_geofence
branch
from
b602a1d to
11de726
Compare
julianoes
approved these changes
Sep 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minimum vertical distance to geofence was never calculated. This made it very easy to breach the geofence.