Turn restriction ignored

[Veeno]

Routing ignores this turn restriction (image included below).

Possibly related issue is Project-OSRM#5380, however, in this case neither of the two way IDs are >32bits, but the node ID is 5071586346 (i.e. 0x12E4A442A), which is a 33bit (unsigned) number.

[wangyoucao577]

Did you just edit it days ago? Both the OSM data download page and demo engine can not reflect the changes immediately. It may take some days or weeks to affect on download page. For demo engine, it depends on when they update the data set. Try to download the OSM data after at least 1 week, make sure the restriction is in the data that downloaded. After that, compile and launch OSRM by yourself.

[Veeno]

Well, the restrictions were present even before my edits, but I opted to edit the intersection because I presumed the issue is in the data rather than the routing algorithm. It is true however that I do not know whether the restrictions are present in whatever data the demo engine uses.