Export Routes – Download Route Data As CSV Files, Destination Notes, And Attachments, Access Export Catalog
Route4Me’s dynamic routing software uses patented route optimization algorithms to help plan time- and cost-efficient multi-destination routes. Optimized routes can be exported to GPS devices and shared with delivery drivers, sales reps, field technicians, dispatchers, and route planners. Exported route data can also be used for reporting, performance analysis, and operational auditing. This guide shows you how to export route data, performance metrics, and route KPIs.
Table of Contents
Export Route Data With Route4Me Route Management Tools
Route4Me’s business route planning software helps you plan and manage routes using tools such as the Routes Page, Routes Map, and Route Editor.
The Routes Page displays all planned and optimized routes in your account; the Routes Map allows you to view and adjust multiple routes on an interactive map; and the Route Editor provides access to detailed destination settings.
Each of these tools also supports exporting route data as a CSV file or as navigation data for GPS devices.
Routes List – Export Routes From Routes List
To export route data from your Routes List, go to “Dynamic Routing” > “Routes” from the Navigation Menu. Then, click the Down Arrow next to a route you want to export, hover over “Export Route“, and select an export option from the menu.
Learn more about export options and how to customize export files in the Detailed Export section of this guide.
To export data for multiple routes, select the routes you want to export. Then, click “Bulk Actions“, hover over “Export Routes“, and choose an export option. NOTE: Navigation exports, except UPD, are not available when exporting multiple routes.
Learn more about export options and how to customize export files in the Detailed Export section of this guide.
The following table provides an overview of the export options available from the Routes List.
| Export Option | Description |
|---|---|
| Export Route | Exports routes as CSV files with customizable data columns, including distance, duration, status, and more. You can create Export Profiles to reuse preferred data selections. |
| Export Route Destinations | Exports route destinations as CSV files with customizable columns such as destination ID, address, coordinates, and related destination data. Export Profiles can be used to save column selections. |
| Export Route Notes | Exports route notes as CSV files with customizable columns, including note ID, note type, and note content. Export Profiles allow you to reuse selected fields. |
| Export Tracking History | Exports route tracking data as CSV files, including timestamps, coordinates, speed, odometer readings, altitude, vehicle ID, and tracking device ID. |
| Export Route Attachments | Exports an archive containing all documents, images, videos, and other media files attached to destination notes on the route. |
| Export Route Map Image | Exports a high-resolution image of the route map with marked stops and the highlighted route path. |
| More Formats | Exports route data for use with GPS navigation devices in formats such as XML, TomTom, KML, and others. See “Export Route Data for GPS Navigation Devices” later in this guide for a full list. |
Routes Map – Export Route Data From Routes Map
To export route data from the Routes Map, go to”Dynamic Routes” > “Routes Map” from the Navigation Menu. Then, click the Down Arrow next to a route that you want to export, hover over “Export“, and select an export option.
To access export options for navigation devices on the Routes Map, hover over “Advanced Route Export” in the “Export” menu. You can learn more about export options and how to customize export files in the Detailed Export section of this guide.
NOTE: If you do not see a separate Routes Map in your account, use the Interactive Route Map on the Routes Page, which includes all the same export tools and functionality.
You can also export data for multiple routes. Just check the boxes next to the routes you want to export and click “File” in the Toolbar. Then, hover over “Export Route” and select one of the available export options from the menu.
NOTE: When exporting multiple routes, export for navigation isn’t available.
You can learn more about export options and how to customize export files in the Detailed Export section of this guide.
The following table provides an overview of the export options available from the Routes Map.
| Export Option | Description |
|---|---|
| Export CSV | Exports route data as CSV files with customizable data columns, including address visit, distance, duration, geofence, and other key details. |
| Export Notes As CSV | Exports route notes as CSV files with customizable columns, including note ID, note type, and note content. |
| Export Minimal Without Addresses | Exports key route data as CSV files with customizable columns, without including any address information. |
| Export Tracking History As CSV | Exports route tracking data as CSV files, including timestamps, coordinates, speed, odometer readings, altitude, vehicle ID, and tracking device ID. |
| Advanced Route Export | Exports route data for use with GPS navigation devices in formats such as XML, TomTom, KML, and others. See “Export Route Data for GPS Navigation Devices” later in this guide for a full list. |
| Export Route Map Picture | Exports a high-resolution image of the route map with marked stops and the highlighted route path. |
Route Editor – Export Routes From Route Editor
To export route data from the Route Editor, click “File” in the toolbar, hover over “Export Route“, and select an export option.
Learn more about export options and how to customize export files in the Detailed Export section of this guide.
Detailed Route Export – Customizable CSV Spreadsheets For Exporting Routes
When exporting routes, you can choose from several formats.
Route data can be exported as a customizable CSV spreadsheet, a Route Map image for individual routes, or as a collection of Route Attachments containing any media or documents linked to destinations.
You can also export route data for use with navigation devices such as Garmin. More information on exporting routes for navigation is provided later in this guide.
| Export Option | Description |
|---|---|
| Export as CSV | Exports routes as CSV files with customizable data columns. You can create custom export profiles which include your preferred data selections. |
| Route Map Image | Exports a high-resolution route map with marked stops and highlighted route path. |
| Route Attachments | Export an archive of all documents, image, video, and other media files attached to destination notes on the route. |
You can customize all CSV exports. From the export menu, you can choose which fields you want to include in the exported file.
Selected fields appear in the panel on the right, where you can drag and reorder them to control the column order in the exported CSV. You can also use the Field Search bar to quickly find fields and the X icon to remove them.
In addition, you create Export Profiles, reusable templates with pre-selected items for route exports. To create a Profile, check the boxes for the data you want to include and enter a Profile Alias in the Export Profile field.
The system saves the Alias automatically. You can then reuse the profile to export CSV spreadsheets with the same details. Just select the profile and click “Export“.
Refer to the following glossary for definitions of terms included in exported files.
| Item | CSV Term | Description | |
|---|---|---|---|
| Route | |||
| Route ID | Route_ID | The unique internal identification number of the route. | |
| Route Name | Route_Name | The name (alias) assigned to the route. | |
| Route # | Route_Number | The route number. This is relevant when you are exporting multiple routes. | |
| Route Total Distance | Route_Total_Distance | The total distance traveled on the route. | |
| Planned Total Route Duration | Planned_Total_Route_Duration | The total estimated time planned for completing the route. | |
| Route Address Count | Route_Addresses_Count | Number of destinations on the route, excluding the departure address (depot). | |
| Planned Total Travel Time | Planned_Total_Travel_Time | The total drive time that is computed based on the Route_Planned_Time + Route_Planned_Total_Service_Time + Wait_Time variables. | |
| Planned Total Service Duration | Planned_Total_Service_Duration | The total planned time required for servicing all destinations on the route. | |
| Scheduled For | Scheduled_For | Scheduled route start date and time. | |
| Destination Status | Stop_Status | The last destination Status that was set or updated for the respective destination. | |
| Destination Status Time UTC | Stop_Status_Time_UTC | The time (in UTC) when the respective destination Status was set or updated for the destination. | |
| Destination Status Time | Stop_Status_Time | The time when the respective destination Status was set or updated for the destination in the time format of the main Route4Me account. | |
| Planned Destinations | Planned_Destinations | Total number of destinations currently without a status: Done, Skipped or Failed. | |
| Failed Destinations | Failed_Destinations | Total number of destinations marked as “Failed” by the assigned User via the Mobile App. | |
| Skipped Destinations | Skipped_Destinations | Total number of destinations marked as “Skipped” by the assigned User via the Mobile App. | |
| Completed Destinations | Completed_Destinations | Total number of destinations marked as “Done” by the assigned User via the Mobile App.” | |
| Facility | Facility | The depot, warehouse, or starting point used for planning the route; serves as the origin for route sequencing and time calculations. | |
| Planned Total Break Time | Planned_Total_Break_Time | The total duration of all scheduled breaks for the route, calculated based on the planned stops and route schedule. | |
| Total Route Man-Hours | Total_Route_Man_Hours | The sum of the planned time required for all stops and travel on the route, representing the total labor hours needed to complete it. | |
| Route Start Odometer | Route_Start_Odometer | The vehicle odometer reading at the beginning of the route. | |
| Route End Odometer | Route_End_Odometer | The vehicle odometer reading at the completion of the route. | |
| Actual Odometer Distance | Actual_Odometer_Distance | The total distance traveled on the route, calculated from the start and end odometer readings. | |
| Route Status | Route_Status | The current state of the route, such as Planned, In Progress, or Completed. | |
| Route Custom Field Alias | Route_Custom_Field_Alias | The name or label assigned to a custom field created for the route. | |
| Route Custom Field Value | Route_Custom_Field_Value | The value or data entered for the corresponding route custom field. | |
| Time | |||
| Planned Route Start Date | Planned_Route_Start_Date | Date when the route is or was planned to start. | |
| Planned Route Start Time | Planned_Route_Start_Time | Time when the route is or was planned to start. | |
| Actual Route End Date | Actual_Route_End_Date | Date when the route is planned to be or was completed. | |
| Actual Route End Time | Actual_Route_End_Time | Time when the route is planned to be or was completed. | |
| Route Start Timestamp | Route_Start_Timestamp | Timestamp of the time when the route was actually started. | |
| Route End Timestamp | Actual_Route_End_Timestamp | Timestamp of the time when the route was actually completed. | |
| Time From Start To First Destination | Time_From_Start_To_First_Destination | Time duration from the start of the route to the first destination on the planned route. Calculated based on the Planned Arrival Time of the first destination on the route. Represents the Travel Time between the route origin (depot) and first destination. | |
| Time From Last Destination To Start | Time_From_Last_Destination_To_Start | Time duration from the last destination on the planned route to the route origin location (depot). Used for round trip routes where the assigned User returns to the route origin (depot) after completing the last destination on the route. | |
| Actual Duration | |||
| Actual Route Duration (User Actioned) | Actual_Route_Duration_(User_Actioned) | Actual Route Duration is calculated based on the received Mobile App GPS data. Duration is measured from when the route was started to when the route was ended by the assigned User on the Mobile App. | |
| Actual Total Route Duration (Grand Total of All Sub-Durations) | Actual_Total_Route_Duration_(Grand_Total_of_All_Sub-Durations) | The total time spent traveling the route, including all individual segments and stop durations. | |
| Actual Total Travel Duration (User Actioned) | Actual_Total_Travel_Duration_(User_Actioned) | The total time spent traveling the route, recorded from driver actions in the Mobile App. | |
| Actual Total Service Duration (User Actioned) | Actual_Total_Service_Duration_(User_Actioned) | The total time drivers spent servicing stops, recorded from actions in the Mobile App. | |
| Actual Total Duration (Mobile_App) | Actual_Total_Duration_(Mobile_App) | The total time recorded for the route, based on driver activity captured in the Mobile App. | |
| Actual Travel Time (Telematics) | Actual_Travel_Time_(Telematics) | The total time spent traveling the route, recorded automatically by connected telematics or GPS devices. | |
| Actual Travel Time (Mobile App + Telematics) | Actual_Travel_Time_(Mobile_App_+_Telematics) | The total time spent traveling the route, recorded from both driver actions in the Mobile App and data from connected telematics devices. | |
| Travel Time Details | |||
| Route Wait Time | Route_Wait_Time | Total amount of time that a driver spent being inactive while driving the route (i.e., a route started before the opening hours and a driver had to wait, a driver arrived at the address before the opening of the Time Window, etc.). | |
| Density | |||
| Stops Per On-Road Hour | Stops_Per_On-Road_Hour | Dynamically predicted number destinations (stops) visited per hour spent driving the route. If the route is completed, this will reflect the actual average value instead of an estimate. | |
| Transactions Per On-Road Hour | Transactions_Per_On-Road_Hour | Dynamically predicted number transactions per hour spent driving the route. If the route is completed, this will reflect the actual average value instead of an estimate. | |
| Driver | |||
| Vehicle ID | Vehicle_Id | Unique identification number of the vehicle associated with the route. | |
| Vehicle Alias | Vehicle_Alias | Alias (name) of the vehicle associated with the route. Vehicle Alias can be used to search for vehicles in the Vehicles List and when assigning vehicles to routes or dispatching routes to vehicles. | |
| User | |||
| User ID | User_Id | Identification number of the team member assigned to the route. | |
| User Email | User_Email | Email address of the team member assigned to the route. | |
| User First Name | User_First_Name | First name of the team member assigned to the route. | |
| User Last Name | User_Last_Name | Last name of the team member assigned to the route. | |
| Assignment & Attribution | |||
| Assigned Customer Name | Assigned_Customer_Name | The name of the customer associated with the route or destination, as defined in the account or order data. | |
| Assigned Contract | Assigned_Contract | The name or identifier of the contract linked to the assigned customer, if applicable, used for tracking or reporting purposes. | |
| Notes | |||
| Route Notes | Route_Notes | Total number of Notes attached to destinations on the route. Normally, Notes are attached to destinations by the assigned User using the Mobile App. | |
| Actual Route Distance | |||
| Actual Travel Distance (Mobile App) | Actual_Travel_Distance_(Mobile_App) | Actual Travel Distance traveled by assigned Users on the route. Actual Travel Distance is calculated based on the on-road Travel Distance between destinations and does not include distance traveled inside Geofences. | |
| Actual Travel Distance (Telematics) | Actual_Travel_Distance_(Telematics) | Actual Route Travel Distance based on the received Telematics GPS data. Actual Travel Distance is calculated based on the on-road Travel Distance between destinations and does not include distance traveled inside Geofences. | |
| Actual Travel Distance (Mobile App + Telematics) | Actual_Travel_Distance_(Mobile_App_+_Telematics) | Actual Travel Distance traveled by assigned User. Actual Travel Distance is calculated based on the on-road Travel Distance between destinations and does not include distance traveled inside Geofences. | |
| Completed Distances | |||
| Completed Planned Distance % (Telematics) | Completed_Planned_Distance_%_(Telematics) | Percentage of the route’s total planned distance that was traveled by the assigned Vehicle calculated based on the received Telematics GPS data. | |
| Completed Planned Distance % (Mobile App) | Completed_Planned_Distance_%_(Mobile_App) | Percentage of the route’s total planned distance that was traveled by the assigned User calculated based on the received Mobile App GPS data. | |
| Completed Planned Distance % (Mobile App + Telematics) | Completed_Planned_Distance_%_(Mobile_App_+_Telematics) | Percentage of the route’s total planned distance that was traveled by the assigned User calculated based on the combined Mobile App and Telematics GPS data. | |
| Remaining Distances | |||
| Remaining Planned Distance % (Telematics) | Remaining_Planned_Distance_%_(Telematics) | Percentage of the route’s total planned distance that was not traveled by the assigned Vehicle calculated based on the received Telematics GPS data. | |
| Remaining Planned Distance % (Mobile App) | Remaining_Planned_Distance_%_(Mobile_App) | Percentage of the route’s total planned distance that was not traveled by the assigned User calculated based on the received Mobile App GPS data. | |
| Remaining Planned Distance % (Mobile App + Telematics) | Remaining_Planned_Distance_%_(Mobile_App_+_Telematics) | Percentage of the route’s total planned distance that was not traveled by the assigned User calculated based on the combined Mobile App and Telematics GPS data. | |
| Deviations | |||
| Deviated From Planned Distance % (Telematics) | Deviated_From_Planned_Distance_%_(Telematics) | Percentage of the route’s total planned distance that was deviated from by the assigned Vehicle calculated based on the received Telematics GPS data. | |
| Deviated From Planned Distance % (Mobile App) | Deviated_From_Planned_Distance_%_(Mobile_App) | Percentage of the route’s total planned distance that was deviated from by the assigned User calculated based on the received Mobile App GPS data. | |
| Deviated From Planned Distance % (Mobile App +Telematics) | Deviated_From_Planned_Distance_%_(Mobile_App_+_Telematics) | Percentage of the route’s total planned distance that was deviated from by the assigned User calculated based on the combined Mobile App and Telematics GPS data. | |
| Progress Metrics | |||
| Sequence Adherence (%) | Sequence_Adherence_% | The number of stops visited in the exact order planned in the optimized route. This metric shows how closely the driver followed the prescribed stop sequence. | |
| Continuous Sequence Adherence (%) | Continuous_Sequence_Adherence_% | The number of consecutive stops visited in the correct order without any deviations. This highlights uninterrupted adherence to the planned route sequence, helping identify where deviations occurred. | |
Export Route Data For GPS Navigation Devices
Route4Me, the best route software for enterprise route planning, also lets you export route data for use with navigation devices such as Garmin GPS and others. Below is a description of the export options for different devices.
NOTE: Export for navigation is not available when exporting multiple routes.
| File Format | Description |
|---|---|
| TomTom | Exports an optimized route file with the route’s data that can be uploaded to TomTom devices and used for driving the exported route, respectively. |
| KML | Exports an optimized KML (Keyhole Markup Language) file that can be uploaded and used on the devices that support the corresponding format. |
| Fugawi | Exports an optimized route file with the route’s data that can be uploaded to Fugawi devices or software and used for driving the exported route, respectively. |
| Navigon 5 | Exports an optimized file with the route’s data that can be uploaded to the devices supporting the Navigon 5 maps and used for driving the exported route. |
| Navigon 6 | Exports an optimized file with the route’s data that can be uploaded to the devices that support the Navigon 6 maps and used for driving the exported route respectively. |
| Freshroute | Exports an optimized file that can be used on Freshroute. |
| Garmin (GPX) | Exports an optimized GPX file with the route’s data that can be uploaded to Garmin devices and used for driving the exported route, respectively. |
| Garmin (GPXX) | Exports an optimized GPXX file with the route’s data that can be uploaded to Garmin devices and used for driving the exported route, respectively. |
| Garmin (GPXTRK) | Exports an optimized GPXTRK file with the route’s data that can be uploaded to Garmin devices and used for driving the exported route, respectively. |
| Garmin (GPXRoute) | Exports an optimized GPXRoute file with the route’s data that can be uploaded to Garmin devices and used for driving the exported route, respectively. |
| LMX | Exports an optimized file with the route’s data that can be uploaded to Nokia devices and used for driving the exported route, respectively. |
| UPD | Exports an optimized route file with the route’s data that can be uploaded to various devices or software and used for driving the exported route respectively. |
Visit Route4Me's Marketplace to Check out Associated Modules:
- Platform
Route Management
- Operations
Ultra High Resolution Route Mapping
About author: Kristian Andreev
