Google API
ProMaps.GoogleAPI History
Hide minor edits - Show changes to output
Changed line 13 from:
%newwin width=500% [[ https://cloud.google.com/maps-platform/user-guide/ | http://www.seedcode.com/rootimages/stikipad/promaps2/mapsplatform.png]]
to:
%newwin width=500% [[ https://cloud.google.com/maps-platform/user-guide/ | http://archive.seedcode.com/rootimages/stikipad/promaps2/mapsplatform.png]]
Changed line 40 from:
If you already have a maps API, add it to purchased version of ProMaps on the "General Settings" section of the Settings tab. API keys are supported in %newwin% [[Version History | version]] 1.05 and higher.
to:
If you already have a maps API, add it to purchased version of ProMaps on the "General Settings" section of the Settings tab. API keys are supported in %newwin% [[Version History | version]] 1.05 and higher. The quit and re-open ProMaps to put the new key into use.
Changed line 36 from:
'''Note''': These docs only apply to '''ProMaps 1.05+'''. If you're looking to add your Google API key to ProMaps 1.03, please [[GoMaps.GoogleAPI | see the docs here.]]
to:
'''Note''': These instructions only apply to '''ProMaps 1.05+'''. If you're looking to add your Google API key to ProMaps 1.03, please [[GoMaps.GoogleAPI | see the docs here.]]
June 18, 2019, at 07:09 PM
by - Added note that these docs are only for 1.05+
Added lines 35-36:
'''Note''': These docs only apply to '''ProMaps 1.05+'''. If you're looking to add your Google API key to ProMaps 1.03, please [[GoMaps.GoogleAPI | see the docs here.]]
September 27, 2018, at 09:00 PM
by - Specified the 3 APIs required for ProMaps to work
Added lines 25-30:
You'll need to enable the access to the following 3 APIs to enable all features of ProMaps:
*Maps JavaScript API
*GeoCoding API
*Directions API
September 25, 2018, at 07:50 PM
by - Added section on changing GoogleAPIKey to global storage
Changed lines 30-32 from:
If you already have a maps API, add it to puchased version of ProMaps on the "General Settings" section of the Settings tab. API keys are supported in %newwin% [[Version History | version]] 1.05 and higher.
to:
If you're running '''ProMaps build 1.053''' or earlier, before adding your API key to ProMaps, you'll need to make one small change to the MapSettings table; Select the "Use global storage" option under the Storage tab of the MapSettings::GoogleAPIKey field. This will allow the GeoCoding scripts to use the API key when querying Google's servers.
If you already have a maps API, add it to purchased version of ProMaps on the "General Settings" section of the Settings tab. API keys are supported in %newwin% [[Version History | version]] 1.05 and higher.
If you already have a maps API, add it to purchased version of ProMaps on the "General Settings" section of the Settings tab. API keys are supported in %newwin% [[Version History | version]] 1.05 and higher.
September 10, 2018, at 05:27 PM
by - Added Predicting Usage section
Added lines 20-21:
[[#GetKey]]
Added line 27:
[[#AddKey]]
Added lines 33-57:
[[#Usage]]
!! Predicting Usage
With Google's new pricing on their API, it's a bit difficult to accurately predict the amount of credit that will be used for each ProMaps solution, but let's take a look at the things in ProMaps that will use the API:
'''Loading the map''':
->Each time the regular map is loaded, including when filters are applied, the "Refresh Map" button is clicked, or the layout is refreshed, will be considered a "Map Load" from Google. These are priced at 0.007 USD per each for the first 100,000, so it would take 28,572 map loads to exceed the $200 monthly credit.
'''Loading the Route map''':
->Depending on whether you have more than 10 waypoints/properties selected or not, loading the route map will cost either 0.005 or 0.01 USD per each for the first 100,000 loads. This means 20,000-40,000 loads of the Route map could exceed the $200 monthly credit.
'''GeoCoding or Constraining''':
->Since we need to get the geolocation of each property in your database, we use the GeoCode API to retrieve that from the address. Each of these calls costs 0.005 USD. Additionally, any time you do a find in the constrain map, we use the Distance API, which also costs 0.005 USD per each.
Since all of these calls to the different APIs add up, you can see why it's difficult to predict the usage based on the number of users in the solution. It's really something that would become more apparent after a few months of use.
Another thing to consider with this is that you can set Quotas in your Google account that limit the API usage so that you'll never exceed the $200 credit. The result of this, though, is that further calls to the API beyond the quota will fail and the map will no longer load. Details on this can be found in the "Manage Your Cost of Use" section of Google's docs here: https://developers.google.com/maps/documentation/javascript/usage-and-billing
July 12, 2018, at 08:38 PM
by - Fixed a typo
Changed line 5 from:
Yes. While Google used to pemit "keyless" usage in a variety of situations, starting on June 11th 2018, "you値l need to enable billing with a credit card and have a valid API key for all projects."
to:
Yes. While Google used to permit "keyless" usage in a variety of situations, starting on June 11th 2018, "you値l need to enable billing with a credit card and have a valid API key for all projects."
Added lines 12-13:
%newwin width=500% [[ https://cloud.google.com/maps-platform/user-guide/ | http://www.seedcode.com/rootimages/stikipad/promaps2/mapsplatform.png]]
Changed line 3 from:
'''NEW June 11th, 2018'''
to:
'''NEW: June 11th 2018'''
Changed lines 3-5 from:
'''Yes'''. While Google used to pemit "keyless" usage in a variety of situations, starting on June 11th 2018, "you値l need to enable billing with a credit card and have a valid API key for all projects."
to:
'''NEW June 11th, 2018'''
Yes. While Google used to pemit "keyless" usage in a variety of situations, starting on June 11th 2018, "you値l need to enable billing with a credit card and have a valid API key for all projects."
Yes. While Google used to pemit "keyless" usage in a variety of situations, starting on June 11th 2018, "you値l need to enable billing with a credit card and have a valid API key for all projects."
Changed lines 3-4 from:
Yes. While Google used to pemit "keyless" usage in a variety of situations, starting on June 11th 2018, "you値l need to enable billing with a credit card and have a valid API key for all projects."
to:
'''Yes'''. While Google used to pemit "keyless" usage in a variety of situations, starting on June 11th 2018, "you値l need to enable billing with a credit card and have a valid API key for all projects."
Changed line 25 from:
If you have an older version of ProMaps, upgrade pricing is 40% off: please %newwin% [[/contact | contact us]] for an upgrade code.
to:
If you have an older version of ProMaps, upgrade pricing is 40% off: please %newwin% [[/contact | contact us]] for an upgrade code.
Changed lines 11-12 from:
Note that having an API key ws always a requirement if you wanted to route more than 8 properties at a time in ProMaps: with an API key you can create routes with 23 waypoints. More here: [[routing limits]].
to:
Note that having an API key was always a requirement if you wanted to route more than 8 properties at a time in ProMaps: with an API key you can create routes with 23 waypoints. More here: [[routing limits]].
Deleted line 15:
Changed line 17 from:
to:
Changed lines 23-25 from:
If you already have a maps API, you'll see a field to paste it into your puchased version of ProMaps on the "General Settings" section of the Settings tab.
to:
If you already have a maps API, add it to puchased version of ProMaps on the "General Settings" section of the Settings tab. API keys are supported in %newwin% [[Version History | version]] 1.05 and higher.
If you have an older version of ProMaps, upgrade pricing is 40% off: please %newwin% [[/contact | contact us]] for an upgrade code.
If you have an older version of ProMaps, upgrade pricing is 40% off: please %newwin% [[/contact | contact us]] for an upgrade code.
Changed lines 1-2 from:
!! Do I need a Google API key to use Maps?
to:
!! Do I need a Google API key to use ProMaps?
Changed lines 17-18 from:
!! Get a Key
to:
!! Get an API key
Changed line 24 from:
If you already have a maps API, add it to puchased version of ProMaps on the "General Settings" section of the Settings tab.
to:
If you already have a maps API, you'll see a field to paste it into your puchased version of ProMaps on the "General Settings" section of the Settings tab.
Changed lines 3-8 from:
Yes. While Google used to pemit "keyless" usage in a variety of situations
You probably don't need oneas Google allows up to 25,000 map loads a day. The [[geo coding]] of addresses is limited to 2,500/day but that is only a problem generally when first integrating after the initial geocode most of our users don't add that many records a day.
Having anAPI key will also let you route more than 8 properties at a time: with an API key you can create routes with 23 waypoints. More here: [[routing limits]].
You probably don't need one
Having an
to:
Yes. While Google used to pemit "keyless" usage in a variety of situations, starting on June 11th 2018, "you値l need to enable billing with a credit card and have a valid API key for all projects."
Some map services will still work without an API key but not well. Here are the details from %newwin% [[https://cloud.google.com/maps-platform/user-guide/ | Google's announcement]]:
->"Keyless calls to the Maps JavaScript API and Street View API will return low-resolution maps watermarked with 'for development purposes only.' Keyless calls to any of the following APIs will return an error: Maps Static API (including Static Street View), Directions API, Distance Matrix API, Geocoding API, Geolocation API, Places API, Roads API, and Time Zone API."
Fortunately, you'll likely never incur any actual charges on your Google Maps API key: along with requiring an API key, Google is also allowing $200 in free billing credits per month. This means most users will never incur any API charges. Here are the details of this $200 credit and how Google see it being applied: %newwn% [[https://cloud.google.com/maps-platform/user-guide/pricing-changes/ | API piricing questions]].
Note that having an API key ws always a requirement if you wanted to route more than 8 properties at a time in ProMaps: with an API key you can create routes with 23 waypoints. More here: [[routing limits]].
Some map services will still work without an API key but not well. Here are the details from %newwin% [[https://cloud.google.com/maps-platform/user-guide/ | Google's announcement]]:
->"Keyless calls to the Maps JavaScript API and Street View API will return low-resolution maps watermarked with 'for development purposes only.' Keyless calls to any of the following APIs will return an error: Maps Static API (including Static Street View), Directions API, Distance Matrix API, Geocoding API, Geolocation API, Places API, Roads API, and Time Zone API."
Fortunately, you'll likely never incur any actual charges on your Google Maps API key: along with requiring an API key, Google is also allowing $200 in free billing credits per month. This means most users will never incur any API charges. Here are the details of this $200 credit and how Google see it being applied: %newwn% [[https://cloud.google.com/maps-platform/user-guide/pricing-changes/ | API piricing questions]].
Note that having an API key ws always a requirement if you wanted to route more than 8 properties at a time in ProMaps: with an API key you can create routes with 23 waypoints. More here: [[routing limits]].
Changed lines 16-17 from:
to:
Changed lines 19-24 from:
Follow the instructions here to get a "Standard API Key": https://developers.google.com/maps/documentation/javascript/get-api-key
to:
Follow the instructions here to get a "Standard API Key": https://developers.google.com/maps/documentation/javascript/get-api-key
!! Adding a Key to ProMaps
If you already have a maps API, add it to puchased version of ProMaps on the "General Settings" section of the Settings tab.
!! Adding a Key to ProMaps
If you already have a maps API, add it to puchased version of ProMaps on the "General Settings" section of the Settings tab.
Changed line 3 from:
to:
Yes. While Google used to pemit "keyless" usage in a variety of situations
Changed lines 12-16 from:
If you have a maps API, add it to ProMaps on the "General Settings" section of the Settings tab.
to:
If you have a maps API, add it to ProMaps on the "General Settings" section of the Settings tab.
!! Get a Key
Follow the instructions here to get a "Standard API Key": https://developers.google.com/maps/documentation/javascript/get-api-key
!! Get a Key
Follow the instructions here to get a "Standard API Key": https://developers.google.com/maps/documentation/javascript/get-api-key
Changed line 7 from:
Having an API key will also let you route more than 8 properties at a time: with an API key you can create routes with 23 waypoints. More here: [[routing limitations]].
to:
Having an API key will also let you route more than 8 properties at a time: with an API key you can create routes with 23 waypoints. More here: [[routing limits]].
Added lines 6-7:
Having an API key will also let you route more than 8 properties at a time: with an API key you can create routes with 23 waypoints. More here: [[routing limitations]].
Changed lines 10-17 from:
Then the contents of "Settings::MapDataTemplate" would need to be updated to reflect the key also. That is just a url for the google maps api script included in the head of the document. So that url would need to be modified in the same way as in the geo code script.
Here are the instructions that google gives:
https://developers.google.com/maps/documentation/javascript/tutorial
So just make sure those two places include the api key in the url and that's it
to:
If you have a maps API, add it to ProMaps on the "General Settings" section of the Settings tab.
Added lines 1-17:
!! Do I need a Google API key to use Maps?
No, but you can add one if you want.
You probably don't need one need as Google allows up to 25,000 map loads a day. The [[geo coding]] of addresses is limited to 2,500/day but that is only a problem generally when first integrating after the initial geocode most of our users don't add that many records a day.
(Here are those usage limits for google maps api:
https://developers.google.com/maps/documentation/javascript/usage )
The Maps url requests can easily be modified to accept your own API key though. The geoCode lookups as part of the script "GeoCodeAddress" for example has a set variable script step that sets the google api URL to the $sc_baseURL var. That would need to be updated to have the api key appended to the url string.
Then the contents of "Settings::MapDataTemplate" would need to be updated to reflect the key also. That is just a url for the google maps api script included in the head of the document. So that url would need to be modified in the same way as in the geo code script.
Here are the instructions that google gives:
https://developers.google.com/maps/documentation/javascript/tutorial
So just make sure those two places include the api key in the url and that's it.
No, but you can add one if you want.
You probably don't need one need as Google allows up to 25,000 map loads a day. The [[geo coding]] of addresses is limited to 2,500/day but that is only a problem generally when first integrating after the initial geocode most of our users don't add that many records a day.
(Here are those usage limits for google maps api:
https://developers.google.com/maps/documentation/javascript/usage )
The Maps url requests can easily be modified to accept your own API key though. The geoCode lookups as part of the script "GeoCodeAddress" for example has a set variable script step that sets the google api URL to the $sc_baseURL var. That would need to be updated to have the api key appended to the url string.
Then the contents of "Settings::MapDataTemplate" would need to be updated to reflect the key also. That is just a url for the google maps api script included in the head of the document. So that url would need to be modified in the same way as in the geo code script.
Here are the instructions that google gives:
https://developers.google.com/maps/documentation/javascript/tutorial
So just make sure those two places include the api key in the url and that's it.
