Comments (14)
from grib2.
I think these can be achieved using a type of first fixed surface set to "height above ground in metres" (103) and set the level value at 10. This is why I am not in favour of creating new parameters
from grib2.
To be more explicit, the usual way to encode these parameters is:
10 m u component of wind:
GRIB key | Code table | Value | Meaning |
---|---|---|---|
discipline | 0.0 | 0 | meteorological products |
category | 4.1 | 2 | momentum |
parameter | 4.2.0.2 | 2 | U component of wind |
first fixed surface | 4.5 | 103 | specified height above ground |
scale factor | n/a | 0 | multiply by 10^-0 --> 1 |
scaled value | n/a | 10 | 10 metres (10 * 10^-0 ) |
10 m v component of wind:
GRIB key | Code table | Value | Meaning |
---|---|---|---|
discipline | 0.0 | 0 | meteorological products |
category | 4.1 | 2 | momentum |
parameter | 4.2.0.2 | 3 | V component of wind |
first fixed surface | 4.5 | 103 | specified height above ground |
scale factor | n/a | 0 | multiply by 10^-0 --> 1 |
scaled value | n/a | 10 | 10 metres (10 * 10^-0 ) |
10 m Wind speed
GRIB key | Code table | Value | Meaning |
---|---|---|---|
discipline | 0.0 | 0 | meteorological products |
category | 4.1 | 2 | momentum |
parameter | 4.2.0.2 | 1 | wind speed |
first fixed surface | 4.5 | 103 | specified height above ground |
scale factor | n/a | 0 | multiply by 10^-0 --> 1 |
scaled value | n/a | 10 | 10 metres (10 * 10^-0 ) |
10m wind direction
GRIB key | Code table | Value | Meaning |
---|---|---|---|
discipline | 0.0 | 0 | meteorological products |
category | 4.1 | 2 | momentum |
parameter | 4.2.0.2 | 0 | wind direction |
first fixed surface | 4.5 | 103 | specified height above ground |
scale factor | n/a | 0 | multiply by 10^-0 --> 1 |
scaled value | n/a | 10 | 10 metres (10 * 10^-0 ) |
from grib2.
Hello @sebvi
thank you for the feedback.
We are a bit concerned about the approach you are proposing here for encoding these parameters.
Our model provides wind outputs at all levels within the model.
We use the approach you have detailed to encode data for the standard model wind parameters.
Our model also includes specific code which implements surface adjustments to provide a specific surface adjusted wind parameter set.
So, there are two alternative formulations for these wind parameters in our model. We are already using the settings described for the ‘standard’ wind diagnostics from the model. We want to have alternative settings for the ‘surface adjusted’ versions of these 4 parameters so that downstream customers can access both sets and differentiate between the differently derived parameters.
These are not deemed to wind parameters which happen to be at a vertical level of 10m. These are specifically adjusted parameters to represent wind at the surface. They are different parameter codes in our model.
There are specific BUFR codes for this concept:
- 11 81 Model wind direction at 10 m
- 11 82 Model wind speed at 10 m
but no specific GRIB2 concepts.
thank you for your consideration
mark
from grib2.
Hello @marqh,
if I understand you correctly, the model is producing 10m wind parameters in 2 different ways but at the end, it is still the same parameters computed/derived. If it is 2 different processes you should be able to distinguish the two sets using the process identifiers octets that are made for this I believe.
We have similar cases at ECMWF, for instance we produce "ozone mass mixing ratio" using different atmospheric composition schemes but we are not going to propose several ozone entries in the chemical constituent table, ozone is ozone!
This is why I am not really in favor of this proposal at the moment. But I am not the one deciding, we need the point of view from others in the team and from @efucile .
from grib2.
Request the following entries -
Product discipline 0 - Meteorological product parameter category 2: momentum 47 U-component of wind (surface adjusted) M/S
Product discipline 0 - Meteorological product parameter category 2: momentum 48 V-component of wind (surface adjusted) M/S
Product discipline 0 - Meteorological product parameter category 2: momentum 49 Wind Speed Surface Adjusted M/S
Product discipline 0 - Meteorological product parameter category 2: momentum 59 - 191 Reserved
from grib2.
Hello, @marqh @richardweedon and @sebvi
Here is my opinion. A surface adjusted wind speed is still a wind speed. I mean, the parameter or the observed quantity is the same, and therefore there should not be the need to add another entry. However, I understand that there is the need to convey the message to the users that there are two wind products and they are different. Unfortunately, we don't have any element in GRIB2 to express this difference, and therefore I think that we have to accept the compromise and add these extra entries in table 4.2.
I also have another comment. As a user, if I read surface adjusted, I am not sure of the meaning and the aim of the adjustment. I believe that we need a clear description of these elements, without going into the specific process of adjustment which may change in the future, but expressing clearly what is the purpose of the adjustment.
from grib2.
@efucile I thought the way to convey the particularity of these parameters would be the background generating process identifier keys which are freely defined by the data producer.
from grib2.
Apologies all this is out of my comfort zone so please bear with me. I have attempted to summarise a rather long email from my colleagues -
A short explanation is:
10m winds should be virtually identical in the UK models
Single level 10m wind in the global models will be stronger than the 10m multi-level wind, as the former attempts to undo some spurious slower down in wind from overzealous turbulent orographic form drag parametrization.
The aim being -
10m wind is re-derived from the diagnosed surface turbulence to provide a more accurate prediction. This addresses the spurious slowing of the resolved wind profile at low levels that the parametrization of turbulent orographic form drag can introduce in some configurations of the model
from grib2.
@marqh @richardweedon It looks like the conversation is still open and will not be ready for FT22-1. If you need this sooner, then please finalize the proposal within a couple days and I will create a branch.
from grib2.
@marqh @richardweedon @sebvi -- Will this proposal be ready for FT2022-2 before June 8?
from grib2.
to be determined for during another fast-track cycle
from grib2.
https://github.com/wmo-im/CCT/wiki/Teleconference-4.10.2022 meeting notes: not discussed
from grib2.
https://github.com/wmo-im/CCT/wiki/Teleconference-21.11.2022 note: not discussed
from grib2.
Related Issues (20)
- Encoding of Drought indexes as defined by WMO HOT 8
- new ocean and ice parameters in Code Table 4.2, Discipline 10 HOT 10
- new probability templates for large ensemble HOT 9
- new templates for probability forecasts based on focal statistics HOT 8
- new section 4 template for further statistics on probabilities based on focal statistics HOT 6
- new hydrology parameters in code Table 4.2 HOT 4
- new fire weather parameter in Code Table 4.2, Discipline 2 HOT 12
- new precipitation type flag in Code Table 4.201 HOT 9
- Create GH actions to generate machine readable codes HOT 3
- new mixed layer depth parameter in Code Table 4.2, Discipline 10 HOT 5
- Deprecate template 4.44, create rectified version as template 4.50 HOT 8
- Additional Anomalies Templates HOT 10
- Code table 4.9: add an entry to encode a probability based on a quantile distribution instead of based on a threshold HOT 6
- Code table 4.101: new entry in code table 4.101 to extend the usage of templates 4.105, 4.106, 4.107 and 4.112 HOT 3
- Code table 1.4, 4.3 and 4.6: Adding new entries to better describe type of forecasting HOT 6
- Code table 4.2 and 4.238: new source/sink entries in code table 4.238 and a new parameter in code table 4.2, discipline 0, category 20 HOT 7
- Code Table 4.1 and 4.2: new category for thermodynamical properties in discipline "land surface" and associated parameters HOT 10
- new normal and tangential velocity components parameter for Code table 4.2, Discipline 10 HOT 10
- Meteorological and hydrological hazards HOT 2
- New section 4 templates and tables for verification scores HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from grib2.