Originally Posted by rgleason
What are those columns that you'd like?
Also do you find the Tree view for Gribs useful, or would it be okay to just have a drop down selector with a button to browse to a new directory?
In principle I could do without the GRIB Control Dialog at all. Anyway, it might start as minimized, always selectiing the first (or closest to current
time) GRIB record
from the newest file in the configured directory.
I usually view the GRIB data as tabular columns in the Route Properties, and I view the GRIB chart by selecting a waypoint in the waypoints list for the route. The "Sync to Route" feature then ensures that GRIB barbs shown correspond to the ETA of the selected waypoint. I can step waypoint-by-waypoint to examine the situation.
This is usally more convenient than stepping through GRIB records via GRIB Control, but not always.
Please note that this is still the Route Properties Dialog, so it does center the chart on selected waypoint, and continuously adjusts everything properly for the Active Route...
What columns to include? Generally - as few as possible, to minimize space taken by the dialog. I think this means what I have now:
- waypoint name
- leg distance
- ETA (including daylight status)
- Nearest tide event, if tides enabled
- Speed for the leg
- Wind forecast
for next leg (including point-of-sail info)
- Sea current
for next leg (with drift effect info), if enabled
Drift column includes 4 values:
- sea current speed in knots
- sea current direction
- net speed effect on boat
in knots (+ or -) along route leg
- net set effect on boat's course (e.g. if boat
speed=0, this equals sea current direction)
whatever is available next is nice to have:
- precipitation (if not shown on GRIB chart as shading)
- sea state forecast
for next leg
If I would program this again today, I would consider the following improvements:
- I would extend dayligt status info to include moon phase
- I would display tide status as relative e.g. HW+3 or LW-1, instead of giving time of nearest HW or LW
- maybe I would show the speed for next leg, instead of speed for past leg
- maybe I would change the method of calculation for sea current effect
I attach another example, showing use of combined wind
and sea current GRIB (from a previous test version).
For long distance planning, I could do with 12 static monthly wind and sea current GRIBS, with data just as in the pilot charts
To view precipitation properly, I have now to use Ugrib...
Good luck in your work!