Skyler Hawthorne <[email protected]> writes: > Hmm, maybe service roads and access have nothing to do with the > problem. If I try to route to the fountain out front, it does the > right thing, but the issue happens when I click on the building and > navigate to that.
I said this before, but: It seems in this area that many routers are having trouble, and osmand is known to do ok with terminal private segments when private access is enabled. Therefore i think it is far more likely that there is something wrong with the OSM data, than that osmand has a bug which produces the observed behavior. I have private accesss turned on in osmand. I routinely drive to places that are reachable by access=private ways (with permission!), and osmand routes on those ways just fine. There are larger issues about doing this right, and I don't claim osmand or any other router is fully correct. Just that I think it unlikely you are suffering from an osmand bug vs something else we don't understand. I did run the JOSM validator on the trailer park data. It found a few things, but they were minor and I uploaded fixes. The only notable one was overlapping ways for the entrance/exit roads, that I think you introduced - and I fixed them. To be fair, there are lots of relations to give names to multi-way roads, and this is more complicated than is typical. (I am of the opinion, perhaps wrong, that using editors other than josm to deal with relations is asking for trouble.) -- 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/rmir1x0ung6.fsf%40s1.lexort.com.
