[BaseCamp] waypoint naming rights
saddle sore
ironbutter at gmail.com
Mon May 18 14:55:49 PDT 2015
I deeply appreciate this group!! Maura's explanation makes sense but is
not the intuitive process for me. I naturally thought that the duplicated
route was a route of the duplicated waypoints. Heck, there's only one
route and a number of waypoints in the List, so common sense to me is that
the route is connecting THOSE waypoints. Well, learn something new every
day. So after changing the names of all my bonus sites and my gas receipt
locations to the way I want them to show up on my GPS screen, I created a
route with them. Ta-da, it worked. Thanks everyone. I appreciate being
untangled -- even if it will simply be for just a short time.
On Mon, May 18, 2015 at 2:48 PM, -=maura=- <moteramaura at gmail.com> wrote:
> The fundamental nature of a route is that it is a collection of specific
> waypoints and how to connect them. If you change the waypoints, duplicate ,
> copy , rename whatever, you have manipulated waypoints, but your route is
> not a collection of these manipulated waypoints, it is a collection of the
> original waypoints. Manipulate your waypoints then make a new route,
> following the path of the old.
>
> Maura
> in
> Vancouver, Canada
>
>
>
> On 18/05/2015 9:45 AM, Greg Horodeck wrote:
>
>> After more thinking, the sequence I outlined should be altered slightly:
>>
>> 1. Create a new List
>>
>> 2. Create your waypoints (original names) and verify using Google Earth
>> Pro
>>
>> 3. Create and finalize your route
>>
>> 4. Export the waypoints from the List (select just the waypoints and use
>> the
>> "Export Selection" option in the Export menu choice)
>>
>> 5. Rename your waypoints to match your sequential naming scheme
>>
>> 6. Import your saved waypoint names (original names) from the file saved
>> in
>> step 4
>>
>>
>> Greg
>>
>> -----Original Message-----
>> From: Greg Horodeck [mailto:greghoro at gmail.com]
>> Sent: Monday, May 18, 2015 11:30 AM
>> To: 'BaseCamp'
>> Subject: RE: [BaseCamp] waypoint naming rights
>>
>> Not sure why this is happening but let me suggest an alternative approach
>> to
>> address this. Some of these steps you have already done.
>>
>> 1. Create a new List
>> 2. Create your waypoints (original names) and verify using Google Earth
>> Pro
>> 3. Export the contents of the List 4. Rename your waypoints to match your
>> sequential naming scheme 5. Create your route using renamed waypoints 6.
>> Import your originally saved waypoint names from the file saved in step 3
>>
>> Greg
>>
>>
>> -----Original Message-----
>> From: Basecamp [mailto:basecamp-bounces at micapeak.com] On Behalf Of saddle
>> sore
>> Sent: Monday, May 18, 2015 8:24 AM
>> To: BaseCamp
>> Subject: [BaseCamp] waypoint naming rights
>>
>> OK, I'm gettiing wrapped around the axle on this exercise. See if you can
>> help untangle me.
>>
>> I have all the Tour of Honor sites loaded. I created a Saddle Sore route.
>> I figured where my gas stops would be and created waypoints for those.
>> Checked everything on Google Earth Pro. So now I want to rename the
>> waypoints SPECIFICALLY to this route, and do not want to mess up the
>> original names or point locations. So I created a new List and moved the
>> route to that List. The only thing I want in this List is things related
>> to
>> this route. When I copied the route to the List, it also copied the
>> waypoints. So I selected everything and opted for Duplicate. So as to
>> not mess up the original names and locations, I selected each original and
>> clicked on Remove From List. This left me with the duplicate waypoints
>> and
>> route. Everything has the original name followed by the number 1, proving
>> it is a duplicate. Good so far.
>>
>> Now I want to rename the waypoints so that I can name them chronologically
>> for this ride, starting with my first gas receipt as 001-Name, then the
>> next
>> stop would be my first TOH site so it would be 002-name, etc.....
>> This way I can load the entire route into my GPS as well as load in all
>> the
>> waypoints -- giving me flexibility to travel by the route or travel by
>> point
>> to point. Still with me?
>>
>> OK, so I open the duplicate named TOH site, rename it, and close the
>> properties box. I do this for a few more waypoints before I realize that
>> the changed name is sitting in the data box on the BC screen like it
>> should,
>> but when I open the route properties box the original name is there. So I
>> flip back over to the original List where all the TOH sites
>> are located and I see the site name has changed there!! Noooooo, I want
>> the original List to remain unchanged and I want all the changes to be
>> happening in the new List where I have all of the duplicated sites.
>>
>> Any ideas why I can't get the duplicated waypoint to have a changed name
>> and
>> have that changed name show up in the duplicated route properties box??
>> The
>> changed name is showing up in the data box on the BC screen but
>> it won't transfer into the route properties box I always thought this is
>> exactly what the duplicating process of waypoints was for - so the
>> originals
>> would remain as original and the changes could be done using the
>> duplicates.
>> Thus when I am done with this ride, I can delete the duplicates and still
>> have the originals left in the original List.
>> Unfortunately, it is not working out that way.
>>
>> Any help/insight would be appreciated,
>> Joe Y
>> western PA
>>
>> To make _ANY_ changes, including unsubscribing from this list, click
>> ----->http://micapeak.com/mailman/listinfo/basecamp
>>
>>
>> To make _ANY_ changes, including unsubscribing from this list, click
>> ----->http://micapeak.com/mailman/listinfo/basecamp
>>
>>
>>
>
> --
> Maura Gatensby Architect 22-1075 Gilford Street Vancouver BC Canada V6G
> 2P3 tel 604 669-6391 cel 604 773-0444 Member of the Architectural
> Institute of British Columbia Certified Professional cel 604 773-0444
>
>
> To make _ANY_ changes, including unsubscribing from this list, click ----->
> http://micapeak.com/mailman/listinfo/basecamp
>
>
More information about the Basecamp
mailing list