Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Zian Choy writes: > OsmAnd routes drivers going to buildings near freeways to use a freeway > offramp rather than the nearby street. It should prefer streets because it > is illegal to park a car on a freeway offramp. I think the real issue is that "compute car route to point" is really "comp

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Related: this issue on GitHub: https://github.com/osmandapp/Osmand/issues/1844 I tried to adept routing.xml to change this.  By allowing footways etc. in car-profile, but with a very low priority. You could try this routing.xml (place it in Osmand folder and restart OsmAnd) https://www.dropbo

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Related: this issue on GitHub:: https://github.com/osmandapp/Osmand/issues/1844 I tried to adept routing.xml to change this. By allowing footways etc. in car-profile, but with a very low priority. You could try this routing.xml https://www.dropbox.com/s/ue8hte6u2vo8hax/routing.xml?dl=0https:/

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

if one is unfamiliar with the area, the brain must be ON permanently, :) and the map review and adjustment the destination is highly recommended. Dne 06/10/2016 v 09:14 Jack Burke napsal(a): > Yes, the user's brain should be engaged, but if one is unfamiliar with the > area, it isn't unreasonab

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Yes, the user's brain should be engaged, but if one is unfamiliar with the area, it isn't unreasonable to follow the router's directions. If the router instructs you to "turn right in 500 feet" and you're driving along a cliff that extends for a few miles, that's one thing. If you're driving o

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

I usually work this way ( Not limited to OSMAnd ) I search for start address, display it on map and choose the point. I search for destination address, display it on map and choose the point. Dne 06/10/2016 v 08:47 Marko Mäkelä napsal(a): > Right, the user brain should be engaged. I think that one

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

I suppose many regions have troubles to have a house numbers in OSM at all.. Dne 06/10/2016 v 08:47 Marko Mäkelä napsal(a): > Right, the user brain should be engaged. I think that one should > sometimes fine-adjust the location that you get from address search. > Do you want the goods delivery e

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Right, the user brain should be engaged. I think that one should sometimes fine-adjust the location that you get from address search. Do you want the goods delivery entrance, the mailbox, the main entrance, some minor entrance, some specific corner of a parking lot, a back yard, or what? These

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Dne 06/10/2016 v 06:52 Marko Mäkelä napsal(a): > On Wednesday, October 5, 2016 at 18:28:20 UTC+3 Poutnik wrote: > > I see it as logical that Avoid_unpaved avoids surface=gravel. > > For what it is worth, my entry to OSM was via mkgmap > , which translates maps in the

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

On Wednesday, October 5, 2016 at 18:28:20 UTC+3 Poutnik wrote: > > I see it as logical that Avoid_unpaved avoids surface=gravel. > For what it is worth, my entry to OSM was via mkgmap , which translates maps in the proprietary Garmin format. The Garmin routing engine s

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

I see it as logical that Avoid_unpaved avoids surface=gravel. On 10/05/2016 05:08 PM, Jack Burke wrote: And that road is being avoided because it's surface=gravel. And I'm the one who set that attribute, too. Go figure. -- You received this message because you are subscribed to the Google

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

And that road is being avoided because it's surface=gravel. And I'm the one who set that attribute, too. Go figure. --jack On Wednesday, October 5, 2016 at 9:25:20 AM UTC-4, Jack Burke wrote: > > Sorry for the super jumbo size font. Doing this from my phone. -- You received this message be

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Sorry for the super jumbo size font. Doing this from my phone. -- 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+unsubscr...@googlegroups.com. For more options,

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Jack. How does it react if you move the destination a few yards East out onto the street called "John."? -- 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

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

I suppose it may have rather something to do with the routing termination conditions. There is probably some distance threshold when destination is considered as reached, and the most close ending to the building is considered as best. I was evaluating my test car BRouter profile Car-test-Template

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

This looks like a hint. The neighborhood of destination may not be routable with Avoid unpaved. Dne 04/10/2016 v 21:52 Jack Burke napsal(a): > [...] Note that this only seems to happen for this destination with > Fuel-efficent and Avoid Unpaved Roads selected; deselecting those > routes properly.

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Maybe sometimes one just has to review the calculated route before embarking on it, and then use a bit of (...errr, sorry, cant think of suitable dimpolatic term) ... Discretion? -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from t

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Dne 03/10/2016 v 21:48 Toby Dickenson napsal(a): > "last mile" heheheh. If the route "finishes" at an onramp, you might > get locked into a detour of many tens of miles. > > Having said that, I've just tried navigating to some buildings (using > address search) which are closer to a motorway than a

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

"last mile" heheheh. If the route "finishes" at an onramp, you might get locked into a detour of many tens of miles. Having said that, I've just tried navigating to some buildings (using address search) which are closer to a motorway than any other mapped road, and osmand seems to be smart enough

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Dne 03/10/2016 v 20:29 Toby Dickenson napsal(a): > [..] > > If the user picked that building from an address search, then it > definitely makes sense to end at a location with likely access to the > building. > Yes, it would make sense. But the likely access to the building is much easier to e

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

I guess it depends on how the destination flag happened to be placed at that location. If the user picked that spot from a map then osmand is doing exactly the right thing. I quite often put the destination point in the middle of a motorway, knowing that I can find my own way from there. If the u

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

On 10/03/2016 03:30 PM, Jack Burke wrote: It looks like the on-ramp is closer to the building centroid than the parking_aisles are, so I'll guess that's the problem: it's trying to route you to the point nearest the centroid. Poutnik, in the U.S., it is illegal access. Since highway=motor*

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

It looks like the on-ramp is closer to the building centroid than the parking_aisles are, so I'll guess that's the problem: it's trying to route you to the point nearest the centroid. Poutnik, in the U.S., it is illegal access. Since highway=motor* is defined to be assumed foot=no, bicycle=no

Re: OsmAnd incorrectly prefers freeway offramps rather than local streets as the final road

Illegal parking is not illegal access. OSMand cannot know what you want to do at destination. Rather such decision should stay at user, choosing destination. BTW, Not sure if OSM data or OBF files contain parking allowed status. Dne 03/10/2016 v 08:43 Zian Choy napsal(a): > > OsmAnd routes drive