Segment of road not considered for routing - why? about osrm-backend HOT 2 CLOSED

There is a dedicated lua script useful for debugging that will help understand how a profile "sees" a given OSM way. For example one of the two you shared seems now perfectly fine:

lua debug_way.lua car 1126408079
{ 
  highway = 'primary',
  maxspeed = '40',
  name = 'Ratapihankatu',
  ['name:fi'] = 'Ratapihankatu',
  oneway = 'yes',
  surface = 'asphalt' 
}
=>
{ 
  backward_classes = {},
  backward_mode = 0,
  backward_rate = 8.8888888888889,
  backward_speed = 32,
  destinations = '',
  duration = 0,
  forward_classes = {},
  forward_mode = 1,
  forward_rate = 8.8888888888889,
  forward_speed = 32,
  is_left_hand_driving = false,
  is_startpoint = true,
  name = 'Ratapihankatu',
  road_classification = { 
    may_be_ignored = false,
    road_priority_class = 4 
  } 
}

Note that this way has been changed right after you posted your message: the proposed: primary that was removed is likely the reason why it was not included in the first place, see this part of the profile.

That is really not a bug, rather a data issue. Can you re-build using a new extract including the latest changes and confirm that those ways are now included?

from osrm-backend.

Thank you, that explains it all. The lua script seems useful.

Seems like the proposed-tag was misused on that way, causing map renderers to show it as a proper functioning way but OSRM profiles considering it as a planned but not ready for use road.

The proposed tag should always be used combined with "highway: proposed" (or amenity/railway/another main tag: proposed). Wouldn't it be better for the profile to ignore the proposed-tag and instead avoid highways with tag "highway: proposed" ? I believe that could be more consistent with the renderers and avoid cases where proposed-tag is forgotten on a way when the road is marked as finished.

from osrm-backend.