Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

module description text amendments #29

Closed
23 tasks done
vogtpet opened this issue Apr 9, 2021 · 4 comments
Closed
23 tasks done

module description text amendments #29

vogtpet opened this issue Apr 9, 2021 · 4 comments

Comments

@vogtpet
Copy link
Contributor

vogtpet commented Apr 9, 2021

Below are some suggestions for text changes in the modules:
All modules:

  • menu title “Select map classes”: maybe better “Select input map classes”
  • button "Download Test Dataset”: add the following text line below this button: Click the button above to download the test files “clc3class.tif" and “example.tif” into the folder “downloads”
  • button "CONVERT THE IMAGE CLASSES": maybe better "CONVERT THE INPUT IMAGE CLASSES"

Specific modules:
ACC:

  • Provide a byte-formatted input image. Recode the classes into the following 4 classes: background (nonforest), foreground (forest), special background 1 (optional, e.g. water) and special background 2 (optional). All remaining classes will be considered as missing data.
  • Dropdown menu text: special background 1 (optional)
  • Dropdown menu text: special background 2 (optional)
  • Dropdown menu text: output options: stats + image of viewport (default)

DIST:

  • Provide a byte-formatted input image. Recode the classes into the following 2 classes: background (nonforest), foreground (forest). All remaining classes will be considered as missing data.
  • Dropdown menu text: Euclidean distance only (default)

FAD/FRAG:

  • Provide a byte-formatted input image. Recode the classes into the following 4 classes: background (nonforest), foreground (forest), special background 1 (optional, e.g. water) and special background 2 (optional). All remaining classes will be considered as missing data.
  • Dropdown menu text: special background 1 (optional)
  • Dropdown menu text: special background 2 (optional)

LM:

  • Provide a byte-formatted input image. Recode the classes into 3 dominant land cover classes. All remaining classes will be considered as missing data.
  • Dropdown menu text: Dominant land cover 3 (Developed)

MSPA:

  • Provide a byte-formatted input image. Recode the classes into the following 2 classes: background (nonforest), foreground (forest). All remaining classes will be considered as missing data.
  • The last slider text should read: intext (instead of the current: int ext)

P223:

  • Provide a byte-formatted input image. Recode the classes into the 3 following classes: background (nonforest), foreground (forest), special background (for P23 only). All remaining classes will be considered as missing data.
  • Dropdown menu title: Computation precision
  • Dropdown menu entry: float precision (default, but requires more disk space)

PARC:

  • Provide a byte-formatted input image. The input image must contain at least 2 different classes. The class value 0 will be considered as missing data.

RSS:

  • Provide a byte-formatted input image. Recode the classes into the following 2 classes: background (nonforest), foreground (forest). All remaining classes will be considered as missing data.

SPA:

  • Provide a byte-formatted input image. Recode the classes into the following 2 classes : background (nonforest), foreground (forest). All remaining classes will be considered as missing data.
  • Dropdown menu: Number of pattern classes: prepend the number of classes before the description like this
    2: Small & linear features (SLF), Coherent
    3: Core, Core-Openings, Margin
    5: Core, Core-Openings, Edge, Perforation, Margin
    6: Core, Core-Openings, Edge, Perforation, Islet, Margin
@12rambau
Copy link
Collaborator

instead of a hint I've added a tooltip to the test download btn

@vogtpet
Copy link
Contributor Author

vogtpet commented Apr 12, 2021

I still think it would be better to write that sentence below, or maybe even better above, the Download button. The tooltip thing I since but not used anywhere else. Writing the text above the button is more obvious because you can always read it and it reminds the user where the files have been downloaded to, without having to hover over the button.

@12rambau 12rambau reopened this Apr 12, 2021
@vogtpet
Copy link
Contributor Author

vogtpet commented Apr 14, 2021

what changed here: only the word below replaced by above in the tooltip? The idea was to not use any tooltips anywhere because tooltips are not evident, they are hidden unless you know where to place the mouse. imo, it would be much better to write the following sentence below the DOWNLOAD TEST DATA button:
Click the button above to download the test images "example.tif" and "clc3class.tif" into the folder "downloads" in your user account.

@12rambau
Copy link
Collaborator

12rambau commented Apr 14, 2021

No in convert_tile.py I removed the tooltip and used a Markdown object instead. So now there are no tooltip bu just text display above the btn.

Capture d’écran 2021-04-14 à 14 05 47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants