Export Routes – Download Route Data in CSV File
Table of Contents
Route4Me’s dynamic routing software uses proprietary and patented route optimization algorithms that allow you to plan the most time-efficient and cost-effective routes with multiple stops in a smooth and effortless manner. With Route4Me route planning software, you can export optimized routes and use them on the preferred GPS devices. The exported route data can also be used for sharing with your team of delivery drivers, sales reps, field technicians, dispatchers, route planners, etc. Moreover, you can also use the exported data for making reports, conducting analysis or audits of your routing operations, and many other activities that can help you in growing and improving your business.
Exporting Route Data from Your Routes List
To export route data from your Routes List, first, go to Routes List from the navigation menu.
Next, click on the gear icon next to the optimized route that you want to export.
After that, hover your cursor over Export, and then, select one of the provided options from the list. You can see the descriptions of all export items and how to customize the export file further in this tutorial.
Exporting Multiple Routes’ Data from Your Routes List
To export multiple routes’ data from your Routes List:
- First, check the boxes next to the routes that you want to export;
- Next, click File in the toolbar, hover your cursor over Download as, and then, select one of the available options respectively.
You can see the descriptions of all export items and how to customize the export file further in this tutorial.
Exporting Route Data from the Routes Map
To export route data from the Routes Map, first, go to Routes Map from the navigation menu.
Next, click on the gear icon next to the route that you want to export.
After that, hover your cursor over Export, and then, select one of the provided options from the list. You can see the descriptions of all export routes items and how to customize the export file further in this tutorial.
Exporting Multiple Routes’ Data from the Routes Map
To export multiple routes’ data from the Routes Map:
- First, check the boxes next to the routes that you want to export;
- Next, click File in the toolbar, hover your cursor over Download as, and then, select one of the available options respectively.
You can see the descriptions of all export routes items and how to customize the export file further in this tutorial.
Exporting Route Data From the Route Editor
To export route data from the Route Editor, first, go to Routes List from the navigation menu.
Next, click on the route that you want to export to open it in the Route Editor.
In the Route Editor, first, click File in the toolbar, hover your cursor over Download as, and then, select one of the provided file formats that you want to export.
The descriptions of all available export formats are provided below:
-
Export CSV: Allows you to export routes as customizable CSV files;
-
Export Notes as CSV: Exports the route notes with the attached photos, videos, text, voice messages, etc.;
-
Export Minimal Without Addresses: Exports only the items from the Route, Time, Time Travel Details, Density, Driver, and User Notes sections of the full export file;
-
Export to 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;
-
Export to KML: Exports an optimized KML (Keyhole Markup Language) file that can be uploaded and used on the devices that support the corresponding format;
-
Export to 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;
-
Export to 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;
-
Export to Freshroute: Exports an optimized file that can be used on Freshroute;
-
Export to Navigon 5: Exports an optimized file with the route’s data that can be uploaded to the devices that support the Navigon 5 maps and used for driving the exported route respectively;
-
Export to 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;
-
Export to 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;
-
Export Tracking History as CSV: Exports the tracking history of the route as a CSV file.
-
Export Route Map Picture: Exports a high-resolution image of the route.
Customizing the Export File
Route4Me allows you to easily customize the export file for your convenience. To customize the export file, first, select the Export CSV option using one of the methods described earlier in this tutorial. Selecting the Export CSV option will open the Export Route Data window that allows you to customize the list of the items that you want to include in the export file.
Use the Field Search to find the items that you want to include in the export file.
Type the full or partial name of the item that you are looking for into the Field Search, and then, select the preferred item(s) from the search results.
Check the boxes next to the items that you want to include in the export file. The added items are displayed in the right section of the window.
To export the items in a specific order, click on the three dots icon next to the item that you want to move and drag it to the preferred position on the list.
Export Profiles allow you to create templates with specifically selected items that can be saved and reused in the future.
To create an Export Profile, first, check the boxes next to the items that you want to include in the export file, then, type the name of the template into the Export Profiles field and click Add. Once the Export Profile is added, it can be reused.
Finally, click Export to download the file with all selected items to your computer/device.
Route Data Glossary
Please refer to the glossary below for clarification of the terms in the exported files.
Term | Description |
---|---|
Actual_Arrival_Time | This is the time when a driver actually arrived at the stop/address. The Actual_Arrival_Time is calculated based on the most accurate data available, for example when the stop was marked as visited manually by a driver or when a driver entered and triggered the geofence around the stop/address and Route4Me automatically generated the Detected as Visited timestamp (M/D/YYYY HH:MM). |
Actual_Arrival_Time_Computation_Method | The method used for computing the actual arrival time (based on Mark_as_Visited, Geofence_Entered, etc.). |
Actual_Departure_Time | This is the time when a driver actually departed from the stop/address. The Actual_Departure_Time is calculated based on the most accurate data available, for example when the stop was marked as departed manually by a driver or when a driver exited and triggered the geofence around the stop/address and Route4Me automatically generated the Detected as Departed timestamp (M/D/YYYY HH:MM). |
Actual_Departure_Time_Computation_Method | The method used for computing the actual departure time (based on Mark_as_Departed, Geofence_Departed, etc.). |
Actual_Distance_Computation_Method | The method used for computing the actual traveled distance on the route (based on the Tracking Data, Estimated, etc.). |
Actual_Distance_From_Previous_Stop | The actual distance traveled from the previous stop/address on the route to the given one. |
Actual_Distance_From_Start | The actual distance traveled from the start of the route to the given stop/address. |
Actual_Drive_Time_Computation_Method | The method used for computing the actual driven time on the route (based on Mark_As_Visited_And_Departed, Geofence_Departed_And_Arrived, etc.). |
Actual_Running_Distance | The actual distance traveled by a driver by the time of reaching the given stop/address on the route. |
Actual_Running_Drive_Time | The actual time that has been driven by a driver by the time of reaching the given stop/address on the route. |
Actual_Running_Service_Time | The actual time spent by a driver on servicing previous stops on the route by the time of reaching the given stop/address. |
Actual_Service_Time | The actual time spent on servicing the given stop/address. |
Actual_Service_Time_Computation_Method | The method used for computing the actual service time of the stop/address on the route (based on Mark_As_Visited_And_Departed, Geofence_Departed_And_Arrived, etc.). |
Actual_Time_From_Previous_Stop | The actual time traveled from the previous stop on the route to the given one. |
Actual_Time_From_Start | The actual time traveled from the start of the route to the given stop/address. |
Address | Information used for describing the location of a stop or destination. Normally an address should contain the following identifiers: street name and number, city, state, country, and zip code. An Address may also be referred to as a Stop or Destination. |
Address_Latitude | The latitude coordinates (decimal form, rooftop) of the stop/address. |
Address_Longitude | The longitude coordinates (decimal form, rooftop) of the stop/address. |
AddressBook_Last_Departed | The time when the given address from the Address Book was last marked or detected as departed. |
AddressBook_Last_Visited | The time when the given stop/address from the Address Book was last marked or detected as visited. |
Address_Type | The type of the stop/address: Pickup, Delivery, Break, Meetup, Visit, Service or Drive-By. |
Alias | Alias (name) assigned to the stop/address. |
Cost | The total cost of servicing the stop/address. |
Cube | The total cubical volume that is picked up or dropped off at the stop/address. |
Curbside_Latitude | The stop’s latitude coordinates (decimal form, curbside). |
Curbside_Longitude | The stop’s longitude coordinates (decimal form, curbside). |
Customer_PO | The purchase order of the customer that is associated with the given stop/address. |
Departed | Binary column indicating whether the address was marked as departed (displays 1 if departed). |
Departed_Latitude | Latitude coordinates of the location where the stop/address was marked or detected as departed. |
Departed_Longitude | Longitude coordinates of the location where the stop/address was marked or detected as departed. |
Device_Type | The type of device that was used for sending and receiving GPS signal and other data from Route4Me’s servers (iPhone, Android, etc.). |
Distance_to_Next | Total distance from the given stop/address to the next one on the route. |
Drive_Time_to_Next | Total travel time from the given stop/address to the next one on the route (HH:MM:SS). |
First_Name | First name of the contact person at the receiving stop/address. |
Fuel_Cost_From_Start | The total cost of the consumed fuel used for getting to the given stop/address on the route. |
Fuel_From_Start | The amount of fuel (in gallons) consumed for getting to the given stop/address on the route. |
Geofence_Departed_Time | The automatically created Detected as Departed timestamp that was generated upon departing from the geofenced area of the stop/address after staying in it for a predefined period of time. |
Geofence_Time_On_Site | The total time spent by a driver inside the geofenced area of the stop/address. |
Geofence_Visited_Time | The automatically created Detected as Visited timestamp that was generated upon entering a geofenced area of the stop/address and staying in it for a predefined period of time. |
Group | The name of the group that is associated with the stop/address. |
Invoice_No | The invoice number associated with the stop/address. |
Last_Name | Last name of the contact person at the receiving stop/address. |
Marked_Arrival_Time | The timestamp that was created when a driver manually marked the stop/address as Visited. |
Marked_Departure_Time | The timestamp that was created when a driver manually marked the stop/address as Departed. |
Marked_Stop_Time | The time that a driver spent on site of the given stop/address and marked it respectively. |
Member_Email | The email address of the member assigned to the route. |
Member_First_Name | First name of the member assigned to the route. |
Member_ID | Identification number of the member assigned to the route. |
Member_Last_Name | Last name of the member assigned to the route. |
Note_Attachment_URL | URL of the file that is attached to the note of the stop/address. |
Note_Content | The content of the note attached to the stop/address (custom text). |
Note_Lat | The latitude coordinates received by Route4Me’s servers upon adding the note to the stop/address. |
Note_Lng | The longitude coordinates received by Route4Me’s servers upon adding the note to the stop/address. |
Note_Time | The timestamp that was created upon adding the note to the stop/address. |
Note_Type | The type of note attached to the stop/address (note status). |
Optimized_Time_Window_End | Time window end after applying time constraint relaxation. |
Optimized_Time_Window_Start | Time window start after applying time constraint relaxation. |
Order_No | The number of the order associated with the stop/address. |
Phone | The phone number of the contact person associated with the stop/address. |
Pieces | The number of pieces to be delivered or picked up from the stop/address. |
Priority | The priority of the stop/address on the route (1 – highest priority; 255 – lowest priority). |
Predicted_Arrival_Time | When a driver arrives at the stop/address a little early or a little later, the Predicted_Arrival_Time of all remaining stops on the route will be affected. The Predicted_Arrival_Time constantly changes to accurately reflect when a driver will arrive at stops/addresses later on the route. |
Predicted_Departure_Time | When a driver arrives at the stop/address a little early or a little later, the Predicted_Departure_Time of all remaining stops on the route will be affected. The Predicted_Departure_Time constantly changes to accurately reflect when a driver will depart to the next stop/address on the route. |
Reference_No | The reference number of the stop/address on the route. |
Remaining_Cube | Positive Remaining_Cube values indicate the occupied space on a vehicle when negative values indicate the reserved/free space on a vehicle upon reaching the stop/address. |
Remaining_Pieces | Positive Remaining_Pieces values indicate the occupied space on a vehicle when negative values indicate the reserved/free space on a vehicle upon reaching the stop/address. |
Remaining_Weight | Positive Remaining_Weight values indicate the occupied space on a vehicle when negative values indicate the reserved/free space on a vehicle upon reaching the stop/address. |
Revenue | The revenue generated from the stop/address. |
Route_Addresses_Count | Number of stops/addresses on the route (excluding the departure address). |
Route_ID | The unique internal identification number of the route. |
Route_Name | The name assigned to the route. |
Route_No | The route number (relevant for multi-route exports). |
Route_Notes | All notes that are attached to the route. |
Route_Planned_Time | The total estimated time required for completing the route. |
Route_Planned_Total_Drive_Time | The total drive time that is computed based on the Route_Planned_Time + Route_Planned_Total_Service_Time + Wait_Time variables. |
Route_Planned_Total_Service_Time | The total estimated time required for servicing all stops on the route. |
Route_Start_Time | The time when the route started. |
Route_Total_Distance | The total distance traveled on the route. |
Route_Wait_Time | The 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.). |
Running_Distance | The total distance traveled by a driver upon reaching the given stop/address on the route. |
Running_Service_Time | The total time spent by a driver on servicing previous stops/addresses on the route upon reaching the given stop/address. |
Running_Travel_Time | The total time traveled by a driver upon reaching the given stop/address on the route. |
Planned_Arrival_Time | This is the estimated arrival time when a driver will arrive at the stop/address. The arrival time is calculated based on the route start time, the travel time to the next stop, the wait time (if applicable) to the next stop, and the service time at each stop. |
Planned_Departure_Time | This is the estimated departure time when the driver will depart from the stop/address. The departure time is calculated based on the route start time, the travel time to the next stop, the wait time (if applicable) to the next stop, and the service time at each stop. |
Scheduled_For | The scheduled time and date of the route’s start. |
Sequence_No | The sequence number of the stop/address on the route. |
Service_Time | The expected amount of time required for servicing the corresponding stop/address (integer minutes or HH:MM:SS). |
SPORH | The estimated number of stops visited per on-road hour. |
Stem_In_Time | The time spent on getting from the depot to the first stop on the route. |
Stem_Out_Time | The time spent on getting to the depot after visiting the last stop on the route. |
Time_Impact | The time impact that the earliness or tardiness of a driver had on the stop/address (expressed in minutes). |
Time_Window_End | The estimated end time of the first time window of the stop/address (HH:MM:SS, military time). |
Time_Window_End_2 | The estimated end time of the second time window of the stop/address (HH:MM:SS, military time). |
Time_Window_Start | The estimated beginning time of the first time window of the stop/address (HH:MM:SS, military time). |
Time_Window_Start_2 | The estimated beginning time of the second time window of the stop/address (HH:MM:SS, military time). |
TPORH | The estimated amount of transactions per on-road hour. |
Vehicle_Alias | The alias/name of the vehicle associated with the route. |
Vehicle_ID | The unique identification number of the vehicle associated with the route. |
Visited_Latitude | Latitude coordinates of the location where the address was marked as visited. |
Visited_Longitude | Longitude coordinates of the location where the address was marked as visited. |
Wait_Time_From_Start | The time of the driver’s inactivity from the start of the route. |
Weight | Total weight capacity of a vehicle upon visiting a stop/address. Positive Weight values indicate the amount of loaded weight on the vehicle when negative weight values indicated the total reserved weight capacity on the vehicle. |
Visit Route4Me's Marketplace to Check out Associated Modules:
- Routing
Route Management
- Operations
Ultra High Resolution Route Mapping