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
Source names rivers_lin2019_v1, vito and globcover are not listed in data_catalog.yml. The source names are listed in the data_catalog.yml file from hydromt-artifacts-0.0.9 (Source code). This seems the correct file.
Also, my recommendation would be to store this file at one location...
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi @verseve I think this has to do with the update of the artifact data, where some dataset pointers were renamed (e.g. rivers_lin2019_v1 to hydro_rivers_lin2019 and vito to vito_2015). This is the related issue for hydromt_delft3dfm: Deltares/hydromt_delft3dfm#159
It includes some relevant documentations (like the changelog containing old vs new names) and the linked PR shows how we resolved this for hydromt_delft3dfm.
Hi @veenstrajelmer, yes the tests run fine now( fixed by@hboisgon). The data_catalog.yml in hydromt-artifacts-0.0.9 (Source code) is incorrect. I would recommend to store this file at one location.
Ok, if I understand you correctly, you are saying that the data_catalog from hydromt-artifacts and the data_catalog in hydromt are different, even though their versions are identical (0.0.9) right? That indeed seems a bit odd to me. I indeed see vito in the first one and vito_2015 in the latter.
HydroMT version checks
Reproducible Example
The hydromt_wflow tests fail in PR #300.
It seems this is caused by the data_catalog.yml file that is downloaded when building a wflow model during the tests from artifact_data.
Current behaviour
Desired behaviour
Source names
rivers_lin2019_v1
,vito
andglobcover
are not listed in data_catalog.yml. The source names are listed in the data_catalog.yml file from hydromt-artifacts-0.0.9 (Source code). This seems the correct file.Also, my recommendation would be to store this file at one location...
Additional context
No response
The text was updated successfully, but these errors were encountered: