-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add TomTom support #76
Comments
@dieghernan I pulled this into master. 👍 Note that I changed the query_api function to return a named list so that we can see the HTTP response status code. I also adjusted the logic in geo(), reverse_geo(), and related tests to use the HTTP status code when checking if a query was successful. |
Agree, the json parsing inside |
@jessecambon I think the error handling of TomTom is not incorporated after the last PR: |
@dieghernan I changed the extract_errors_from_results() function in utils.R so that it will just display the raw content if it is not valid JSON: Line 155 in 739853f
That worked for me with TomTom when I passed an invalid api key, but let me know if you spot any issues. That function will only be called if the HTTP response status != 200. |
Thanks!! I’ll check and would let you know |
Following #62 , I have implemented TomTom:
See the checklist below:
Data
data-raw/api_reference.R
updatedR/data.R
Sandbox
sandbox/query_debugging/tomtom_test.R
sandbox/reverse_queries/tomtom_reverse.R
Code
R/utils.R
- Utils added for TomTomR/query_factory.R
updatedR/geo_methods.R
updatedR/geo.R
updatedR/reverse_geo.R
updatedBatch
R/batch_geocoding.R
updatedR/reverse_batch_geocoding.R
updatedTesting
testthat
test addedregression_testing.Rmd
Misc
R/reverse_geo.R
to avoid errors onno_query = TRUE
I am polishing the PR with a final huge batch geocoding test, but overall my experience on this is that TomTom runs smoothly and fast, I think it could be a great addition to the package
The text was updated successfully, but these errors were encountered: