search

osmandapp / OsmAnd

OsmAnd
https://osmand.net
Other
4.72k stars 1.03k forks source link

Osm live "barrier" bug #2499

Closed xmd5a2 closed 7 years ago

xmd5a2 commented 8 years ago

https://www.openstreetmap.org/node/4090258858 Netherlands_gelderland_europe_16_04_01.obf 2016_04_01/netherlands_gelderland_europe_15_30.osm.gz This barrier does not exists in 16_04_01 and 16_04_00. Parent highway (osmid 406991107) presents in 15_30, 17_00, 16_00.

poutnikl commented 7 years ago

It may be worthy to reevaluate the approach to default access of obstacles, if there is lack of explicit relevant access tags. E.g. for nodes barrier=bollard and cars the default access should be NO unless tagged YES. ( like BRouter car profiles do )

aceman444 commented 7 years ago

The access for a car is intended to NOT be allowed by default on a bollard, see https://github.com/osmandapp/OsmAnd-resources/blob/master/routing/routing.xml.

Is this a problem with live Updates as xmd5a2 marked it?

poutnikl commented 7 years ago

I revoke my previous comment, based on some misunderstanding, or rather misreading of routing.xml content.

vshcherb commented 7 years ago

@aceman444 the problem is related to fetching of the changeset, so during change the bollard won't be fetched in OSC (osm change file) and that's why OsmAnd will get an incomplete obf file where bollard won't exist on the line which obviously will lead to routing mistake.

vshcherb commented 7 years ago

The issue fixed since September updates