Comments (12)
I think that it would be better to have a new table also for the parameters in Numeric**** units. We should avoid putting information in the notes. Let's remember that notes are not in the xml or csv format of the tables which is used in by the decoders and are only in the pdf version of the manual.
from grib2.
I am not in favor of using and expanding Code Table Discipline 1, Category 1 . My understanding is that parameters containing "probability of ..." are deprecated in favor of using the Template 4.5,setting type of generating process to "probability forecast", setting the probability type using Code Table 4.9, and then your limits for the probability in the following octets.
This is why I don't think the parameters in discipline 1, category 1 should not be accepted/added, they can already be encoded using the mechanism described above. (Note as well that 2 of your parameters have an entry in the reserved area for local code of the table).
What is the difference between your snow level and discipline 0, category 1, number 11?
For the "presence of ..." parameters, I would change the units to "boolean". What these fields provide is in fact a bitmap.
from grib2.
I should also add that in GRIB3, discipline 1, category has been considered deprecated and has been deleted. I am in the process of committing the tables in the GRIB3 repository.
from grib2.
cc @jbathegit
Thanks @sebvi . I have updated the proposal above by removing probability parameters in lieu of implementing with PDT 4.5, and updated the units of the presence parameters as booleans (per 4.222).
Note also I've changed snow level to parameter number from 36->40 given #25. See the following paper as reference/example of the term "Snow level". We could also name this parameter "Snow level (melting level)" to reduce ambiguity if desired.
from grib2.
@tomkralidis @ypell I have created a branch for this issue, with changes implemented in the table mentioned above. Could you please check it? Thanks.
from grib2.
Thanks @chenxiaoxia2019; in comparing https://github.com/wmo-im/GRIB2/compare/issue-17 to the proposal above, is there any update on the below?
Parameter | Product Discipline | Parameter Category | Parameter number | Units |
---|---|---|---|---|
Thunderstorm intensity index | 0 | 7 (Thermodynamic stability) | 20 | Code table 4.246 proposed new table |
Snow level | 0 | 19 (Physical atmospheric) | 40 | m |
from grib2.
@tomkralidis Hi, Tom. Thanks for your check. The above mentioned parameters have been updated in GRIB2_CodeFlag_4_2_CodeTable_en.csv. Please check it.
from grib2.
Thanks @chenxiaoxia2019 . I see tables 4.246 and 2.247 are non-existent. I updated the proposal above. Can you update the branch with 4.246 and 4.247?
from grib2.
@tomkralidis Hi, Tom, I updated the branch with tables 4.246 and 4.247. Could you please check it? Thanks.
from grib2.
Thanks @chenxiaoxia2019 . Looks good to me. +1.
from grib2.
SUMMARY: Add entries to Code Table 4.2, add Code Tables 4.246 and 4.247
from grib2.
Approved by FT-2020-2.
from grib2.
Related Issues (20)
- 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
- remove date from XML script
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.