-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Table 1-01-05 new code for Suspended sediment discharge #432
Comments
https://github.com/wmo-im/tt-wigosmd/wiki/2022.11.22-TT-WIGOSMD notes: Hydrological editiing team will be working on this |
Maybe we could change 'rate of movement of ...' for 'amount of ... crossing a stream section per unit time' |
Updated proposal based on comments |
https://github.com/wmo-im/tt-wigosmd/wiki/2023.01.12-TT-WIGOSMD notes: |
@jbianchi81 if/when the branch is ready for my review, please open a PR to merge into the FT2023-1 branch |
…spended-sediment-discharge into FT2023-1 branch Update 1-01-05.csv #432
…01-05-new-code-for-suspended-sediment-discharge #432 table 1 01 05 new code for suspended sediment discharge, m
Initial request
Suspended sediment discharge
Current definition: Rate of movement of sediment which is suspended by turbulence in flowing water for considerable periods of time without contact with the bed transported at a given cross-section. [Based on 'suspended sediment' in International Glossary of Hydrology (WMO-No. 385). 2012 edition.]
Comments:
Amendment details
Comments
This code was proposed during FT2022-2 and received comments. Therefore, it was removed and should be discussed further.
Requestor(s)
Fulford, Janice M (USGS), William Bolhofer (NOAA)
Stakeholder(s)
National Hydrological Services, WHOS
Publication(s)
Example: Manual on Codes (WMO-No. 306), Volume I.3, WMO Codes Registry, Code table 1-01-05
Expected impact of change
LOW
Collaborators
@amilan17, @jbianchi81, @disiiwash, @jkorhonen, José Valles, Paolo Leoni, Joao Carlos Carvalho (JET-HYDMON)
References
No response
Validation
No response
The text was updated successfully, but these errors were encountered: