I'm having an issue with one of my GPS files:
SEO15 Crix n Creeks <-downlaod link from dropbox
If someone could download it and send it on their GPS and see if it accepts it.
I'm sure it will come up in your Basecamp as this is native to the file. I made it with via points, probably too many!?.
Will not load from Basecamp onto my Zumo 665. Too many via points. I know for some of the dirt bikes GPS runs we break a loop into sections so that the entire loop will load as a number of routes. A Garmin 660 series GPS is limited to 200 Via Points per route. Some Garmins have a limit of 50 via points per route.
Thanks Bill. Same thing with my gips,but I think I'm allowed up to 5000 VP's; only now after the latest software update. I have re-made the route with less via-points but 200 is pretty skimpy on a 300mi route with many twists and turns and many hop over roads connecting-to. Of course if I go with too little of VP's, then we get some straight lines on some of the tight turns (for the longer loops), and, considering the wide variety of Garmin Mapsets that will probably be used at this event, I was trying to basically "force" the route.
Now, if everyone loads the .GPX (files) into their BaseCamp first before exporting the route to their gips, then S/B no problem, as you can always use the "recalculate route" trick if it doesn't match the users mapset.
I'm only being finicky with this because last year, after following the "West Loop" several of us came back and said those maps had glitches. Like the road went in both directions with no indicationof which way to go etc. Small things I know, but I'm trying to do better than that, and, with the vast array of GPS's and (questionable) users knowledge of making these routes their own
. It all comes down to incompatibility of maps (mapsets).
I'm using Garmins latest build of:
CN North America NT 2015.40
Now if I create a
track (w no turn by turn directions) it seems to be more adaptable to other mapsets (I'm testing with a couple of older Nuvi's). But, a
route with TxT directions (in BC with it's default and much more basic mapset), the route sometimes is off a tad on some of the roads or turns. So I've been using my GPS's mapset (above) as I have free lifetime updates, plugged into BC to use that mapset. I can use very few VP's and have it match up perfectly, but this seems to not be very acceptable to older Gips. Not only viewing in BC, but exported and reviewed within the GPS itself; where the real test is.
So that's why I have been leaning so heavy on the VP's (or old term WayPoints). I'm making the VP's as not tracked or displayed (background embedded), so they are invisible to users, but, I still want to have as many as possible for accuracy amongst all the different Gips we'll have using them.
If everyone is BC savvy?, then it doens't matter; as they can just recalculate the route with their Gips connected to BC and it will align right up exactly to their mapset. But, I know many "dislike" BC and probably do not want to do this. So my experimenting goes on..............
I made some w more last year, maybe the last updat to my GPS has nixed this extreme number of via points. I can easily chop the via points down and still keep the loop intact. Back to work, thanks Tim!
