2.0.4 starting/ending point too far from nearest road

[Jack Burke]

Is anyone else having problems with starting or ending point too far from nearest road messages in the 2.0.4 release version?

I'm getting an awful lot of those, especially on long trips. They occur even wheni just select a road as my destination.

-jack

[Max Erickson]

Are your maps up to date? For a destination 1/2 mile from a road, I do not get the message. If I select a destination that is outside of the maps I have downloaded, I get the destination too far from road message (with the notifications endlessly looping in turn with a java exception).


Max

[Randall Mason]

I've also had a few of these.  Long trips that cross boundaries of a few different maps.  I haven't experimented much, but one time I open the program it works, then I try to do the same route again, and it says my destination or way-point is too far from the nearest road, so it's not consistent for me.  Even with the same maps loaded and the same way-points.

[Χάρης Καραχριστιανίδης]

I had also this problem, when it starts the only solution for me is to uninstall and re-install the program...

[Jim Barton]

Routing from home to 9.7 miles away, where home is 10 yards off a road gave this problem. 

[Harry van der Wolf]

Same for me. My house address is 12 meters from road based on the address data. It doesn't work anymore.

What's more: with roads-only maps it gives an application error.

Harry

--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Χάρης Καραχριστιανίδης]

What do you do when this happens? How do you go out of this situation? The only way I found is uninstall and re-install Osmand. Is there a simpler solution?
Thank you!

[Harry van der Wolf]

The problem as it seems is that some favorites are based on addresses and are therefore next to the road instead of on the road. AFAIK that's also causing the error with roads-only maps as roads-only maps only know roads and absolutely nothing more. 

We had this bug several times before where the distance between a routable road and a favorite or POI was too big. There is some variable that determines which distance is allowed.

My work-around though is that I check one of my points and simply remove it and replace it with a point on the road.

Harry 

2015-05-19 6:35 GMT+02:00 Χάρης Καραχριστιανίδης <hari...@gmail.com>:

What do you do when this happens? How do you go out of this situation? The only way I found is uninstall and re-install Osmand. Is there a simpler solution?
Thank you!

--

[Randall Mason]

On Tue, May 19, 2015 at 10:43 AM, Harry van der Wolf <hvd...@gmail.com> wrote:

My work-around though is that I check one of my points and simply remove it and replace it with a point on the road.

This doesn't seem to be the same problem that I had, where it worked one time, I restarted the navigation with the same points, and it didn't work the second time.  Exact same maps and points.

Randall Mason
ran...@mason.ch

[Norbert]

I experienced this problem during my holiday on Gran Canaria often with v2.0.4. Nevertheless route calulcation has started...

[Jack Burke]

Harry, I've never downloaded the roads-only maps. Also, my start and end points are favorites that worked well with the 1.9.x releases.

In github, one person pointed out that it might have something to do with a route that uses multiple map files. I tested this on a trip from South Florida to North Georgia, about 475 miles, that I've made many times with the 1.9 releases. With just my current location as the start point and my apartment as the end point, I got the error. When I added waypoints just on either side of the Georgia/Florida border, the error went away and route calculation succeeded.

-jack

[Eric]

On Wednesday, 20 May 2015 19:50:38 UTC+2, Jack Burke wrote:

In github, one person pointed out that it might have something to do with a route that uses multiple map files.

This may also be the reason I have this issue.
I've navigated from The Netherlands to Germany. It's just a 80 minute trip (mostly on the highway). OSMAnd is probably using different maps that have some overlapping regions: road-only Netherlands, complete Venlo (city in the Netherlands), road-only West-Germany and complete Duesseldorf (city in Germany).

I've read on this forum that the old version of OSMAnd had to render the map and calculate the route many times when multiple maps have overlapping regions... but it worked correct, it just took more time.

[Jack Burke]

I have to make the observation that I just tried generating a route for one of my usual long (almost 500 mile) road trips using nightly build 2.1.0 #7394D, and it is markedly improved.

I still get the "too far" message, but it does go ahead and calculate a good route, and does so fairly fast, even without waypoints.

--jack

[Jim Barton]

I never had this in 1.9 or earlier.  I do not have any roads only maps.  My route is only 9.7 miles and is all well within the one map. I was routing from a favourite, which I've used before. It didn't calculate  a route at all.

[Jack Burke]

Jim, which build/release version are you using?

[Harry van der Wolf]

If it happens between several maps then it might be a version question.

Does it happen for you if all maps are from the same date (or at least same map run)?

Harry

2015-05-24 20:57 GMT+02:00 Jack Burke <burk...@gmail.com>:

Jim, which build/release version are you using?

[Jim Barton]

2.0.4 as the title of the thread.

I have even re-set the sharing point to a nearby road junction, and it still says the starting point is to far from the nearest road.

On 24 May 2015 19:57, "Jack Burke" <burk...@gmail.com> wrote:

Jim, which build/release version are you using?

--
You received this message because you are subscribed to a topic in the Google Groups "Osmand" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osmand/v_2aUJK0nJ8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osmand+un...@googlegroups.com.

[Jim Barton]

Aargh. Auto xxxx correct. I meant to say set the starting point to a nearby road junction.