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
Thanks for reporting this. The issue was that in the reverse_geo() function the set of (duplicated) coordinates was being put into the query instead of the single unique coordinate.
You can install the bug fix from the main GitHub branch for now:
reverse_geo
throws an error if I supply the same pair of coordinates multiple times and the input has only one unique pair of coordinates.If I supply the same pair of coordinates multiple times, but this is not the only unique pair, reverse geocoding works fine. Here's a minimal example:
Created on 2021-08-21 by the reprex package (v2.0.1)
(
geo
, however, works fine if the same location string is supplied multiple times.)The text was updated successfully, but these errors were encountered: