You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.Rmd
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ output:
17
17
18
18
<!-- badges: end -->
19
19
20
-
Geocode with the [OpenCage](https://opencagedata.com/) API, either from place name to longitude and latitude (forward geocoding) or from longitude and latitude to the name and address of the location (reverse geocoding).
20
+
Geocode with the [OpenCage](https://opencagedata.com) API, either from place name to longitude and latitude (forward geocoding) or from longitude and latitude to the name and address of the location (reverse geocoding).
21
21
22
22
## Installation
23
23
@@ -27,7 +27,7 @@ Install the package with:
27
27
install.packages("opencage")
28
28
```
29
29
30
-
Or install the development version using [remotes](https://remotes.r-lib.org/) with:
30
+
Or install the development version using [remotes](https://remotes.r-lib.org) with:
31
31
32
32
```{r, eval = FALSE}
33
33
remotes::install_github("ropensci/opencage")
@@ -64,14 +64,14 @@ But remember, the vignettes are really great! We have:
64
64
65
65
## About OpenCage
66
66
67
-
The [OpenCage](https://opencagedata.com/) API supports forward and reverse geocoding.
67
+
The [OpenCage](https://opencagedata.com) API supports forward and reverse geocoding.
68
68
Sources of OpenCage are open geospatial data including
Copy file name to clipboardExpand all lines: cran-comments.md
+6-15Lines changed: 6 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,10 @@
1
1
## Release summary
2
2
3
-
### v0.2.1
4
-
* Fixed two URLs, one of which was rejected on the v0.2.0 submission.
5
-
6
-
### v0.2.0 (unreleased)
7
-
* Rewrite of the package, see NEWS.md for details.
8
-
* Change of maintainer:
9
-
* New Maintainer: Daniel Possenriede <possenriede+r@gmail.com>
10
-
* Old maintainer: Maëlle Salmon <maelle.salmon@yahoo.se>
3
+
### v0.2.2
4
+
This patch version fixes a test that caused an error on CRAN's Solaris (<https://github.com/ropensci/opencage/pull/131>, <https://www.r-project.org/nosvn/R.check/r-patched-solaris-x86/opencage-00check.html>).
"Get started with the opencage R package to geocode with the OpenCage API, either from place name to longitude and latitude (forward geocoding) or from longitude and latitude to the name and address of a location (reverse geocoding)."
8
8
output:
@@ -46,7 +46,7 @@ There are three safer ways to set your API key instead:
46
46
From there it will be fetched by all functions that call the OpenCage API.
47
47
You do not even have to call `oc_config()` to set your key;
48
48
you can start geocoding right away.
49
-
If you have the {[usethis](https://usethis.r-lib.org/)} package installed, you can edit your `.Renviron` with `usethis::edit_r_environ()`.
49
+
If you have the {[usethis](https://usethis.r-lib.org)} package installed, you can edit your `.Renviron` with `usethis::edit_r_environ()`.
50
50
We strongly recommend storing your API key in the user-level `.Renviron`, as opposed to the project-level.
51
51
This makes it less likely you will share sensitive information by mistake.
52
52
@@ -66,7 +66,7 @@ If you have a "Free Trial" account with OpenCage, you can skip to the next secti
66
66
67
67
If you have a paid account, you can set the rate limit for the active R session with `oc_config(rate_sec = n)` where `n` is the appropriate rate limit.
68
68
You can set the rate limit persistently across sessions by setting an `oc_rate_sec` option in your `.Rprofile`.
69
-
If you have the {[usethis](https://usethis.r-lib.org/)} package installed, you can edit your `.Rprofile` with `usethis::edit_r_profile()`.
69
+
If you have the {[usethis](https://usethis.r-lib.org)} package installed, you can edit your `.Rprofile` with `usethis::edit_r_profile()`.
As you probably know, cache invalidation is one of the harder things to do in computer science.
@@ -249,4 +249,4 @@ Besides `oc_forward_df()` and `oc_reverse_df()`, which always return a single ti
249
249
Depending on what you specify as the `return` parameter, `oc_forward()` and `oc_reverse()` will return either a list of tibbles (`df_list`, the default), JSON lists (`json_list`), GeoJSON lists (`geojson_list`), or the URL with which the API would be called (`url_only`).
250
250
Learn more in the ["Output options"](output_options.html) vignette.
251
251
252
-
Please report any issues or bugs on [our GitHub repository](https://github.com/ropensci/opencage/issues) and post questions on [discuss.ropensci.org](https://discuss.ropensci.org/).
252
+
Please report any issues or bugs on [our GitHub repository](https://github.com/ropensci/opencage/issues) and post questions on [discuss.ropensci.org](https://discuss.ropensci.org).
Copy file name to clipboardExpand all lines: vignettes/opencage.Rmd.src
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ There are three safer ways to set your API key instead:
54
54
From there it will be fetched by all functions that call the OpenCage API.
55
55
You do not even have to call `oc_config()` to set your key;
56
56
you can start geocoding right away.
57
-
If you have the {[usethis](https://usethis.r-lib.org/)} package installed, you can edit your `.Renviron` with `usethis::edit_r_environ()`.
57
+
If you have the {[usethis](https://usethis.r-lib.org)} package installed, you can edit your `.Renviron` with `usethis::edit_r_environ()`.
58
58
We strongly recommend storing your API key in the user-level `.Renviron`, as opposed to the project-level.
59
59
This makes it less likely you will share sensitive information by mistake.
60
60
@@ -74,7 +74,7 @@ If you have a "Free Trial" account with OpenCage, you can skip to the next secti
74
74
75
75
If you have a paid account, you can set the rate limit for the active R session with `oc_config(rate_sec = n)` where `n` is the appropriate rate limit.
76
76
You can set the rate limit persistently across sessions by setting an `oc_rate_sec` option in your `.Rprofile`.
77
-
If you have the {[usethis](https://usethis.r-lib.org/)} package installed, you can edit your `.Rprofile` with `usethis::edit_r_profile()`.
77
+
If you have the {[usethis](https://usethis.r-lib.org)} package installed, you can edit your `.Rprofile` with `usethis::edit_r_profile()`.
78
78
79
79
### Privacy
80
80
@@ -210,4 +210,4 @@ Besides `oc_forward_df()` and `oc_reverse_df()`, which always return a single ti
210
210
Depending on what you specify as the `return` parameter, `oc_forward()` and `oc_reverse()` will return either a list of tibbles (`df_list`, the default), JSON lists (`json_list`), GeoJSON lists (`geojson_list`), or the URL with which the API would be called (`url_only`).
211
211
Learn more in the ["Output options"](output_options.html) vignette.
212
212
213
-
Please report any issues or bugs on [our GitHub repository](https://github.com/ropensci/opencage/issues) and post questions on [discuss.ropensci.org](https://discuss.ropensci.org/).
213
+
Please report any issues or bugs on [our GitHub repository](https://github.com/ropensci/opencage/issues) and post questions on [discuss.ropensci.org](https://discuss.ropensci.org).
0 commit comments