Export Routes – Download Route Data In CSV And Navigation File Formats
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 shared with your team of delivery drivers, sales reps, field technicians, dispatchers, route planners, etc. Moreover, you can also use the exported data to make reports, perform data analyses, audit your routing operations, and perform many other activities that can help you grow and improve your enterprise business. In this guide, you will learn how to export route data from the Routes List, Routes Map, Route Editor, export detailed route data with export profiles, and more.
Table of Contents
Export Route Data With Route4Me Route Management Tools
Route4Me’s Business Route Planning Software enables you to plan and manage routes with a variety of tools like the Routes List, where you can view all of the planned and optimized routes on your Route4Me account, the Routes Map, where you can view multiple routes on an interactive map simultaneously and move stops within and between routes, and the Route Editor, where you can access and modify route stop details, and more. Additionally, each of these tools enables you to export route data either as a CSV spreadsheet or as navigation data for use with a GPS navigation device.
Routes List – Export Routes From Routes List
To export route data from your Routes List, go to “Routes” and then “Routes” from the Navigation Menu. Then, click the Gear Icon next to the route you want to export. After that, hover over “Export” and select the preferred option from the menu. You can see the descriptions of all export items and how to customize the export file further on this page.
Additionally, you can export the data from multiple routes. 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” from the top menu bar and hover over “Export Routes“. Then, select one of the available export options from the menu. NOTE: When exporting multiple routes, export for navigation isn’t available.
You can see the descriptions of all export items and how to customize the export file further on this page.
Routes Map – Export Route Data From Routes Map
To export route data from the Routes Map, first go to”Routes” and then “Routes Map” from the Navigation Menu. Then, click the Gear Icon next to the route that you want to export. After that, hover over “Export” and select one of the options from the menu. You can see the descriptions of all route items and how to customize the exported file further on this page.
Additionally, you can export the data from multiple routes. To export multiple routes’ data from your Routes Map, first check the boxes next to the routes that you want to export. Next, click “File” from the toolbar and hover over “Export Route“. Then, select one of the available export options from the menu. NOTE: When exporting multiple routes, export for navigation isn’t available.
You can see the descriptions of all export items and how to customize the export file further on this page.
Route Editor – Export Routes From Route Editor
To export route data from the Route Editor, go to “Routes” and then “Routes” from the Navigation Menu of your enterprise route optimizer. Next, click the Open Icon next to the route you want to export to open it in the Route Editor.
In the Route Editor, click “File” in the toolbar, hover over “Export Route” and select one of the available export options from the menu. You can find more details about each option further in this guide. 
Detailed Route Export – Customizable CSV Spreadsheets For Exporting Routes
When you export routes from the Routes List, Routes Map, or Route Editor, you can select a variety of export formats. You can export route data as a CSV spreadsheet, exports route notes and tracking history as CSV, and export a Route Map Picture when exporting individual routes. Additionally, you can export route data for import into navigation devices such as Garmin. In detail, you can find more information on exporting route data for navigation further in this guide.
| Export Option | Description |
|---|---|
| CSV | Allows you to export routes as CSV files with customizable data columns. Additionally, you can create custom export profiles that include your preferred data. |
| Notes as CSV | Exports the route notes with the attached photos, videos, text, voice messages, etc. as CSV files. |
| Minimal AS CSV | Exports only the items from the Route, Time, Time Travel Details, Density, Driver, and User Notes sections of the full export file. |
| Tracking History as CSV | Exports the tracking history of the route as a CSV file. |
| XML | Exports the selected routes as markup XML files for convenient import into other software or systems. |
| Route Map Picture | Exports a high-resolution image of the 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. |
Route4Me’s fastest route management software allows you to easily customize the exported file for your convenience. To customize the exported file, click “File” from the top menu bar, hover over “Export Route“, and select “Export CSV” from the menu. This will open the “Export Route Data” window that allows you to customize the list of items that you want to include in the exported CSV file. Specifically, you can use the “Field Search” bar to find the items that you want to include in the exported file. Type the full or partial name of the item that you are looking for into the “Field Search” bar, and select the preferred items from the search results.
Check the boxes next to the items that you want to include in the exported file. The added items are displayed in the right section of the window, where you can change their order, which will change the order of the columns in the exported CSV file, or remove them from your selected items.
To export the items in a specific order, click and hold the Position Icon next to the preferred item and drag it to your preferred position in the list. Furthermore, this will adjust the column order in the exported route CSV.
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, check the boxes next to the items you want to include in the exported file, then type a preferred export template name into the Export Profiles field. The Export Profile can then be reused to export route data CSV spreadsheets with the same series of preferred items. Finally, click Export to download the file with all selected items to your device.
You can refer to the glossary below for clarification of the terms in the 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 assigned to the route. | |
| Route Number | route_no | 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. | |
| Route Planned Time | Route_Planned_Time | The total estimated time required for completing the route. | |
| Route Addresses Count | Route_Addresses_Count | Number of stops or addresses on the route, excluding the departure address (depot). | |
| Route Planned Total Drive Time | 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 | Route_Planned_Total_Service_Time | The total estimated time required for servicing all stops on the route. | |
| Scheduled for | Scheduled_For | The scheduled time and date when the route will start. | |
| Destination Status | Stop_Status | The last stop status that was set or updated for the route stop or address. | |
| Destination Status Time UTC | Stop_Status_Time_UTC | The time in UTC when the respective stop status was set or updated for the stop or address. | |
| Destination Status Time | Stop_Status_Time | The time when the respective stop status was set or updated for the stop or address in the time format of the main Route4Me account. | |
| Address | |||
| Destination ID | Destination_ID | Unique internal identification number of the stop or address. | |
| Alias | Alias | Сustom alias or name of the route stop (address). You can assign aliases to route stops (addresses) for faster and easier route searches or other operating requirements. | |
| Address | Address | Information used for describing the location of a stop or destination. Normally, an address should contain the location’s identifiers, such as street name and number, city, state, country, and zip code. An Address may also be referred to as a Stop or Destination. | |
| Address Type | Address Type | The type of the stop or address from the available address types. Specifically, Pickup, Delivery, Break, Meetup, Service or Visit. | |
| Address Latitude | Address_latitude | Latitude of the stop or address in decimal form at the rooftop of the location. | |
| Address Longitude | Address_longitude | Longitude of the stop or address in decimal form at the rooftop of the location. | |
| Curbside Latitude (Curbside Stop Latitude) | Curbside_latitude | Curbside stop’s latitude in decimal value. | |
| Curbside Longitude | Curbside_longitude | Curbside stop’s longitude in decimal value. | |
| Customer | |||
| Group | Group | Custom ID of the Address Book Group associated with the route stop (address). | |
| Customer PO (Customer Purchase Order) | Customer PO | Purchase order (PO) of the contact or customer associated with the route stop (address). | |
| First Name | First_Name | First name of the expected contact person at the receiving stop or address. | |
| Last Name | Last_Name | Last name of the expected contact person at the receiving stop or address. | |
| Email address of the contact person for the receiving route stop or address. | |||
| Phone | Phone | Phone number of the contact person for the receiving route stop or address. | |
| Order | |||
| Priority | Priority | Visitation priority of the route stop. The highest stop priority is 1, and the lowest stop priority is 999999. Accordingly, route stops (addresses) with higher priority are visited earlier on the route. | |
| Invoice Number | Invoice_No | Custom number of the invoice associated with the stop or address. | |
| Reference Number | Reference_No | Custom reference number of the stop or address on the route. Useful for identifying individual stops. | |
| Order Number | Order_No | The number of the order associated with the stop or address. | |
| Weight | Weight | Total weight capacity of a vehicle upon visiting a stop or address. Positive Weight values indicate the amount of loaded weight on the vehicle, while negative weight values indicate the total reserved weight capacity on the vehicle. | |
| Cost | Cost | Cost of the order associated with the stop or address. | |
| Revenue | Revenue | Revenue generated from servicing the stop or address. | |
| Cube | Cube | Total cubical volume that is picked up or dropped off at the stop or address. | |
| Pieces | Pieces | Total number of pieces or deliveries that are picked up or dropped off at the stop or address. | |
| Tracking Number | Tracking_Number | Tracking number associated with the stop, address, or respective delivery. | |
| Time | |||
| Service Time | Service_Time | Service Time (integer minutes or HH:MM:SS) required to service the route stop or address. | |
| Time Window Start | Time_Window_Start | Start time of the Time Window (working hours) when the route stop can be visited and serviced (Day 1, + HH:MM:SS or military time. For example: “Day 1, 9:00 AM”). Learn more about Route4Me’s Time Windows Route Optimization Constraint. | |
| Time Window End | Time_Window_End | End time of the Time Window (working hours) when the route stop can be visited and serviced (Day 1, + HH:MM:SS or military time. For example: “Day 1, 5:00 PM”). | |
| Time Window Start 2 | Time_Window_Start_2 | Start time of the Second Time Window (working hours) when the route stop can be visited and serviced (Day 2, + HH:MM:SS or military time. For example: “Day 2, 9:00 AM”). | |
| Time Window End 2 | Time_Window_End_2 | End time of the Second Time Window (working hours) when the route stop can be visited and serviced (Day 2, + HH:MM:SS or military time. For example: “Day 2, 5:00 PM”). | |
| Optimized Time Window Start | Optimized_Time_Window_Start | Time window start after applying time constraint relaxation. | |
| Optimized Time Window End | Optimized_Time_Window_End | Time window end after applying time constraint relaxation. | |
| Planned Arrival Time | Planned_Arrival_Time | Estimated arrival time when a driver will arrive at the stop or 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 | Planned_Departure_Time | Estimated departure time when the driver will depart from the stop or 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. | |
| Predicted Arrival Time | Predicted_Arrival_Time | When a driver arrives at the stop or address earlier or later, the Predicted_Arrival_Time of all remaining stops on the route will be affected. | |
| Predicted Departure Time | Predicted_Departure_Time | When a driver departs from the stop or address earlier or 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 or address on the route. | |
| Time Impact (Driver Time Impact) | Time_Impact | Time impact (expressed in minutes) that the earliness or tardiness of a driver had on the stop or address. | |
| 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. | |
| Route End Date | Route_End_Date | Date when the route is planned to be or was completed. | |
| Route End Time | Route_End_Time | Time when the route is planned to be or was completed. | |
| Route Start Button Timestamp | Route_Start_Button_Timestamp | Timestamp of the time when the route was actually started. | |
| Route End Button Timestamp | Route_End_Button_Timestamp | Timestamp of the time when the route was actually completed. | |
| Stem In Time (Time to First Stop) | Stem_In_Time | Time spent getting from the depot to the first stop on the route. | |
| Stem Out Time (Time from Final Stop) | Stem_Out_Time | Time spent getting from the last stop on the route back to the depot. | |
| Address Visit Details | |||
| Visited | Visited | Column indicating whether the address was marked as “Visited” or not. | |
| Address Book Last Visited | AddressBook_Last_Visited | Time when the given address from the Address Book was last marked or detected as visited. | |
| Address Book Last Departed | AddressBook_Last_Departed | Time when the given address from the Address Book was last marked or detected as departed. | |
| Marked Arrival Time | Marked_Arrival_Time | Timestamp that was created when a driver manually marked the stop or address as Visited. | |
| Marked Departure Time | Marked_Departure_Time | Timestamp that was created when a driver manually marked the stop or address as Departed. | |
| Marked Destination Time | Marked_Destination_Time | Time that a driver spent on-site at the given stop or address and marked so respectively. | |
| Visited Latitude | Visited_latitude | Latitude coordinates of the location where the address was marked as visited. | |
| Visited Longitude | Visited_longitude | Longitude coordinates of the location where the address was marked as visited. | |
| Departed | Departed | Column indicating whether the address was marked as “Departed” or not. | |
| Departed Latitude | Departed_latitude | Latitude coordinates of the location where the stop or address was marked or detected as departed. | |
| Departed Longitude | Departed_longitude | Longitude coordinates of the location where the stop or address was marked or detected as departed. | |
| Geofence Visited Time | Geofence_Visited_Time | The automatically created Detected as Visited timestamp that was generated upon entering the geofenced area of the stop or address after staying in it for a predefined period of time. | |
| Geofence Departed Time | Geofence_Departed_Time | The automatically created Detected as Departed timestamp that was generated upon departing from the geofenced area of the stop or address after staying in it for a predefined period of time. | |
| Geofence Time on Site | Geofence_Time_On_Site | Total time spent by a driver inside the geofenced area of the stop or address. | |
| Distance | |||
| Distance to Next | Distance_to_Next | Total distance from the given stop or address to the next one on the route. | |
| Time Travel Details | |||
| Drive Time to Next | Drive_Time_to_Next | Estimated drive time from the given stop or address to the next one on the route. | |
| Running Service Time | Running_Service_Time | Total time spent by a driver on servicing previous stops or addresses on the route upon reaching the given stop or address. | |
| Running Travel Time | Running_Travel_Time | Total time traveled by a driver upon reaching the given stop or address on the route. | |
| Running Wait Time | Running_Wait_Time | Total amount of inactive time spent by a driver upon reaching the given stop or address on the route (i.e., arrived at an address before the opening hours and a driver had to wait, etc.) | |
| 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.). | |
| Distance Travel Details | |||
| Running Distance | Running_Distance | Total distance traveled by a driver upon reaching the given stop or address on the route. | |
| Fuel | |||
| Fuel from Start | Fuel_From_Start | Amount of fuel (in gallons) consumed for getting to the given stop or address on the route. | |
| Fuel Cost from Start | Fuel_Cost_From_Start | Total cost of the consumed fuel used for getting to the given stop or address on the route. | |
| Operations | |||
| Remaining Weight | Remaining_Weight | A positive Remaining_Weight value indicates the occupied space on a vehicle, while negative values indicate the reserved or free space on a vehicle upon reaching the stop or address measured in weight. | |
| Remaining Pieces | Remaining_Pieces | A positive Remaining_Pieces value indicates the occupied space on a vehicle, while negative values indicate the reserved or free space on a vehicle upon reaching the stop or address measured in pieces | |
| Remaining Cube | Remaining_Cube | A positive Remaining_Cube value indicates the occupied space on a vehicle, while negative values indicate the reserved or free space on a vehicle upon reaching the stop or address measured as cubic space. | |
| Notes | |||
| Note Type (Note Status) | Note_Type | The type of note (note status) attached to the stop or address. | |
| Note Content (Note Text) | Note_Content | The content (custom text) of the note attached to the stop or address. | |
| Note Attachment URL | Note_Attachment_URL | Web address URL of the file that is attached to the note of the stop or address. | |
| Note Time | Note_Time | Timestamp that was created upon adding the note to the stop or address. | |
| Note Latitude | Note_Lat | Latitude coordinates received by Route4Me’s servers upon adding the note to the stop or address. | |
| Note Longitude | Note_Lng | Longitude coordinates received by Route4Me’s servers upon adding the note to the stop or address. | |
| Device Type | Device_Type | The type of device that was used for recording note data or sending and receiving GPS signals and other data from Route4Me’s servers (iPhone, Android, etc.). | |
| Route Notes | Route_Notes | All custom text notes added to each stop, separated by vertical lines. If Note_Content is selected, it will show separate addresses and the text of each address next to it. | |
| Actual Visit Details | |||
| Actual Arrival Time Computation | Actual_Arrival_Time_Computation | TBD | |
| Actual Departure Time Computation | Actual_Departure_Time_Computation | TBD | |
| Actual Arrival Time | Actual_Arrival_Time | Time when a driver actually arrived at the stop or 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 or address and Route4Me automatically generated the Detected as Visited timestamp (M/D/YYYY HH:MM). | |
| Actual Departure Time | Actual_Departure_Time | Time when a driver actually departed from the stop or 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 or address and Route4Me automatically generated the Detected as Departed timestamp (M/D/YYYY HH:MM). | |
| Expected Actual Distance from Previous Destination | Expected_Actual_Distance_From_Previous_Destination | Expected actual distance traveled from the previous stop or address on the route to the respective one. | |
| Expected Actual Time from Previous Destination | Expected_Actual_Time_From_Previous_Destination | Expected actual time traveled from the previous stop or address on the route to the respective one. | |
| Expected Actual Running Distance | Expected_Actual_Running_Distance | Actual distance traveled by a driver by the time of reaching the given stop or address on the route. | |
| Expected Actual Running Drive Time | Expected_Actual_Running_Drive_Time | Actual time that has been driven by a driver by the time of reaching the given stop or address on the route. | |
| Expected Actual Running Service Time | Expected_Actual_Running_Service_Time | Actual time spent by a driver on servicing previous stops on the route by the time of reaching the given stop or address. | |
| Actual Distance Computation Method | Actual_Distance_Computation_Method | Method used for computing the actual traveled distance on the route (based on the Tracking Data, Estimated, etc.). | |
| Actual Drive Time Computation Method | Actual_Drive_Time_Computation_Method | Method used for computing the actual driven time on the route (based on Mark_As_Visited_And_Departed, Geofence_Departed_And_Arrived, etc.). | |
| Actual Arrival Time Computation Method | Actual_Arrival_Time_Computation_Method | Method used for computing the actual arrival time (based on Mark_as_Visited, Geofence_Entered, etc.). | |
| Actual Departure Time Computation Method | Actual_Departure_Time_Computation_Method | Method used for computing the actual departure time (based on Mark_as_Departed, Geofence_Departed, etc.). | |
| Actual Service Time Computation Method | Actual_Service_Time_Computation_Method | Method used for computing the actual service time of the stop or address on the route (based on Mark_As_Visited_And_Departed, Geofence_Departed_And_Arrived, etc.). | |
| Expected Actual Time from Start | Expected_Actual_Time_From_Start | Expected actual time traveled from the start of the route to the given stop or address. | |
| Expected Actual Distance from Start | Expected_Actual_Distance_From_Start | Expected actual distance traveled from the start of the route to the given stop or address. | |
| Total Actual Route Distance | Total_Actual_Route_Distance | Actual total distance to complete the route, accounting for detours, delays, and other factors | |
| Total Actual Route Time | Total_Actual_Route_Time | Actual total time to complete the route, accounting for all wait times, delays, and other factors. | |
| Actual Route Start Time | Actual_Route_Start_Time | Actual time when the route started. | |
| Actual Route Start Date | Actual_Route_Start_Date | Actual date when the route started. | |
| Custom | |||
| Custom Data | your_custom_data | Custom Data added to the stop or address will appear as a new column with the respective header and data contained in the column. | |
| Density | |||
| SPORH (Stops Per On-Road Hour) | SPORH | Estimated number of stops visited per hour spent driving on the route. If the route is completed, this will reflect the actual average value instead of an estimated value. | |
| TPORH (Transactions Per On-Road Hour) | TPORH | Estimated amount of transactions per hour spent driving on the route. If the route is completed, this will reflect the actual average value instead of an estimated value. | |
| Driver | |||
| Vehicle ID | Vehicle_Id | Unique identification number of the vehicle associated with the route. | |
| Vehicle Alias (Vehicle Name) | 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 | |||
| Member ID | Member Id | Identification number of the team member assigned to the route. | |
| Member Email | Member Email | Email address of the team member assigned to the route. | |
| Member First Name | Member First Name | First name of the team member assigned to the route. | |
| Member Last Name | Member Last Name | Last name of the team member assigned to the route. | |
Export Route Data For GPS Navigation Devices
Additionally, for your convenience, the best route software enables you to export route data in a format that can be imported into navigation devices such as Garmin GPS devices and others. Below, you can see a description of the export options for different navigation devices. NOTE: When exporting multiple routes, export for navigation isn’t available.
| 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. |
| TSX | 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. |
| 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. |
Export Route Notes With Route4Me Route Management Tools
Route4Me’s best route planner enables you to add notes to routes which can serve as proof of delivery (POD) and proof of service. The Android and iOS route planner apps instantly sync data with the Web Platform. They enable you to increase the security of your operations and make POD files instantly available across devices connected to your account. Notes can contain delivery statuses, text, images, video, audio files, and other types of important data. You can export POD files and route notes, share the exported files with your team members, make reports, and conduct analyses or audits of your routing operations.
Routes List – Export Route Notes From Routes List
To export route notes from your Routes List, go to “Routes” and then “Routes” from the Navigation Menu. Then, click the Three-dot Icon next to the route that contains the notes and POD files you want to export. Next, hover over “Export” and select “Export Notes as CSV“. You can see all available export items and how to customize the export file further in this guide.
Additionally, the most reliable route management software enables you to can export notes from multiple routes simultaneously. To do so, select your preferred routes by checking the boxes next to them. Then, click “File” from the top menu bar, hover over “Export Routes“, and select “Export Notes as CSV“. You can see all available export items and how to customize the export file further in this guide.
Routes Map – Export Route Note Data From Routes Map
To export route notes from the Routes Map, go to “Routes” and then “Routes Map” from the Navigation Menu. The “Notes” column shows which routes contain attached notes and the number of the attached notes, respectively. If the header in your “Routes Map” doesn’t have the “Notes” column, right-click the header and select “Notes” from the list. Then, click the gear icon next to the route that contains the notes you want to export, hover over “Export” and select “Export Notes as CSV“. You can see all available export items and how to customize the export file further in this guide.
Additionally, you can export notes from multiple routes simultaneously. To do so, select your preferred routes by checking the boxes next to them. Then, click “File” from the top menu bar, hover over “Download as“, and select “Export Notes as CSV“. You can see all available export items and how to customize the export file further in this guide.
Route Editor – Export Route Notes From Route Editor
To export route notes from the Route Editor, go to “Routes” and then “Routes” from the Navigation Menu to open the Routes List. Then, click Open Icon next to the route that contains the notes you want to export to open it in the Route Editor.
Any destinations with Notes have a corresponding Note Icon with a number under their address showing the number of notes attached to the respective destination. To export Notes on the Route Editor, click “File” from the top menu bar, hover over “Export Route“, and select “Export Notes as CSV” from the list.
Detailed Notes Export – Customizable CSV Spreadsheets For Exporting Notes
After you select one of the above export methods, you can customize the Note export file to your preference. When exporting route Notes, the Export Route Data window allows you to customize the list of items that you want to include in the exported CSV file. Specifically, you can use the “Field Search” bar to find the items that you want to include in the exported file. In the “Notes” section, check the boxes next to the items you want to include in the export file. The added items are displayed in the right section of the window, where you can change their order, which will change the order of the columns in the exported CSV file, or remove them from your selected items.
You can refer to the glossary below for clarification of the terms in the exported files.
| Item | Description |
|---|---|
| Note Type | The type of the note attached to a stop (note status). |
| Note Content | The content of the note (custom text). |
| Note Attachment URL | URL of the file (image, video, etc.) that is attached to the note. |
| Note Time | The timestamp that was created upon adding the note to the stop. |
| Note Lat | The latitude coordinates of the location where the note was added to the stop. |
| Note Lng | The longitude coordinates of the location where the note was added to the stop. |
| Device Type | The type of the device that was used for adding the Note to the stop (iPhone, Android, Web, etc.). |
| Route Notes | The content of all notes attached to a stop (custom text). |
Visit Route4Me's Marketplace to Check out Associated Modules:
- Platform
Route Management
- Operations
Ultra High Resolution Route Mapping
