Any chance we will be able to marquee an area or intersection in BaseCamp to avoid, so BaseCamp would route you around the selected area or a proximity setting of a POI?
Consider an alternate form of naming Trip Planner routes in sort friendly order, i.e. YYYY/MM/DD. That way, My Collection sorts routes in date order rather than month order. It also avoids the Euro DD/MM/YYYY and US MM/DD/YYYY confusion.
Any chance we will be able to marquee an area or intersection in BaseCamp to avoid, so BaseCamp would route you around the selected area or a proximity setting of a POI?
Consider an alternate form of naming Trip Planner routes in sort friendly order, i.e. YYYY/MM/DD. That way, My Collection sorts routes in date order rather than month order. It also avoids the Euro DD/MM/YYYY and US MM/DD/YYYY confusion.
Consider an alternate form of naming Trip Planner routes in sort friendly order, i.e. YYYY/MM/DD. That way, My Collection sorts routes in date order rather than month order. It also avoids the Euro DD/MM/YYYY and US MM/DD/YYYY confusion.
I name all my routes (before I go) and tracks (after I've been) using exactly this convention. It's especially important in BC, where everything lives in the same database -- no possibility of duplication. With MapSource I usually left the year off, since I was working in separate files that were associated with yearly folders, but those days are gone now.
There are times when I think Garmin is an exercise in seeing what consumers will adapt to (put up with) in order to get whatever functionality they need out of what's available.
The ability to prepare routes with different profiles for different segments is a very good feature, e.g. Motorcycling and Direct. That would allow a route to continue past areas where the map has no routing data. I just wonder how devices will handle such routes. Can a Zumo 660 or a Montana accommodate such routes, or can they only be used on newer devices?
The ability to prepare routes with different profiles for different segments is a very good feature, e.g. Motorcycling and Direct. That would allow a route to continue past areas where the map has no routing data. I just wonder how devices will handle such routes. Can a Zumo 660 or a Montana accommodate such routes, or can they only be used on newer devices?
I've heard customers use multi-profile routing on the Montana with some success. It should work on the Zumo as well.
The device might not pick up the route leg profile properly (the old devices don't understand the route extension that specifies the route leg profile) but as long as the device doesn't recalc I believe it will route whatever you have planned in BaseCamp. Please let us know if it doesn't.
P.S. The 4.2.0.2 Beta isn't actually writing out the proper extension yet, a follow-up Beta should fix that.
Postcode search has been added for the UK but does not seem to work for other countries. Searching addresses by postcode works well in MapSource and should be available also in BaseCamp for other countries than the UK.
The 4.2 Beta uses US date/time standards. Presume that the final version will use the date/time standards from the local PC/Mac system?
If I'd like to send maps to Mobile PC, then I would have to run MapInstall manually. This is some kind of inconsistency. I hope you won't delete support form MapInstall.
