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
Inside Smarty® - Irina O'hara
Arrow Icon
Irina O'Hara is one of our uniquely clever, expert frontend developers. She’s immensely talented and has had a vital impact on our website redesign. When it came time to spotlight her, Irina was a joy to sit down with and get to know a little better. To get to the basics, she writes code and creates awesome websites, and she’s darn good at both. BackgroundIrina was born and raised in St. Petersburg, Russia. However, she wasn't born a development expert and had other aspirations from the start.
How I reduced my returned mail from 27% to 1% using address autocomplete
Arrow Icon
The following is based on a true story. Some of the names and relationships have been changed to protect the anonymity of individuals and companies. However, the numbers are 100% accurate. In 2023, I wanted to mail some really fancy cards to 165 businesses. I collected their addresses by asking for them or finding them in their online listing and collected them all in a neat little row. Then, I went a step further and ran these addresses through Smarty's bulk address validation tool. Everything was set and perfect.
The ROI of accurate healthcare address validation: Stop hemorrhaging red on your financial statements
Arrow Icon
In healthcare, the havoc an inaccurate address can wreak on your financial results is significant in more ways than one, and the boost in overall profitability from maintaining a clean address database is equally worth noting. Accurate healthcare address validation improves operational efficiency, patient engagement, and compliance and builds revenue to heights that couldn’t be met without it. Here’s what we’ll be covering:Healthcare address validation pros and consCon: Increased claim denials and organizational costsPro: Reduced claim denials and reprocessing costsCon: Increasing patient match error ratesPro: Improved patient matching and data qualityCon: Complicated billing and collections processesPro: Streamlined billing and collections capabilitiesCon: Exposure to legal liabilitiesPro: Enhanced regulatory compliance and risk aversionCon: Misplaced market strategyPro: Data-driven decision-making and market insightsEpilogue: Avoiding the pain (see our summarized financial savings)Healthcare address validation pros and consThere’s a pro and a con associated with having (or not having 🫣) accurate address data in your healthcare systems.

Ready to get started?