HomeMicrosoft


How to export a route from Microsoft Streets and Trips 2010 to Garmin Nuvi
zrxh14
Malaki, your GPS does not support routes.
malaki86
Actually, I think I killed the stupid thing...

I copied the file to the GPX folder, just like it said. Unplugged it from the computer and now it won't boot up - it gets stuck on the "Loading Maps" screen. At one point it did come up with a full page warning that said something along the lines of "No detail maps can be located". I plugged it back into the computer and still have nothing - the computer doesn't even see it now...

Time to call Garmin...
malaki86
Yup - I killed it. Garmin doesn't think it was the file I uploaded - they think when I disconnected the unit from the laptop it may have surged the power in it just enough to wipe the on-board memory... $69 for a repair for it. I may just trash it (it's just over 2 years old now and was only $200 new) and get a new one.
Ken in Regina
Quote:
Originally Posted by malaki86
I found this page which gives a little info on exporting the actual route:
Sorry to be so picky but it doesn't show how to export the actual route. It gives info on how to export the route points (and it says that).

As has been mentioned in various threads about the new GPX capabilities of Streets, it does not export the actual route, only the route points.

Let me illustrate. First, here's the relevant portion of the GPX file that Streets exports for a short route:
Code:
<rte>
<rtept lat="50.4863338172436" lon="-104.643798060715">
<name>Dalgliesh Dr, Regina SK</name>
</rtept>
<rtept lat="50.4769691359252" lon="-104.57678466104">
<name>Hodsman Rd, Regina SK</name>
</rtept>
</rte>
That's it. Just the route points.

Now here's what Garmin's Mapsource program exports when you ask it to export the same route:
Code:
<rte>
<name>Dalgliesh Dr to Mcdonald St N</name>
<extensions>
<gpxx:RouteExtension xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3">
<gpxx:IsAutoNamed>true</gpxx:IsAutoNamed>
<gpxx:DisplayColor>Magenta</gpxx:DisplayColor>
</gpxx:RouteExtension>
</extensions>
<rtept lat="50.4861104" lon="-104.6440523">
<time>2009-10-09T03:46:28Z</time>
<name>Dalgliesh Dr</name>
<cmt>Dalgliesh Dr</cmt>
<desc>Dalgliesh Dr</desc>
<sym>Waypoint</sym>
<extensions>
<gpxx:RoutePointExtension xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3">
<gpxx:Subclass>0600DD487B00A5CD010001802200110E0000</gpxx:Subclass>
<gpxx:rpt lat="50.4861104" lon="-104.6440523">
<gpxx:Subclass>0600DD487B00A5CD010021160000FC050E00</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4863405" lon="-104.6437454">
<gpxx:Subclass>0600DD487B00A5CD01001F000600AC949B00</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4876280" lon="-104.6437454"/>
<gpxx:rpt lat="50.4876280" lon="-104.6437454"/>
<gpxx:rpt lat="50.4890871" lon="-104.6437454"/>
<gpxx:rpt lat="50.4894304" lon="-104.6437454"/>
<gpxx:rpt lat="50.4896879" lon="-104.6437454">
<gpxx:Subclass>0600DD487B0095D801001F0206006B944900</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4896879" lon="-104.6412992">
<gpxx:Subclass>0500DD487B00A88606001F02060084940001</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4896879" lon="-104.6412992"/>
<gpxx:rpt lat="50.4847097" lon="-104.6412992"/>
<gpxx:rpt lat="50.4844093" lon="-104.6412992"/>
<gpxx:rpt lat="50.4841948" lon="-104.6412992">
<gpxx:Subclass>0500DD487B00D08806001F261600FBD80900</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4841948" lon="-104.6409988">
<gpxx:Subclass>0500DD487B00D88606001F00160020D99802</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4842377" lon="-104.6404839"/>
<gpxx:rpt lat="50.4850531" lon="-104.6327162"/>
<gpxx:rpt lat="50.4850960" lon="-104.6325445"/>
<gpxx:rpt lat="50.4856110" lon="-104.6276093"/>
<gpxx:rpt lat="50.4856110" lon="-104.6276093"/>
<gpxx:rpt lat="50.4859114" lon="-104.6243906"/>
<gpxx:rpt lat="50.4860401" lon="-104.6233606"/>
<gpxx:rpt lat="50.4864264" lon="-104.6188974">
<gpxx:Subclass>0200DD487B006A7407001F001800610A4D01</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4864264" lon="-104.6185541"/>
<gpxx:rpt lat="50.4864264" lon="-104.6182108"/>
<gpxx:rpt lat="50.4865122" lon="-104.6076536">
<gpxx:Subclass>0200DD487B00567107001F001800430A7803</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4865122" lon="-104.6064949"/>
<gpxx:rpt lat="50.4865122" lon="-104.6046066"/>
<gpxx:rpt lat="50.4863834" lon="-104.6028900"/>
<gpxx:rpt lat="50.4861689" lon="-104.6015167"/>
<gpxx:rpt lat="50.4859114" lon="-104.6005297"/>
<gpxx:rpt lat="50.4856539" lon="-104.5998859"/>
<gpxx:rpt lat="50.4856539" lon="-104.5998859"/>
<gpxx:rpt lat="50.4853106" lon="-104.5989418"/>
<gpxx:rpt lat="50.4848385" lon="-104.5980835"/>
<gpxx:rpt lat="50.4826069" lon="-104.5946503"/>
<gpxx:rpt lat="50.4826069" lon="-104.5946503"/>
<gpxx:rpt lat="50.4812336" lon="-104.5925903"/>
<gpxx:rpt lat="50.4797316" lon="-104.5902300"/>
<gpxx:rpt lat="50.4793453" lon="-104.5896721"/>
<gpxx:rpt lat="50.4782724" lon="-104.5878696"/>
<gpxx:rpt lat="50.4763412" lon="-104.5836210">
<gpxx:Subclass>0900DD487B006D7207001F8A1800320A7C00</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4745817" lon="-104.5805311">
<gpxx:Subclass>0900DD487B006D7207001F2616001CD81A00</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4745817" lon="-104.5805311"/>
<gpxx:rpt lat="50.4742384" lon="-104.5798016">
<gpxx:Subclass>0300DD487B00D9FA06001F00170065892500</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4744959" lon="-104.5795441"/>
<gpxx:rpt lat="50.4746675" lon="-104.5793295"/>
<gpxx:rpt lat="50.4748821" lon="-104.5791149">
<gpxx:Subclass>0300DD487B006DF706001F00170076891200</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4751825" lon="-104.5787287">
<gpxx:Subclass>0300DD487B006DF706001F0017002D891F00</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="50.4757347" lon="-104.5781766">
<gpxx:Subclass>0300DD487B006DF706002117000031000000</gpxx:Subclass>
</gpxx:rpt>
</gpxx:RoutePointExtension>
</extensions>
</rtept>
<rtept lat="50.4757348" lon="-104.5781766">
<time>2009-10-09T03:47:30Z</time>
<name>Mcdonald St N</name>
<cmt>McDonald St N</cmt>
<desc>McDonald St N</desc>
<sym>Waypoint</sym>
<extensions>
<gpxx:RoutePointExtension xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3">
<gpxx:Subclass>0300DD487B006DF7060001800100811E0000</gpxx:Subclass>
</gpxx:RoutePointExtension>
</extensions>
</rtept>
</rte>
As you can see, there's a bit of difference between exporting the actual route and only the route points. ;)

Specifically, the Streets export file does not provide the route it calculated. It doesn't provide a usable route at all, only the points in the route. The route has to be recalculated by the receiving program or device and may not be exactly the same as what Streets calculated.

The full route file, as exported by Mapsource, is the exact route as calculated by Mapsource. Any other program or device that can use the full detailed route file will follow it exactly as originally calculated.

Just for the record, Streets also won't import a full detailed route file. It will only import the route points, so you can't necessarily duplicate a route that was calculated in another program or device. You have to get Streets to recalculate it. It might create an identical route and it might not.

Disclaimer: This is not a criticism of Streets&Trips GPX capabilities, just a tutorial so people will have correct expectations of what it will and won't do regarding Route Import/Export.

...ken...
zrxh14
Ken, what you say is obviously true. However, if I create a route in S&T 2010 and Export to GPX I put it in the Garmin GPX folder. Then I go to My Data and import that route. Then I call up that route and it shows the map of the route. If the Garmin calculates the route I don't care as I have seen how the route goes in S&T and have put in enough points to make it route where I want it to go. Still much easier than creating the route in the Garmin.
tcassidy
The chances are the device receiving the list of waypoints in this format is quite capable of creating its own route. As has been stated before, that might not be the same route in a complex trip. However, I think that is the exception, not the rule. Although the 2 devices may (or may not) use the same map data, I would want the final device to do the routing. What it needs is the list of stops in the correct order and instructions that it is a route, not a collection of waypoints. the basic gpx export appears to perform that function.

Terry
Ken in Regina
As I said, that post was not intended as a criticism. It's simply important that people who want to use that feature have appropriate expectations.

Anyone who only wants to use Streets for planning and then transfer the Start, Stops and End points to another program or device so they don't have to enter them again will be very happy with the feature. This is probably the majority of people who will use it.

Anyone who wants to be able to share an exact route without having to add enough extra Stops in it to force it to work properly on any possible routing calculation will be a little disappointed. They're going to have to insert enough Stops in Streets to ensure that whatever program or device it goes into will reproduce the same route.

I'm just saying....

...ken...
onelostronin

Okay somewhat new to forums but I know enough to research my question and hopefully not force anyone to repeat what has been stated.

However after weeks of trying to get an answer through Garmin and Microsoft and various web based searches I am still at a loss.

Garmin Nuvi 255 and 270 series. MIcrosoft Streets & Trips 2010. I optimize a multi stop route, export to .GPX file and load into the Garmin via MS Live, POI, Mapsource, Direct to device, via SD card. No matter what it takes the optimized order and re-orders it either by numeric or alpha. Mapsource wil recalculate but if its end result is considered "optimal" then I might as well go back to pencil and manual route sheets. It does not take direct roads to a location, it goes past a stop or around the block.

Any help beyond what is already on this site would be much appreciated.
t923347
I think your biggest problem is that you have 2 Nuvi devices that don't support multi point routes. So what your loading to the Nuvis in the GPX files are really just waypoints. Waypoints on a Nuvi will only be shown in distance order from your present location.
Ken in Regina
There a couple of quirks in Garmin's routing and in Streets&Trips placing of waypoints that might be having an impact.

First, as you have already discovered, Garmin's devices never use the route as it was transferred to them. They always recalculate. Always. Even if you calculate a perfect route on Mapsource and transfer it to either of your Nuvis, the Nuvis will just recalculate it again anyway. Sometimes they'll give the same results. Sometimes not.

But that's not one of the quirks I want to mention.

First, Garmin's routing calculations will always try to put you on the correct side of the street if you are navigating to anything containing an address (address search, Favorite with an address, POI, etc.). Sometimes that means taking you off the intuitively most direct route past that stop and shuttling you around the block so you get to that stop on the correct side of the street for stopping/parking.

Second, Streets&Trips has the odd habit of sticking "route point" locations near, but not exactly at, the actual address.

If you do some address searches and save the results as pushpins, then select a few of those pushpins to use in a multi-stop route, take a look very closely (zoom in really tight) at the actual stop location (yellow block) on the map and you will see that sometimes it is not exactly at the pushpin location. Depending on where it actually put the stop location, this can have an effect on how the route will be calculated when transferred to a Garmin device.

Another thing to consider is whether you have identical routing preferences set in the source program (e.g. Streets&Trips) and the target device (Mapsource or Nuvi). This is not easy and it's so not intuitive. Garmin's preferences are relatively obvious (shorter time, shorter distance, Avoid: u-turns, toll roads, limited access roads, etc.). But Streets&Trips has a bunch of sliders that default to the middle and aren't especially obvious about what they'll actually do if you move them either way. What is clear from my experience is that the default middle setting is nothing like the defaults Garmin provides in the time/distance and Avoid settings.

I know you probably wanted a simple solution rather than a long-winded description of things that might be causing the problem, but without a lot more detail, including exact examples of the waypoints, it's not possible. I have Streets&Trips 2010 and a Nuvi 765T so I could look at a specific example if you wanted.

If your Nuvi models don't fully support multi-point routes (e.g. routes with Vias), as was mentioned, that's a whole other issue, too. Many Nuvi models do not.

...ken...
Jax
This is great site for an information junkie (which is me!!).

I'm a newbie. I just bought my first GPS - Garmin Nuvi 855 for several reasons - accepts voice commands, adding Streets & Trips files and use it for geocaching. This is my retirement gift to me to keep my brain working

This is my first post (newbie at this also.) Anyway, after this preamble, thanks to the leads I actually managed to load a .gpx file onto the 855 last night and got a simulated drive (its amazing what these things can do). This morning I goofed and removed the data from the route so will try again tomorrow and report back on how the gps worked with the .gpx file.

Again, As an aside, I initially used the information from this site to set up my netbook (Acer) with S&T & GPS but quickly decided that I didn't want to use the netbook in the car. Then I used the site to explore whether I could follow through using Streets & Trips with an automotive GPS. I have also used the site to understand Garmin's broad range of maps and licensing restrictions. (Didn't I say I was an information junkie!!)

So
Marvin Hlavac
Hi Jax, :welcome: to Laptop GPS World. It's good to have you here.
Ken in Regina
Thanks for the feedback, Jax. It's very helpful to know not just that folks are benefiting from the site but also getting an idea of how they are benefiting. It's especially useful when it comes from folks like yourself who found most everything they needed just by reading. Sometimes those of us who are active on the site forget just what a knowledge base gets built up in these discussions over time.

For what it's worth, I've been trying to make my laptop or my netbook work for me in the car but it's just too intrusive for us. So I continue to use a personal navigation device. I just bought a Nuvi 765T a few weeks ago and I'm still exploring its possibilities. I've managed to move my ~200 waypoints to it. I like that it supports multiple categories for each waypoint and also that I can get addresses and a phone number into it.

I've also loaded a whack of custom POIs into it (golf courses in Western Canada, Superstore gas bars in Western Canada, Ikeas in North America, etc.). Now that I know how to do that I'm going to take a look at the POI Megafile and see if I can get it into the Nuvi and Mobile PC.

But first I'm going to upgrade my desktop from WinXP to Win7 this weekend.

...ken...
tcassidy
Upgrading from XP to Win 7 is child's play compared to putting custom POIs in Mobile PC.

Terry
Jax
Well, here's what happened on the way to work. The imported Streets & Trips worked just dandy (voice prompts and all) until I detoured from the route. The last I heard from the Nuvi was "recalculating"!! So it seems with the 855 it is possible to import a route and have the file work nicely but one deviation from the route and the Nuvi doesn't know what to do. What can one say, it is a computer after all.

I recently upgraded from Vista to Windows 7 and wondered if all my maps and connections would work. They have, like a charm. I much prefer Windows 7 to Vista.

Lastly, this information junkie missed the part in the 855 specifications that says it is not geo-caching friendly. I'm not daunted. I've downloaded a couple of local caches to try out.

I'm heading to Sedona in May - lots of route planning and POI's to explore and add.

Cheers
laptopgpsworld.com About