Hi,
I am new here and exploring Microsoft Streets & Trips 2010.
I imported a GPX file into S&T 2010 and thought every thing went fine, after zooming in on the track I something very strange, the track left the Interstate almost on every Exit and went on the Interstate at the next Exit.
Sometimes the track was on a highway parallel on the Interstate and some times the track went back via an Exit on the Interstate in the opposite direction.
The track mentioned above was made by my self last year, from Detroit to Gary for 100 % on Interstate 94. The track was made with my PDA a HP Ipaq HW 6915, the program was GPSTuner 5.4. The track is converted with Route Converter 1.29 to GPX.
My question is what went wrong or what did I wrong.
Sorry about my sentence building.
Henk
Netherlands.
I am new here and exploring Microsoft Streets & Trips 2010.
I imported a GPX file into S&T 2010 and thought every thing went fine, after zooming in on the track I something very strange, the track left the Interstate almost on every Exit and went on the Interstate at the next Exit.
Sometimes the track was on a highway parallel on the Interstate and some times the track went back via an Exit on the Interstate in the opposite direction.
The track mentioned above was made by my self last year, from Detroit to Gary for 100 % on Interstate 94. The track was made with my PDA a HP Ipaq HW 6915, the program was GPSTuner 5.4. The track is converted with Route Converter 1.29 to GPX.
My question is what went wrong or what did I wrong.
Sorry about my sentence building.
Henk
Netherlands.
Hi Henk,
:welcome: to Laptop GPS World.
You've come across an "imperfection" of Microsoft Streets & Trips. The program doesn't route well when a "Stop" is set at a limited access highway. In my experience, when you move such misbehaving stops with your mouse a few millimeters, then the routing corrects itself.
(Thanks for editing your posting by adding the screen shot. That helped me understand the issue )
:welcome: to Laptop GPS World.
You've come across an "imperfection" of Microsoft Streets & Trips. The program doesn't route well when a "Stop" is set at a limited access highway. In my experience, when you move such misbehaving stops with your mouse a few millimeters, then the routing corrects itself.
(Thanks for editing your posting by adding the screen shot. That helped me understand the issue )
I would not be to quick to blame the problem on S&T; it could be coming from the source mapping software.
Actually, I find that if I place a waypoint or "Stop" on an Interstate, S&T performs quite happily with that waypoint.
I think the bottom line is that any time you import a GPX file, it is probably a good idea to check in detail whether or not the route features are where you want them to be. It is best not to be too trusting.
Actually, I find that if I place a waypoint or "Stop" on an Interstate, S&T performs quite happily with that waypoint.
I think the bottom line is that any time you import a GPX file, it is probably a good idea to check in detail whether or not the route features are where you want them to be. It is best not to be too trusting.
Henk, would the routing be as expected if you delete all the stops from 27 to 33?
Marvin,
Thanks for your reply.
If I remove all the stops where I haven't been, then the route will be as we drove it last year.
Thus importing a converted track(trk) to GPX doesn't make any sence. It's easyer to make a new trip and ad the stops between startpoint and endpoint. As spadefush also mentioned.
Henk
Thanks for your reply.
If I remove all the stops where I haven't been, then the route will be as we drove it last year.
Thus importing a converted track(trk) to GPX doesn't make any sence. It's easyer to make a new trip and ad the stops between startpoint and endpoint. As spadefush also mentioned.
Henk
Similar Topics