Quote:
Originally Posted by Arno
To test I just entered
Start: Toronto, ON
Destination: Albany, NY
Stop-overs: Prescott, ON; Tupper Lake, NY; Lake Placid, NY;
and it calculated the correct way with reasonably fast processing time.
Saving it to the device as an itn will eliminate the need to follow my previous habit of putting town centers in a custom POI and call up the next destination just before I get to this town.
|
First line just meant just now, not when I made a Toronto area test before.
It appears that earlier today,
just like then, I only looked at the route shown in the software.
After
gatorguy's post I decided to run the itinerary in Demo mode and it failed.
It showed the correctly numbered waypoints
Screen042.jpg
but then, after completing the calculations, it displayed
no route found
Screen043.jpg
I opened the file with Notepad and saw a couple of quotation marks on the last line (below the finish line, ending with |2| and deleted them.
Double clicked on the itn file, opened it and it showed properly with TYRE
Screen044.jpg
Tried to run it in Demo mode and got the same
no route found as before.
Opened it with Notepad and compared it to other itineraries and noted that some started out with a 0 (zero) and others with a 1 (one). I changed the 0 for the Start to 1, tried again and the Demo works.
To confirm all of the above I made another short local 2 waypoints itinerary.
Looking at the file made by ZRP-Routenoptimierung I get everything on one line with a square box symbol as the last item per instruction.
Opening it with TYRE and saving it I again get the
normal one line per instruction with a double quotation mark in a line below the Finish instruction |2|.
BOTH ran without a hitch in Demo mode.
Having tried it over and over I am a little discouraged as I could not find out why it wouldn't work on the Albany test.
In spite of my normal lapel button I will make an exception this time
Warning.jpg
and will accept advice gracefully
Arno