Open dittaeva opened 11 years ago
I don't have enough experience with the mobile interface to really comment on how useful it is. I also have only limited possibility to test it because your database is limited to Norway which is far away from my geolocation, so I end up with routes that are all more than a thousand km away. In that case, the length really clutters up the screen because of the large numbers. You might want to consider to put it under the route name instead of in its own column.
Well, my use case is more or less like this:
User is travelling as a tourist outside of his home area, he has mobile internet or is on a wireless network at hotel / camping ground / tourist office. User would like to know what hiking opportunities there are in the area he is in right now. In addition to information about the route itself, information about how close it is, how to get there, where to park, and more would be interesting. This issue is about "how close" the route is.
In such a user scenario, whether the route is national, regional, local, etc. is probably not very interesting, but for now we're still keeping the separation.
There is still an outstanding issue: the START of a round trip where there is a usually a car park ...
And what is the issue with that, and how does it relate to this specific Waymarked Trails issue?
Because, roundtrip routes, although you can of course start from wherever you want, have a starting point and an ending point (which are the same). Hence, for the moment I do NOT close a roundtrip, because Waymarked Trails and others do not consider the startin/ending point of a roundtrip route.
This is functionality that is under development on https://github.com/WNRI/route.is/issues/18, please provide feedback, positive or negative.
For the user to see how far it is to routes in the route list calculate the distance from the user to nearest (end)point of the route in straight line (no routing).