Skip to content

Releases: openforis/sepal_ui

v_2.2.0

30 Sep 12:02
4113695
Compare
Choose a tag to compare

changes will be available in changelog

New reclassify tool

15 Sep 14:29
b6b95c0
Compare
Choose a tag to compare
Merge pull request #281 from 12rambau/master

ci: create automated changelog

New reclassify tools

15 Sep 14:08
db164cf
Compare
Choose a tag to compare

Among many other things that will be displayed in the changelog.md file. A new reclassify tool is now availabel in sepal_ui and can be used in any app.

improve drawing tool

22 Jun 21:41
Compare
Choose a tag to compare
  • remove legacy print statement
  • add crs to drawn shapes
  • reset shape when starting a new drawing

general bug fix

17 Jun 14:56
b776690
Compare
Choose a tag to compare
  • improve AOIReset
  • map attribution
  • automatic creation of the release branch in module factory
  • improve the assetSelect component

small bug fix

15 Jun 17:31
Compare
Choose a tag to compare
v_2.0.4

Merge branch 'master' into release

adapt to geemap

09 Jun 11:43
Compare
Choose a tag to compare

a geemap method (ee_to_shp) is incompatible with a release in SEPAL. Thus with avoid the use of the ee_to_geopandas method until geemap 0.8.17 is released

debug v2

08 Jun 16:12
Compare
Choose a tag to compare
  • small bug fix of the sepal_ui v2 version
  • first version that will be released to SEPAL prod environment

fix local aoi residual bugs

02 Jun 13:37
Compare
Choose a tag to compare
v_2.0.1

fix merge

end the forced GEE dependency

26 May 12:50
94722fc
Compare
Choose a tag to compare

SEPAL_UI v_2.0.0

content

The new version of sepal_ui is not relying only on GEE anymore. The request was build when we started to create apps based on the planet API or the GWB. Sepal_ui will not change drastically to the end user but the developper will now have the possiblity to choose between using GEE or not. As it lead to major changes in the lib we decided to also embed the modification that we couldn't made for non-regression. This version is thus not compatible with app developped previously. The next section will describe what are the changes that developer need to make to meve from sepal_ui 1.1.4 to sepal_ui 2.0.0.

The test coverage dropped from 90% to 80% in the process please let us know if you encounter some strange behaviours

changelog

mandatory

  • the aoi interface have been completely overwritten, the new tile component is called sepal_ui.aoi.AoiTile and it's embeding 2 other aoi classes: AoiModel and AoiView. You're thus not force to use a map to create an AOI selector (for example in data explorer). This new aoi interface is bind to gee FAUL or alternatively to GADM 2021 (non-GEE).
  • If you don't use an AoiTile but an AoiView with a custom map, make sure that the map is a SepalMap and has a DrawingControl (dc=True)
  • get_aoi_name has been removed, now it's a member: aoi_model.name
  • get_aoi_ee has been removed, now it's a member: aoi_model.feature_collection
  • get_shp has been removed, now it's a member: aoi_model.gdf
  • the done trait of the StateBar object has been permanently removed, us loading instead
  • the isAsset method have been moved from utils to gee (and renamed is_asset)
  • for sementic reasons, the former output member of the Tile component have been renamed alert
  • the zoom_bounds function of the SepalMap is not using cardinal points of the bounding box any more but the 4 extreme coordinates as given by Shapely.bounds
  • in load_asset, load_points and load_vector, the v_model are now Dict so all the getter and setter have been removed. access these data directly from the dictionnary
  • for sementic reason we decided to change the name of the tiles. it is now "aoi_tile" and "about_tile"

optional

  • to access the colors we were using the ipyvuetify.theme.themes.xxx with xxx the color. Now the colors are all stored in sepal_ui.color.xxx. the switch between light and dark theme will thus be handled automatically
  • There is now no need to use the "voila-theme=dark" option in urls as the color of the background is handled by the App component (using a z=-1 overlay)
  • You can now use the Model object to create what we called previously io, more information will come in the documentation but notice that it's embeding saving and binding methods
  • the bind method of the alert component is now deprecated, consider moving to Model methods