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 very much for the great wbopendata package.
Since the last update (I think), I have noted that metadata that contain url links create an error when they are displayed.
For example: wbopendata, indicator(EN.ATM.CO2E.KT)
or wbopendata, indicator(EG.ELC.FOSL.ZS)
create errors.
Still, the data is correctly uploaded.
The issue becomes more problematic when several indicators are to be uploaded, because the error causes wbopendata to stop.
For example: wbopendata, indicator(EN.ATM.CO2E.KT ; NY.GDP.MKTP.KN)
only loads data from the first indicator and then stops.
In such cases, using option clear and/or nometadata solves the problem, but that is of course not totally satisfactory.
I have tried to solve the issue by myself and it turns out that the error is located in _website.ado, but I could not determine precisely where.
Thanks for your help.
Sylvain Weber
The text was updated successfully, but these errors were encountered:
SylWeber
changed the title
Error when displaying metadata that contains a url link
Error when displaying metadata that contain a url link
Jan 31, 2022
Hi,
Thanks very much for the great wbopendata package.
Since the last update (I think), I have noted that metadata that contain url links create an error when they are displayed.
For example:
wbopendata, indicator(EN.ATM.CO2E.KT)
or
wbopendata, indicator(EG.ELC.FOSL.ZS)
create errors.
Still, the data is correctly uploaded.
The issue becomes more problematic when several indicators are to be uploaded, because the error causes
wbopendata
to stop.For example:
wbopendata, indicator(EN.ATM.CO2E.KT ; NY.GDP.MKTP.KN)
only loads data from the first indicator and then stops.
In such cases, using option
clear
and/ornometadata
solves the problem, but that is of course not totally satisfactory.I have tried to solve the issue by myself and it turns out that the error is located in
_website.ado
, but I could not determine precisely where.Thanks for your help.
Sylvain Weber
The text was updated successfully, but these errors were encountered: