Hi there, yesterday I decided to plan a trip via the XT Trip Planner appl, not using Basecamp, I've noticed the following.
If the trip is just a direct route from the Start Location to the Destination no issues, but adding an intermediate location may lead to unexpected results.
To deep dive the the issue today I just created a simple trip between 3 locations (Sassoleone>Monzuno>Rioveggio) all 3 are small towns in my area in Italy close to Bologna. I've simply used the "Search" function, selected the Start Location (Sassoleone), then the Destination (Rioveggio) then the middle location as I wanted my trip passing via Monzuno.
Whenever a middle location like a Town is selected the XT asks "Selecting a city will stop at the city centre. Routing without stopping instead?" (Yes/No). Answering "No" an actual waypoint is created in the trip (orange flag sign) and everithing runs as expected, when the trip is calculated the waypoint is part of the trip.
Answering "Yes" the location apparently becomes a "shaping point" (blue dot icon) but is not considered in the trip, I've the impression that the XT is not able to manage this shaping points in the Trip planner. The intemediate locations can be easily switched from waypoint to shaping ponts clicking the orange flag (if created ad waypoint answering No) or the blue dot (if created as shaping point answering Yes), but once created as shaping points they are not considered correctly even if switched to waypoint.
Moreover some crazy, unwanted, shaping points appear, sometimes, in the trip, always linked to the "Yes" answers, the other type of locations like addresses or saved waypoints or categories item etc. etc. are set by default as waypoints, but if you switch them to shaping points same mess occurs.
The above both with "fast route" or "shorter distance", I'm currently in v2.70 with CN Europe NTU v2020.30
Ciao
Trip planner strange behaviour
Re: Trip planner strange behaviour
Trip planner is quite bad from my experience.
Very hard to add an intermediate point, i also had this issue with the "yes/no" for the routing, couldn't figure out what was the difference =D.
Also, several time i lost trips while making them, because i was looking on maps/phone/asking my girl where we wanted to go, after 3min the unit is shutting down =( , and there is no "temporary memory", all gone.
Very hard to add an intermediate point, i also had this issue with the "yes/no" for the routing, couldn't figure out what was the difference =D.
Also, several time i lost trips while making them, because i was looking on maps/phone/asking my girl where we wanted to go, after 3min the unit is shutting down =( , and there is no "temporary memory", all gone.
-
- Posts: 56
- Joined: Sat Jun 13, 2020 12:18 am
- Location: Minnesota
- Has liked: 6 times
- Been liked: 4 times
Re: Trip planner strange behaviour
Set mine to 5min, which is the max (otherwise it's never, which is not ok neither)
-
- Posts: 2814
- Joined: Sat Oct 19, 2019 4:17 pm
- Location: West Yorkshire, Uk
- Has liked: 369 times
- Been liked: 789 times
Re: Trip planner strange behaviour
Changing a via point to a shaping point on the XT and the 595 can often result in the point being renamed and moved to a different location.
I have tested it with 3-point routes:
Where the mid point is deliberately placed to force the route to take a minor road, when changing it to a shaping point, it often moves it onto a road that would be on the fastest route between the start and end point ie by-passing the original intended road.
I have reported it a while back. It was acknowledged as a fault, but after 3 updates, it still has not been fixed.
Perhaps if more people complained ..... ?
Nb 2.90 fixed many issues with closest entry point, although it was never mentioned. Perhaps if you update ??
I have tested it with 3-point routes:
Where the mid point is deliberately placed to force the route to take a minor road, when changing it to a shaping point, it often moves it onto a road that would be on the fastest route between the start and end point ie by-passing the original intended road.
I have reported it a while back. It was acknowledged as a fault, but after 3 updates, it still has not been fixed.
Perhaps if more people complained ..... ?
Nb 2.90 fixed many issues with closest entry point, although it was never mentioned. Perhaps if you update ??
Have owned Zumo 550, 660 == Now have Zumo XT2, XT, 595, 590, Headache
Use Basecamp (mainly), MyRouteApp (sometimes), Competent with Tread for XT2, Can use Explore for XT - but it offers nothing that I want !
Links: Zumo 590/5 & BC . . . Zumo XT & BC
Use Basecamp (mainly), MyRouteApp (sometimes), Competent with Tread for XT2, Can use Explore for XT - but it offers nothing that I want !
Links: Zumo 590/5 & BC . . . Zumo XT & BC