viaroute vs table

[jellevictoor]

I got some locations in Belgium where the from/to distance is totally different than what I got from the viaroute. Since it is only the distance that is giving strange results, I think it is only applicable in this fork.

table?loc=50.99775,3.81409&loc=50.9974473,3.8097512

{"status":200,"source_coordinates":[[50.997887,3.814247],[50.998238,3.810463]],"destination_coordinates":[[50.997887,3.814247],[50.998238,3.810463]],"distance_table":[[[0,0],[797,660]],[[714,177],[0,0]]]}

viaroute?loc=50.99775,3.81409&loc=50.9974473,3.8097512

{"status":200,"hint_data":{"locations":["pIgDAJDQEgD5XwAAMQMAAAcAAAAAAAAAiQEAAMR2BACUAwAAgCoKA2czOgAAAAEB","sTYOAP____-lEQAAAgAAABIAAAAVAAAAAAAAAAHVAwCUAwAA2ysKA58kOgACAAEB"],"checksum":3979845711},"route_name":["",""],"via_indices":[0,14],"via_points":[[50.997887,3.814247],[50.998238,3.810463]],"found_alternative":false,"route_summary":{"end_point":"Brusselsesteenweg (N9)","start_point":"Collegebaan","total_time":80,"total_distance":353},"status_message":"Found route between points","route_geometry":"_gtgBmuxgFqN|f@}BlMoBpRqCt_@sBb_@oDnp@HIwCbb@q@zHO`Gj@fCfH|DfDyJrDgL"}

viaroute?loc=50.9974473,3.8097512&loc=50.99775,3.81409

{"status":200,"hint_data":{"locations":["sTYOAP____-lEQAAAgAAABIAAAAVAAAAAAAAAAHVAwCUAwAA2ysKA58kOgACAAEB","pIgDAJDQEgD5XwAAMQMAAAcAAAAAAAAAiQEAAMR2BACUAwAAgCoKA2czOgAAAAEB"],"checksum":3979845711},"route_name":["",""],"via_indices":[0,12],"via_points":[[50.998238,3.810463],[50.997887,3.814247]],"found_alternative":false,"route_summary":{"end_point":"Collegebaan","start_point":"Brusselsesteenweg (N9)","total_time":71,"total_distance":311},"status_message":"Found route between points","route_geometry":"u|tg`B}hqgFdEqPt@wBcBuEaNaEkCcCIaInDop@rBc_@pCu_@nBqR|BmMpN}f@"}

[RhinoDevel]

@jellevictoor Thanks for the info.

• Is this the only case you found where there is such a difference?
• Have you tried @niemeier-PSI 's solution? If so, does the same problem occur? See Distance support for table service Project-OSRM/osrm-backend#2764