Waypoints which can't be deleted

To make some tests I clicked on some waypoints in a Map so that they are shown in "my collection". After finishing the tests, I tried to get rid of this waypoints. But the delete command is greyed out. Renaming does not help. To bring it in a list and to delete this list together with its content deletes this list and normal waypoints, but not this one which I copied from a map.
So I thought to start a new database "my collection". But another thread mentiones here only a workaroud, which requires to delete all the content after back up. And this deletion does not work.
The database is stored somewhere. Does somebody know the details?
Perhaps I can try to delete this folder or files to create a new and empty database.
  • Former Member
    0 Former Member
    Is that waypoint part of a route?

    You'll have to delete the route first, or remove that waypoint from the route.

    This behavior isn't very obvious, so we'll see if we can make some changes to make this more apparent.
  • I too have observed this. At times I create a route from waypoints I've created. Once I have the route, I no longer need the waypoints which I am not allowed to delete.

    Also observed, if I send the route to my GPSMAP 62s, the waypoints are included in the file route0.gpx even though I did not select them to be sent. Looking at the file in Windows Notepad, these waypoints (<wpt>) are listed ahead of the route itself where they, of course, appear as route points (<rtept>). These waypoints may be deleted within the GPS or by editing the file in Notepad.
  • Former Member
    0 Former Member
    Are you trying to delete waypoints in a Route on the main page in the left column under My collection or from the list in library? Or are you bringing up the Route>Properties and deleting waypoints from the Properties Window? I edit waypoints in the Properties window and haven't had any problems.
  • We are trying to delete waypoints that are used to create a route, not the points within the route. These waypoints are listed as individual distinct waypoints in My Collection outside the route.

    BC will not allow deletion of the waypoints until the entire route is deleted or, as stated above, corresponding point is deleted from the route.
  • Former Member
    0 Former Member
    The problem is that if you use a waypoint in a route it IS the route waypoint, and we don't allow the user to delete is (because it would break the route).

    I freely admit that this seems very odd. We are looking into changing this behavior.

    The initial thought was that the user would specify waypoints that could be used in several routes. Then by changing the waypoint (name, symbol or even position) the user would update all routes at once, with no need to individually change each route waypoint.
  • FALAGAR...I understand what you are saying however, this behavior is not consistent. I have created routes in BC where only SOME, not all, waypoints behave like this. The other waypoints used to create the route are not sent along with the route.gpx file and may be freely deleted.

    Additionally, once the route is in the GPSMAP 62s, these waypoints may be deleted without affecting the route. The waypoints may also be deleted by opening the file in Notepad and editing in that manner.

    The gpx file begins with the waypoints (<wpt> blah, blah, blah </wpt>) and then continues with the route and its "route points" (<rtept> blah, blah, blah </rtept>). Deleting the <wpt> entries does not affect the <rtept> entries even though they may represent the same point.
  • Former Member
    0 Former Member

    The initial thought was that the user would specify waypoints that could be used in several routes. Then by changing the waypoint (name, symbol or even position) the user would update all routes at once, with no need to individually change each route waypoint.


    Would you please describe the Use Case where by one would benefit from this waypoint linkage to multiple Routes?

    Cheers,
  • Former Member
    0 Former Member
    I am not sure there are many good use cases, which is why we are considering to change this behavior.

    One use case might be that you have a bunch of waypoints that contain extra information (comments, address, phone number etc). Each of these waypoints is used for route planning (in more than one route), these waypoints could represent frequent destinations for when you tend to travel in the same area many times on different routes. Now if some of that information changes, you only need to update one waypoint, and all the waypoints in all the routes will be updated (because it's really the same waypoint). If each waypoint were unique to the route, you'd have to update every single one.
  • Former Member
    0 Former Member
    I am not sure there are many good use cases, which is why we are considering to change this behavior.

    One use case might be that you have a bunch of waypoints that contain extra information (comments, address, phone number etc). Each of these waypoints is used for route planning (in more than one route), these waypoints could represent frequent destinations for when you tend to travel in the same area many times on different routes. Now if some of that information changes, you only need to update one waypoint, and all the waypoints in all the routes will be updated (because it's really the same waypoint). If each waypoint were unique to the route, you'd have to update every single one.


    Thanks FALAGAR. I think your first comment was right-on. I was around when RDB's were invented and can see lot's of really great uses but for the most part creating/editing/deleting Waypoints/Routes/Tracks don't have to many workflows so having functions that make it a bit more logical would help a lot.

    Hopefully both version's of BC will converge so we will see the same data management functions on both OS's. Having a few new functions like, Where Used and the ability to use the same Name on multiple objects will come in the near future.

    Cheers,