BaseCamp 3.3.0.3 Beta available

Custom symbol files should have the same names between BC and newer GPS devices.

MapSource also uses the current naming convention of the Custom symbol display.

Hello everybody

Pair of weeks using Beta 3.3.0.3, very good news regarding the improvements in data management and track statistics. Thank you for the effort Basecamp Team!!


My report of issues:

1.- After creating route from track, the route elevation data is showing only Min/Max/Avg, but Ascent/descent/Grade data are missing (althoug the source track shows correctly all the information)

2.- The speed customizing is disabled for hiking profile.

3.- Joining two tracks or routes removes the source paths by default. If it's the intended behaviour, could be useful to the user to be asked (or at least advised) for this behaviour to avoid unexpected data loss.


Some other suggested improvements (from my humble point of view):

1.- When importing a track, it would be nice to place it automatically on the selected list folder. i.e, if i'm importing a track from a hike in the Alps, I could select my folder named "Alps" and import directly to it, instead of having to move it later.

2.- When creating a route from track, the naming of via point is always taking the track name plus a correlative number. Actually that's a very large name to display, because the name of the track usually describes the path (i.e. Village-Mount_Summit-Blue_Lake-Village). It would be desirable that the user could choose an abbreviation (like vp01,vp02) or something like this instead of having every via point named "Village-Mount_Summit-Blue_Lake-VillageXX".

3.- Regarding the above point, the user could also choose the default icon for waypoints and via points,changing the blue flag (at times annoying on small screens lige my etrex legend have). I have done it opening the waypoint key in regedit, but for sure it's not very desirable and confortable.

4.- Regardind the speed customizing, I have read in some thread about the posibility to select also the stopped time speed rate, that would be very useful for analysing tracks.
Some other softwares let the user do that. Specifically, CompeGPS have a GPS.ini file with two parameters:

Stopped_Points_Speed = 0.3
Minimun_Altitude_Acumulation = 3.0 ( to avoid small errors or deviations of the unit count as ascent/descent rates)


Thank you very much for your work and support.


BASECAMP 3.3.0.3 BETA, WINDOWS XP, ETREX LEGEND HCx, TOPO SPAIN V3

Mapsource type categories vs BaseCamp implementation

Re: KAGANSHIRT:

I can't think of any benefit. Can you?

Yes, I can see a benefit for me to having the planning lists available on the device as I'm traveling because I have found the routing on most longer trips to be very organic. The route traveled turns out to be different than what I had planned. Sometimes the changes are forced due to events out of my control. Other times I just want to go a different way. Having my complete set of planning data quickly and easily available is a great benefit to me. Others of course may not have this need or may address it in a different fashion.

Hint: the only reason for categories is to make finding things on the device simpler and quicker.


When using categories on Mapsource with my 276C I would quite often run into limitations due either to the number of categories available or in attempts to reuse them. So, in that respect Lists seem to be superior. Unfortunately, I've not yet been able to afford a newer device along the lines of the Montana so I've not been able to fully explore this new BaseCamp categorization paradigm in the field.

Hello everybody

My report of issues:

1.- After creating route from track, the route elevation data is showing only Min/Max/Avg, but Ascent/descent/Grade data are missing (althoug the source track shows correctly all the information)

2.- The speed customizing is disabled for hiking profile.

3.- Joining two tracks or routes removes the source paths by default. If it's the intended behaviour, could be useful to the user to be asked (or at least advised) for this behaviour to avoid unexpected data loss.


Some other suggested improvements (from my humble point of view):

1.- When importing a track, it would be nice to place it automatically on the selected list folder. i.e, if i'm importing a track from a hike in the Alps, I could select my folder named "Alps" and import directly to it, instead of having to move it later.

2.- When creating a route from track, the naming of via point is always taking the track name plus a correlative number. Actually that's a very large name to display, because the name of the track usually describes the path (i.e. Village-Mount_Summit-Blue_Lake-Village). It would be desirable that the user could choose an abbreviation (like vp01,vp02) or something like this instead of having every via point named "Village-Mount_Summit-Blue_Lake-VillageXX".

3.- Regarding the above point, the user could also choose the default icon for waypoints and via points,changing the blue flag (at times annoying on small screens lige my etrex legend have). I have done it opening the waypoint key in regedit, but for sure it's not very desirable and confortable.

4.- Regardind the speed customizing, I have read in some thread about the posibility to select also the stopped time speed rate, that would be very useful for analysing tracks.
Some other softwares let the user do that. Specifically, CompeGPS have a GPS.ini file with two parameters:

Stopped_Points_Speed = 0.3
Minimun_Altitude_Acumulation = 3.0 ( to avoid small errors or deviations of the unit count as ascent/descent rates)

Thank you very much for your feedback!

Issue 1: We'll see if there is anything we can do about this, but currently this only works if you do the conversion using a map with DEM (elevation) data.

Issue 2: I understand that it might be desirable to set your speed for the pedestrian profiles, but we haven't gotten around to making this work.

Issue 3: I would suggest to duplicate a track first if you are worried about losing it. You can also undo a join. But maybe we should make it more obvious that the source tracks will be consumed.

Improvement 1: That's definitely on our list.

Improvement 2: That's a good suggestion, probably of a somewhat lower priority though.

Improvement 3: That's also something we'd like to do at some point.

Improvement 4: There will be a registry setting MovingSpeedThreshold (in meters/second) at HKEY_CURRENT_USER\Software\Garmin\BaseCamp\Settings in 3.3.1.

With the exception of the improvement 4, none of this is likely to happen in the 3.3 timeframe.

If you are using 3.3.0.3 it should work for maps with DEM data. It didn't work in 3.3.0.2.

I don't have Topo Spain v3 available for testing, but it is working with other DEM maps that I did test with.

I do have Topo Espana v4 available and it works with that.

Maybe there are some quirks with v3, I believe it is fairly old.

basecamp database location

Please make location a user setting!

Regards
Rob

How do I sum all my selected route distances?

When I highlight multiple routes in MapSource, the bottom of the left pane shows how many miles are contained in the selected routes.

I highlighted multiple routes in BaseCamp, expecting that properties of multiple routes would summarize that distance. It does not. The summary line at the bottom of the left pane does show how many routes are selected. It would be useful to also have the distance and travel time summarized there.

I highlighted multiple routes in BC and copied. I went to Excel, expecting the columns of data could be pasted there and it cannot. MapSource also allows me to paste data copied from the route list or the directions into Excel. Both are very useful features.

• Fixed zumo 5x0 and 4x0 route transfer issues. Note that this may cause route transfer issues on the zumo 660. A future firmware update on the 660 will address this issue
  

I feel it's worth mentioning that this change appears to have fixed an ongoing issue I have had with importing routes from BaseCamp into my Nuvi 1450, as well as into a colleague's Nuvi 1450T. Previously, any attempt to import routes in the device that had been sent from BaseCamp would result in either the device locking up or a hard reboot. Thank you very much for fixing this issue, as it has been a major roadblock for me in the past!