dmd docs
OSM locations queries consistently timeout
Submitted by vlad / miro • #64 • 1d ago • updated 3h ago
On some tracks —as for instance OSM25812855, eg 51.00768, -1.24189— OSM queries systematically timeout. On other tracks it’s hit and miss. Not sure why, could be the timeout period is too short? I believe as a consequence of this, the planner refuses to put waypoints there. Screenshots show the timeout and that the location is known to OSM and legal to vehicles (I just refreshed the OSM record myself). If I am barking up the wrong tree here, eg you don’t use those queries to route, I apologise for wasting your time.
More in general —and this is not related to timeouts— I think that surely you must *not* route automatically through trails OSM thinks aren’t allowed to motor vehicles, but when the user explicitly insists on putting a waypoint on a certain track, that should take priority (possibly with a warning “do you know what you’re doing?”) as OSM is full of errors, the user probably knows best, and anyway they ride under their own responsibility.
Discussion (2)
J
Johny Pear
9h ago
This was actually our Overpass server which is a local server, running on a different IP address than it should.
V
vlad / miro
3h ago
Thanks Johny! It is still hit and miss, but mainly works. Still, why is it that can’t put any waypoints on that lane? I can’t attach a screenshot here, but all the metadata is all green: highway: track, motor_vehicle: yes, why does the planner refuse waypoints attached to that lane? What is missing/wrong?
0
Vote