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

TODO: Add New List to Issues #16

Open
johannesliem opened this issue May 8, 2014 · 2 comments
Open

TODO: Add New List to Issues #16

johannesliem opened this issue May 8, 2014 · 2 comments
Labels

Comments

@johannesliem
Copy link
Contributor

  1. Display more than 1 spp on a given map? Maybe address this issue by displaying Reclass Maps
  2. Refresh/redraw button
  3. Zoom in more closely
  4. Standardize scales between map panes
  5. Be able to save custom legends
  6. Change default color ramp (keep color ramp in one color
    • Color blindness considerations
  7. Directly useful metrics for CNF people: volume measure (cubic feet?)
  8. Make background darker to distinguish landscape features? Switch background layers akin to google maps
  9. Cannot distinguish 0 value cells from inactive cells. Are 0 value cells clear or white?
  10. 3 default breaks in data range
  11. Add CNF boundary (or any other admin boundary of interest, Leech Lake)
@johannesliem
Copy link
Contributor Author

Comments/Questions from Johannes:

  1. multiple landis-layers on one map is a possible future enhancement (for comparisson use the side-by-side view); but I am not sure if it makes that much sense, because the cells will hide other cells below ... depends on the data ... so a clever reclassification would make maybe more sense ...
  2. What does the refresh/redraw button exactly? (What elements are going to be refreshed/redrawn)
  3. Zoom in more closely: that is going to be ajustable with the PreProcTool (but: zooming in more closley means: more data is generated; increase of PreProcTools runtime and amount of data)
  4. "scales" in sense of "map-scales" or in sense of "classification-scale"?
  5. at the moment i am working on a system where you can store the current view and open it up later again (with a url parameter) ... that means that the legends will be stored as well ... or would there be a special use case you are thinking about?
  6. I will think about a way to incooperate this ... so you can set the default color ramp in the PreProcTool ... mabey later it would be interessting to add a color-ramp chooser ...
  7. We could introduce a conversion system in the back and you could choose in a pref pane if you want to use the original units or the special defined units ... (but this will be a future enhancement)
  8. I can add configuration sliders (Brightness, Contrast, Saturation) ... so the base map could be changed on the fly; at the same time I think it should be not to copliated to add other base maps (but both more a future enhnacement) ... for now I will add this to the configurationfile in the PreProcTool
  9. How can I distinguish between 0 and inactive cells? Or: which datasets/outputs have inactive-cells? If there are inactive cells in a dataset, do they always have the value 1 (like in the base wind dataset)?
  10. The inital number of breaks will be adujstable with the preproctool (and will be also based on the data)
  11. The used map library (Openlayers3) is in development ... at the moment when a landis-layer (on the fly colloring) is used I am not able to add vector (shape) files on top (but this will change within this year, since this is allready in development).

latest update: May 28 by Johannes :)

@mslucash
Copy link
Collaborator

mslucash commented Jun 6, 2014

Here are my comments.

  1. This seems complicated. I would ignore for now.
  2. The refresh button will be unnecessary as soon as you get all the maps synchronized right when the screen opens.
  3. Good. Folks just wanted to zoom in a bit more than they could.
  4. They are talking about the classification/colors being the same between all the windows displayed on the screen at one time.
  5. That will be fine.
  6. The idea was just if you were viewing biomass for example, you'd just want shades of green- light for low biomass, dark green for high biomass. Not red for low and blue for high. Or if you were red/green color blind you might want to select a different color ramp. It could be specified in the PreProc or on the Viz Tool. Viz tool would be ideal, but maybe not feasible this round.
  7. Just wait on that.
  8. Config sliders should be fine on the fly and would solve the problem of making sure there's enough contrast.
  9. The ecoregion has the inactive cells marked as zero.
  10. OK. Good.
  11. It doesn't have to be a vector map. Raster outline of landscape types or ecoregion map (maybe black and white like background?) would be fine. We could discuss this more later.

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

No branches or pull requests

2 participants