Related

BaseCamp 4.3.0.3 BETA is Now Available

Former Member
Former Member
BaseCamp 4.3.0.3 BETA is now available and can be downloaded here:

http://developer.garmin.com/apps/BC/BaseCampBeta_4.3.0.3.exe

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.2 BETA will be replaced.

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

Improved UI for address search
Improved results for address search auto-complete
Fixed a bug where Top Results search didn't refresh in advanced
Fixed a bug where cancelling the address search find did not work
Fixed a bug where address searches were not yielding results on device maps
Improved matching of serach results if search results exactly match user entered criteria
Fixed inversion of route departure times
Update free-form search string whenever advanced search parameters change
Fixed a bug where attemping to do an address search forces a POI search
Fixed not being able to clear departure time on last via if set after inverting route

Post here if you have questions.

The BETA is currently only for English users.

Before using this release, back up your data.

NOTE: We are aware of some issues with routing. Moving waypoints caused the route to leave roads unexpectedly. We know about this issue, and a fix is undergoing QA, however it did not make it into this build. There is no need to report on this issue, we believe we have that under control.

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.

Again, thank you for all who participate.
  • 0
    Two remarks related to use with the Zumo:

    A.
    Reading the above I understand you have not been working on the curvy roads. Still: pls ask your collegues to pay some extra attention to that:

    When planning a route for e.g. Amsterdam to Rotterdam the route will be 90% interstate; no matter if interstate is set to avoid or not.

    I was involved in testing the zumo590 too; at first it had the same behaviour; improved a bit in the final firmware. But especially in regions with few curves (like in the flat Netherlands) it will choose too high roadclasses. I know that they are looking in to that for the zumo-firmware; but hope the effects will also show in Basecamp. Improving this will make a very interesting BC-feature.

    B:
    In Europe we tend to use much more via's in a motorcycle route than in the US. There will be a via on avarage every 2 to 3 km.

    As such it would be MUCH better if Basecamp default would be to using shaping points instead of by default to "alert on arrival" (I call them "hard via's") ; only using "altert on arrival" when a user manually sets a point to do so. For motorcycle-use this would be a major improvement.

    There are three problems with "hard via's":
    - it ruins the feature of autmatically skipping via's when returning to the route after a short detour (eg because of roadwork).
    - "hard via's" are called out, which mostly is irritating rather than usefull
    - a route in the zumo is limited tot 30 hard via's. If one downloads a route form the net all via's will be hard - unless edited alle routes will be split up after importing to the zumo.

    Please consider.
  • 0
    Another suggestion using 'find adress'

    After typing in only parts of an adress pushing 'ENTER' should trigger the search.

    Now I need to press the 'reload' arrow right below.

    E.g.: when entering just a streetname and press enter i just hear a beep ans get the message 'enter a street number for better results'. No search results shown..

    However: when I press the arrow 'refresh search results' i immediately see the results.

    Ir would be more unituitive if pressing ENTER would have the same effect as pressing 'refresh search results'.

    Also: I notice that a streetname with spaces if difficult to find, using the general find-field. E.g. 'groen van prinstererlaan' will result is streets starting with 'groen', ignoring what comes after the space. Using the adress-field it works fine.

    I general: major improvements to the find-option!
  • 0
    [...]
    Reading the above I understand you have not been working on the curvy roads. Still: pls ask your collegues to pay some extra attention to that:

    When planning a route for e.g. Amsterdam to Rotterdam the route will be 90% interstate; no matter if interstate is set to avoid or not.

    I was involved in testing the zumo590 too; at first it had the same behaviour; improved a bit in the final firmware. But especially in regions with few curves (like in the flat Netherlands) it will choose too high roadclasses. I know that they are looking in to that for the zumo-firmware; but hope the effects will also show in Basecamp. Improving this will make a very interesting BC-feature.
    [...]

    Thank you for addressing the curvy roads issue. I made the same observations with this function on german streets.
    Basecamp mostly uses Interstates (Autobahn) and ignores the curvy roads nearby.

    Canario
  • Former Member
    0 Former Member
    Two remarks related to use with the Zumo:

    A.
    Reading the above I understand you have not been working on the curvy roads. Still: pls ask your collegues to pay some extra attention to that:

    When planning a route for e.g. Amsterdam to Rotterdam the route will be 90% interstate; no matter if interstate is set to avoid or not.

    I was involved in testing the zumo590 too; at first it had the same behaviour; improved a bit in the final firmware. But especially in regions with few curves (like in the flat Netherlands) it will choose too high roadclasses. I know that they are looking in to that for the zumo-firmware; but hope the effects will also show in Basecamp. Improving this will make a very interesting BC-feature.

    B:
    In Europe we tend to use much more via's in a motorcycle route than in the US. There will be a via on avarage every 2 to 3 km.

    As such it would be MUCH better if Basecamp default would be to using shaping points instead of by default to "alert on arrival" (I call them "hard via's") ; only using "altert on arrival" when a user manually sets a point to do so. For motorcycle-use this would be a major improvement.

    There are three problems with "hard via's":
    - it ruins the feature of autmatically skipping via's when returning to the route after a short detour (eg because of roadwork).
    - "hard via's" are called out, which mostly is irritating rather than usefull
    - a route in the zumo is limited tot 30 hard via's. If one downloads a route form the net all via's will be hard - unless edited alle routes will be split up after importing to the zumo.

    Please consider.


    Can you send to me some of your route information so I can recreate what you're saying? This would be a lot easier for me to diagnose and open cases on if you're willing to share some of your data. It won't be shared with anyone.
  • Former Member
    0 Former Member
    Another suggestion using 'find adress'

    After typing in only parts of an adress pushing 'ENTER' should trigger the search.

    Now I need to press the 'reload' arrow right below.

    E.g.: when entering just a streetname and press enter i just hear a beep ans get the message 'enter a street number for better results'. No search results shown..

    However: when I press the arrow 'refresh search results' i immediately see the results.

    Ir would be more unituitive if pressing ENTER would have the same effect as pressing 'refresh search results'.

    Also: I notice that a streetname with spaces if difficult to find, using the general find-field. E.g. 'groen van prinstererlaan' will result is streets starting with 'groen', ignoring what comes after the space. Using the adress-field it works fine.

    I general: major improvements to the find-option!


    This has been addressed.
  • 0
    Printing routes: Route is overlapping Road labels and makes them unreadable

    I am just planning some routes for the oncoming vacation with the motorcycle. Some of the riders have no GPS-unit. Therefore, I want to print them out a roadbook that they can use.

    When printing a map of the route and the corresponding route directions there are some issues:

    • The Route is overlapping Road labels and makes them unreadable (also a problem while planning a route).
    • The route boundaries are to close. There is no space between the route and the map frame.
    • Names of custom waypoints are disappearing even when the map details are set to maximum. There would be still enough space on the map to show the names.
    • Route Labels are disappearing even when the map details are set to maximum and there is no route line covering them. There would be still enough space on the map to show the Road labels.
    • Dividing the map by sectors is not efficient and makes the readability of the roadbook difficult. It would be fine, if the detail maps could be predefined by the user (like in www.motoplaner.de) or by automatism (e.g. Google Maps).


    All these points together preventing a good readability and comprehensibility of the roadbook.

    These points are not specific to the beta version but may be they can be addressed to the team that is already working on the next official Basecamp version.

    Thanks
    Canario
  • 0
    To print route directions try this:

    Right click in the Route Directions and choose 'Select all', then right click and 'copy'. Paste into Excel and under the Data menu select “text to columns”, choose delimited and check comma. You get all the data separated nicely into columns. From here you can do anything you want in Excel.
  • 0
    This works fine for editing the route directions, thank you.

    The issue for the reader is that it is difficult or rather impossible to identify the roads (labels) and also the concerning directions on the map.
    Improving this roadbook function would make a very powerful Basecamp feature.

    Canario
  • 0
    Can you send to me some of your route information so I can recreate what you're saying? This would be a lot easier for me to diagnose and open cases on if you're willing to share some of your data. It won't be shared with anyone.

    Will do.
  • 0
    Thank you for addressing the curvy roads issue. I made the same observations with this function on german streets.
    Basecamp mostly uses Interstates (Autobahn) and ignores the curvy roads nearby.

    Canario


    This has been observed here as well. Perfect example: Route between Silver Spring, MD USA and Antietam National Battlefield with Curvy Roads Enabled still prefers routing up very straight Interstate 270, even though Interstates are explicitly disabled in the Avoidances (and it is less curvy than many of the more secondary roads anyways) My intent was to find a curvy and twisty back road route to the destination as a start then tweak the route accordingly (I do not expect BC to find the perfect roadset every time, but curvy roads becomes a great starting point).

    Curvy roads should take into account current Avoidance settings and should ignore both the Faster Time and Shorter distance directives.
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries