Open JMPivette opened 3 years ago
I found the underlying issue here: https://github.com/etalab/adresse.data.gouv.fr/issues/622
So it happens only when there are less than 5 rows in the tibble and there are non-ASCII characters.
For information, my workaround so far is to rename my search using stringi::stri_trans_general(id = "Latin-ASCII")
I guess this issue is not directly linked to banR but to the underlying API.
If one of the searched address contains non-ASCII characters we end up with Unicode characters in the results instead of UTF-8. (\xe2 instead of â for example):
In the following example using évron instead of evron results in a different encoding for my second search (Chatelaillon).