Error in OSRM routing; how to handle this case?

[perrygeo]

http://router.project-osrm.org/nearest?loc=44.530765,-122.510725
and
http://router.project-osrm.org/nearest?loc=44.530451,-122.517537

both return something like:

'{"version":0.3,"status":0,"mapped_coordinate":[44.530607,],"name":"","transactionId":"OSRM Routing Engine JSON Nearest (v0.3)"}'

Note the incomplete coordinate (no longitude returned). This results in:

line 59, landing.py:  json.loads(binary)

*** ValueError: No JSON object could be decoded

We will need to guard against this case and/or work with OSRM to fix it.

[perrygeo]

inquiry on the OSRM mailing list: http://lists.openstreetmap.org/pipermail/osrm-talk/2013-August/000239.html

EDIT: Dennis, the lead dev at OSRM, has clearly acknowledged the issue as of Aug 14 but hasn't been very responsive in fixing it.

[perrygeo]

For now the forestplanner is just ignoring properties where this occurs. Unfortunately, it appears to be a systematic problem with the osrm service so hopefully it gets resolved soon.

[perrygeo]

Submitted a github issue and patch to fix it. Project-OSRM/osrm-backend#723

If the patch is not accepted, we may need to fork and run our own server?

[DennisOSRM]

Already fixed earlier Project-OSRM/osrm-backend@a6c52fd

[perrygeo]

@DennisOSRM Thanks!