Introduction
The following are the steps to enable and disable Navigation and Trip Planner within your Eleos application. Trip Planner and turn-by-turn Navigation are related to one another but are controlled separately.
If Trip Planner is enabled the user will see a suggested route found for the Load run. There is also a HOS Driving Range in Trip Planner.
| If Navigation is enabled, a user will also be able to click on a green arrow icon, that will provide turn by turn directions for along the route.  |
Within the Eleos API documentation there is a section for Loads that explains the two features in their platform. https://dev.eleostech.com/platform/#operation/getLoads
Eleos controls these features from a master level, so if you have Trip Planner and Navigation on, they suppress them if needed. Since Eleos requests a Support Request, and often clients may have various ways they want to control things internally, we recommend having Eleos toggle both on and using the Database settings to control either.
Database Layer
Both Navigation and Trip Planner are found for your integration in Databases in your TMS under Functions.
Trip Planner (Map Overview for Load)
trip_planner_enabled | boolean Nullable Controls whether the Trip Planner will be shown for this load, which allows drivers to see an overview map of their whole trip. To enable Trip Planner, set this to true. To prevent Trip Planner from showing, set this to false. If this flag is not specified, the default value depends on your account. If Trip Planner is available to your drivers at no additional cost, it will be shown by default. If showing Trip Planner will incur additional charges, it is opt-in and will not be shown by default. Trip Planner is available in version 1.36 and above. Enabling Trip Planner for drivers running previous versions of the app will have no effect. |
Locate the function “ELEOS.usp_GetLoads_Trips”, which is responsible for selecting load-level properties.
- TripPlannerEnabled = @False at the load level and this will remove the map.
- TripPlannerEnabled = @True will display the map.
Navigation (Turn by Turn Routing)
prevent_navigation | boolean Nullable When true, turn-by-turn navigation is disabled for stop navigation and POI navigation. This flag overrides prevent_navigation at the stop level. Default value is false. |
Locate the function “ELEOS.udf_StopNavigation” within the database.
- PreventNavigation = @False will allow navigation.
- PreventNavigation = @True will disable navigation.
Be mindful to ensure you are not changing COALESCED values, otherwise if set earlier in the process, it will defer to that.
Integration Layer
For Navigation to be enabled properly you also must verify the proper Geotab settings in the “appsettings” file within the integration. 
In the “appsettings” file locate the “Geotab” object where its properties are being defined:
For navigation to show, a latitude and longitude must exist, this is done by setting “Enabled” to true as well as “GeocodeStops” to true:
Since the GeocodeStops logic may also be often used by customers for lat/long creations, many have this true regardless of if they use Geotab or not, or even if they have navigation disabled. This could be for automatic lat/long creations for master data, or geocoding lat/longs for other routing products. Check with ASR if you are unsure.
It is best to leave this True unless it is conflicting with other software you have that generates lat/longs for you.