-
Notifications
You must be signed in to change notification settings - Fork 0
/
Google API info
121 lines (78 loc) · 4.91 KB
/
Google API info
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
-- This files gives you all the necessary info required to use any of the available packages from Google APIs
# Run -- '?register_google' command on your R console to see all the details as provided below:
register_google {ggmap} R Documentation
Register a Google API
Description
This page contains documentation for tools related to enabling Google services in R. See the Details section of this file for background information.
Usage
showing_key()
ggmap_show_api_key()
ggmap_hide_api_key()
scrub_key(string, with = "xxx")
register_google(key, account_type, client, signature, second_limit,
day_limit, write = FALSE)
## S3 method for class 'google_credentials'
print(x, ...)
google_key()
has_google_key()
has_google_account()
google_account()
google_client()
has_google_client()
google_signature()
has_google_signature()
google_second_limit()
google_day_limit()
Arguments
string
a url string to be scrubbed. currently key, signature, and client keywords are scrubbed from the url and replace with the with argument
with
a string to replace
key
an api key
account_type
"standard" or "premium"
client
client code
signature
signature code
second_limit
query limit per second (default 50)
day_limit
query limit per day (default 2500 for standard accounts, 100000 for premium accounts)
write
if TRUE, stores the secrets provided in the .Renviron file
x
a google credentials class object
...
a dumped formal argument to the generic print method
Details
As of mid-2018, the Google Maps Platform requires a registered API key. While this alleviates previous burdens (e.g. query limits), it creates some challenges as well. The most immediate challenge for most R users is that ggmap functions that use Google's services no longer function out of the box, since the user has to setup an account with Google, enable the relevant APIs, and then tell R about the user's setup.
To obtain an API key and enable services, go to https://cloud.google.com/maps-platform/. This documentation shows you how to input the requisite information (e.g. your API key) into R, and it also shows you a few tools that can help you work with the credentialing.
To tell ggmap about your API key, use the register_google() function, e.g. register_google(key = "mQkzTpiaLYjPqXQBotesgif3EfGL2dbrNVOrogg") (that's a fake key). This will set your API key for the current session, but if you restart R, you'll need to do it again. You can set it permanently by setting write = TRUE, see the examples. If you set it permanently it will be stored in your .Renviron file, and that will be accessed by ggmap persistently across sessions.
Users should be aware that the API key, a string of jarbled characters/numbers/symbols, is a PRIVATE key - it uniquely identifies and authenticates you to Google's services. If anyone gets your API key, they can use it to masquerade as you to Google and potentially use services that you have enabled. Since Google requires a valid credit card to use its online cloud services, this also means that anyone who obtains your key can potentially make charges to your card in the form of Google services. So be sure to not share your API key. To mitigate against users inadvertantly sharing their keys, by default ggmap never displays a user's key in messages displayed to the console.
Users should also be aware that ggmap has no mechanism with which to safeguard the private key once registered with R. That is to say, once you register your API key, any function R will have access to it. As a consequence, ggmap will not know if another function, potentially from a compromised package, accesses the key and uploads it to a third party. For this reason, when using ggmap we recommend a heightened sense of security and self-awareness: only use trusted packages, do not save API keys in script files, routinely cycle keys (regenerate new keys and retire old ones), etc. Google offers features to help in securing your API key, including things like limiting queries using that key to a particular IP address, as well as guidance on security best practices. See https://cloud.google.com/docs/authentication/api-keys#securing_an_api_key for details.
Author(s)
David Kahle david.kahle@gmail.com
See Also
https://cloud.google.com/maps-platform/, https://developers.google.com/maps/documentation/maps-static/get-api-key,
https://developers.google.com/maps/documentation/maps-static/usage-and-billing
Examples
# this sets your google map for this session
# register_google(key = "[your key]")
# this sets your google map permanently
# register_google(key = "[your key]", write = TRUE)
has_google_key()
google_key()
has_google_client()
has_google_signature()
geocode("waco, texas", urlonly = TRUE)
ggmap_show_api_key()
geocode("waco, texas", urlonly = TRUE)
ggmap_hide_api_key()
geocode("waco, texas", urlonly = TRUE)
scrub_key("key=d_5iD")
scrub_key("key=d_5iD", "[your \\1]")
scrub_key("signature=d_5iD")
scrub_key("client=a_5sS&signature=d_5iD")
[Package ggmap version 3.0.0 Index]