The Route Scout function Save/Share creates an RS Triplog on HAZ. Which is the combination of a triplog plus an embedded GPS Route.
After recording a hike on Route Scout: Files > tap the file > Save/Share [ Example
Legacy standalone GPS Routes ( +Add > GPS Route ) are intended for Official Routes. They take significantly more resources for HAZ to serve/share vs an RS Triplog with an embedded route. Processing equipment and third-party API services are the top two resources.
About the route in an RS Triplog
The route is directly viewable from a triplog: Popup & MapDEX. MapDEX is intended for advanced planning, it uses resources that are not necessary for a quick dynamic overview.
The route populates in key places standalone GPS Routes are found too:
- MapDEX (Plan>Map)
- Mini Map & Route tab list on profile pages
The embedded route may be downloaded, Send to Route Editor
is in the elevation profile on MapDEX.
When an RS Triplog is found on MapDEX, the entire triplog displays when selected without leaving the page.
The embedded route may optionally be edited before the final triplog "Post" and up to 5 days after.
Private / Public
RS Triplogs have the option to set the route as private.
RS Triplogs use a different structure and method to deliver the "view" of the route. It is more efficient than legacy GPS Routes for both HAZ* and the now market share of mobile** devices vs desktop/laptop.
* Super efficient for HAZ, could easily serve a billion vs 100k standalone.
** Minimal but a quicker experience for the end-user. Test any RS Triplog and Popop is faster than MapDEX.
Save/Share is very helpful in keeping HAZ online.