New Garmin Montana

[atlas cached]

Originally Posted by Emmbeedee

There may be "dozens of glitches included with each firmware update" but this is only of interest if you're keeping count or they affect you directly. I can't think of one which affects me right now. I'm very happy with my Montana and 62S.

Lucky you!

Quite a few glitches/bugs currently prevent me from using my Montana as intended.

Originally Posted by Emmbeedee

Basecamp could be easier to use, but it still is better than anything else in the consumer gps industry.

I don't agree.

Have you used TopoFusion?

Much easier to use, and far more powerful than BaseCramp.... I still use it, but Garmin deliberately programmed BaseCramp to be incompatible with *.GPX files created by any other software title, so if I want to use the very advanced editing capabilities of TopoFusion, I can forget importing into BaseCramp after.

[Albie]

Originally Posted by atlas cached

I wasn't only referring to routes.

I am thinking more about the dozens and dozens of glitches included with each GPSr firmware update, and an absolute lack of useful functions/controls with their PC/MAC software. It's almost as if none of Garmins engineers actually use their own products.

Of course, that is just my opinion.

I agree 100%. Having worked in telecom and other high tech industries it amazes me how really piss poor Garmin software is.

[Rocky TFS]

Originally Posted by Rocky TFS

Perhaps the answer is obvious, but this is stumping me.

.....

Anybody actually want to answer my question?

[konfucius]

Originally Posted by Albie

Ahh, guess i need to e-mail the support team. Hit them up for more then 50 via points again as well.

Please do, it's a BIG problem! As it is now I need to split a days route into four or more pieces...


I'll send them a mail again to.

[AugustFalcon]

Originally Posted by atlas cached

... but Garmin deliberately programmed BaseCramp to be incompatible with *.GPX files created by any other software title, so if I want to use the very advanced editing capabilities of TopoFusion, I can forget importing into BaseCramp after.

Perhaps if TopoFusion and other folks actually wrote their GPX files to more strictly adhere to the published standard there would be fewer problems reading them in BaseCamp.

The Garmin BaseCamp team is looking into relaxing their input code so tht it will not so strictly enforce the published standards.

You might also try running the non-standards compliant code through something like GPSBabel to rewrite it to the published standard before importing it into BaseCamp.

[DRTBYK]

Originally Posted by Rocky TFS

Anybody actually want to answer my question?

The issue you have is that the Montana is trying to route you but it still has data from a previous map set. The Montana does not support using Route data from a map set that is not equivalent to the one on the unit.

You WILL need to recalculate your old Routes using the same map version in BaseCamp as the one on the Montana. I repeat, you will need to RECALCULATE your Routes - NOT recreate them. And yes, you will want to check your recalculated routes to make sure that they are now taking the same path as before.

If you want to use Routing this is the price you pay. I don't think Garmin is going to change that condition.

Cheers,

[DRTBYK]

Originally Posted by AugustFalcon

Perhaps if TopoFusion and other folks actually wrote their GPX files to more strictly adhere to the published standard there would be fewer problems reading them in BaseCamp.

I absolutely agree. I spend way to much time "fixing" GPX data from these great applications to enable it in the "STANDARDS" world of Garmin. Don't forget, this community was one of the loudest when it came to Garmin getting onboard with the GPX standard. I for one am glad they did.

My only request of BaseCamp with respect to GPX compliance is that the program give me the line # that failed so I don't have to retest the file in my XML editor to find it.

Cheers,

[atlas cached]

Originally Posted by DRTBYK

I absolutely agree. I spend way to much time "fixing" GPX data from these great applications to enable it in the "STANDARDS" world of Garmin. Don't forget, this community was one of the loudest when it came to Garmin getting onboard with the GPX standard. I for one am glad they did.

My only request of BaseCamp with respect to GPX compliance is that the program give me the line # that failed so I don't have to retest the file in my XML editor to find it.

Cheers,

OK, I can try this.

Which XML editor do you test GPX files with?

[DRTBYK]

Originally Posted by atlas cached

OK, I can try this.

Which XML editor do you test GPX files with?

First thing I do is run bad files through XML Validator

Then for GPX specific issues (and other XML stuff) I use XMLmind's XML Editor Professional Edition on my Mac.

Cheers,

[atlas cached]

Originally Posted by DRTBYK

First thing I do is run bad files through XML Validator

Then for GPX specific issues (and other XML stuff) I use XMLmind's XML Editor Professional Edition on my Mac.

Cheers,

Thank You!

Now I can't wait to get home this evening and test some GPX files...

[Rocky TFS]

Originally Posted by DRTBYK

I repeat, you will need to RECALCULATE your Routes - NOT recreate them. .

Cheers,

A VERY important distinction!

So, further experimentation has revealed that all issues with Recent finds went away after clearing the cache. (See original post)

I have gone over about 25 routes in Basecamp that I use often, merely changing the activity to direct and back to automobile, then back to direct for transfer to the unit, while CNNA 2013.2 is selected as the map. They all appear to work correctly, although I haven't ridden them yet. When selected on the unit with 2013.2 as the selected map, they show as a direct route, after few seconds the route disappears and comes back as an along road route.

As I go through all my routes, some of which have not been used for years, I will have to clean up other stuff, such as having WAY more than 50 viapoints, if I want to use them on the Montana. The problem with this is I have many old routes created for the Etrex or 76C the old fashioned way, with lots of waypoints to approximate the route. Since I still USE the 76C on my dirtbike with just the 100K topo or a non-routable state map, I'm not sure I want to change all of these. So I will most likely end up with the old routes in Mapsource for the 76C and the newer ones using CNNA in Basecamp, saving the possibility of recalculating an old route that is NOT intended for the Montana thus rendering it useless on the 76C.

I use the F650GS almost 100% on the pavement and the TW200 almost 99% in the dirt, so this may work fine.

Life just seems to get more complex the older you get......

[moto-treks]

Originally Posted by atlas cached

Have you used TopoFusion?

Windows only don't these guys know OS X rules

[atlas cached]

Originally Posted by Rocky TFS

As I go through all my routes, some of which have not been used for years, I will have to clean up other stuff, such as having WAY more than 50 viapoints, if I want to use them on the Montana. The problem with this is I have many old routes created for the Etrex or 76C the old fashioned way, with lots of waypoints to approximate the route. Since I still USE the 76C on my dirtbike with just the 100K topo or a non-routable state map, I'm not sure I want to change all of these. So I will most likely end up with the old routes in Mapsource for the 76C and the newer ones using CNNA in Basecamp, saving the possibility of recalculating an old route that is NOT intended for the Montana thus rendering it useless on the 76C.

I use the F650GS almost 100% on the pavement and the TW200 almost 99% in the dirt, so this may work fine.

Life just seems to get more complex the older you get......

You might consider making a copy of each route, performing the recalculation for the current mapping, and appending the name with something like [CN2013.20] or [Montana] and [eTrex], and store them in separate folders in BaseCamp...

[Rocky TFS]

Originally Posted by atlas cached

You might consider making a copy of each route, performing the recalculation for the current mapping, and appending the name with something like [CN2013.20] or [Montana] and [eTrex], and store them in separate folders in BaseCamp...

Now THAT is a GREAT idea!!!! What would I do without all you guys!

[atlas cached]

Originally Posted by DRTBYK

First thing I do is run bad files through XML Validator

Then for GPX specific issues (and other XML stuff) I use XMLmind's XML Editor Professional Edition on my Mac.

Cheers,

So, the validator says some of my GPX files are in poor form....

What do I do now?