fwiw, in my experience it was the Forerunner that had the ability to import routes with >100 points and thus the better navigational abilities than the Edge, not vice versa. It’s interesting to read the other poster claim that both units have identical capabilities with routes and courses, so either it is somehow user error or he is wrong. My experience leans me toward the latter, but I do not rule out the former. There seem to be “tracks”, “routes”, “courses”, and “history”, each of which seem to me to be a set of long/lat points. In the Forerunner we would import a track and it would become a track that we would navigate. In the Edge we could not import tracks, so had to Save As a route and then import that, but it would truncate at 100 points. Again, maybe user error…
Baffling to hear other’s negative experiences with altitude and the Forerunner. Maybe in France we had signal to a large number of satellites so the readings were always accurate, but over 3 weeks and 2200 miles, both the Forerunner and Edge were always very near spot on. I don’t know about total gain calculations, though.
No offense, but this is not a claim, but a fact.
The problem here is the use of terminology. Using routes for navigation a user is limited to 100 total waypoints (this is a limitation of the units, so you can have 5 routes with 20 wayponts each, or 1 with 100, and both of which would be further limited if you have any individual waypoints stored on your units). Waypoints are simply a set of lat/long points though may also contain elevation data. This is exactly the same for both units.
Courses are the only way, aside from using the “back to start feature,” to navigate using more than 100 “points”. These work with trackpoints, and can utilize about 13,000 of these points depending upon the presence of any coursepoints (special points used to designate points of interest like turns, water stops, summits, etc)which additionally tax memory. Trackpoints, in addition to containing navigation features (lat/long/elevation) also contain performance metrics based on previous activities, or unit “history,” (or arbitrary metrics if you use a 3rd-party course creator rather than your own history to create the course).
“Routes” and “courses” are not the same thing at all. Routes offer very basic navigation (simple connecting of dots) compared to courses (which can offer info like off course warnings, upcoming turn notifications, etc.).
“Tracks” are not used at all on either of these units, though it is terminology/feature commonly used in other GPS units.
I cannot account for your differing experience between the two without knowing more about how you are creating the routes/courses you were attempting to navigate and how you loaded them into the unit, however, think with a little experimentation you’ll be pleasantly surprised to find both units fully capable of the same features.