Beeline always 20m wrong?

Comments

11 comments

  • Gregor Erdmann

    I got my beeline moto today, and had a test in the car. I agree with the above post.

    I think that there are two issues going on here. 

    1) There is some lag, so that when I reach the corner it shows 40m to go.

    2) I think the beeline is measuring distance to the corner based on the apex of that corner. So if I come to a stop at the corner it shows that I have around 15m to go (depends on the size of the intersection and whether its a left or right turn)

     

    As a quick fix, I think you can try to calculate distance to start of the turn - maybe subtract a fixed distance. A future enhancement might be to subtract a variable based on left or right turns, depending on which side of the road we drive on. Or perhaps the map already can return start of turn. 

    Second improvement would be to cater for lag based on vehicle speed. 

    Maybe beeline worked fine for cycling speeds, but on a motorcycle we will often overshoot intersections. 

    0
    Comment actions Permalink
  • albert de la varga

    I received my moto yesterday and I've tested it by going to work and back home.

    In my case, it marks the intersection before, not after and changes the view before turning.


    Edit: The first day it seemed to me that it matked the intersections before, but when using it more, it signals the turn after it, always.

     

    0
    Comment actions Permalink
  • melensdad

    I also noticed the problem. Some intersections it was off by maybe 20 meters, but others by as far as 100 meters. And in every case I was signaled to turn AFTER the intersection. To make matters more confusing many times it indicates to turn 1/2 way between 2 different intersections!

    0
    Comment actions Permalink
  • Scott Mountifield

    Agreed... tested mine just this weekend. I have mine set to miles and feet (we're weird in the UK) and I noticed that whilst the arrow always pointed at the correct time, the distance countdown was usually 100ft out... If I stopped at all it would eventually countdown to around 30ft but but never to zero unless I went beyond it.

    Not having a visual map on the device, this is an essential element to get right... No point in having a navigation tool that can't navigate you correctly... #needsimprovement 

    0
    Comment actions Permalink
  • Stuart Blain

    I was about to post exactly this comment, word-for-word!

    I have just started using my Beeline, and every junction I pass through tells me it's 30-40m away as I'm in it....I assume it's GPS inaccuracy?  This is not too much of a problem on open roads, but very much a problem in built-up areas, where the junctions can be close together...

    I have to say I'm delighted with the device, it's a brilliant bit of kit, but this issue needs to be resolved.

    Also, I notice that when stopped at traffic lights, it will often "lose" itself, and start the whirly circle thing....

    0
    Comment actions Permalink
  • Scott Mountifield

    @Stuart Blain and all others, I have sent an email to Beeline about this and a couple of other issues related to trying to understand how the device is getting it's mapping (GPS or mobile data fro the phone)... I'll update here with any response...

    1
    Comment actions Permalink
  • Stuart Blain

    Excellent, thanks Scott....I'd be interested in the mapping source, mine doesn't know about the first roundabout I meet...

    0
    Comment actions Permalink
  • melensdad

    I use FURKOT to do the mapping.  FURKOT allow you to pick the exact roads you want to be on, or it can route you automatically, it can be set for avoiding some types of roads, etc.  

    Once you have your route you simply save it as a .GPX file.  

    Currently BEELINE only accepts routes with 25 waypoints or less.  That is apparently being fixed.  

    Upload the .GPX file and then the fun begins.  In my case it signals turns into farm fields, after the intersection, in between 2 intersections, etc.  

    0
    Comment actions Permalink
  • Scott Mountifield

    The waypoint thing is an issue and someone did post on another thread that this was being fixed (or at least being looked into). I use RidewithGPS for my bicycle route planning so if the way points are to be fixed then I will just use that and import the GPX...

     

    0
    Comment actions Permalink
  • Stuart Blain

    I've just spotted the Google emblem on the app map...very odd, as Google Maps has that roundabout, Beeline ignores it...

    I'm going to have to try it out on completely unfamiliar roads to see how I get on, remove the comfort of knowing what it's telling me to do...

    0
    Comment actions Permalink
  • Scott Mountifield

    Exactly the same Stuart... I went over a missed roundabout and it was focused on the roundabout 2 miles down the road... Checked the route on my phone afterwards and the roundabout was clearly there...

    As mentioned, I will offer up any feedback around distance lag and inaccuracy/GPS and phone signal/missing turns and junctions...

    0
    Comment actions Permalink

Please sign in to leave a comment.