Grib Enhancements

[Littlechay]

Originally Posted by rgleason

Jean Pierre re Littlechay above, in the Tracker, see FS#1237 - UI Wind barbs/feathers in Knots only as is standard for other programs. Also http://weather.rap.ucar.edu/info/about_windbarb.html PS Jean Pierre, you should also be able to change status for Tracker, grib items. I changed to the FS#1237, 993, 1220 to implemented in current beta.

No Rick,

We are talking about the points, not the feathers that show wind strength. The arrows should have feathers and not points

[Ptizef]

Originally Posted by Littlechay

No Rick,

We are talking about the points, not the feathers that show wind strength. The arrows should have feathers and not points

Is the shot attached better ?
very easy to correct if every body agree
Jean Pierre

[CarCode]

No, please let it the way as zyGrib shows them also.

Gerhard

[Littlechay]

Originally Posted by Ptizef

Is the shot attached better ?
very easy to correct if every body agree
Jean Pierre

Perfect, now we are all showing the same information in the same way. Attached some screen grabs from other programmes and a definition from NOAA

[Littlechay]

Originally Posted by CarCode

No, please let it the way as zyGrib shows them also.

Gerhard

I disagree Gerhard, ZyGrib shows wind as arrows that look more like current arrows with out any feathers indicating wind strength, or conventionally as shafts and wind strength barbs.. see previous post comparing some different programmes.

If you want points on your arrows I suggest it's left as an option, but it's not correct.

Chris

[CarCode]

Originally Posted by Littlechay

I disagree Gerhard, ZyGrib shows wind as arrows that look more like current arrows with out any feathers indicating wind strength, or conventionally as shafts and wind strength barbs.. see previous post comparing some different programmes.

If you want points on your arrows I suggest it's left as an option, but it's not correct.

Chris

Chris,
of course you can change the display of zyGrib as you want. But the default setting is like the attached pic here. And if you want to change the display until it's not readable anymore you might do that. But I don't. So please respect other people.
Gerhard

[rgleason]

No Rick,

We are talking about the points, not the feathers that show wind strength. The arrows should have feathers and not points

Not to put to fine a point on it, but that is what I thought I was saying. I think Jean Pierre has been very quick and cooperative, and I do not think it is necessary to get too torqued up about this. The data is there and looks great and I can read it easily!!!

Thank you Jean Pierre.

Also Littlechay, carcode an others for pointing these items out.

[Littlechay]

Originally Posted by CarCode

Chris,
of course you can change the display of zyGrib as you want. But the default setting is like the attached pic here. And if you want to change the display until it's not readable anymore you might do that. But I don't. So please respect other people.
Gerhard

If you want to clutter your screen with the unnecessary then please do but also give those of us who want a standard, uncluttered, and clean look to have that option too please.

So please respect other people!

[Littlechay]

Originally Posted by rgleason

Not to put to fine a point on it, but that is what I thought I was saying. I think Jean Pierre has been very quick and cooperative, and I do not think it is necessary to get too torqued up about this. The data is there and looks great and I can read it easily!!!

Thank you Jean Pierre.

Also Littlechay, carcode an others for pointing these items out.

Sorry Rick, I thought you were referring to the tracker that you quoted that was for the knots v m/s thing.

Yes Jean Pierre has been very responsive. Thank you for that.

I hope that there can be an option to have the arrows as international standard at least. Those who want the clutter of bells and whistles on their arrows can have their option too I guess.

Chris

[rgleason]

OpenCPN generally tries to stay simple without unnecessary options, because they require more cpu, lookup etc, but with Gribs which already has a large set of user selectable parameters, Jean Pierre may make it an option in preferences, if enough people want it and he agrees to do so.

Suggestion: Sooo people who are interested in this detail could post in Tracker Grib_pi project, with proposed user options for grib arrow/feather display, and then get users to VOTE for the change in Tracker. I am sure Jean Pierre will listen. There's no need to get too concerned about this, it can be adjusted, there are other things we need to figure out that are more important...

such as Keyboard Shortcuts and Macros....touch screens, etc.

[rgleason]

Found the Plugin API and Plugin version number designations in
grib_pi.h (towards the top) in ...\opencpn-git\plugins\grib_pi\src

Accordingly the Plugin Version 2.2 and Plugin API 1.7

HOWEVER, I THOUGHT THIS PLUGIN's API WAS SUPPOSED TO BE 1.8!!!
Can someone who knows please advise? Perhaps the API # should be changed??

From the Developers Manual
Different Plugin API Versions | Official OpenCPN Homepage

Plugin (pi) API Versions and OpenCPN Version Compatibility

pi18 (1.8) = OpenCPN 3.0
pi19 (1.9) = OpenCPN 3.2
pi110 (1.10) = OpenCPN 3.3.x (under design and development now).
pi110 (1.10) = OpenCPN 3.4

I would be surprized if the current grib ran in Opencpn 3.0!!!
So, I would guess that it is actually a higher number than API 1.8.
Will someone knowledgeable please advise?

So we name the plugin properly...
grib_pi_win32_pi17 (??) _v22_ov331117.dll

==

#define PLUGIN_VERSION_MAJOR 2
#define PLUGIN_VERSION_MINOR 2

#define MY_API_VERSION_MAJOR 1
#define MY_API_VERSION_MINOR 7

[nohal]

Rick...
As you can easily confirm at https://github.com/OpenCPN/OpenCPN/b.../grib_pi.h#L58 - The API level needed really should be 1.7. I didn't try if there's something else that could cause problems though...

Pavel

[rgleason]

Pavel, should have thought of that too, but I had just git pulled, so it was the same.... Thanks for the response...

Howver I'll go out on a limb here and challenge the current plugin to run on OpenCPN 2.5, 2.6 or whatever and will probably not run on Opencpn 3.0 eitherr !

Wouldn't that make it a later API?

Or should I just label it gib_pi_win32_pi17_v22_ov331117.dll?

Thanks

[nohal]

Rick...
You can try, but remeber that you have to build the plugin against the old core codebase to give it a chance to run with the old versions. We are just forward binary compatible, not backward...

Pavel

[Aikiguy]

Sorry a tiny bit off of topic here, but how do I get on the beta for opencpn and plugins. Would love to be able to add to this particular thread by doing some testing...

Thanks,
Guy
:-)