The mobile app is currently running blind. By this I mean that when a waypoint is set by tapping or by search by name, there is no attempt to locate the nearest point on the cyclable network. This leads to a lot of failed routing, similar to the report at #30 where undefined values are set for waypoints.
This problem is easily reproduced by setting a waypoint over the sea.
The enhancement is to use the API call at: http://www.cyclestreets.net/api/nearestpoint/ to snap to the routeable network before trying to generate a route.
The mobile app is currently running blind. By this I mean that when a waypoint is set by tapping or by search by name, there is no attempt to locate the nearest point on the cyclable network. This leads to a lot of failed routing, similar to the report at #30 where undefined values are set for waypoints.
This problem is easily reproduced by setting a waypoint over the sea.
The enhancement is to use the API call at: http://www.cyclestreets.net/api/nearestpoint/ to snap to the routeable network before trying to generate a route.