BaseCamp 4.3.0.2 BETA is Now Available

Former Member over 11 years ago

BaseCamp 4.3.0.2 BETA is now available and can be downloaded here:

http://developer.garmin.com/apps/BC/BaseCampBeta_4.3.0.2.exe.zip

You will need to unzip the file before installing.

This release does not support XP.

You do not have to uninstall BaseCamp 4.2.5 and it will not overwrite that installation. The BETA and an official release of BaseCamp will live side-by-side but must be used separately. However the 4.3.0.1 BETA will be replaced.

Below is a list of changes. This is only a BETA release.

Added “Find Intersection” to the Find menu
Added parsing of the primary find text into address search fields
Improved ordering of auto-complete results
Improved street auto-complete results when searching for streets with prefixes and suffixes
Improved some usability issues with address and intersection searching
Improved recovery from corrupted cache information from device maps

Post here if you have questions.

The BETA is currently only for English users.

Before using this release, back up your data.

Please post any bugs you may find here. This release is to assist us in testing with a wider user base and wider set of devices. Bugs may be present, and any feedback is welcomed.

NOTE: We are aware of several issues with address searching on devices. We ask our users to please test this very well and let us know of the issues you find. Some of them will be duplicates of issues we have already found, but the advanced address search is new for this release and we need a good test bed to be sure that the feature is working correctly when we do the full release.

Again, thank you for all who participate.

0 SUSSAMB over 11 years ago

For a number of technical reasons the behavior will be staying the same currently. However, I did make one concession. See the following screenshots below this post. We now do as the Mac does on PC where we say "User Data in <list or folder name>" It will refresh with every search you do. I do agree that users did not have a way to know where they are searching so this is the compromise for today. This is not in the beta.

OK thanks, that helps for now. Hopefully we'll see a more consistent and useable approach going forward ... with POIs and User Data working the same way and based on center of view, or whatever else is selected in the Location box. I haven't lost sight of the fact the search process is much improved, just needs some tidying up at the edges :)

0 Former Member over 11 years ago

And fair enough. Just try to keep in mind that the center of view is taken into account because User Data is sorted by distance from that point. Like I said above, if you search for a track in Seattle and your view is in Phoenix, it will show up but it will be towards the bottom of the list. If you're view is over Seattle, then it will be higher. Searching through all of our User Data is a very time-consuming and resource-intensive process. In order for BaseCamp to remain responsive this was a necessary trade-off. Another factor is due to the fact that User Data and POI's are disjoint... meaning that one depends on the map, the other does not.

0 SUSSAMB over 11 years ago

Yes I followed that, but my guess would be for the majority of users there'll be far more POI data to search through than user data so I'm unclear why searching user data is more of a problem than searching through POIs, intuitively I'd have thought it would be the other way around? The new search algorithm seems so fast now that I wouldn't have thought either was an issue.

It also (to me anyway) doesn't make sense that if I have a single list/folder selected I'll only get user data from that list (and therefore possibly nowhere near the selected Center of view) but by ensuring I select My collection selecting Center of view produces the correct result (and almost instantaneously). I fail to understand the issue therefore, as to why Basecamp doesn't simply behave that way regardless of what list/folder is selected :confused:

Clearly I'm missing something. In any case now I know that's the way it behaves I can work around it, but it sure will confuse users new to Basecamp and/or unaware of our conversation :)

0 Former Member over 11 years ago

Auto-choosing My Collection will not search devices either. Device searching is one of the things is that is very slow.

0 SUSSAMB over 11 years ago

I understand that but I only use it to search user data in Basecamp not on a device.

0 Former Member over 11 years ago

Task Launcher icon begone!!! :D

(It can now be turned off)

Why not just have My Collections HotSync to your Garmin GPS. That way, whatever is on your maps will sync to what is on your gps. You are making too complicated for the average user.

0 Former Member over 11 years ago

Why not just have My Collections HotSync to your Garmin GPS.

No doubt that'll happen when Apple releases the iGPS :D

0 BigLew55 over 11 years ago

Why not just have My Collections HotSync to your Garmin GPS. That way, whatever is on your maps will sync to what is on your gps. You are making too complicated for the average user.

Thanks, but no thanks. I have a lot of stuff on my PC that doesn't need to be on my GPS. I like to keep my data on my GPS pretty constrained to the task, be it normal, local stuff, or a long trip plan.

I don't need ten years of history and 5 years of planned stuff that is easily managed on my PC to be on my GPS.

0 dandemandan over 11 years ago

Thanks, but no thanks. I have a lot of stuff on my PC that doesn't need to be on my GPS. I like to keep my data on my GPS pretty constrained to the task, be it normal, local stuff, or a long trip plan.

I don't need ten years of history and 5 years of planned stuff that is easily managed on my PC to be on my GPS.

Ditto...

I have many, many trips in BaseCamp on the PC, but would not want hundreds of waypoints in the GPS not relevant to the current trip I'm on. I too have a local stuff folder, and each major trip has it own folder on the PC.. I only upload the relevant folder for what I'm traveling into the GPS.

If I imported all the old trips from MapSource I'd have over 26 years of cross country trips.. too much to even put in BaseCamp.....

0 BigLew55 over 11 years ago

Ditto...
...If I imported all the old trips from MapSource I'd have over 26 years of cross country trips.. too much to even put in BaseCamp.....

This is another reason I wish they'd add support for naming convention on their db. I have several waypoints from different trips such as "night one" or "Turn one" or "Home", or trips/routes such as "Home to Florida" that would duplicate as I add old trips. Too much clean-up, if I did that. :(

Right now, I've only got about 2,800 points/trips in BC. I'm still not a fan of sharing them across trips/folders, as one change has ripple effects, and that usually cause a bunch of work to correct.

I have come to a point that Basecamp is a better option than Mapsource with this Beta release, but it has barely tipped the scales. I certainly hope they continue to make this db concept more usable for those of use who use BC for keeping large quantities of trip data.