When sending Waypoint from GPS to BaseCamp incorrect BaseCamp Waypoint is selected for copy if Waypoint names are not unique.
Example:
1. BaseCamp: Existing [BaseCamp Waypoint, name=001].
2. GPS: Create new Waypoint without name, name=001.
3. BaseCamp: Send waypoints from GPS to [BaseCamp folder].
Result:
[BaseCamp waypoint, name=001] IS VISIBLE in [BaseCamp folder].
[GPS waypoint, name=001] is NOT visible in [BaseCamp folder].
No warming like "duplicate name", "not unique" or "overwrite?".
This behaviour is new for BaseCamp 4.3.1. Not for previous versions.
Etrex 30.
TESTED BaseCamp 4.2.5 and BaseCamp 4.3.1:
Restored BaseCamp 4.2.5 database and tested with both BaseCamp 4.2.5 and BaseCamp 4.3.1
BaseCamp 4.2.5
[GPS waypoint 004] > [BaseCamp waypoint 00432] = OK
[GPS waypoint 005] > [BaseCamp waypoint 00529] = OK
[GPS waypoint 006] > [BaseCamp waypoint 00631] = OK
[GPS waypoint 007] > [BaseCamp waypoint 00725] = OK
All Waypoints are renamed correctly to resolve name collision, correct location (identical to GPS waypoint)
BaseCamp 4.3.1
[GPS waypoint 004] > [BaseCamp waypoint 004] = ERROR = name collision, location is [BaseCamp waypoint 004], not [GPS waypoint 004]
[GPS waypoint 005] > [BaseCamp waypoint 005] = ERROR = name collision, location is [BaseCamp waypoint 005], not [GPS waypoint 005]
[GPS waypoint 006] > [BaseCamp waypoint 006] = ERROR = name collision, location is [BaseCamp waypoint 006], not [GPS waypoint 006]
[GPS waypoint 007] > [BaseCamp waypoint 00725] = OK = renamed correctly to resolve name collision, correct location (identical to GPS waypoint)
Conclusion: issue is new for BaseCamp 4.3.1. However the issue is not alway reproduced (in my test 25% is OK).
Issue is still open for BaseCamp 4.3.4.
