[OSRM-talk] Routing profiles / access tags and tracks beeing used in mobility data

[Florian Lohoff]

Hi,

On Wed, Dec 06, 2023 at 02:14:03PM +0100, Anne-Laure Buisson wrote:
> We are using OSRM to calculate map matched itinerary of trucks, and until
> now it worked smothly.
> 
> But the restrictions on some roads in OSM are starting to create problems
> for our solution :
> 
>    - the pedestrian zones are used by truck for deliveries (center of
>    cities for exemple)
>    - some truck use track in rural area
>    - some street are considered private (with exceptional permit) and OSRM
>    don't allow truck to use those way-id.
> 
> We've got GPS points every 30 secondes, and we see the vehicles using
> thoses way-id, but they are not allowed by car.lua, and the resulting map
> matching is falsely correcting the itinerary.
> 
> 
> We tried to change the content of access_tag_blacklist and
> access_tag_whitelist in car.lua (adding private in white list, or
> commenting it in black list), and we tried to add track as a possible road
> type, but the script stop during the selection of usable way-id, and we are
> not sure to understand how to modifie the file.
> 
> Is there a documentation somewhere ? Or does someone have solved the same
> issue ?

The problem is more the deteriorating OSM data. I am doing Routing
Quality Assurance using OSRM and i see the same things. Another thing
is broken/misunderstood/guessed turn restrictions.

The problem with "fixing" osrm profiles is that you accidentally make
other roads which REALLY SHOULD NOT BE USED usable. 

access=private should take no public traffic, and should be signed as
such. Either "No trespassing" or some physical barrier. access=private
is explicitly not a statement of ownership, but mappers often confuse
this.

Routing is a kind of problematic issue in OSM as users mapping
have no clue about routing and dont immediatly see their mapping results
breaking routing.

So there are multiple things you can do:

- To get better attention on routing issues in the OSM Dataset give a talk
  on one of the upcoming State of the Map conferences and present your
  problem.

Depending on the scale of your Problem:
- If on a small scale
  - Open notes on the OSM Website stating the issues at the road
    segments
  - Start fixing the OSM data yourself
- If on a larger scale extract road segments which get used in your mobility data,
  but which are tagged as unusable (track, access=private) create
  Maproulette challenges for mappers to have a look at these specific
  locations possibly fix them.
- Or if possible create a mobility data overlay with the problematic
  road segments and invite mappers to fix them.

On the specific issues:

When trucks use "highway=track" these are wrongly tagged in the OSM
data. A track is defined to be a road mostly or exclusively used for
agricultural traffic. So if there is legal through traffic this has
been tagged wrong.

When trucks use access=private roads and these are not on the last or
first leg of the journey these are used as through roads and most likely
are accidentally tagged as private.

Flo
-- 
Florian Lohoff                                                     f at zz.de
  Any sufficiently advanced technology is indistinguishable from magic.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/osrm-talk/attachments/20231207/6418a34c/attachment.sig>