Bug 257781 New: Review Request: cnvgrib - GRIB1 GRIB2 conversion Bug 257781 New: Review Request: cnvgrib - GRIB1 GRIB2 conversion utility. From: bugzilla redhat com. To: fedora-package-review redhat com. Subject: Bug 257781 New: Review Request: cnvgrib - GRIB1 GRIB2 conversion utility.
Date: Mon, 27 Aug 2007 15:40:01 -0400 Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: cnvgrib - GRIB1 GRIB2 conversion utility Product: Fedora Version: devel Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: medium Component: Package Review AssignedTo: nobody fedoraproject org ReportedBy: pertusus free fr QAContact: extras-qa fedoraproject org CC: fedora-package-review redhat com,notting redhat com Spec URL: SRPM URL: Description: This command line utility program converts every GRIB message in the input file from one GRIB edition to another. It currently converts GRIB1 to GRIB2, and GRIB2 to GRIB1 using WMO master tables as well as various NCEP local tables.
Configure bugmail: - You are receiving this mail because: - You are on the CC list for the bug, or are watching someone who is. Follow-Ups:. From: bugzilla.
Raw Message Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: cnvgrib - GRIB1 GRIB2 conversion utility Product: Fedora Version: devel Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: medium Component: Package Review AssignedTo: nobody at fedoraproject.org ReportedBy: pertusus at free.fr QAContact: extras-qa at fedoraproject.org CC: fedora-package-review at redhat.com,notting at redhat.com Spec URL: SRPM URL: Description: This command line utility program converts every GRIB message in the input file from one GRIB edition to another. It currently converts GRIB1 to GRIB2, and GRIB2 to GRIB1 using WMO master tables as well as various NCEP local tables. Raw Message Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
Bug 257781 depends on bug 257701, which changed state. Bug 257701 Summary: Review Request: w3lib - GRIB1 encoder/decoder and search/indexing routines What Old Value New Value - Status ASSIGNED CLOSED Resolution NEXTRELEASE. Raw Message Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Patrice Dumas changed: What Removed Added - Status NEW CLOSED Resolution WONTFIX - Comment #2 from Patrice Dumas 2009-03-02 09:00:50 EDT - I have left fedora, so the best is certainly to close that submission. Raw Message Please do not reply directly to this email.
All additional comments should be made in the comments box of this bug. Bug 257781 depends on bug 257761, which changed state.
Bug 257761 Summary: Review Request: g2lib - GRIB2 encoder/decoder and search/indexing routines What Old Value New Value - Status ASSIGNED CLOSED Resolution WONTFIX.
Note: An older version of this information is available under the Documentation Tab of both and as. This page is maintained and should be considered the definitive version.
We get this question often from users setting up their data workflow, particularly for datasets for which the data translation option, 'Get Converted Files' is available. Data Access Matrix for ds083.2, which is available in its native GRIB1 and GRIB2 formats or translated to NetCDF. If you want data translation to NetCDF, click on the options circled in red. The answer (or non answer) is it depends upon which dataset you want to use (and dates within the series) and which tool(s) you will use to analyze the data. Is a World Meteorological Organization (WMO) international standard for exchanging GRidded BInary or General Regularly-distributed Information in Binary form data. Is the older format.
Improves upon the standard with the same compression software commonly used for images to gain a roughly 50% reduction in file size over GRIB1. Recently, version 2 of GRIB2 was released. It uses a slightly less aggressive form of compression, which leads to about 10% larger files than the first version of GRIB2, but decompresses about 10x faster. Is another binary format in common use in the weather and climate community. All three claim to be self-describing in the sense that the files tell you whats in that particular file.
GRIB1 descriptors are short and can be very cryptic. GRIB2 is slightly better, with longer self-descriptions. However, GRIB files in general depend on external tables referred to as to explain the details of the file contents. NetCDF file metadata tends to be more complete and descriptive. You can perform many data processing tasks on GRIB files with (for GRIB1) and (for GRIB2).
You can process and visualize GRIB files with (NCAR Command Language), (Climate Data Operators), (Interactive Data Language), (with or ), and (using the package) You can use the extensive if you convert the files to NetCDF. However, be mindful that NetCDF files are not as compact as GRIB2, even when compressed. A 15 MB GRIB2 FNL ds083.2 file from 2014 can be 30 MB if translated to GRIB1 (an option we no longer support) or 86 MB in NetCDF format. Even with gzip compression, the GRIB1 and NetCDF files are 24 and 31 MB respectively. Read for details.
Select your files, then click 'View Selected Files/Convert to NetCDF.' When the pop-up window appears, click on 'Request converting format to NetCDF for selected files.'
In summary, try to store and use the data in it's native format. This is not an endorsement of any given data format because there are shortcomings and strengths to all of them (but not with the same ratio). If you want a partisan but fair critique, I recommend John Caron's discussion,. But, if you are already familiar with data tools for a different data format such as NetCDF, and you have the bandwidth to handle the larger file size, then go ahead and translate it. You decide the tradeoff between download time and your learning time.
If you are going to work with weather and climate data, then you will need to learn how to play with GRIB. You will probably also need to learn to play with NetCDF and HDF5.
Digital To Analog Tv Converter Box
Stay tuned for our series about how to get started with GRIB and then NetCDF4/HDF5.
Bug 257781 Review Request: cnvgrib - GRIB1 GRIB2 conversion utili Thread Next Bug 257781 Review Request: cnvgrib - GRIB1 GRIB2 conversion utility. From: bugzilla redhat com. To: fedora-package-review redhat com.
Subject: Bug 257781 Review Request: cnvgrib - GRIB1 GRIB2 conversion utility. Date: Mon, 2 Mar 2009 09:00:09 -0500 Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Bug 257781 depends on bug 257761, which changed state. Bug 257761 Summary: Review Request: g2lib - GRIB2 encoder/decoder and search/indexing routines What Old Value New Value - Status ASSIGNED CLOSED Resolution WONTFIX - Configure bugmail: - You are receiving this mail because: - You are on the CC list for the bug.
Thread Next.
There is a separate for questions related to the installation of gribapi. What are namespaces? A namespace in GRIB API is just a fancy word for a grouping of related keys.
The following are available:. ls: This is the namespace used by the tool and has the most-commonly used keys e.g. Centre, shortName, level etc. parameter: Contains keys like paramId, shortName, units which relate to the meteorological parameter. statistics: Contains keys that relate to the statistics of the data values e.g.
Maximum, minimum, average, standard deviation etc. time: Contains keys that describe the forecast runs e.g. Forecast date, validity date, steps etc.
geography: Contains keys that describe the grid geometry e.g. Bounding box of the grid, number of points along a parallel etc. vertical: Contains keys that describe the levels and layers e.g. Type of the level, list of coefficients of the vertical coordinate etc. mars: Contains the list of MARS (ECMWF's Meteorological Archive and Retrieval System) keywords like class, stream, type etc Why am I not able to set the missing value in the GRIB message? Missing values cannot be encoded in a GRIB message. The GRIB format does keep track of missing values but through the use of a bitmap It does not allow the specification of a missing value.
Setting the missing value is a feature that can be used only when reading the data values stored in a GRIB message. This of course means that is the responsibility of the user to know what missing value is meaningful to the data being read. A default value of 9999 is set for the missing value in the library (not the GRIB message!). That means that when retrieving the values from a message without having set the missing value key, all missing values in the data will be replaced with the default value of 9999. A small example on the use of the missing value during encoding can be found here:. During decoding it is advisable to query the bitmap directly to discover missing data values. See example here: How do I append messages to an existing GRIB file?
Try using gribopenfile (Fortran interface) with mode 'a' instead of 'w'. The 'a' mode means: Append to a file. Writing operations append data at the end of the file. The file is created if it does not exist. How do I copy a selected number of messages from a GRIB file? Say you want to copy the first 3 messages. This can be done with:% gribcopy -w count=1/2/3 in.grib out.grib But it is better to write a rules file and use gribfilter.
The use of the multi-field feature is not recommended. Why can I read certain parameters using the grib tools, but not from my program? Your file may be encoded as a multi-field grib file.
By default, grib tools have multi-field support enabled and the API disabled. Check the examples to know how to enable this feature on your program:. For Fortran77:. For Fortran90:. For C: Confused about stepUnits?
The key stepUnits is a transient key and it is not written in the grib message. So, you cannot expect to get the same stepUnits as when you have encoded the data.
By convention, when encoding, GRIB API will choose the best unit to encode the step in so that it fits the space available in the grib message. When decoding, GRIB API will return the step in hours by default. The stepUnits can only be set in the following situations:. before encoding, in order to tell GRIB API what units are we dealing with. when decoding, in order to tell GRIB API what units to get the step in Examples. % gribls -s stepUnits='m' -p startStep,endStep,stepRange,stepUnits:s,stepType out.grib Confused about key types?
Some keys like shortName are strings (native type string) and it doesn't make any sense to set them as an integer or float as they are not possible values for the key. Some keys are native type integer like number and you can set/get them as integer, float or string as you like. Some keys are codetables and for them you have a code (integer) and an abbreviation (string) like for example 'centre'. You can set them as a string or as an integer, not as a float because there is no mapping for those keys into a float. An example is.
Discipline 0 parameterCategory 7 parameterNumber 6 typeOfFirstFixedSurface 1 typeOfSecondFixedSurface 8 in the grib and there isn't a better match of keys in the list. Again saying shortName=123 doesn't make any sense as in the context of shortName we don't need numbers. The idea is that the user should know what to set before choosing the type to use. In the sense that the user should know the meaning of the key before setting it to a value.
Shareware and freeware software. Results 1 - 48 of 1736. Socrates Estate Planner Library Manual and Forms on CD new sealed. Free shipping. Ending Today at 3:44PM PST23h 43m. Keep your kids safe online with parental controls: block web sites and search results, plus limit how much time they spend online. Brand: McAfee. Authormyibay eBay bid sniper. Platform Win 98/Vista/2000/2003/XP. CategoryUtilities - System Utilities. USB Drive Blocker download. Usb drive blocker software helps to how to. USB port blocker program protects or lock. Windows data recovery software. Aug 11, 2017. Once you're out of school, finding friends and spending time with themfalls by the wayside to work, family, and other obligations. So, tell us, how did you stumble. Express Helpline- Get answer of your question fast from real experts. You have not yet voted on this site! If you have already visited the site,. Results 1 - 48 of 15330. H&R Block Premium 2017 Federal & State Tax Software for Windows & Mac. Five free federal e-Files and unlimited federal preparation and printing. Compatible Platform(s): Mac, Windows. One state download. Expert Service. Unbeatable Price. Brand: Intuit. Free shipping.
At this purpose we have built the documentation and I agree that we need to do a big review (with your help) of it to fix all the wrong things and to add what is missing. There was a bit of confusion regarding the type of step and paramId for the following reason: step For me step was a string because you can have values like 24-36 which you cannot represent as numbers. In mars the step is only the endStep and therefore I had to modify gribapi to be mars compliant. Now the step is an integer and is step=endStep. As we need a step indicating a range I have introduced stepRange which is a string and cannot be set as an integer and will never be set as an integer because it allows values like stepRange=24-36. It is true that most of the time you have stepRange=36 or stepRange=24 or another single number, but this is because in those cases you have also stepType=instant and endStep=startStep and we don't want to write stepRange=24-24 which is only redundant.
We also use to write stepRange=24 when stepRange=0-24 (mars compatibility which I don't like). If you prefer to set the step as an integer instead of using a string you have starStep, endStep which are integers and they can also be set as string because it is possible to convert for example the number 24 into the string '24'. Therefore you can do. % gribset -s endStep=24 in out% gribset -s endStep:s=24 in out paramId It is a concept like shortName and unfortunately in the previous version the native type for a concept was string even if the meaning of it is number. In the new version paramId is still a concept, but it has native type number. This means that it can be set as a number, but cannot be set as a string because only the numbers are valid values for paramId. It can still be get as a string because it is possible to convert a number into a string.
You cannot set as a string because it isn't always possible to convert a string into a number. Why I cannot set negative values for the longitude in GRIB 2 GRIB 1 regulates that the longitude can be in either -180, 180 or 0,360, GRIB 2 regulates that the longitude can only be in the interval 0,360. GRIB API does comply with these regulations and in the case of GRIB 2, it will scale the longitude to fall in the interval 0,360. GRIB API does not offer an edition independent view of the longitude because of the uncertainty brought by GRIB 1, where you do not know what interval a longitude is in exactly. For GRIB edition 1, why does the centre change when I set stepType? This happens for stepType of 'max' and 'min'.
Unfortunately edition 1 does not support maximum and minimum in its 'Time Range Indicator' table (Table 5). So we invented our own centre-specific combination to support this. There is no such issue in GRIB edition 2. Why is the 'bottomLevel' of Soil Temperature level 4 reported as MISSING?
The parameter 236 (Soil temperature level 4) specifies that its top level is 100cm and its bottom level is 289cm so to encode this information in GRIB edition 1 we would need to set the value of the key 'bottomLevel' to 289 (octet 12 in section 1. However since this key is only one octet it cannot accommodate any value larger than 255!
Therefore it is not possible to encode levels larger than that value in GRIB1 so we simply set all the bits to 1 (which means MISSING). GRIB edition 2 addresses this shortcoming. Possible GOTCHA with wave spectra fields Courtesy of I've just been investigating an issue with the decoding of the wave spectra fields with the new default version of GRIB API (version 1.9.16). I want to make you all aware of this in case any of your users hit the same problem. In the wave spectra, all frequency/direction components with values less than some (field-dependent) threshold are set to 'missing' when encoded in GRIB; values larger than this threshold are encoded as log10 of the actual value to an accuracy of 9 bits (bitsPerValue=9). % gribcompare file1.grib1 file2.grib1 long binaryScaleFactor: -4!= -11 double referenceValue: -1.e+03!= -1.e+01 absolute diff.
= 1206.73, relative diff. = 0.98961 tolerance=0.000244141 long N: 2694!= 1958 long P: 1385!= 712 double values: 4139 out of 4160 different max absolute diff.
= 9.617188e+01, relative diff. = 0.319192 max diff. Element 0: 1.e+02 2.e+02 tolerance=0.000000e+00 packingError: 0.0313721 0.000244617% gribcompare -bbinaryScaleFactor,referenceValue,N,P file1.grib1 file2.grib1 double values: 4139 out of 4160 different max absolute diff. = 3.000000e+04, relative diff.
= 0.711452 max diff. Element 78: 1.e+04 5.e+04 tolerance=0.000000e+00 packingError: 0.5 0.5 You can see when we used the blacklist, the results reported are different! This is because these keys are used to decode the values and blacklisting them causes the differences. In these situations it is best to include what you want to compare rather than exclude with a blacklist.
% gribcompare -c values file1.grib1 file2.grib1 Now only the values array is compared. Now you can use the -P, -R and -A flags to control the tolerances. What are the keys numberOfDataPoints, numberOfValues and numberOfMissing? NumberOfDataPoints: This is the total number of points on the grid and includes missing as well as 'real' values numberOfValues (=numberOfCodedValues): These two keys are the same (one is an alias for the other). This is the number of 'real' values in the field and excludes the number of missing ones numberOfMissing: You guessed it. The number of missing values in the field So you can write the equation: numberOfDataPoints = numberOfCodedValues + numberOfMissing How can I multiply the field values by a constant?
One way is to use gribset with the key 'scaleValuesBy'. Let's say you have a field in orig.grib whose values you want to multiply by 2.1. First check the original data value statistics. % gribls -p min,max,avg out.grib min max avg 492.563 655.376 585.853 For adding or subtracting a constant, you can use the key 'offsetValuesBy'.
Configure script: What features are enabled/disabled by default? First do a./configure -help which will list the features available to be turned off/on. If a feature is turned off by default, then its prefix is '-enable-' and if it is turned on by default, then its prefix is '-disable-'. So for example if the help text shows '-enable-python' you know it is disabled by default (i.e. If you do not pass this option to configure you will not get python support). Similarly if the help text shows '-disable-fortran' you know Fortran support is enabled by default.
Is GRIB-API thread-safe? GRIB API is not thread-safe by default, unless it is built with pthread support. To do so, you need to make sure that the option '-enable-pthread' is present in your configure command (Note: there are known thread safety issues when multi-field support is enabled). For CMake, use the option: -DENABLEGRIBTHREADS=ON Building on High Performance Computer systems Some HPC batch systems have a different hardware architecture for their login (or frontend node) to the batch node, but the frontend compilation system is targeted at the batch nodes.
This is known as cross-compilation. If this is the case you may see failures in the 'make check' stage because the checks, although compiled for the backend batch nodes, are being run on the frontend nodes and therefore may not work correctly.
If this is the case on your system, we recommend using a batch job to do the 'configure; make; make check; make install' steps. In some cases, the batch system cannot be used for compilation at all. In this case, you have to compile on the frontend but without extra flags 'configure' will assume the build is for the frontend. You can make use of the -host option to ensure the build is correct for the architecture of the batch system. Again though, the tests will fail, a small serial batch job is recommended to make sure gribapi is installed correctly.
Note if you plan on using the gribapi software in your own software that runs on the frontend nodes you will need to install gribapi twice; one for the batch system and again for the frontend system. If you have any questions installing gribapi in this type of environment, please contact: for assistance. How do I create my own local definitions? See the slides in this Where can I find the version history?
Feature Requests. How can I get the number of grib messages from my index selection?
(usw) maybe something like gribindexgetselectedmessagessize(index, &numselectedmessages);. Can a C-version of the gribgetdata function be implemented?
(usw) Iterating over geo-referenced values in a grib file can be done in the C interface by using the 'gribiterator'. Mosin nagant history by serial number. There is also a 'gribgetdata' present, but not documented.
What it basically does is to use an iterator to return ALL geo-referenced values in an input array. Prototype for that is. Int gribgetdata(gribhandle.
h,double. lats, double. lons,double.
values,sizet. size);. Can we have function to de-select a selection from an index? (usw). Can we implement the '-i index' option in gribget (as in gribls)?
(usd) DONE. Can we make 'gribcopy -p key' actually print something without needing the -v option?
(usd). Can gribgetdata print the correct latitude and longitude values for rotated grids? (usd) DONE. Can we have more documentation about the namespaces (e.g., statistics, mars, ls)? Look further up in this FAQ.
Can we have more documentation about the computed keys (distinctLatitudes, distinctLongitudes, etc)?
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |