Fenix 5 - „X” specific - missing features – list updated for current firmware

[/LIST]Elevation auto calibrated to waypoints with elevation data. I often add various waypoints when doing ultra trails. It would be extremely useful to auto calibrate watch altitude once a waypoint is reached or simply is near enough. This is going to have a positive impact for data fields like: elevation to next waypoint etc.

• Easy way to add waypoints / course points that are recognized while following a track or navigating. Various reports show workarounds for this, but it’s been never fully implemented by garmin. And again… in devices like gpsmap62 one can upload a waypoint in gpx format and device will use it in every route or track that happens to cross this specific point. As an example PZ1 waypoint visible in screenshot above is a user defined WP for a refreshment station. I didn’t add to the route. I simply saved the location on a raw map.
  
• Navigation data fields (working properly!) for: distance to next WP, time to next WP, elevation to next WP
  
• Missing FIX for correct distance to target - currently while following a course distance to dest on map screen shows a "crown fly" estimate instead of correct distance along the route
  
[/LIST]

Here is a list of things / features I find missing in Fenix 5X. They are all related to the “X” variant of our watch and what’s most important they are not just ideas of mine, but most often features that were / are available in other (much older) devices.

I’d like Garmin to consider adding them. As Fenix 5X is advertised as the best of the best it should not miss mapping / routing / navigating specific options.

Please feel free to add your suggestions. I’ll edit this post each time a new FW is released or new suggestions are made.

Also if moderators will allow, I’ll bump it whenever a valid update is made.

• Autogenerated Summits / Valleys waypoints from a gpx track (available in old handheld devices like GPSMap62) – each time a GPX track file is placed in a device like gpsmap62s it will autogenerate course points (waypoints) along the track according to elevation data. This results in summits and valleys points that one can easily see in on map and use them in specific datafields:
  
• A data screen with all track / route / course events listed – just like old gpsmap62s (see link above)
  
• Zoomable elevation plot while following a track, navigating a course etc. This would be especially useful for longer tracks where, where entire profile plot for courses of 40+km is simply too cluttered and unreadable
  
• Elevation auto calibrated to waypoints with elevation data. I often add various waypoints when doing ultra trails. It would be extremely useful to auto calibrate watch altitude once a waypoint is reached or simply is near enough. This is going to have a positive impact for data fields like: elevation to next waypoint etc.
  
• Easy way to add waypoints / course points that are recognized while following a track or navigating. Various reports show workarounds for this, but it’s been never fully implemented by garmin. And again… in devices like gpsmap62 one can upload a waypoint in gpx format and device will use it in every route or track that happens to cross this specific point. As an example PZ1 waypoint visible in screenshot above is a user defined WP for a refreshment station. I didn’t add to the route. I simply saved the location on a raw map.
  
• Navigation data fields (working properly!) for: distance to next WP, time to next WP, elevation to next WP
  
• Missing FIX for correct distance to target - currently while following a course distance to dest on map screen shows a "crown fly" estimate instead of correct distance along the route
  

Totally agree with your request. Especially elevation calibration based on saved waypoints would be extremely useful for more accurate elevation and ascent/descent data.
You're mentioning data field "elevation to next waypoint". I was looking for information like this (vertical distance to next waypoint) but couldn't find an appropriate data field. Do you get this information and if yes how?

Thanks for your support.

Also elevation calibration can be done via contour line data of maps. But for me elevation seems to be working fine as long as a GPS activity is running. It doesn't go extremes...

NoTex, according to Garmin support "Vert Dist to Next" works (but only according to them).
I haven't heard from them any updates so far.

We’ve already submitted your suggestions to the engineers and will have to wait to see whether or not they will be added. Repeated submissions of the same suggestions will not produce additional results, and may not elicit an email response.

We are aware of the turn by turn and other routing issues with the fenix 5X, and are looking into it.

We understand the importance of this issue, as well as the frustration this and other issues cause.