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

Distinguish between ocean and true wetlands on surface dataset #1886

Closed
billsacks opened this issue Oct 27, 2022 · 5 comments · Fixed by #2372
Closed

Distinguish between ocean and true wetlands on surface dataset #1886

billsacks opened this issue Oct 27, 2022 · 5 comments · Fixed by #2372
Labels
enhancement new capability or improved behavior of existing capability
Milestone

Comments

@billsacks
Copy link
Member

billsacks commented Oct 27, 2022

Currently we use the wetland landunit to represent ocean points as well as true (inland) wetlands. This could cause problems for the changes in #1878 as well as for those in #1716. For the sake of those changes and possibly other reasons, we should distinguish between ocean points and true wetlands on the surface dataset by adding a new PCT_OCEAN field and using that rather than the PCT_WETLAND field for points where we don't have any land cover data. At runtime these could still be combined into the wetland landunit (though with the changes for #1878 ocean would instead be changed to bare ground), but separating them would allow us to distinguish between these two very different land covers for #1878 and #1716 – and we could possibly also have some metadata describing the separation of the wetland landunit into ocean vs. true wetland for each grid cell.

Currently we (by default) do not include inland wetlands on the surface dataset, so this isn't a problem, but it would become problematic if we started including inland wetlands again.

@billsacks billsacks added enhancement new capability or improved behavior of existing capability priority: low Background task that doesn't need to be done right away. labels Oct 27, 2022
@ekluzek
Copy link
Collaborator

ekluzek commented Oct 27, 2022

The fact that wetland means ocean-points in CTSM is very confusing for users. So making this clear by calling it what we actually use it for makes the code much more readable. And it makes the surface datasets more readable and understandable as well. So I really like this idea. I was going to suggest it as well.

@wwieder
Copy link
Contributor

wwieder commented Aug 30, 2023

To avoid confusion can we go ahead and call these coastal areas PCT_OCEAN in CTSM5.2 to avoid confusion on PCT_WETLAND, especially since we don't actually have inland wetlands?

@ekluzek
Copy link
Collaborator

ekluzek commented Aug 30, 2023

@wwieder I do support that idea. It would require some code changes. But, hopefully not too hard. @billsacks you worked on the current implementation how hard would it be to do this? I don't think you should do it, but if you can assess it as not being too hard someone else could and get advice from you on what to do...

@billsacks
Copy link
Member Author

I would budget a few days of work for this. It will require changes in mksurfdata as well as surfrdMod.

@ekluzek ekluzek added next this should get some attention in the next week or two. Normally each Thursday SE meeting. and removed priority: low Background task that doesn't need to be done right away. labels Aug 30, 2023
@ekluzek ekluzek added this to the ctsm5.2.0 milestone Aug 30, 2023
@ekluzek ekluzek removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Feb 15, 2024
@ekluzek
Copy link
Collaborator

ekluzek commented Feb 15, 2024

Done on the ctsm5.2 branch and will close with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants