How to...? Share my adventure, "Save as...", join tracks, and download waypoint symbo

How do I join contiguous tracks, without BaseCamp adding a straight like from the beginning of the first track to the end of the second track? I.e., how do I tell BaseCamp that I want a one-way track, not a loop?

How do I "Save as..." an adventure? I.e., I want to edit my tracks and waypoints without losing the original tracks.

Can I download more waypoint symbols from somewhere? I need "junction," "trail," "cairn," and "warning."

How do I send my adventure to my friends? I tried to upload the adventure to myGarmin.com but it didn't work. I looked on my.garmin.com but I didn't see where adventures upload to. Where is my adventure stored in my computer? Can I e-mail the file to a friend?

0 Former Member over 11 years ago

1. Basecamp always joins tracks from head to tail, e.g., tracks are directional. So, before joining you need to ensure the tracks are both going in the direction you wish. If one is not then right click on it and invert it

2. Duplicate the tracks and then work with the duplicates. Again, right click and duplicate

3. Short answer: no, you can't. If you want custom symbols make them yourself. Be aware that not all GPS devices have the same symbol set and if you make custom symbols you will need to put the on the GPS device.

4. Don't know.

0 azdrmn over 11 years ago

1. BaseCamp will add a line from the end of the first track to the beginning of the second track. Change the order of the tracks in the dialog to make sure the tracks are in the right order and as August said, you can reverse the tracks using the gear icon menu if needed, but that's unusual.
4. By far the easiest way to share your adventures is by publishing them. When you say it didn't work, what happened? There should have been an error message. Unfortunately, sometimes it requires more than one try. The number 1 reason that uploads seem to fail is pictures with non-standard characters in the name.

0 TDKEHOE over 11 years ago

1. That worked! Thanks!

2. I'm hoping to take my adventure and then add a proposed route for our next trip. If I duplicate the tracks I'll have to start over. Is there a way to duplicate a finished adventure?

3. Custom symbols aren't important, no problem.

4. The problem with publishing my adventure is that it uploads halfway, then hangs. I tried removing the photos, and putting them back with filenames that are just ABC123, etc., and resizing them from several megabytes to around 500K. That didn't help. Then I removed all the photos and it uploaded without a problem. Is there a limit to the number of photos, their size, etc.?

0 azdrmn over 11 years ago

2. I'm hoping to take my adventure and then add a proposed route for our next trip. If I duplicate the tracks I'll have to start over. Is there a way to duplicate a finished adventure?

I may not be understanding your use case, but you can add data including a route to your adventure.

4. The problem with publishing my adventure is that it uploads halfway, then hangs. I tried removing the photos, and putting them back with filenames that are just ABC123, etc., and resizing them from several megabytes to around 500K. That didn't help. Then I removed all the photos and it uploaded without a problem. Is there a limit to the number of photos, their size, etc.?

There isn't a limit (that I know of). There is one adventure with 1600 pictures! The pictures are automatically scaled to 1 megapixel on upload, so the size of the originals shouldn't matter either. I'll talk to our server team and see if they can see why you are having an issue. If your myGarmin ID is different than your forum ID, please PM me with it.

0 azdrmn over 11 years ago

4. The problem with publishing my adventure is that it uploads halfway, then hangs. I tried removing the photos, and putting them back with filenames that are just ABC123, etc., and resizing them from several megabytes to around 500K. That didn't help. Then I removed all the photos and it uploaded without a problem. Is there a limit to the number of photos, their size, etc.?

I checked with our server group and they see your failed attempts, but for some reason no pictures were being sent. So 2 questions: Are you using the Mac or Windows version of BaseCamp? How many pictures are you sending when it fails? Apparently there is a scaling issue with Windows BaseCamp that has some problems if you try to publish more than 50 pictures. I know of no such issue with the Mac version. Either way you may try adding 20 pictures to your already published adventure and see if it works. Sorry for the inconvenience.

0 Former Member over 11 years ago

When I try and publish I get "Failed to resample, then the name of the picture" Any idea what I'm doing wrong?

0 azdrmn over 11 years ago

When I try and publish I get "Failed to resample, then the name of the picture" Any idea what I'm doing wrong?

I've never seen that issue. Can you send the original picture so we can try to reproduce and hopefully fix the issue. Thanks.

0 kevingardner_ over 11 years ago

I have this issue too. It fails on the first photo in the adventure. If I delete this photo it then fails on the next, so I surmise it will fail on all of them. Any ideas ? There is no context with the error message, simply "Failed to resample....."

0 azdrmn over 11 years ago

If you'll attach a copy of one of the photos (or send it to [email][email protected][/email]), we should be able to diagnose and hopefully fix the issue. What was the picture taken with? Thanks.

0 Former Member over 11 years ago

Failed to resample photo on publishing changes issue still there in basecamp 2.3.1.0

If you'll attach a copy of one of the photos (or send it to [email][email protected][/email]), we should be able to diagnose and hopefully fix the issue. What was the picture taken with? Thanks.

I uploaded an adventure successfully with pictures. I then locally updated the adventure description and hit "publish change" I then get the "failed to resample <photofile> message. I don't think it's the photo, as I deleted the forst that t was trying to "resample" and it complained about the second -- and these photos had already been published.