Adding GPX files to Basecamp?

[Ex-Call Centre Chimp]

Hi,
I have an organised bicycle ride planned & would like to add the route to my Nav V.



The organiser is good enough to send us links to upload GPX files which I download onto my laptop no problem.



I can get these onto my bicycle Sat Nav/Computer easily enough but for the life of me cannot see how to grab them from the laptop & add them to Basecamp so I can then add them to the Nav V.
Any tips please?

 

[AberdeenAngus]

Wapping to the Basecamp help desk please. Wapping to the help desk.

 

[Redboots]

Any tips please?

1. Click File from the File menu
2. Click Import
3. Browse to the GPX file location from the Import File window
4. Click open for Windows or import for MAC

The information in the GPX file will now be displayed under Library in the My Collection and Recently Imported from folders.

 

[Ex-Call Centre Chimp]

Cheers, appreciate it. I've just done that (thanx again) but for some reason the route has been shortened quite considerably somewhere along the line from 103 miles to 66? I've limited the no. of way points to 10. I wonder if that could be the problem.....
More fannying around to be done I suspect.



Setting it to 'automatic' keeps the same route (103 miles) but creates 753 waypoints.

Arse.It won't save it now - too many waypoints I suspect. Bollocks. Anybody know how many the unit can handle so I can over-ride the automatic setting to an appropriate level?


Edit: What I have noticed is that once you've imported the route you can choose a route preference of:
Faster Time (default)
Curvy roads
Off Road
Or
Shorter Distance.

 

[walrus]

The answer might be in here. Nicked form an earlier post.

https://www.youtube.com/watch?feature=player_embedded&v=T-2wOLCqrjg

 

[Ex-Call Centre Chimp]

Cheers. Aye I saw that which is why I started by dropping the no. of waypoints to 10. Thanx again though, appreciate the gesture.

 

[Bumpkin]

I suggest that you just use the routing tool to trace the imported track to create a new route. I accept that this isn't the automated solution that you're looking for but it's quick to do and allows you to select the placement of the via-points/nodes yourself.

 

[Wapping]

I think that tracing over might be the only option.

Do take a bit of care though:

1. That you trace the direction of travel in the correct direction

2. I had a problem when I traced over some routes created on a PC in Mapsouce. When I went to load the route into my Nav V it would not load. Now, this was in the early days of mucking about in BaseCamp and with a Mac, so it's quite possible I did something wrong. That being said, I do know that there is a difference between Mapsource and BaseCamp files, meaning that old Mapsouce files will not load. I think, after tracing, some vestige of the Mapsouce route remains, blocking transfer.

Have a play about. The great thing is that you can't break it.

 

[Wapping]

PS It may be easiest to have the route open in one window and copy it manually into BaseCamp in another window. I have done this several times.

 

[Ex-Call Centre Chimp]

Thanx guys, appreciate the help.
In actual fact I did manually create the route which took about 2 hours but there's a tiny part of one road that Garmin's map seems to think doesn't exist. It's only about 20 yards but caused all sorts of problems. In the end I had to make 2 seperate routes, 1 from the start up to the point where Garmin thinks the road ends for 20 yards, the second starting 20 yards later going to my finish point.

Bizzarely when I imported them into the Nav V it automatically created 2 seperate routes for my part B if you see what I'm saying as the route was 'too long' ( at 93 miles).

When I look at the imported gpx track on Garmin's map it has no problem traversing the 20 yards of 'no man's land'.

You're quite right though Richard the good thing is I can fanny around with it and quickly delete the cak. I do also feel that most of the problems are user error and if nothing else I'm learning a lot about the capabilities of Base camp & the Nav V for when I really need to use them, along with confirming my own severe limitations.

 

[Wapping]

It's rare, but not unheard of, for the map to be missing about 20 or so yards of otherwise perfectly ordinary road.

I have encountered it a couple of times when plotting routes.

You can report mapping problems direct to Garmin, very easily. Do it and they'll fix it. It helps if you send them a file with the gap highlighted.



PS Without a doubt the best way to learn is to plot real live routes that you'll use. I found that out, for sure.

 

[Andy B]

It's only about 20 yards but caused all sorts of problems.

I remember a similar problem a while ago and I fixed it by plotting a track in Mapsource and then converting it to a route. I then imported it into the route where it was missing and joined it up to create one route of the whole.

It can be done - but the brain's a bit hazy on how I did it at the time!

 

[Bumpkin]

When I look at the imported gpx track on Garmin's map it has no problem traversing the 20 yards of 'no man's land'.

A true Garmin track is a record of where you've been and is not related to their mapping data either on your GPS or your computer. You could ride across a field and it would, within the limits of your GPS's accuracy at the time, faithfully record where you've been.

Converted KML files etc. will be the same.

It's only when you try to convert these to a route, and recalculate if they are straight line point to point, will they be compared to the mapping data and any anomalies become apparent

 

[Ex-Call Centre Chimp]

I remember a similar problem a while ago and I fixed it by plotting a track in Mapsource and then converting it to a route. I then imported it into the route where it was missing and joined it up to create one route of the whole.

It can be done - but the brain's a bit hazy on how I did it at the time!

Must admit I've not got Mapsource. I was hoping to be able to do all I needed on Basecamp.

A true Garmin track is a record of where you've been and is not related to their mapping data either on your GPS or your computer. You could ride across a field and it would, within the limits of your GPS's accuracy at the time, faithfully record where you've been.

Converted KML files etc. will be the same.

It's only when you try to convert these to a route, and recalculate if they are straight line point to point, will they be compared to the mapping data and any anomalies become apparent

I appreciate what you're saying but what I believe I've imported is a GPX file of an actual route. I can xfer the whole route, via the file & a 'Host' website (their equivalent of BaseCamp) to my bicycle sat nav no problem & it builds the route prefectly in less than a second.
When I xfer the GPX file into BaseCamp, BaseCamp makes it a track but shows the complete route on all of the correct roads on it's map. It's only when I try to convert that to a route that the trouble starts, and that seems to be a 'Waypoints' issue as I get a warning that there are too many waypoints so the route can't be created. Interestingly enough it was very specific today, it said that the route can't be created as there are 'More than 29 Waypoints', so the next thing I'm going to try is to over-ride the no. of waypoints to 29 when I'm converting thev track to a route in BaseCamp & see how that pans out.

It's really not that important on this occasion but as Wapping noted earlier it is proving a good practice for when I might need to use it properly.

 

[Bumpkin]

I appreciate what you're saying but what I believe I've imported is a GPX file of an actual route. I can xfer the whole route, via the file & a 'Host' website (their equivalent of BaseCamp) to my bicycle sat nav no problem & it builds the route prefectly in less than a second.
When I xfer the GPX file into BaseCamp, BaseCamp makes it a track but shows the complete route on all of the correct roads on it's map. It's only when I try to convert that to a route that the trouble starts, and that seems to be a 'Waypoints' issue as I get a warning that there are too many waypoints so the route can't be created. Interestingly enough it was very specific today, it said that the route can't be created as there are 'More than 29 Waypoints', so the next thing I'm going to try is to over-ride the no. of waypoints to 29 when I'm converting thev track to a route in BaseCamp & see how that pans out.

It's really not that important on this occasion but as Wapping noted earlier it is proving a good practice for when I might need to use it properly.

Tracks can be, and are, saved as GPX files. If it has hundreds, probably thousands, of points then it's a track for sure. To find out open the GPX file in a text editor, it's just an XML file with a different extension, and see if there's an opening <trk> tag a few lines in. Each point should be in <trkpt> tags.

Like this:

[COLOR="#B22222"]<gpx creator="Garmin Desktop App" version="1.1" xsi:schemaLocation="[url]http://www.topografix.com/GPX/1/1[/url] [url]http://www.topografix.com/GPX/1/1/gpx.xsd[/url] [url]http://www.garmin.com/xmlschemas/WaypointExtension/v1[/url] [url]http://www8.garmin.com/xmlschemas/WaypointExtensionv1.xsd[/url] [url]http://www.garmin.com/xmlschemas/TrackPointExtension/v1[/url] [url]http://www.garmin.com/xmlschemas/TrackPointExtensionv1.xsd[/url] [url]http://www.garmin.com/xmlschemas/GpxExtensions/v3[/url] [url]http://www8.garmin.com/xmlschemas/GpxExtensionsv3.xsd[/url] [url]http://www.garmin.com/xmlschemas/ActivityExtension/v1[/url] [url]http://www8.garmin.com/xmlschemas/ActivityExtensionv1.xsd[/url] [url]http://www.garmin.com/xmlschemas/AdventuresExtensions/v1[/url] [url]http://www8.garmin.com/xmlschemas/AdventuresExtensionv1.xsd[/url] [url]http://www.garmin.com/xmlschemas/PressureExtension/v1[/url] [url]http://www.garmin.com/xmlschemas/PressureExtensionv1.xsd[/url] [url]http://www.garmin.com/xmlschemas/TripExtensions/v1[/url] [url]http://www.garmin.com/xmlschemas/TripExtensionsv1.xsd[/url] [url]http://www.garmin.com/xmlschemas/TripMetaDataExtensions/v1[/url] [url]http://www.garmin.com/xmlschemas/TripMetaDataExtensionsv1.xsd[/url] [url]http://www.garmin.com/xmlschemas/ViaPointTransportationModeExtensions/v1[/url] [url]http://www.garmin.com/xmlschemas/ViaPointTransportationModeExtensionsv1.xsd[/url] [url]http://www.garmin.com/xmlschemas/CreationTimeExtensions/v1[/url] [url]http://www.garmin.com/xmlschemas/CreationTimeExtensionsv1.xsd"[/url] xmlns="[url]http://www.topografix.com/GPX/1/1"[/url] xmlns:xsi="[url]http://www.w3.org/2001/XMLSchema-instance"[/url] xmlns:wptx1="[url]http://www.garmin.com/xmlschemas/WaypointExtension/v1"[/url] xmlns:gpxtrx="[url]http://www.garmin.com/xmlschemas/GpxExtensions/v3"[/url] xmlns:gpxtpx="[url]http://www.garmin.com/xmlschemas/TrackPointExtension/v1"[/url] xmlns:gpxx="[url]http://www.garmin.com/xmlschemas/GpxExtensions/v3"[/url] xmlns:trp="[url]http://www.garmin.com/xmlschemas/TripExtensions/v1"[/url] xmlns:adv="[url]http://www.garmin.com/xmlschemas/AdventuresExtensions/v1"[/url] xmlns:prs="[url]http://www.garmin.com/xmlschemas/PressureExtension/v1"[/url] xmlns:tmd="[url]http://www.garmin.com/xmlschemas/TripMetaDataExtensions/v1"[/url] xmlns:vptm="[url]http://www.garmin.com/xmlschemas/ViaPointTransportationModeExtensions/v1"[/url] xmlns:ctx="[url]http://www.garmin.com/xmlschemas/CreationTimeExtension/v1">[/url]

  <metadata>
    <link href="[url]http://www.garmin.com">[/url]
      <text>Garmin International</text>
    </link>
    <time>2014-01-02T19:48:08Z</time>
    <bounds maxlat="35.616517066955566" maxlon="-83.708953857421875" minlat="35.302333831787109" minlon="-84.283397197723389" />
  </metadata>

  [B]<trk>[/B]
    <name>Cherohala/Dragon loop</name>
    <extensions>
      <gpxx:TrackExtension>
        <gpxx:DisplayColor>DarkGray</gpxx:DisplayColor>
      </gpxx:TrackExtension>
    </extensions>
    <trkseg>
      [B]<trkpt lat="35.465798377990723" lon="-83.919882774353027" />[/B]
      <trkpt lat="35.465948581695557" lon="-83.919882774353027" />
      <trkpt lat="35.466291904449463" lon="-83.919990062713623" />
      <trkpt lat="35.466420650482178" lon="-83.920032978057861" />
      <trkpt lat="35.466570854187012" lon="-83.92005443572998" />[/COLOR]

 

[Ex-Call Centre Chimp]

Oh right I see. That could be the problem then. Thanx.

 

[Wapping]

Just one very wild thought.

If your bicycle GPS can build the route, can it also export it once it's built it?

If so, try re-exporting the rebuilt route back to your computer and try again.

 

[JoeBiff]

............... for some reason the route has been shortened quite considerably somewhere along the line from 103 miles to 66? I've limited the no. of way points to 10. I wonder if that could be the problem.....

.

Have you checked the Activity Profile setting, in BC?

............... Anybody know how many the unit can handle so I can over-ride the automatic setting to an appropriate level?
.........

The device's limitations wont affect the number of waypoints in the GPX file you're trying to transfer.

HTH

 

[Ex-Call Centre Chimp]

Have you checked the Activity Profile setting, in BC?

Yes. I've tried the default setting, motorcycle & bicycle - doesn't appear to make any difference.

The device's limitations wont affect the number of waypoints in the GPX file you're trying to transfer.

It's actually the contrary in that the no. of waypoints on the file are too numerous for the device to handle - the message I got back was that it couldn't build a route 'because there are more than 29 waypoints'.

I appreciate your help though. Thanx.
HTH

Just one very wild thought.

If your bicycle GPS can build the route, can it also export it once it's built it?

If so, try re-exporting the rebuilt route back to your computer and try again.

Hmm. honestly I'm not sure if it can. Well, it can certainly send them to a Host system but I'm not sure if I can dig them out of there & send them anywhere else. Worth having a go though next time we have a rainy day. Thanx for the thought.

 

[JoeBiff]

...The message I got back was that it couldn't build a route because there were more than 29 waypoints...

I built a route last night from GE track, initially it had 450 points, but subsequently automatically reduced to 150 for the device - so I'm puzzled where the "29" comes from.
If it's any help, you may wish to email me the GPX file and I'd be happy to have a look on my BC, for you. Just let me know.

JB