v8 Control Hero Item

Truck Routing API

Designed for professional transportation routing logistics


Truck Routing API

 

When routing commercial vehicles, there are special requirements that need to be considered, outside of plotting a path from one location to another. Considerations such as vehicles that exceed the standard size, speed limits, legal requirements for the transportation of goods (such as transporting hazardous materials), road restrictions, and more. Designed for professional transportation routing logistics, the Bing Maps Truck Routing API calculates routes that take into consideration the attributes for trucks and commercial vehicles that may not be able to leverage the same routing services as standard vehicles.


Bing Maps Truck Routing Attributes and Considerations

Truck Attributes
Truck Attributes

Height, length, width, turning radius

Road Restrictions
Road Restrictions

Maximum bridge/underpass weight or height

Legal Restrictions
Legal Restrictions

Hazardous materials, waterways, and more

Traffic Conditions
Traffic Conditions

Speed limit, construction, lane closures

Other Conditions
Other Conditions

Strong crosswinds, toll roads, road gradient

 

Truck Routing Demo

Click the sample scenarios to see a route calculated for a truck based on predefined truck attributes. See why the truck route is different from a route calculated for a car by clicking on "Explore in Streetside Imagery"


Explore in Streetside Imagery
Truck Attributes

Optimized Routing for Professional Transportation

With the Bing Maps Truck Routing API, you can determine a safe and efficient route for your commercial vehicles, saving time and money, as well as avoiding unsafe conditions and legal restrictions. In addition, use the Streetside imagery capabilities of the Bing Maps platform to view why your vehicle needs to take a different route, such as a low bridge, sharp corner, waterway, and more.

Currently, the Bing Maps Truck Routing API coverage is available in 80 countries and growing.

LEARN MORE

Legend

Car

Truck

Start

End


Bing Maps Fleet and Logistics API Services

From personalized experiences to advanced scenarios in the logistics sector, Bing Maps has you covered. Check out the geospatial API services and solutions for enhanced fleet management, routing, vehicle tracking and more.
  • Distance Matrix API – Calculate travel times and distance in many-to-many scenarios, with an optional histogram to predict traffic.
  • Isochrone API – Provides time-specific isochrones, given the area that can be reach in the time and space criteria.
  • Snap to Road API – Snap the path to the most logical path, using the vehicles GPS trace, as well as returns road attributes, such as speed limit and elevation.

Get Started

Truck Routing API uses billable transactions. If you have a Bing Maps key, review the Truck Routing API documentation to learn more and start developing your solution. If you don’t have a Bing Maps key, create a Bing Maps account and create a key to authenticate your application. Then follow the documentation to start developing your solution.

For Licensing questions, contact a Bing Maps Sales Specialist.


CONTACT US

FAQ

A: To try this service, create a basic account, which will provide up to 125K transactions per calendar year at no charge. Above this usage limit, you will need to purchase a license. To purchase a Transactions license, contact a Sales Specialist. To start developing with this API, use the Truck Routing API documentation.

  • Truck Routing API is available for Internal Website Transactions licensing. It is not available for Known or Light Known users.
  • For Mobile Asset Management, the Truck Routing API is available by purchasing an add-on license (Note- you must have the underlying Asset Management per asset license first).

A: Enterprise Customers will be able to license via the following options:

  1. Internal Website Transactions (when using in an application that is not related to asset tracking) - If you are not licensed for Internal Transactions, you can purchase these from your sales partner.
    • You will need to create a separate account ID on the Bing Maps Dev Center that will be specific to your internal transaction usage.
    • The Truck Routing API is available for Internal transaction website licensing. It is not available for Public transaction website licensing, or for Known or Light Known users.
      Note - This API will increase the consumption of billable transactions, which may result in the need to purchase additional transactions.
  2. Per Asset (applicable when being used as part of asset tracking solution) - To use the Truck Routing API, you will need an underlying Asset Management per asset license (with or without routing) and will the need to purchase an additional per asset license for the use of this new service. For licensing and pricing questions, please contact a Sales Specialist.

A: You will need to purchase billable transactions based upon your consumption. For a transaction model, consumption of the API is 1 call = 3 billable transactions. For per asset model pricing, contact a Sales Specialist.

A: The Truck Routing API supports up to 25 waypoints, with a minimum of 2 waypoints per call. See the Truck Routing API documentation for more information.

A: To try the Truck Routing API, you will need to create a Basic key. When you are ready to deploy into production, you will need to upgrade to an Enterprise key.

A: The Truck Routing API is available for Basic and Enterprise accounts (normal TOU limits will apply for Basic accounts), and is available for Internal Website transactions only. It is not available for Known or Light Known users, or for Asset Management per asset licensing.

If you would like to try the API, you can create a Basic key. To deploy into production, you will need to upgrade to an Enterprise key.

A: Currently, we support coverage in 80 countries, with plans to expand as more information becomes available in other countries regarding its road segment restrictions. Truck Routing support coverage: Albania, Andorra, Argentina, Australia, Austria, Bahrain, Belgium, Bosnia and Herzegovina, Botswana, Brazil, Brunei, Bulgaria, Canada, Chile, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Germany, Gibraltar, Greece, Hungary, Iceland, India, Indonesia, Ireland, Isle of Man, Israel, Italy, Jordan, Kazakhstan, Kosovo, Kuwait, Latvia, Lesotho, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malaysia, Malta, Mexico, Moldova, Monaco, Montenegro, Morocco, Namibia, Netherlands, New Zealand, Norway, Oman, Philippines, Poland, Portugal, Qatar, Réunion, Romania, Russia, San Marino, Saudi Arabia, Serbia, Singapore, Slovakia, Slovenia, South Africa, Spain, Swaziland, Sweden, Switzerland, Taiwan, Thailand, Turkey, Ukraine, United Arab Emirates, United Kingdom, United States, Vatican City, Vietnam.

A: The Truck Routing API does not support waypoint reordering. You can use the Bing Maps Distance Matrix API, in a many-to-many waypoint scenario, for enhanced route optimization along with the Truck Routing API. First, use the Distance Matrix API to get an estimate of times for each route and then determine the best time for each route. Once you have the order of each route, use the Truck Routing API to get turn-by-turn directions for each route (point A to point B).

A: To develop and deploy this service, refer to the Truck Routing API documentation. If you have licensing questions, please contact a Sales Specialist. For Enterprise Customer Support, click here. Or check out the Bing Maps Developer Network forum.

A: You can use the Truck Routing API for navigation; however, to advance to the next instruction, the user would need to initiate the switch to the next step (i.e. push a button), rather than the application automatically advancing to the next instruction based on the GPS position of the device. Similarly, if the user were to go off course, they would need to initiate the action to calculate a new route rather than this being initiated automatically based on a sensor event.
This is a restriction as per the Terms of Use, section 3.2 (e): Present or alert an end user to individual maneuvers of a route in any way that is synchronized with the end-user’s sensor-based position along the route (e.g. turn by turn navigation that tracks end-user’s position using GPS and communicates a maneuver as the end-user approaches the location for such maneuver).

Bing Maps Resources

  • Click herefor Bing Maps case studies.