-
Notifications
You must be signed in to change notification settings - Fork 22
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
Table 1-01-01, Revision of winds variables #417
Comments
https://github.com/wmo-im/tt-wigosmd/wiki/Meeting-2022.09.22 notes:
|
I think we need five basic variables: wind direction, wind speed, u, v, and w. The vertical profile of wind can be described using attributes in the upcoming WMDR 2.0. The existing codes, i.e., 12005, 12006, 310, and 307, look confusing to me. Would like to see if and how they have been used. However, it would be rather difficult to update the description with additional information. Looking for comments and suggestions! |
Wind Speed: commonly refer to the speed of horizontal wind, a ratio of the distance covered by the air to the time taken to cover it. This scalar quantity can be used to represent a value at given location and time or average over spatio-temporal extent or values as a function spatio-temporal coordinates Wind Direction: the direction of horizontal wind expressed in degrees at which the wind originates, i.e., 0° for north or northerly wind, 90° for east or easterly wind, 180° (or -180°) degree for south or southerly wind, and 270° (or -90°) for west or westerly wind. This scalar quantity can be used to represent a value at given location and time or average over spatio-temporal extent or values as a function spatio-temporal coordinates u: east-west component of the horizontal wind vector, positive value for eastward wind or west wind. This scalar quantity can be used to represent a value at given location and time or average over spatio-temporal extent or values as a function spatio-temporal coordinates v: north-south component of the horizontal wind vector, positive value for northward wind or south wind . This scalar quantity can be used to represent a value at given location and time or average over spatio-temporal extent or values as a function spatio-temporal coordinates. w: vertical component of the 3-D wind vector. positive value for upward wind, This scalar quantity can be used to represent a value at given location and time or average over spatio-temporal extent or values as a function spatio-temporal coordinates. Looking comments and suggestions! |
A few follow-up thoughts on @gaochen-larc's comments:
|
https://github.com/wmo-im/tt-wigosmd/wiki/2022.10.06-TT-WIGOSMD meeting notes: Comment from Michael Shoot (NASA) above; in progress |
Sent email to secretariat that supports ET-UAM to find a volunteer to review. |
@amilan17 Could you update the issue to reflect the discussion, so that we see what is specifically proposed? |
Hi everyone, Gao, I've included my comments below. Brackets alone are comments. Bracketed italicized and bold words/phrases are my suggested edits. Thanks all, Wind Speed: commonly refers to the speed of horizontal wind, a ratio of the [horizontal] distance covered by the air to the time taken to cover it [that distance]. This scalar quantity can be used to represent a value at a given location and time [instantaneous] or average over spatio-temporal extent or values as a function of spatio-temporal coordinates. [I like that you’ve included the difference between instantaneous vs averaged/down-sampled here, most users aren’t familiar with the time averaged wind measurements]. Wind Direction: the direction of horizontal wind expressed in degrees at which the wind originates, i.e., 0° for north or northerly wind, 90° for east or easterly wind, 180° (or -180°) degree for south or southerly wind, and 270° (or -90°) for west or westerly wind. This scalar quantity can be used to represent a value at given location and time or average over spatio-temporal extent or values as a function spatio-temporal coordinates [I like that you’ve defined the coordinate system here- oceanography uses the reverse convention, so it is important that it be well defined]. u: east-west component of the horizontal wind vector, positive value for eastward wind or west wind. [This seems confusing – consider “positive value for eastward moving or west-to-east wind"]. This scalar quantity can be used to represent a value at given location and time or average over spatio-temporal extent or values as a function of spatio-temporal coordinates. v: north-south component of the horizontal wind vector, positive value for northward wind or south wind. [This seems confusing – consider “positive value for northward moving or south-to-north wind"]. This scalar quantity can be used to represent a value at given location and time or average over spatio-temporal extent or values as a function of spatio-temporal coordinates. w: vertical component of the 3-D wind vector. positive value for upward wind, This scalar quantity can be used to represent a value at given location and time or average over spatio-temporal extent or values as a function of spatio-temporal coordinates. [w has a meteorological definition of dz/dt; may be worth also including a definition for omega as well for completeness]. |
@gaochen-larc |
https://github.com/wmo-im/tt-wigosmd/wiki/2022.12.08-TT-WIGOSMD notes: |
Hi Goa, |
https://github.com/wmo-im/tt-wigosmd/wiki/2023.01.12-TT-WIGOSMD notes: |
https://github.com/wmo-im/tt-wigosmd/wiki/2023.02.16-TT-WIGOSMD notes: Gao will update the proposal summary with details. |
The principal conventionally observed quantities are
|
@gaochen-larc @joergklausen @amilan17 |
https://github.com/wmo-im/tt-wigosmd/wiki/2023-03-17-TT-WIGOSMD notes: |
https://github.com/wmo-im/tt-wigosmd/wiki/2023.04.21-TT-WIGOSMD notes: |
Branch updated |
https://github.com/wmo-im/tt-wigosmd/wiki/2023.05.04-TT-WIGOSMD/notes: |
https://github.com/wmo-im/tt-wigosmd/wiki/2023.06.15-TT-WIGOSMD notes: Lara reviewed the branch and noted that the issue summary is different than the branch (see comment above); there was a discussion about "north" vs "true north"; DECISION: remove units from horizontal wind direction; @gaochen-larc update branch, issue summary and create PR; |
Should 310 be superseded by another code? If not, then I recommend changing the status to "Retired". 310,"\Atmosphere\Wind\Upper wind (X, Y components, horizontal)",,,"Upper wind (X, Y components, horizontal)",Horizontal component of wind as a vector in an orthogonal coordinate system. |
retired=deprecated? Yes, I believe so. |
Agree |
https://github.com/wmo-im/tt-wigosmd/wiki/2023.06.30-TT-WIGOSMD notes: validated; code 310 will be retired; |
…evision-of-winds-variables #417 table 1 01 01 revision of winds variables
Publication of these amendments is on hold pending further discussions |
https://github.com/wmo-im/tt-wigosmd/wiki/2024.02.15-TT-WIGOSMD notes: |
@gaochen-larc @joergklausen @amilan17 |
Re 12005: Given the comment further up by @mshook2012, I don't think it hurts to eliminate possible ambiguity about what 'north' is meant. Furthermore, the condition of windspeed > 0 is not reflected, either. So I would expand by saying "The direction of horizontal wind at which the wind originates expressed in degrees, i.e., 0 deg for true north or northerly wind, 90 deg for east or easterly wind, 180 deg (or -180 deg) degree for south or southerly wind, and 270 deg (or -90 deg) for west or westerly wind. Scalar quantity to represent a value at a given location and an instantaneous time, or average over spatio-temporal extent, or values as a function of spatio-temporal coordinates. Note: wind direction is not defined for zero wind speed." BTW (arrrgh) I initially looked at the proposal at the top to put @JohnEyre 's comments into perspective. Alas, this has not been updated in a long time. @amilan17 We need to review how to deal with changes to the initial proposal during its evolution. The only solution I see, really, is
|
@joergklausen @amilan17 @JREyre Other definitions, moved from the regulatory material to GIMO, which might be relevant here are:
|
Amendment Details (working version)
|
@meulenvd: Thank you! |
#522) * issue #417, updated to match this comment #417 (comment) * Github Action Commit --------- Co-authored-by: amilan17 <amilan17@users.noreply.github.com>
* issue #506, manual update, editorial * issue #417, updated to match this comment https://github.com/wmo-im/w… (#522) * issue #417, updated to match this comment #417 (comment) * Github Action Commit --------- Co-authored-by: amilan17 <amilan17@users.noreply.github.com> * New 499 table 5 02 01 add descriptions (#521) #499 * commit ttl files that will be overwritten * commit files that will be overwritten * update new branch #499 * Github Action Commit --------- Co-authored-by: amilan17 <amilan17@users.noreply.github.com> * Update 1-01-01.csv (#519) #502 * Update 1-01-01.csv notation 646: corrected ammonium from ammonia. * Github Action Commit --------- Co-authored-by: joergklausen <joergklausen@users.noreply.github.com> * Github Action Commit --------- Co-authored-by: amilan17 <amilan17@users.noreply.github.com> Co-authored-by: Jörg Klausen <34302947+joergklausen@users.noreply.github.com> Co-authored-by: joergklausen <joergklausen@users.noreply.github.com>
Proposal Summary
The wind variables in WMDR - 12005, 12006, 310, 307 - are inconsistent and incomplete. They should be revised to include:
Summary and Purpose
Update and add variables to adequately support wind measurements.
Proposal
Update the existing wind variables and add new ones as necessary
Current Observed Variable Measurand Code
Recommend removing 310 as it is not meaningful without definition of XY coordinates.
Reason
[your reasoning why the proposal resolves the issue]
Stakeholder(s)
ET-UAT
ET-SSU
Consultations
[include names and emails or handles of individuals or groups that reviewed the proposal]
Context
[include references to manuals or guides that are reviewed to ensure alignment, if proposal differs then document how and why]
Expected Impact of Change
[enter LOW (for editorial changes to existing codes), MEDIUM (for new codes) or HIGH (for deprecated and superseded codes]
The text was updated successfully, but these errors were encountered: