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 text was updated successfully, but these errors were encountered:
crijke
changed the title
__discuss: retrieve regions from elasticsearch instead of catalogue__
Retrieve regions from elasticsearch instead of catalogue__
Jul 9, 2019
crijke
changed the title
Retrieve regions from elasticsearch instead of catalogue__
Retrieve regions from elasticsearch instead of catalogue
Jul 9, 2019
Until now datenguide-api has used a bundled list of regions, which got out of sync with the current statistics in the meantime.
With the next release of datenguide-api (v0.2.0) we will load regions from the automatically updated names.json schema from data.genesapi.org to ensure region data is always up to date.
@crijke would it be okay/preferred to use names.json from data.genesapi.org in the R and Python packages re: CorrelAid/datenguideR#18 (as opposed to querying the datenguide-api for this)?
currently regions are fetched from the destatis catalog and not from the actual data. should we fetch them from the actual data instead?
also see CorrelAid/datenguideR#18
The text was updated successfully, but these errors were encountered: