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
I don't think that describing the file naming of the output maps in a README pdf stored in the output directory is the best idea. I think this information suits perfectly the repo's README. @peterdesmet, @amyjsdavis, what do you think about it?
The text was updated successfully, but these errors were encountered:
Its location could be in data/processed but since that directory contains all generated files, it's maybe better to avoid. Since it is rather small, I agree that it would be good to have in the main README at root
I see what you mean. My motivation for having this stand alone readme.pdf file in the output directory is for risk assessors who are downloading the pdfs of the risk maps from the repo and need to understand the file naming structure. I see now that it does not make sense to have risk assessment documents here with the modeling work flow. I will be happy to incorporate it into the original README at root.
I don't think that describing the file naming of the output maps in a README pdf stored in the output directory is the best idea. I think this information suits perfectly the repo's README.
@peterdesmet, @amyjsdavis, what do you think about it?
The text was updated successfully, but these errors were encountered: