Interruptions between waypoints
-
Some time ago it was made clear to me that, when two points do not allow joining through an itinerary, it means that there is a closed port or some other obstacle. In these cases the "Skip" icon can be used.
In this route: "https://www.myrouteapp.com/route/open/4134259" some points do not cross ports and, in addition, a few days ago all the waypoints were joined, why now they are not joined and forces to use "Skip"? -
Some time ago it was made clear to me that, when two points do not allow joining through an itinerary, it means that there is a closed port or some other obstacle. In these cases the "Skip" icon can be used.
In this route: "https://www.myrouteapp.com/route/open/4134259" some points do not cross ports and, in addition, a few days ago all the waypoints were joined, why now they are not joined and forces to use "Skip"?@manuel-grasa That looks like a bug. When I use the route, all points starting from 49 seem to be set to "Skip". I would submit a ticket from the "Support" section of MRA Planner.
-
@manuel-grasa That looks like a bug. When I use the route, all points starting from 49 seem to be set to "Skip". I would submit a ticket from the "Support" section of MRA Planner.
a few days ago all the waypoints were joined, why now they are not joined and forces to use "Skip"
They were joined before. They aren't any longer. Instead, indeed points 72 and 73 are set (read : changed) to "skip".
Question was : why is this ?
-
@manuel-grasa That looks like a bug. When I use the route, all points starting from 49 seem to be set to "Skip". I would submit a ticket from the "Support" section of MRA Planner.
@herko-ter-horst Editing an already reacted-upon reaction makes the stuff pretty much ununderstandable, if you ask me...
-
@herko-ter-horst Editing an already reacted-upon reaction makes the stuff pretty much ununderstandable, if you ask me...
@sudolea I didn't see your reaction until after I changed my response because my initial response wasn't completely correct. You could have easily prevented any confusion by changing or removing your reaction, but instead you chose to bitch about me changing mine, which isn't helpful to anyone.
-
@sudolea I didn't see your reaction until after I changed my response because my initial response wasn't completely correct. You could have easily prevented any confusion by changing or removing your reaction, but instead you chose to bitch about me changing mine, which isn't helpful to anyone.
@herko-ter-horst What you're saying is understandable, it can happen. On the other hand, I didn't exactly have any "bitching about" in mind with my proper reaction, rather informing future readers that my reaction was to be considered as having become invalid due to an edit which had obtained some totally different message than it initially had had... Peace !
-
@manuel-grasa That looks like a bug. When I use the route, all points starting from 49 seem to be set to "Skip". I would submit a ticket from the "Support" section of MRA Planner.
@herko-ter-horst
Efectivamente, los puntos están configurados como "Omitir" porque de no hacerlo asà la ruta no se dibuja en el mapa.
Otras veces no se dibuja tampoco aunque se configuren los puntos como "Omitir".
Además, estos inconvenientes cambian con los dÃas. Estoy pensando que quizá se deba a la distinta ocupación de los servidores en los que reside la aplicación. -
@herko-ter-horst
Efectivamente, los puntos están configurados como "Omitir" porque de no hacerlo asà la ruta no se dibuja en el mapa.
Otras veces no se dibuja tampoco aunque se configuren los puntos como "Omitir".
Además, estos inconvenientes cambian con los dÃas. Estoy pensando que quizá se deba a la distinta ocupación de los servidores en los que reside la aplicación.@manuel-grasa I'm sorry, I don't speak Spanish. You're posting in the "General" section of the forum, where English is used. If you don't speak English, it may be better to post in the Spanish-language sub-forum.
-
@manuel-grasa I mangled your post through Google Translate, and saw this message (in English translation) :
"In addition, these inconveniences change with the days. I'm thinking maybe it's due to the different occupancy of the servers where the app resides."
I don't think so. My 5 cents are that this is not caused by the servers, but by the reigning culture in MRA's development process. I too am noticing all the different phenomena these last days. I think they are caused by the (may I say : overly inmature) introduction of the segment-specific navigation settings in OpenStreetMap. But then again...
Putting everything together (from last days' events going back to the last weeks or even months), I dare to state that MRA treats its customer as continuous beta-testers. They also don't have even the most primitive test plan, let alone regression tests. So, they don't value providing the customer what he needs : a STABLE application.
This is especially bad nowadays, where everyone starts creating new routes, or starts using older routes which "once upon a time" had worked flawlessly - recently a route of mine (had worked fine before) started showing times and distances that were completely off as well in distance as in time. Starting to plan a multi-days trip ? MRA doesn't care providing reliable info. Instead, they are tweaking and fiddling "until it works again", often breaking other things on their way ...
No, MRA is continuously working on the Route Planner as if it were still in test phase. The net result of this is : on a good day you find it working, but most of the time there is "some loose bolt". Imagine what would happen if your car mechanic let you drive your car while he's changing the wheels. It could also be stated in another way : car mechanics value "useability" better than MRA does...
-
@manuel-grasa I mangled your post through Google Translate, and saw this message (in English translation) :
"In addition, these inconveniences change with the days. I'm thinking maybe it's due to the different occupancy of the servers where the app resides."
I don't think so. My 5 cents are that this is not caused by the servers, but by the reigning culture in MRA's development process. I too am noticing all the different phenomena these last days. I think they are caused by the (may I say : overly inmature) introduction of the segment-specific navigation settings in OpenStreetMap. But then again...
Putting everything together (from last days' events going back to the last weeks or even months), I dare to state that MRA treats its customer as continuous beta-testers. They also don't have even the most primitive test plan, let alone regression tests. So, they don't value providing the customer what he needs : a STABLE application.
This is especially bad nowadays, where everyone starts creating new routes, or starts using older routes which "once upon a time" had worked flawlessly - recently a route of mine (had worked fine before) started showing times and distances that were completely off as well in distance as in time. Starting to plan a multi-days trip ? MRA doesn't care providing reliable info. Instead, they are tweaking and fiddling "until it works again", often breaking other things on their way ...
No, MRA is continuously working on the Route Planner as if it were still in test phase. The net result of this is : on a good day you find it working, but most of the time there is "some loose bolt". Imagine what would happen if your car mechanic let you drive your car while he's changing the wheels. It could also be stated in another way : car mechanics value "useability" better than MRA does...
@sudolea
We have had mixed experiences with this app. I have been using it for years with full satisfaction, since when I was Tire. It is true that sometimes there have been small irregularities, but never like now. I hope it gets fixed. -
@manuel-grasa I'm sorry, I don't speak Spanish. You're posting in the "General" section of the forum, where English is used. If you don't speak English, it may be better to post in the Spanish-language sub-forum.
@herko-ter-horst
Sorry. Since my browser presented it to me translated into Spanish, I thought it would also work the other way around. -
Some time ago it was made clear to me that, when two points do not allow joining through an itinerary, it means that there is a closed port or some other obstacle. In these cases the "Skip" icon can be used.
In this route: "https://www.myrouteapp.com/route/open/4134259" some points do not cross ports and, in addition, a few days ago all the waypoints were joined, why now they are not joined and forces to use "Skip"?There is a problem with the OSM server, will be fixed asap
