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
The API is asynchronous so the process is Send POST > wait until status is completed (can be checked via GET) > Retrieve via GET. This makes the batch geocoding code a bit longer.
When sending POST, the results returns a RequestID. This is used for the subsequent GET processes. The good point is that you can retrieve previous runs using that RequestID and skipping the POST. This has been implemented.
Batch geocoding results are in a different format than Single results, and the fields on batch results needs to be selected via the POST request. I have selected what I consider the most relevant, but those can be modified by the user via a custom query.
There are other bits of the code that are discretional, as seconds between GET status calls, some warnings, etc. Some feedback would be appreciated.
HERE Batch Geocoding is really slow. It can be useful for very large requests (limit of 1,000,000 plus the possibility of retrieving previous jobs as mentioned before), but I decided to force the batch mode only if the user requests it. Note that this is not the default behaviour for the rest of batch geocoder (batch by default if n>1 and mode is not single) but from an user perspective it can be frustating to wait 1 minute for geocoding two addresses.
Glad to know your feedback, specially on the batch geocoding implementation.
Regards
The text was updated successfully, but these errors were encountered:
Following #62 , I have implemented HERE:
See the checklist below:
Data
data-raw/api_reference.R
updatedR/data.R
Sandbox
sandbox/query_debugging/here_test.R
sandbox/reverse_queries/here_reverse.R
Code
R/utils.R
- Utils added for HERER/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
About HERE batch geocoding service
Some notes on batch geocoding on HERE:
mode
is notsingle
) but from an user perspective it can be frustating to wait 1 minute for geocoding two addresses.Glad to know your feedback, specially on the batch geocoding implementation.
Regards
The text was updated successfully, but these errors were encountered: