Calculating a GPX

openrouteservice
1

Hello folks,
from the ORS API I’m trying to obtain a gpx with the foot-walking profile, but I obtain the error ‘could not find routable point whitin radius of 350.0 metres…’. But the coordinates have a distance of 3/4 km… Using the ‘foot-hiking’ profile it working fine! I give you the coords that I’m using:
[9.303036,46.197362],[9.3061,46.150123]

2

Hi,
You probably mix up the coordinates order as suggested in the FAQ.
Cheers!

3

Hi andrzej, I’m using the code which have worked until now and, finally, I have the issue in foot-walking profile only, in the foot-hiking the same call is working fine

4

I tried too with the API playground, from the official ORS website and, with the same coordinates, I get the same error.. I don’t understand where is the mistake…

5

Hey,

You are trying to calculate a route in the Italian Alps, from Baggio down to Lago di Como.
Most paths around the area have a sac_scale key to distinguish their difficulty.

In line with openrouteservices tag filtering process, the foot-walking-profile only allows routing on roads with sac_scale=strolling or sac_scale=hiking (or absent).

For pedestrian routing on paths with sac_scale=mountain_hiking, demanding_mountain_hiking, alpine_hiking, demanding_alpine_hiking, difficult_alpine_hiking, the foot-hiking-profile exists.

Thus, foot_hiking finds a route, but foot_walking does not.

Best regards

6

Then, if I understood, my foot-walking request into a zone not too… ’easy’ cannot to be accepted by the specific profile, for this specific path I can use the foot-hiking profile. Is it correct?

Anyway, the returned error about the ‘….350 m…’ is misleading, I think that in requests with ‘profile=foot-walking’ where ‘sac-scale > sac_scale=hiking’, the message should be different to make it clear why..

Thanks for the support

7

Hey,

exactly.

The error message is indeed technically correct, as a routable point within a radius of 350m could not be found.
But as we all know, technically correct is the best kind of correct :sweat_smile: and I agree that the error message for that case could be improved.

Improve user feedback if no routable points can be found · Issue #2226 · GIScience/openrouteservice · GitHub is the corresponding issue - I would not expect this to be fixed soon, however, as it might be the case that it is not destinguishable from the case where no roads exist at all around in the area in question…

Best regards

8

I worked in IT for 40 years, and I agree with you that ‘technically correct is the best kind of correct’, unfortunately the real world is very different, the real users need to be drived… then ‘we’ need to go down a couple of levels… Thanks for the issue, anyway I’m happy to contribute to ORS improvement

1 Like