bicycle profile: change barrier_whitelist to barrier_blacklist#5076
bicycle profile: change barrier_whitelist to barrier_blacklist#5076TheMarex merged 2 commits intoProject-OSRM:masterfrom
Conversation
MichalPP
changed the title
|
and maybe routing over |
blacklisting barriers allow routing over barrier=some_tag
|
@MichalPP thanks for taking a stab at this! Can you explain a little bit more why you think a |
|
@TheMarex compared to car, going on foot/bicycle, you can physically pass basically any barrier (so access tags are respected). the whitelist would be very long. plus blacklisting is a lot less prone to mistakes/typos/new invented tags. |
This is significant - car routing in/out of central London with OSRM was broken for several months because someone had invented a new tag ( |
|
Hrm - yes that makes sense to me. Thanks for pushing this forward! |
- Changes from 5.18.0:
- Optimizations:
- CHANGED: Use Grisu2 for serializing floating point numbers. [Project-OSRM#5188](Project-OSRM#5188)
- ADDED: Node bindings can return pre-rendered JSON buffer. [Project-OSRM#5189](Project-OSRM#5189)
- Profiles:
- CHANGED: Bicycle profile now blacklists barriers instead of whitelisting them [Project-OSRM#5076
](Project-OSRM#5076)
- CHANGED: Foot profile now blacklists barriers instead of whitelisting them [Project-OSRM#5077
](Project-OSRM#5077)
- CHANGED: Support maxlength and maxweight in car profile [Project-OSRM#5101](Project-OSRM#5101]
- Bugfixes:
- FIXED: collapsing of ExitRoundabout instructions [Project-OSRM#5114](Project-OSRM#5114)
- Misc:
- CHANGED: Support up to 512 named shared memory regions [Project-OSRM#5185](Project-OSRM#5185)
4 participants
change barrier_whitelist to barrier blacklist in foot profile
fix #5067 and #3890 and #4823