08/03/2018: Google Maps API Changes

A new pay-as-you-go pricing model is now in effect for those using the Google Maps API Platform. This can affect anyone who has configured the Data Hub ETL task Geocode to use the service provider Google. This can also affect anyone who has configured the GeoPlot Map Chart to use a tile server offering by Google. As terms and policies for web service providers continue to be an ever-changing atmosphere, please reach out to our Support Team to discuss additional implications, solutions, or changes.

1. Geocoding web service
2. GeoPlot Map Chart tile server

 1. Geocoding web service

The Data Hub has the ability to geocode address data. This takes place in the ETL editor using the 'Geocode' task. Geocoding can only be achieved by submitting address data to an online geocoding web service provider. The configuration for this task allows the user to choose from three web service providers: OpenStreetMap (default), Bing and Google. Using the default selection of "OpenStreetMap" will not require an API key while Bing and Google will require an API Key. An API Key is used by the service provider so that quotas and limits can be placed on the number of calculations they are willing to perform. 

Pricing and Billing Changes:

• • Google Developers: Important Updates
  • Google Developers: Usage and Billing
  • Google Developers: Authentication
  • Requests per Day (QPD) limits have ended, effective June 11, 2018
  • New Pay-As-You-Go Pricing went into effect on July 16, 2018.
  • Other Usage Limits and additional Terms of Use

Existing Configurations using Google as the service provider:

• • • Google Developers: Maps User Guide

If your geocoding task is configured with OpenStreetMap or Bing, no changes are needed at this time. However, configurations using Google will experience a change in behavior resulting in the termination of making geocode requests - the ETL job will error and the geocode values will be returned as null. 

Options if currently using Google as the service provider:

1. 1. 1. Reconfigure the Geocode task to use OpenStreetMap or Bing.
      2. Establish a payment plan with Google and obtain a new API Key for the geocode task.
      3. Remove the Geocode task from the ETL job and explore other methods for retrieving latitude and longitude data.

2. GeoPlot Map Chart Tile Server

The GeoPlot Map Chart is preconfigured to use map tiles (the images that come from a web service which form the graphics of the map) using an OpenStreetMaps server we host. Users can reconfigure the map tile server to a different map service provider, including Google. Using Google as a map tile server has restrictions, quotas, and limits – those are provided in the User Manual documentation. At the current time, there are no additional restrictions to continue using a Google map tile server.

Disclaimer: Technical Support Engineers are not proficient in the Management and Integration of every API that exists as new APIs are being created everyday with each company that wants to provide seamless integration with other software. However, we do our best to help you make these connections because we want to assist you in your success. If you do not see an article for a connection you would like to make please contact Dashboard Support and know that it will take a bit of time to figure out what is necessary for this integration.