El ds. 04 de 04 de 2020 a les 11:31 -0400, en/na 'Xavier' via OsmAnd va escriure: > On Sat, Apr 04, 2020 at 07:31:14AM -0700, Skyler Hawthorne wrote: > > Hello, I'm having trouble getting OSM/And to route correctly to a > > house inside of a mobile home park. An example route is here (two > > random locations, but shows the problem): > > > > https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=37.3968%2C-122.0233%3B37.4078%2C-122.0001#map=17/37.40673/-122.00073 > > The issue does not seem to be OsmAnd. > > > I'm using OSMAnd 3.6.3 with the California San Francisco offline > > map, > > last updated at 2020-04-04 05:55 PDT. Although as you can see, it > > happens on the standard OSM home page too. > > The fact that it happens on the OSM home page indicates a problem > with > the OSM data. > > > The problem is the whole park only has two entrances, the main one > > being at 849WC232+95, and a smaller one being at 849VCX3V+8V. The > > entire park is walled off, so all routes should go in and out of > > one > > of these two entrances. However, it seems to give up outside the > > wall of the park if you give it any destination that's one of the > > houses on 10th Street or D street. > > If you look at the OSM data for this park, you'll find that not only > is the entrance (Recreation Drive) at West Tasman Driv marked > access=private, but every single road within this park is marked > access=private. > > The definition of access=private is here: > https://wiki.openstreetmap.org/wiki/Tag:access%3Dprivate > > And the first paragraph explains the issue: > > The access=private tag is generally used in combination with the > road > network tags to indicate that the road is not to be used by the > general public, and on other facilities. Access is only with > permission on an individual basis. > > and a bit further down: > > Routing programs are able to detect this tag, and knows to avoid > these roads when routing. > > So both the OSM home page, and OsmAnd, are doing exactly what they > have > been told by the underlying OSM data. > > So the solution would be, assuming the access=private is incorrect, > for > you or a local mapper to remove the access=private tags from the > various roads (ways in OSM) that have the tag attached. Then the > routing programs will no longer be told to avoid using those roads, > and > should be able to find a route that goes into the park.
I don't know if those roads are really private, but anyway I think that osmand have a setting in which you could tell it to not avoid private routes In route parameters -> allow private access HTH Pere > -- 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/5f2c09dd4bf5a318d9d74b41598294c195c21d07.camel%40gmail.com.
