Skip to content
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

Predictions occasionally very inaccurate #77

Open
Steppschuh opened this issue Jun 6, 2018 · 1 comment
Open

Predictions occasionally very inaccurate #77

Steppschuh opened this issue Jun 6, 2018 · 1 comment
Assignees
Labels
bug Unintended behaviour core lib Core Library location prediction Affects location prediction sample app Sample App
Milestone

Comments

@Steppschuh
Copy link
Contributor

May be caused by empty / null locations or a rendering bug. Anyway, it shouldn't happen.

screenshot_20180606-100800

@Steppschuh Steppschuh added bug Unintended behaviour core lib Core Library sample app Sample App labels Jun 6, 2018
@Steppschuh Steppschuh added this to the 1.0.0 milestone Jun 6, 2018
@Steppschuh Steppschuh added this to To Do in Java Core Library via automation Jun 6, 2018
@Steppschuh Steppschuh added the location prediction Affects location prediction label Oct 25, 2018
@Steppschuh
Copy link
Contributor Author

Probably caused by missing latitude or longitude in predicted locations. Rendering bug happens in BeaconMap:

    protected PointF getPointFromLocation(Location location) {
        if (location == null || !location.hasLatitudeAndLongitude()) {
            return new PointF(0, 0); // <--------
        }
        float x = canvasProjection.getXFromLocation(location);
        float y = canvasProjection.getYFromLocation(location);
        return new PointF(x, y);
    }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended behaviour core lib Core Library location prediction Affects location prediction sample app Sample App
Projects
Development

No branches or pull requests

2 participants