Grasscatcher Posted April 8, 2010 Share Posted April 8, 2010 Here's the problem.... I hike a lot in some rugged terrain and create "pre-hike routes" from aerial photos, several topo maps, etc. Generally, the first route point is placed at a point on an established trail where I need to leave that trail (based on topography) to start bushwhacking cross country "toward" point #2, then 3, etc. In most cases, this is NOT the shortest distance between #1 and #2. (ie possibly detour off to a side canyon that intersects at Pt #1 and angles away. Pt #2 may be a mile up/down that canyon but only 1/4 mile from the closest point on the established trail) If I create this route, starting at other than my present location, then send it to my Garmin (Oregon 550, 76CSx, 76CS) and select it to use for navigation, my unit (any,all) start with directions to Route Point #2.........I DON'T NEED to be directed to Pt#2 YET...... I NEED to be directed to Pt#1 first, ......THEN to Pt #2. In many cases, I/You cannot physically get "directly" to point #2 from current location. I can "force" it to direct me to the starting point #1 only by adding a second, duplicate Route Pt #1 to the route ( now I have Two Number 1s) which seems redundant and stupid , like a philosophy that may have originated in Washington DC. If a "Track" is selected to be used for navigation, the unit(s) correctly direct the user to the "Start Point". This would mean that any "track" used would have to be a hand drawn guesstimate (since it hasn't yet been traveled and logged), then the user would have to manually switch from the "track" to the "route" once they were "on course" As I said, I have a "work around" that so far works, but seems so unnecessary. How many people have been confused by being mistakenly directed to th incorrect point? Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.