Debugging Route Upload Errors — TollGuru GPS traces to Toll API & Route Polyline to Toll API
By: Maneesh Mahlawat
Tags: Web Development, Mapping, Technology, API, Travel

Debugging Route Upload Errors — TollGuru GPS traces to Toll API & Route Polyline to Toll API

TollGuru GPS traces to Toll API and Polyline to Toll API allows fleets, logistic companies, ride-shares, and car rentals to calculate tolls from GPS traces and mapping route polylines. Customers can

upload their GPS traces (as CSV files) and receive tolls for the GPS trace. upload route polyline and receive tolls for the route.

However, the response from TollGuru sometimes has “Location not found” or “Pair not found” errors for tolls for the ticket systems.

What should you do in this case?

First, it is important to understand how a ticket system works. As you know, you pay tolls on a ticket system based on where you got on (your entry plaza) and where you got off (your exit plaza). For example, New Jersey Turnpike, Pennsylvania Turnpike, New York State Thruway, Kansas Turnpike, Ohio Turnpike, Central Florida GreeneWay, Maine Turnpike, Indiana Toll Road, Florida’s Turnpike and Turner Turnpike and Will Rogers Turnpike in Oklahoma are ticket systems.

You can see a simple ticket system in the following figure. While traveling eastbound, you can get on the ticket system at either mainline toll plaza 1 or ramp toll plaza 3 and get off on mainline toll plaza 4 or ramp toll plaza 2. Mainline toll plazas 1 and 4 are the start and end of this simple ticket system.

“Location not found” or “Pair not found” errors occur when

the GPS coordinates are captured after the user is already on the ticket system (entry unknown error)

Say the GPS coordinates are first captured when the vehicle is west of plaza 4 and the GPS track ends east of plaza 4. In this case, the vehicle could have entered the system at either mainline plaza 1 or ramp plaza 3. Without knowing the exact combination (entry 1 and exit 4 or entry 3 and exit 4), we cannot calculate toll rates.

the GPS coordinates end in middle of the ticket system before exiting from the ticket system (exit unknown error)

Say the GPS coordinates are first captured when the vehicle is west of plaza 1 and the GPS track ends east of plaza 1. In this case, the vehicle entered the system at mainline plaza 1 but could have exited at either ramp plaza 2 or mainline plaza 4. Without knowing the exact combination (entry 1 and exit 2 or entry 1 and exit 4), we cannot calculate toll rates.

the GPS coordinates are captured after the user is on the ticket system and the capture stops before the user exits the ticket system (both entry and exit unknown error). Say the GPS coordinates are first captured when the vehicle is west of plaza 1 and 2 and the GPS track ends east of plaza 3 and plaza 4. Since both the entry and exit combinations are unknown, tolls cannot be calculated.

Solution

What can you do when you see a “Location not found” or “Pair not found” errors? Ideally the users would need to add extra GPS coordinates such that GPS coordinates cover both the entry and exit plazas on the ticket system. If you are unsure of the error, please email api@tollguru.com for the TollGuru testing team to find and fix the source of the error.

About TollGuru

TollGuru, a product of MapUp Inc., calculates tolls for all toll roads, bridges, and tunnels in the United States, Canada, Mexico and India for all vehicle types. TollGuru provides smart toll exchange and navigation platform.

TollGuru mapping service is designed for real America — where both costs and times figure in route decisions. TollGuru shows the cheaper routes not shown by any other mapping applications such as Google maps, Apple maps, Waze, HERE maps, MapQuest, Scout GPS, Garmin, etc. Unlike other mapping applications, our routes consider two vectors — travel time and travel cost (fuel and tolls) to provide a real-time decision platform.