[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: River Forecasting Center FMRC Aggregations

On 8/1/2012 8:01 PM, David Blodgett wrote:
Hi John,

We are trying to figure out what's up with the RFC aggregations. Jordan already sent you one note.

I followed a link to display this: http://motherlode.ucar.edu:9080/thredds/catalog/grib/NPVU/RFC/KMSR-North-Central-RFC/files/catalog.html?dataset=grib/NPVU/RFC/files/KMSR/NPVU_RFC_KMSR_NWS_152_20120730.grib1 in the toolsUI (the link at the bottom of the dataset page.

That brought me into a thredds catalog chooser tab showing four grib1 datasets that are not listed in the root catalog from 7/30, 7/31, 8/01, and 8/02.

I dug in and found that http://motherlode.ucar.edu:9080/thredds/dodsC/grib/NPVU/RFC/files/KMSR/NPVU_RFC_KMSR_NWS_152_20120802.grib1 exists, but is not listed in the catalog and is not included in the FMRC aggregation.

We've got some beach water quality monitoring folks who REALLY want this data to work reliably to drive models that predict beach closures so… we're getting some pressure to get things working again.

Any ideas?

Thanks!

Dave Blodgett
Ok, so what happened is that on 7/30 the GRIB files started showing up with a slightly shifted grid. All the records that use that new grid are now in a group called

RFC/PolarStereographic_350X450 (Center 43.70N 93.40W)

which you can see from this catalog:

My diagnostics show:

compare gds1 - gds22
 Start x diff : 2.355558
 Start y diff : 2.421718
 End x diff : 2.355558
 End y diff : 2.421718
 Center lon diff : 0.031485
 Center lat diff : 0.015480

so apparently it shifted 2.3 km in both x and y direction.

I can "fix" this by telling the server to ignore this shift. Is that what you want? If so, which grid (old or new) do you want to use? I assume that going forward it will be on the new grid, but perhaps you can find out if the shift is real or a bug.

PS:

We are running released versions of TDS 4.3 on motherlode.ucar.edu:8081, and development testing on 9080. So i would recommend that you move to 8081  server for now. We will eventually mover 4.3 onto the "production" server on port 8080, and you will want to move again when that happens.