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
here's a proposed geocoding mechanism that provides a set of predefined backends (currently Nominatim and Google), as well as the ability to use a custom geocoding function. It definitely may need some polishing (no unit tests or a detailed documentation so far) - think of it as of a proof of concept rather than an ultimate solution :-)
here's a proposed geocoding mechanism that provides a set of predefined backends (currently Nominatim and Google), as well as the ability to use a custom geocoding function. It definitely may need some polishing (no unit tests or a detailed documentation so far) - think of it as of a proof of concept rather than an ultimate solution :-)
Best,
-p-
nominatim should not be in here since it's not on CRAN.
Because it seems that there are no geocoding APIs that will work anonymously, then I think we should just pick the smallest package that works and go with that. If users want the geocoding, then they will have to register for a key in any way they can.
@zkamvar Well, it's in Suggested, so it's not a strict requirement, but I get your point.
If we assume that it's up to the user to geocode their locations (and get an API key if need be), we may as well stay with ggmap. The only downside of this approach is that it might be impossible (or at least difficult) to unit-test that function - unless we manually create a mockup response from Google's API and provide a testing switch in add_coordinates().
@zkamvar Well, it's in Suggested, so it's not a strict requirement, but I get your point.
If we assume that it's up to the user to geocode their locations (and get an API key if need be), we may as well stay with ggmap.
agreed.
The only downside of this approach is that it might be impossible (or at least difficult) to unit-test that function - unless we manually create a mockup response from Google's API and provide a testing switch in add_coordinates().
I believe this is the premise of the vcf or webmockr packages.
@zkamvar Thanks, I didn't know that vcr had been ported to R!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Folks,
here's a proposed geocoding mechanism that provides a set of predefined backends (currently Nominatim and Google), as well as the ability to use a custom geocoding function. It definitely may need some polishing (no unit tests or a detailed documentation so far) - think of it as of a proof of concept rather than an ultimate solution :-)
Best,
-p-