MapQuest plans, whether at the self-serve or Enterprise Edition level, generally operate on a quota system, in which customers purchase a set number of monthly or annual transactions. In most cases, a transaction is a request made to an underlying MapQuest service, such as a request to the Directions API or Geocoding API. To provide additional transparency on geocoding transactions and how they count towards your plan, we developed this post with further detail.

Embedded Transactions

Based on the request type, more than one transaction may be counted towards your quota for a specific request. This type of transaction is an embedded transaction. Embedded transactions must call out to another service in order to complete the initial request.

For example, a request to the Directions API can generate geocoding or reverse geocoding transactions depending on the nature of the request. When making a request to the Directions API with an origin and destination, 3 transactions will count towards your plan: 1 Direction transaction and 2 Geocode transactions.

Reverse Geocoding and Embedded Transactions

Another example of embedded transactions is found in one of our advanced routing options, our reverse geocoding. When routing to/from latitude and longitude coordinates, the Directions API will call the Geocoding API to reverse geocode the coordinates. Since an additional service outside of the Directions API is leveraged, more than one transaction will accumulate towards your plan.

This behavior is controlled by the doReverseGeocode parameter, which is set to ‘true’ by default. In order to prevent the Directions API from reverse geocoding the provided coordinates, the doReverseGeocode parameter can be set to ‘false’ instead by updating the code.

API Response Details and Setting Parameters for Reverse Geocoding 

When routing to/from latitude and longitude coordinates, the Directions API will call the Geocoding API to reverse geocode coordinates. Location information will populate the Locations block in the Directions API response. This is reflected in example 1A below:

Example 1A:

http://www.mapquestapi.com/directions/v2/route?key=yourkeyhere&doReverseGeocode=true&from=39.75939757682461,-105.0499391555786&to=39.76563251993667,-105.00723838806151

In order to prevent the Directions API from reverse geocoding the provided latitude and longitude coordinates, the doReverseGeocode parameter can be set to ‘false,’ which is shown in example 1B below:

Example 1B:

http://www.mapquestapi.com/directions/v2/route?key=yourkeyhere&doReverseGeocode=false&from=39.75939757682461,-105.0499391555786&to=39.76563251993667,-105.00723838806151

When the doReverseGeocode parameter is set to ‘false’, location information about each set of latitude and longitude coordinates will not be populated in the response.

Note: The destination maneuver text will be affected by updates to the doReverseGeocode parameters. If doReversGeocode parameter is set to ‘false’, printed directions will show, “You have arrived at your destination.” When set to ‘true’, destination text will include “1555 Blake Street is on your right.”

You can find plan information and the number of transactions used at any given time after logging into your account through our website.

Enterprise Edition customers are encouraged to contact their Account Manager or the Technical Support team for answers regarding transactions, the Directions API best practices, or correct usage of the doReverseGeocode parameter. Self service customers should reference our documentation on the Developer Network or contact developer-services@mapquest.com.

 

Previous Articles

As a user of the legacy MapQuest Free & Open license, we want to let you know about upcoming changes in licensing that may affect you and your application. To ensure that we can continue to offer the best service and product lineup possible, we are transitioning to a new licensing structure that will ultimately require our users to sign…

Read More

We’ve been working on a number of infrastructure upgrades over the past few months and recently released one of the most visible updates: the new MapQuest Developer Network! The new Developer Network — along with a quite a few other important upgrades — sets the foundation for a much-improved developer experience that will be rolled…

Read More

Let’s face it. In the mapping space, you have options. But not all options are created equal, especially when it comes to your business needs. Beyond reliability, accuracy and legacy, here are the three reasons that MapQuest Enterprise is truly the only option you need: No daily limit on service: Unlike the Community Edition license,…

Read More

Attention, users of the MapQuest-hosted Nominatim Search Service! During the next few weeks, we will be making upgrades to the back-end systems that power our instance of Nominatim and this involves a complete data refresh. During this time, OSM data updates will be temporarily suspended. It is possible that users may temporarily experience inconsistent results…

Read More

Did you know that MapQuest offers the ability to use our maps, geocoding, and routing with the open-source Leaflet mapping library? The interest and feedback provided during our public beta was truly overwhelming and today we are excited to announce the first production release of the MapQuest Plugins for Leaflet, utilizing both our Licensed and…

Read More

As many of you know, MapQuest hosts a version of the Nominatim Search Service as a part of our Open Data API and SDK product line, so we wanted to share an important update about this service that will have an impact on users of this service. The Nominatim Search Service will be unavailable on…

Read More

Within the next few weeks, MapQuest will unveil a completely revamped Developer experience. While we prepare for these exciting upgrades, we will be making critical infrastructure updates and will be pausing the creation of new Free & Open AppKeys on the Developer Network as of today, May 1, 2015. If you currently have a Free…

Read More

Attention, users of Community Edition on Licensed Data! We are in the process of simplifying our licensing structure and have a few upcoming changes that we want you to know about. Currently, MapQuest offers three types of licenses for use of our APIs, SDKs, and associated Developer Tools: Community Edition (Open Data), Community Edition (Licensed…

Read More

Today we are excited to announce quite a few JavaScript Maps API updates! The JavaScript Maps API v7.1.0 and Open JavaScript Maps API v7.1.0 have been officially released to production and include a great mix of new functionality as well as enhancements to existing functionality. We’ve also simplified and updated our list of currently supported…

Read More

Follow @MapQuestTech on Twitter

MapQuest DevBlog RSS

Want to stay updated on all the latest advances? Subscribe to our blog feed and be among the first to receive the news!