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

Revise text files in the Erosion modeling assignment #26

Open
wenzeslaus opened this issue Apr 13, 2016 · 1 comment
Open

Revise text files in the Erosion modeling assignment #26

wenzeslaus opened this issue Apr 13, 2016 · 1 comment

Comments

@wenzeslaus
Copy link
Member

There is a lot of text files with different syntaxes in the Erosion modeling assignment (hydrology_erosion.html). Simplification is needed.

  • cfactor.txt see separate issue Move cfactor.txt file from data to some rich text in the Erosion modeling assignment #25
  • lu_labels.txt is unused, labels are (or should be) in the raster, remove to simplify instructions
  • rename cfac_rules.txt and cfac_color.txt to something like cfactor_...
  • cfac_color.txt, soilloss_color.txt, erdep_color.txt: decide on using spaces or colons to separate RGB components in color rules (see other assignments and GRASS manual)
  • erdep_color.txt beautify and perhaps explain comments
  • cfac_rules.txt: possible to simplify syntax or use another module to avoid duplicating numbers (e.g. 4:4:0.8:0.8 -> 4:0.8)?
  • erdep_class.txt: it should be possible to use simpler syntax: old_low:old_high:new_val (desired when the opposite is not possible?)
  • erdep_label.txt use comma for separator and rename to CSV (CSV is more common format)
@hmitaso
Copy link
Contributor

hmitaso commented Apr 13, 2016

Just a comment - based on my experience people have no idea what csv is, I
don't see it much better than txt. As for GRASS - in terms of what is more
common format for GRASS it depends on who you talk to. In general people
are now used to hidden suffix so it is more like what do we need to have
this being open with to read (text editor/notepad or spreadsheet) and how
it is used by GRASS.
The rules formatting is purely due to the GRASS requirement that the
recoding reclassifies from interval of values to interval of values - it
would be nice to simplify it, it was always confusing for people who do not
read manuals.
I don't see much advantage in changing cfac to cfactor, both shorten the
important part and that is the c for cover.

On Wed, Apr 13, 2016 at 4:40 AM, Vaclav Petras [email protected]
wrote:

There is a lot of text files with different syntaxes in the Erosion
modeling assignment (hydrology_erosion.html). Simplification is needed.

  • cfactor.txt see separate issue Move cfactor.txt file from data to some rich text in the Erosion modeling assignment #25
    https://github.com/ncsu-osgeorel/geospatial-modeling-course/issues/25
  • lu_labels.txt is unused, labels are (or should be) in the raster,
    remove to simplify instructions
  • rename cfac_rules.txt and cfac_color.txt to something like
    cfactor_...
  • cfac_color.txt, soilloss_color.txt, erdep_color.txt: decide on using
    spaces or colons to separate RGB components in color rules (see other
    assignments and GRASS manual)
  • erdep_color.txt beautify and perhaps explain comments
  • cfac_rules.txt: possible to simplify syntax or use another module to
    avoid duplicating numbers (e.g. 4:4:0.8:0.8 -> 4:0.8)?
  • erdep_class.txt: it should be possible to use simpler syntax:
    old_low:old_high:new_val (desired when the opposite is not possible?)
  • erdep_label.txt use comma for separator and rename to CSV (CSV is
    more common format)


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ncsu-osgeorel/geospatial-modeling-course/issues/26

Helena Mitasova
Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://www4.ncsu.edu/~hmitaso/
http://geospatial.ncsu.edu/

email: [email protected]
ph: 919-513-1327 (no voicemail)
fax 919 515-7802

@wenzeslaus wenzeslaus modified the milestones: Fall 2017, Fall 2016 Jan 31, 2017
@wenzeslaus wenzeslaus modified the milestones: Fall 2017, Fall 2018 May 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants