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
In the interim and processed data of the name server species, some names are written with incorrect encoding characters, such as Agaricus xantholepis F.H. Møller, 1952 instead of Agaricus xantholepis F.H. Møller, 1952 (e.g. in this file).
The problem is related to the way the GBIF API is requested. With the requests library (used in e.g. the gbif_name_matching utility), there are no issues:
But the name server list is so big, that an asynchronous request is necessary. This is implemented in this notebook. Apparently the asyncio or other library that is used to request GBIF does not handle the result as UTF8?
The text was updated successfully, but these errors were encountered:
In the interim and processed data of the name server species, some names are written with incorrect encoding characters, such as
Agaricus xantholepis F.H. Møller, 1952
instead ofAgaricus xantholepis F.H. Møller, 1952
(e.g. in this file).The problem is related to the way the GBIF API is requested. With the
requests
library (used in e.g. the gbif_name_matching utility), there are no issues:Returns:
But the name server list is so big, that an asynchronous request is necessary. This is implemented in this notebook. Apparently the
asyncio
or other library that is used to request GBIF does not handle the result as UTF8?The text was updated successfully, but these errors were encountered: