Bart Eisenberg <[email protected]> writes: > After experimenting on the California map, I think this comes down to how a > given road is classified on OpenStreetMap--which provides OsmAnd with its > underlying data. And it looks to me like Car navigation assumes that a > given road can be navigated by an ordinary passenger car. So if you're > planning for 4x4 travel, you might have to use the bicycle or even the > pedestrian mode. And if the route still isn't going where you like, add > some intermediate destinations.
I think that's good advice. The real underlying issue is that OSM doesn't really have a clear and complete "this road is passable by this vehicle" data model. Yes, a highway=unclassified/residential/service should be passable by an ordinary passenger car, but is not necessarily paved. highway=track sort of implies passability for 4-wheel vehicles; there are grades where I'd say at one end, you really need a capable 4WD vehicle with high clearance, and at the other a passenger car should be ok. (Track is more than a phsyical description as it is tied up with the notion that the way represented by it is not a road in the normal legal sense. Note that while I think this is the majority view, there is not full agreement on this point.) highway=path implies that a 4-wheel vehicle cannot pass. Separately, there are acccess restrictions, and it's a good guess that if a vehicle cannot pass it will either 1) be tagged not for access or 2) the type will imply. With all of that, keep in mind that all data is subject to being wrong. If Petra wants to make 4WD routing work, I think a routing mode that allows some tracks is needed, perhaps as a variant of car. I would not assume that the car mode gets the subtleties of tracks right. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/rmi4kubgddx.fsf%40s1.lexort.com.
