All:
I’m not on the gdal-dev@lists.osgeo.org mailing list, so I can not report this here. NOAA/NCEP is producing new hourly CONUS NEXRAD radar-based meteorological data – my interest is precipitation. The data is available now via a UCAR LDM process, described in the 1st link. The problem is (using the downloadable sample data), gdal recognizes the data files as grib2, but it will not decode the data (I have not previously had any problems). The Google docs file states that there is an issue and points to an updated wgrib2 that can handle the grib2 decoding (which it does) – the second link.
wgrib2 v0.2.0.1 7/2014 Wesley Ebisuzaki, Reinoud Bokhorst, Jaakko Hyvätti, Dusan Jovic, Kristian Nilssen, Karl Pfeiffer, Pablo Romero, Manfred Schwarb, Arlindo da Silva, Niklas Sondell, Sergey Varlamov
https://docs.google.com/document/d/1LeVcn_taIXZgzZb5JgWqaVr0xVs7GmA6RpHcb8ZGiwk/edit
http://www.cpc.noaa.gov/products/wesley/wgrib2/
When I used wgrib2 to produce a binary file, I could then import the example data file into GRASS:
r.info map=MRMS_GaugeCorr_QPE_01H_00.00_20141208_120000@teaiii
±---------------------------------------------------------------------------+
| Map: MRMS_GaugeCorr_QPE_01H_00.00_ Date: Mon Jan 19 20:36:05 2015 |
| Mapset: teaiii Login of Creator: teaiii |
| Location: world_location |
| DataBase: /home/teaiii/grass/data |
| Title: ( MRMS_GaugeCorr_QPE_01H_00.00_20141208-120000 ) |
| Timestamp: none |
|---|
| Type of Map: raster Number of Categories: 0 |
| Data Type: FCELL |
| Rows: 3500 |
| Columns: 7000 |
| Total Cells: 24500000 |
| Projection: Latitude-Longitude |
| N: 55N S: 20N Res: 0:00:36 |
| E: 60W W: 130W Res: 0:00:36 |
| Range of data: min = 0 max = 210.5 |
| Data Description: |
| generated by r.in.bin |
| Comments: |
| r.in.bin -f input="/home/teaiii/Downloads/MRMS_GRIB2_SAMPLE-precip/t\ |
| est.bin" output=“MRMS_GaugeCorr_QPE_01H_00.00_20141208-120000” bytes\ |
| =4 header=8 bands=1 order=“native” north=55 south=20 east=-60 west=-\ |
| 130 rows=3500 cols=7000 anull=-3 flip=“v” |
| ±---------------------------------------------------------------------------+ |
So, I thought the community would be interested in (1) knowing about the data and (2) the GRASS/gdal decoding issue.
Cheers!
Tom