pi - Grib

This is the Bug Report, Feature Request and Patch tracker for the GRIB plugin.

FS#562 - Data Support Fails to load US Navy significant wave height GRIBs

Attached to Project: pi - Grib
Opened by Hamish B (HamishB) - Saturday, 25 June 2011, 23:26 GMT-7
Last edited by Rick Gleason (rgleason) - Tuesday, 17 September 2013, 07:20 GMT-7
Task Type Feature Request
Category Backend / Core
Status Assigned
Assigned To Dave (bdbcat)
Operating System Linux
Severity Medium
Priority Normal
Reported Version future version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No



the US Navy publishes several weather model outputs in GRIB format for general consumption. for example,

waves: peak_wav_dir, peak_wav_per, sig_wav_ht
winds (@10m): wnd_ucmp, wnd_vcmp

wget "ftp://usgodae.org/pub/outgoing/fnmoc/models/ww3/2011/2011062600/$FILE"

ln -s "$FILE" hsig_latest.grb

then in the grib plugin window browse to that dir, select the file, select the forecast time (one option), sig. wave height value shows reasonable values in the grib plugin window as I cursor around the chart. At the same time I notice these messages in the console:

(opencpn:6962): Gdk-CRITICAL **: gdk_drawable_get_image: assertion `GDK_IS_DRAWABLE (drawable)' failed
(opencpn:6962): Gdk-CRITICAL **: gdk_image_get_colormap: assertion `GDK_IS_IMAGE (image)' failed
(opencpn:6962): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

but otherwise the wave height values seem ok.

However, if I zoom out a little it quickly kills opencpn & returns me to the command prompt with this error message:

The program 'opencpn' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 54688 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

tested with 2.4.620 on debian/stable amd64, debiangis build rules.

This task depends upon

Comment by Hamish B (HamishB) - Saturday, 25 June 2011, 23:34 GMT-7
starting with "opencpn --sync", it errors out as soon as I select the time from within the grib file.
Comment by Jean Pierre (ptizef) - Monday, 24 February 2014, 07:59 GMT-7
Is this task still valid ?
The links above lead to two years old files
And do these file give more information than the well known WW3 files from zyGrib and/or Saildocs?
Jean Pierre