Chances are you’ve heard a few things about our geocode quality codes. You’ve probably heard that they are some of the most granular in the mapping business, but you might be wondering what that means.

How can a quality code, granular or not,  help your business?

First, what is a quality code?

A quality code, simply speaking, is an indicator for the degree of accuracy in a geocode result. Many mapping applications will tell you, on a grade-letter scale, how confident they are in a geocode result. We take it a step further and analyze every piece of the query, from the street name to the zip code, so that you can ensure your drivers or deliveries know exactly where they are going.

Let’s look at an address for an example: 1060 W. Addison St., Chicago, IL 60613. This returns a quality code of L1AAA from our geocoder, which is one of the best possible geocode results, but let’s break down why.

 Screen Shot 2016-04-05 at 10.58.56 AM.png

L1: This means that the geocoder is certain where this street address, or “Location” is located. The letters each correspond to a segment of the address. An ‘A’ is an exact match, a ‘B’ is a good match, a ‘C’ is an approximate match, and an ‘X’ indicates this information was not provided. Looking at this address, you can infer that the geocoder knows exactly where this location is, and that the street address, city and zipcode provided are exact matches. If this was a delivery address, you could dispatch your driver knowing exactly where they are going!

Assuming that, on occasion, people make mistakes when they enter an address, let’s see what happens if we tweak this address just slightly and request 1060 W. Addison Ave., Chicago, IL 60613. The geocoder now returns an L1BAA. This tells you that the geocoder is still quite certain where this location is, but that the street address wasn’t an exact match. However, a ‘B’ is still a good result, and capable of receiving a delivery.

When making a determination as to whether or not you would dispatch a driver to a location, both of these addresses are good examples. But, you may be wondering, could quality codes tell your business when you might not want to drive to an address? Absolutely! Let’s look at 2345 Martin, Dallas, TX. The geocoder returns an L1CAX. Let’s break that down:

When searching for this address, the Geocoder did find a result for 2345 Martin Luther King Jr. Blvd, so it returned an L1 because it knows where this location is, however, for the street address it returns a ‘C’ because it’s taking a best guess that the user meant Martin Luther King Jr. Blvd. The city and state gets an ‘A’ code, but the user did not provide a zip code, so the geocoder returns an ‘X.’

As a business, you might decide there is too much margin of error with this quality code, and you don’t want to waste valuable time having your driver hunt for this questionable address. Which saves both time and money, and gets you to your next delivery faster.

We have more than a dozen quality code indicators, and you can read even more about them in our developer documentation.

 

Previous Articles

MapQuest is committed to delivering cutting-edge solutions to our customers by leveraging the most updated technology. As a result, we’re transitioning our foundational structure to the cloud and with this transition comes updates to our current offerings. On Monday, July 11, 2016, our direct tile access to MapQuest legacy maps will be discontinued. After Monday,…

Read More

Additional MapQuest account information will soon be available at your fingertips! New features are being added over the next month to the Enterprise account management portal, helping you better manage your account and keep a pulse on your transaction usage. Previously, the number of transactions during a given time and the type of APIs and…

Read More

Nothing spoils a good user experience in a location-based application faster than an inaccurate address input. Sometimes it’s a missing a digit, other times it’s a case of searching for a street with an unusual spelling (Iliff Avenue, anyone?). One of the biggest challenges your application faces is ensuring the search query is as accurate…

Read More

Weight constraints? Height constraints? No problem. We recently added new routing options, to the avoids string collection, letting you easily avoid bridges or tunnels on your next trip. We’ve added these bridges and tunnels to our avoid string collection. The complete list now includes: Limited Access (highways) Toll Road Ferry Unpaved Approximate Seasonal Closure (Seasonal…

Read More

Sound the alarms— Location Services 5.0 is here! We’ve made big improvements to search architecture, handling and geocoding in the U.S. and Canada in order to provide more accurate geocoding results for your applications. So, what does this mean for you? Simply stated, we’re helping you create a better experience for your users. We’re hyper-focused…

Read More

MapQuest maps are getting a shiny new look. The good news? You don’t have to do anything! The even better news? Our newly styled maps will elevate the overall experience and interactions your users have with the maps on your site or within your app. Over the next month, we’re transitioning to a new, modern…

Read More

We have a lot of exciting things going on here at MapQuest. Our new mobile map SDK will allow you to deliver a fully native mapping experience across all platforms and the ability to control the look of your maps along with vector-based traffic. In addition, we’re modernizing across the board with an updated map…

Read More

Do you ever wonder what our developers are up to when they’re not working on new mapping or routing solutions? Check out what steps our development takes when improving our current API set in this recent post from Kumiko Yamazaki on DZone.    

Read More

Here at MapQuest, we’re focused on improving our products and solutions to meet our customer needs. We make a point to listen to our customers and incorporate their feedback when evaluating our offerings and prioritizing new features. Today, we’re happy to announce one of our top offerings is now available to our Business  and Business…

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!