New 42-day free trial
Smarty

Cloud geocoding APIs vs. on-premise pros and cons

On-premise geocoding used to be the clear choice. With new technology, some cloud geocoders are surpassing local installs for speed, security, and price.
Davin Perkins
Davin Perkins
 • 
June 3, 2022
Tags

On-premise vs. the cloud is a constant debate when it comes to software purchases. Geocoding software is no different. How your geocoding solution is deployed can greatly impact both the performance and the cost.

In our ebook, 8 Questions to Ask When Selecting a Geocoding API, we talk about the pros and cons of on-premise and cloud-based geocoding options, as well as other key features to consider.

In this article, we’ll summarize why on-premise versus cloud-based matters, and touch on another deciding factor for your API purchase: third-party basemaps.

On-premise & cloud-based geocoding options

On-premise geocoding

On-premise geocoding is geocoding without calling cloud-based web services on the internet. Everything takes place on your servers, behind your firewall.

Pros of on-premise:

  • May have higher speed potential.
  • Good for companies or industries that have strict data compliance policies.
  • Beneficial if a transaction-based business model doesn’t work for your organization.

Cons of on-premise:

  • Your company is responsible for installation and network and server maintenance.
  • Usually requires an annual license fee, plus implementation costs.

Cloud-based geocoding

Cloud-based geocoding is geocoding through a web-based software service, commonly known as “software as a service” or SaaS.

Pros of cloud-based:

  • Easy to scale up or down based on business needs.
  • Cloud-based geocoders can achieve the same or better capacity and speed than on-premise solutions.
  • The performance, server and network responsibilities rest with the provider—you aren’t responsible for updates or security.

Cons of cloud-based:

  • You have less control over setup and security.
  • If your internet connection fails, you can’t get any work done.

Questions to ask about on-premise versus cloud geocoding

  • Do our internal privacy, security, data, or other policies require the extra complexity of an on-premise solution?
  • (If on-premise) - What are the time and technical requirements for initial setup?
  • (If on-premise) - What are the ongoing costs, time, and technical requirements for maintenance, security, updates, and licensing?

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

Your organization’s needs, privacy rules, and technical knowledge will all factor into your decision of on-premise versus cloud-based. Once you’ve chosen your deployment method, you can narrow down your list of potential providers and start to consider other features, like compatibility with third-party basemaps.

Is use with third-party basemaps permitted?

Geocoding allows you to transform your information databases into easy-to-understand visual maps. Displaying complex data on a map can be an effective and compelling way to present your company’s data, whether that information is where the highest concentration of your target customer resides, your factory locations, floodplains or high fire risk areas, or other subjects.

However, even if your provider allows you to store geocodes (not all do!), that doesn’t mean the terms of service also allow you to display them on third-party maps.

If you’re allowed to store geocodes, you should also ask if the provider allows you to display their geocodes on another mapping or GIS platform such as ArcGIS, QGIS, BatchGeo, or OpenStreetMaps.

The most well-known map provider, Google, does not allow use with third-party mapping platforms. If you’re going to display a geocode from Google on a map, you must display them on a Google Map—end of story!

However, other geocoding providers like Esri and Smarty do play nice with third-party mapping platforms. This opens up a world of possibilities for you.

For example, a Smarty client, the American Red Cross, uploaded addresses in bulk for verification and then used the latitude/longitude information to geocode and create accurate maps of home fire risk and predictive models based on the maps.

Questions to ask about use with third-party basemaps

  • Would my business data be easier to read or benefit from being displayed on a map?
  • Do the terms of service allow for geocodes to be used in conjunction with third-party maps?

To learn more about on-premise versus cloud, third-party basemaps, and other factors in choosing a geocoding provider, download the full ebook, “8 Questions to Ask When Selecting A Geocoding API” today!

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

Subscribe to our blog!
Learn more about RSS feeds here.
rss feed icon
Subscribe Now
Read our recent posts
Ecommerce shipping efficiency tools you need: Address autocomplete and verification
Arrow Icon
We know it’s not New Year's anymore, but we can still push for improvement and efficiency in our lives. Maybe you’ve lapsed on that goal to be healthier or slightly slipped on your new reading and writing regimen. No worries. Not only are we here to remind you to KEEP GOING on whatever goals you have, but we’re also here to give you an easy-to-implement solution that will create shipping efficiency and stop sending packages into the void. I mean, we’re assuming you don’t like wasting money. If you do… that’s how we’re different.
Patient form optimization: The $17.4 million problem
Arrow Icon
Let's start with a number that should make every hospital administrator do a double take: $17. 4 million. That’s how much the average hospital loses annually—just from denied claims due to patient misidentification. This isn’t from equipment costs, not from staffing shortages, and not even from insurance negotiations—just from keeping bad patient data. Surely, our forms aren’t that bad. (Yes, they are, and stop calling me Shirley. )But here’s the reality: According to the 2016 Ponemon Misidentification Report, 30% of hospital claims get denied, and over a third of those denials are caused by inaccurate or incomplete patient information.
The GPS adventures of a distracted developer
Arrow Icon
My name is Jeffrey Duncan, and at the pestering of Smarty’s editor, I’m writing a blog about the many adventures I’ve had in life and how address data has played a big part in them. I met my wife about eight years ago on a dating website. At the time, I lived in Provo, Utah, while she lived in Palmwoods, Australia, on the east coast of Queensland. On this dating app, I entered the area where I was interested in finding someone, about a 25-mile radius of Provo, Utah. I had no intention of leaving the valley, definitely not the state, and certainly not the country.

Ready to get started?