Grib Enhancements

[rgleason]

Grib Currents development, Tidetech route optimization on ipad with Weather4D and iNavX

[Taarnskov]

What is the reason for the text on the screen "Please zoom or scale out to view suppressed grib overlay" as can be seen on the screenshot below.

Lars

[bazzer]

Originally Posted by rgleason

Grib Currents development, Tidetech route optimization on ipad with Weather4D and iNavX

I searched for route on inavx, but found nothing, can you help?

[Hakan]

Originally Posted by Taarnskov

What is the reason for the text on the screen "Please zoom or scale out to view suppressed grib overlay" as can be seen on the screenshot below.

Lars

Lars..
It happens if you for any wind, wave etc in the config tab have choose to view a "overlaymap" and the zoom don't cover most of the grib's rectangle. I can't say if this is intentional or just a coincidence.
Håkan

[rgleason]

Grib Currents development, Tidetech route optimization on ipad with Weather4D

searched for route on inavx, but found nothing, can you help?

All I know is this link I don't see it on inavx website but it does say it supports grib and currents, but does not do optimizaton like qtVlm does. -I posted because there seems to be more development in current grib use.

[rgleason]

German Current Gribs bsh.de
Strömungen
Ftp website - (right click, save link as..)
ftp://ftp.bsh.de/Stroemungsvorhersagen/

This website is in the process of converting over use of Grib2
---------

Another Current Grib file from Noaa Atlantic RTOFS
there are many location for these gribs
http://polar.ncep.noaa.gov/ofs/download.shtml?
The one I checked had grib2 files.
ftp://ftpprd.ncep.noaa.gov/pub/data/.../ofs.20130306/

----------
Several Current Gribs have this message or similar and do not display.

This file came from the Expedition website http://www.goflow.com/bbs2010.htm where there is a download of a Current Grib file bbs2010.grb or bbs2010.zip

--------

[rgleason]

Here is a Current Grib file that works. I've found several that can play in the the new enhanced grib plugin by Sean. This plugin enables "play" of a sequence of files and has a configuration setup for setting visible display elements of the various grib files.

The files are
MERCATOR_Currents_Global.grb,
MERCATOR_Currents_Global.grb.bz2
WWe_DIRSW_HTSGW_Whole_domain.grb.bz2,
MERCATOR_Currents_Global.grb.bz2
NCOM_U_V_SSH_Whole_domain.grb.bz2
NCOM_V_SSH_Whole_domain.grb
GLO_rfvl_all.grb
GLO_rfvl_all.grb.bz2

I believe these are from Noaa RFOS website but I can't find where I download them. Perhaps someone else knows.

Two screenshots one with the Config

This is a very nice plugin, I hope eventually it will support more formats including grib2

[rgleason]

Pavel wrote:

This is a different beast, a clone of the whole opencpn source repository, not just the plugin itself...

go to your toplevel OpenCPN source directory and do
git remote add sean git://github.com/seandepagnier/OpenCPN.git

followed by
git fetch --all
git branch -a

will now show that you have more branches available
git checkout sean/grib_enhancements

will then switch (change directory - cd dos) to the branch where the grib plugin is modified. Once in this branch, try to build as normally

Then I followed this:

Go to the plugin subdirectory in your OpenCPN source tree
git clone https://github.com/seandepagnier/cel...igation_pi.git
Build as normally:
cd ..
cd build
cmake ..
cmake --build .

You have to create a subdirectory celestial_navigation\data in your plugin folder and place the following files there:
https://raw.github.com/seandepagnier...%20Basics.html
https://raw.github.com/seandepagnier...ata/IGRF11.COF
https://raw.github.com/seandepagnier...ta/vsop87d.txt

***Actually now these are found in the Plugins directory, but they must reside (you must copy them) in the appropriate Opencpn program directory for the plugin to work. ...More on that later.

And I have been doing the following to compile other plugins:

Go to the plugin subdirectory in your OpenCPN source tree
git clone git://github.com/seandepagnier/weatherfax_pi.git
Build as normally:
cd ..
cd build
cmake ..
cmake --build .

Go to the plugin subdirectory in your OpenCPN source tree
git clone https://github.com/seandepagnier/cel...igation_pi.git
Build as normally:
cd ..
cd build
cmake ..
cmake --build .

Now to update to Opencpn 3.2 what do I do?

git fetch --all
git branch -a
Then what should it be?

git checkout origin/HEAD
git checkout origin/beta31_stable
git checkout origin/master

Then switch (change directory -dos cd) to the branch where the grib plugin is modified. Once in this branch, try to build as normal

Tried the following from opencpn-git/build directory:

git checkout origin/beta31_stable and reply was "Previous HEAD position was 4f66ac7... Merge remote branch 'upstream/master' into HEAD is now at 2532d4d... Merge branch 'master' into beta31_stable.

Is this correct branch or should it be origin/master?

If it is the correct one, do I then just go to MS VC+++ and compile normally or do I have to issue a git fetch -all command again?

If it is not the correct one, do I just issue a
git checkout origin/master
and then compile normally?

Thanks very much.

[rgleason]

Tried compiling with MS VC++ it was still Opencpn 3.1.1417

Then issued from ...opencpn-git/ directory

git branch -a

which lists various branches available.

git checkout origin/master

reply "Previous HEAD position was 2532d4d... Merge branch 'master' into beta31_stable HEAD is now at 36c7f6a... Move manuall pictures to images folder to avoid the problems caused by spaces"

Compile with MS VC++ Release version.

Prompts for certain files that are different.
Reload from disk? Yes or Ignore? Hit ignore this time.

Compile with MS VC++ Debug version.

Came up with Opencpn Version 3.2.0

Checking opencpn-git/plugins directory, the grib_enhancements_pi directory seems to be gone but the other plugins celestial_navigation_pi and weatherfax_pi are there. I guess I just git that again.

[rgleason]

Now trying to git clone grib_enhancements_pi
Issued

git fetch --all
git branch -a
git checkout sean/grib_enhancements_pi
git clone git"//github.com/seanpagnier/grib_enhancements_pi.git

...responds "Cloning into grib_enhancements_pi ..
fatal remote error: Repository not found.

So it failed and there is no opencpn-git/plugins/grib_enhancements_pi directory available to build.

Tried several other commands, did not work.
Any ideas?

Should I git branch delete sean/grib_enhancements_pi?
and start over.

[nohal]

rgleason...
There's no repository for these enhancements - you got it right at the beginning of http://www.cruisersforum.com/forums/...ml#post1178702 - you have to take Sean's OpenCPN repo and switch to the right branch...

Pavel

[cagney]

I downloaded the latest grib code and tried a rtofs current grib from saildocs. The direction arrows are hardly visible. Is there anything to do about that?



Thomas

[seandepagnier]

That screenshot is not my enhanced plugin. There is not a timeline. Did you switch to the right branch?

[cagney]

Originally Posted by boat_alexandra

That screenshot is not my enhanced plugin. There is not a timeline. Did you switch to the right branch?

I just forgot to "make install", to overwrite the normal plugin version with your version.


This is a much better display. Current directions needs adjusting 180, though. The current arrows seems to be treated like wind arrows, but a currents direction is where it's heading, not where it's coming from.


Thomas

[seandepagnier]

Originally Posted by cagney

I just forgot to "make install", to overwrite the normal plugin version with your version.
Attachment 57013

This is a much better display. Current directions needs adjusting 180, though. The current arrows seems to be treated like wind arrows, but a currents direction is where it's heading, not where it's coming from.


Thomas

So, should the fixed arrows be flipped 180 for all cases, (wind swell and current) and the barbed arrows stay the same? I find that both arrows point the same way right now, and this seems correct as the wind barbs also point in the direction the wind is going, so in all cases the arrows point in the direction the data is going.