<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA['Couldn’t calculate route' - suggested improvement]]></title><description><![CDATA[<p dir="auto">It would be very helpful to know which waypoint(s) caused the routing engine to not be able to route, especially when there are a lot of waypoints, and you didn't notice the warning because it scrolled off the screen (due to the waypoint list auto-expanding).</p>
<p dir="auto">The first indication of something wrong was that the waypoints wouldn't snap to the route, even though the problem was far away from the new waypoint I was trying to drop in. Quite confusing. As soon as the faulty waypoint is moved/removed, the waypoint snap works again.</p>
<p dir="auto">It's not a bug as such (it was one of my special 'dropped in the sea' waypoints), but it might help idiot users to get out of a mess if the problem was highlighted. <img src="https://forum.myrouteapp.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f644.png?v=06c51928fc7" class="not-responsive emoji emoji-android emoji--face_with_rolling_eyes" style="height:1.4em;width:auto;vertical-align:middle" title=":face_with_rolling_eyes:" alt="🙄" /></p>
]]></description><link>https://forum.myrouteapp.com/topic/12798/couldn-t-calculate-route-suggested-improvement</link><generator>RSS for Node</generator><lastBuildDate>Mon, 16 Nov 2026 19:21:24 GMT</lastBuildDate><atom:link href="https://forum.myrouteapp.com/topic/12798.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 16 Nov 2026 18:59:10 GMT</pubDate><ttl>60</ttl></channel></rss>