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
It seems SEPAL is using it's own set of geometries to define countries. this lead to inconsistences of depth when dealing with countris that have never been part of any projects. As applications are exlusively relying of FAO GAUL 2015 dataset from GEE would it be possible to do the same for the recipes?
IF it makes thing easier and if you have access to Python scripts inside the widgets, I've created a subset of sepal_ui just to deal with FAO GAUL geometries: https://github.com/12rambau/pygaul
It seems SEPAL is using it's own set of geometries to define countries. this lead to inconsistences of depth when dealing with countris that have never been part of any projects. As applications are exlusively relying of FAO GAUL 2015 dataset from GEE would it be possible to do the same for the recipes?
IF it makes thing easier and if you have access to Python scripts inside the widgets, I've created a subset of sepal_ui just to deal with FAO GAUL geometries: https://github.com/12rambau/pygaul
the documentation is there: https://pygaul.readthedocs.io/en/latest/usage.html (if your computer is using the dak theme, the maps will be grey I don't know why yet).
The functionality that could be very usefull is
get_names
to populate the dropdown with "name" - "code" pairs.The text was updated successfully, but these errors were encountered: