Related

basecamp changes WP numbers when importing...

Former Member
Former Member
re-raising the issue as the previous thread was closed...

I understand the issue as was explained in the now closed thread that the DB can have only one WP for a specific name. and that annoyingly BC will append a number to the WP name to make it particular to that WP.. but this was not a good practice of working for many users on the previous thread.

my own problem is that after deleting all essences of the WP's in all lists and ALL unlisted data folder and restarting BC... the WP called "AH1" for example is still renamed "AH110" after importing the GPX file into BC..
but if I search "My Collection" for "AH1" there is no result, AH1 is not found...?
  • Former Member
    0 Former Member
    I haven't experienced this weird renumbering issue. Is the gpx you are importing publicly available? If it is and you give us the link I wouldn't mind doing a test with it.
  • Former Member
    0 Former Member
    no it's actually copyrighted sorry, but it's not an issue with that particular GPX.. its just an example of what I have came across before and which I noted before but did not look into further.. so this time I did a bit of searching and ended up here..

    read the closed thread for much more details -
    https://forums.garmin.com/showthread.php?33536-Base-Camp-waypoints-and-Track-names-changed-when-import-from-Map-Source&highlight=waypoints+change+import

    I am using the latest version of BC 4.5.0
  • 0
    It sounds as if something has gone wrong with your installation. What you describe should not happen. I assume you have checked the gpx file to make sure the Waypoint isn’t actually named something other than AH1.

    In the past, (MapSource and at least early versions of BaseCamp) users were not allowed to delete a Waypoint if it was used in a route without first deleting the route. I believe that BaseCamp changed this in some way – I think a Waypoint in Routes gets changed to Shaping/Via point when the Waypoint is removed from the database, but I am not sure. Is it possible that AH1 was used in a Route? If so, does exporting, then deleting the routes solve the problem? Even if it does, this is still and indication of a bug and should be reported.

    Perhaps someone can chime in with the best way for the op to recover from a corrupt file/cache short of a full un-install re-install.
  • 0
    Is it possible that AH1 was used in a Route?

    I'm pretty sure that this is the case. The database contains points, routes and tracks. The points can be via points, waypoints or both; the routes contain references to points. Earlier you couldn't remove waypoints in routes, now you can. However, when you do so the point isn't really deleted, it's only that the "waypoint" flag is removed from the point and thus not visible anymore. The point still exists and still has the same name. The restriction of unique names doesn't apply to waypoints only but to all points, including via points.
    This is not a bug, it's by design (it isn't a well-thought design choice though...)
  • Former Member
    0 Former Member
    took me a while but, Yes the was an existing WP called "AH1" in another route.. but it did not show up in the search results (top right of screen)
    so at least I know why the naming was changed.. anyway..!!