Evaluating Geocoding API Capacity and Speed

How fast is your geocoder? Some APIs hit 27 geocodes per second, others achieve 100,000+. Evaluate before committing to save time, cut costs, and improve data.
Subscribe Now
May 25, 2022
by Davin Perkins
Man Evaluating Geocoding API for Capacity and Speed

The right geocoding API can help your business reduce costs and increase profits through accurate location data. But how do you know if a service can handle your data needs? Capacity and speed are two key topics to consider when comparing geocoding services.

You can find out more about all the questions you need to ask in our eBook, 8 Questions to Ask When Selecting a Geocoding API by clicking the link here:

Download '8 Questions to Ask When Selecting A Geocoding API' Now.

API Capacity and Speed: What You Need To Know

The higher the capacity and faster your geocoding API works, the faster you can utilize that address data and make money. Your accounting department is already smiling just thinking about it.

Let’s get into how we measure geocoding speed and what’s considered fast versus slow.

Geocoding API speed is measured in “query per second” rates, or QPS. That means we’re tallying how many addresses can be geocoded per second. There’s a wide spectrum or published geocoding API provider speeds—from 27 QPS all the way up to 100,000+ QPS.

Most businesses find that producing dozens, hundreds, or even thousands of geocodes per second simply isn’t fast enough.

Speed and capacity are closely linked. If a service provider doesn’t have enough server capacity, they can’t handle a mass quantity of geocodes at one time. When too many geocodes overload the system, there’s typically one of two reactions:

  1. The geocoding system bogs down and slows to a turtle-like speed.
  2. The geocoder behaves as a cranky hall monitor and forces all users into a line.

Both scenarios have the same outcome—SLOW speeds.

So what’s the solution to your need for speed?

Look for a cloud-based geocode provider that can spin up new servers almost instantly to accommodate near infinite usage. This provides very high speeds and nearly unlimited capacity for users.

Think you don’t need Sonic the Hedgehog level speeds for your address data? Consider this use case:

In the property and casualty insurance industry, profitability hinges on the accuracy of risk assessments—location being a key factor in those assessments. Because location attributes change frequently, many insurance companies update geocodes for their whole database of hundreds of millions of addresses every month. That’s simply not practical without a fast geocoding solution.

Operationally efficient, high-performing businesses shouldn’t be forced to wait. Choose a geocoding provider with high capacity and high speeds to get the most benefit from your address data.

Questions to Ask About Geocoding API Capacity & Speed

  • Will the speed and capacity fit my business needs?
  • What hardware / software limitations might affect the provider’s speed?
  • What does the provider’s SLA (Service Level Agreement) state about downtime, latency, outages, response time, QPS, and server capacity that impact speed and capacity?

Of course, while important, speed and capacity aren’t the only factors to consider when choosing your geocoding service.

You also want to consider things like on-premise versus cloud, and whether a provider is compatible with third-party basemaps. To find out the answers to these questions, click the link to download the full eBook:

Download '8 Questions to Ask When Selecting A Geocoding API' Now.

The leader in location data intelligence

Ready to get started?