route and elevation data while exporting

wahou.... thanks for all this literature, I read your post several times... I will see to recalculate the route with Global Map (never did this), otherwise I will end up using track, I didn't see any difference on my edge 820, either riding a route, or a track, navigation is similar with TBT or turn guidance

cheers

So after long tests here and there, results are not promising..... recalculating a route on a different map obvioulsy gives a completely different route, as details on the map vary a lot..

Created a route using OSM map from german website, elevation profile OK on basecamp, but NOK on the Edge 820
Created a route using OSM map from openfietsmap, elevation NOK on both
Created a route on TOPO map, OK in basecamp, NOK on the edge 820
Recomputed a route on DEM map, OK on basecamp, NOK on the edge 820, cue sheet is meaningless
Created a route direct on DEM map from a track, OK in basecamp, NOK on the edge 820, cue sheet is meaningless

Whatever I do, I have no elevation profile for every route I created, all works fine with track..... Certainly something to do with the edge itself.. On my previous post I was saying that the gpx export does not contain elevation data, I was wrong, just that the file is so big I missed them, they are dispacthed on every "rtep"; within a rtep I have ele, time, name, cmt, desc, sym, extensions....

If someone has a clue, I will be happy to know, otherwise, I will just use track

cheers

jerome

I should have given a better explanation. A digital elevation model (DEM) on the device is required to see elevation data for an Automated Route (this is any Activity Profile other than Direct). If the map in BaseCamp with the DEM isn?t on the device then it won?t work.

I?ll try to explain the trick better. An Automated Route created on my device (gpsmap 62) only stores the User Points in the file it creates? these are the points seen on BaseCamp?s Route Properties tab; it does not store the paths between the points. When an Automated Route is created in BaseCamp and sent to a device, the path between user points are included. In the gpx file the <rtep> is a user point and a <gpxx:rtp> is a path point. The path points do not have elevation data. Devices will only utilize the data in a gpx file they are programmed to use and ignore any other data. Therefore, different devices will behave differently.

If I create an Automated Route using a map with a DEM, it will assign elevation data to the user points. If I then switch to the Global Map, which doesn?t have routable features, and recalculate the Route (same Activity Profile), the Route will only contain the user points, but not the paths between the points, and the elevation data for the user points will remain. In BaseCamp, the route will appear as straight lines between user points.

When this route is sent to a device, it will only have the user points and it will not be designated as a Direct Route. On my device this Route will be calculated each time it is activated and since I have DEM data on the device, I would expect to see an elevation plot. The main advantage on my device would be that auto-rerouting would be guaranteed to work. This was not always the case in earlier firmwares for my particular device.

The other option I gave was to convert the Route to a Track to a Direct Route and send that to your device. To do this, use the BaseCamp map with the DEM and change the Activity Profile to Direct before pressing the Create Route on the Track Properties tab. The catch is that Devices are only allowed a limited number of user points in a Route (mine is 250 yours may be less). If you exceed this limit, the Route might send an error message when activated on the Device or it may truncate the route. The appearance of the Route on the Map will be similar, but not exact. If you still do not see an elevation plot (the Route Properties tab should show elevation data on the Properties Tab), then it is likely that your device does not use the elevation data in a Route.

Tracks behave differently because all track points store elevation data if available. When tracks are logged in real time, the elevation data comes from the gps location solution or the pressure sensor if the device has one. When created in BaseCamp a map with a DEM is required.

I fully understand, and indeed looking closer to the gpx from the route, I do have elevation only for the user points, and not for the path point as you perfectly described. Where I am stuck, is that the TOPO itself does have DEM data, and the TOPO is also on my device, this is the map I always use. On the device I also have the DEM garmin map...so why my device is not plotting this elevation profile i can see in basecamp, no clue, maybe as you said, the device does not use elevation data in a route..

Any other user of garmin edge 820?

And many thanks BTLAAKE, i learnt a lot thanks to your post

jerome

Sorry I couldn't be of more help. But without owning your particular unit, it is hard to give concrete device. If it is possible, you should create a route, or perhaps it is called a course, on your device and see if shows an elevation plot. If it does, take a look at the gpx file on your device and see what was stored by the device. (I assume the firmware on the device is up to date.)

sorry for the delay responding. I did as per your suggestion, indeed called a course on the device, but the course I create has to be used directly, I cannot save them...unless I am mising something. The only course I can create and save is when creating a course from a past activity, in order to compete against..virtual partner.

Activity profile is great in the unit, extract the gpx to the computer, and open it via notepad, the gpx is actualy a track, not a route..

So I ended up creating track from route in basecamp prior loading it to the unit. I do not see any difference in riding as the Edge automatically create the TBT instructions..I am surely lacking functionalities of a route, but I do not see which one.

cheers

You may be missing the capability to auto-reroute in the event of an unexpected detour. But I'm am not that familiar with the edge devices.

I was poking around in Edge and Oregon and 64s "manuals" one day, but am totally in the dark on fitness files, or the Garmin condensed version of them. Is it possible that converting route files to human readable "fit" files and then converting those files to a format that the Edge could import would give elevations in TBT "routes"?

I believe that OP?s Edge can import gpx files. But, an automated Route only contains elevation data for the user points and then only if a map with a DEM is selected. The paths between user points do not contain elevation data.

I would have expected the device to grab elevation from a DEM if it was available on the device. That is what an Oregon or 64 would do when importing a Route.

Tracks differ in that all the points will have elevation data if available.

I'm also not familiar with the contents of fit files or what extensions Garmin may have added. If you?re interested in fit files you should look on the thisisant.com site. They might provide some details.