Here's my trail of tears in case any of you are feeling curious, generous, and wise. There should be sufficient info there to reproduce (or LMK if it doesn't? !!) and dissect. It's a real science project. I am using an up-to-date zumo 396 with up-to-date BaseCamp on Win10. City Navigator North America NT 2023.1 (in Virginia).
I created and exported a route to the GPS, it said it imported, the trip count increased by 1, but there was no route there. I clicked through on the device to re-import, and it gave the cannot import error message for Routename 1 (i.e. it knows Routename is [sort of] there). I can't for the life of me figure out why. So the device says I have, for example, 10 routes but there are only 9 there and
I wind up resetting device (data and settings), took a complete Mulligan, and everything repeated the same. Also sent the route to a friend (also 396) and she had the same result.
I then flailed at a few things in the source route, like duplicating it and exporting the duplicate, still got the fail.
I then split the route in two, re-reset the GPS, tried to import all three parts -- original part 1, part 2. All three seemed to process, Trip Planner shows three route, but only the part 1 route is there to select. Part 2 gave the same phantom result (trip count goes up, but no route there). Here is the GPX file: those three routes, some waypoints, and the reference tracks. https://1drv.ms/u/s!Am5GnNzOpxmXpbokwsj ... g?e=kHIp3S. Part 1 was enough for me to get it done, so I stopped there.
If you try to import, please let me know if you have the same problem, i.e. only part 1 will load and be available, the other two will pretend to load then not be there, though you'll be +3 on route count in Trip Planner.
Other info:
- The route isn't the simplest one because it couldn't be, but it's not anything out of spec for # via points, shaping points, etc. After being split in half, it's even more in spec.
- I did have another issue with some anomalies around moved routepoints. Discussed here: viewtopic.php?t=1787 IDK if it's related or just concurrent. I can't isolate a POI-turned-routepoint in part 2 of the route that is causing the problem.
- It was lousy timing since I was up late getting ready for a long day of ride escort. I have seen the phantom route issue before, years ago. I can't find if/how I solved it, I don't think I did, just re-set my way out of the mis-count when I got sick of looking at the anomaly. Then this reared its ugly head again when I was under the gun