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

Revision of winds variables #418

Closed
JohnEyre opened this issue Jun 13, 2022 · 3 comments
Closed

Revision of winds variables #418

JohnEyre opened this issue Jun 13, 2022 · 3 comments

Comments

@JohnEyre
Copy link
Collaborator

Proposal Summary

The wind variables in WMDR - 12005, 12006, 310, 307 - are inconsistent and incomplete. They should be revised to include:

  • wind specified in speed and direction or in components,
  • wind at a single level or a vector of levels,
  • wind at specified heights or pressures, or at specified distances from reference levels,
  • more complete definition of wind direction - an angle measured clockwise from North.

Summary and Purpose

[add brief overview]

Proposal

[your specific proposal to resolve the issue - update when decision on proposal is finalised]

Reason

[your reasoning why the proposal resolves the issue]

Stakeholder(s)

[include names and emails or handles of individuals or groups that introduced the proposal]

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]

@amilan17
Copy link
Member

duplicate issue with #417

@amilan17 amilan17 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 22, 2022
@gaochen-larc
Copy link
Contributor

gaochen-larc commented Oct 5, 2022

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!

@gaochen-larc
Copy link
Contributor

Wind Speed: 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 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants