The programmers have provided capability to read tidal harmonics, other programmers have written programs to use those harmonics (Rasbats) with a whole string of plugins, UKtides, OTcurrent to name several, others have provided
plugin frameworks for tides, such as AdmiraltyTides, (which I have tried to shepard and support) which requires users to enter the data. (Nobody has bothered to use it because it is too much work I guess.)
Also there is the ability to modify and improve the tidal harmonics and even to load and use different tidal files for different areas that might be better and more accurate. I don't know why users have not been more aggressive about
learning about tides and using the tools available.
No users have dissected and taken the time to publish how these files actually work. No users have really contributed knowledge or means to improve the tides and currents coverage. Some of the tidal plugins have languished because users did not take up the challenge to populate them with data and maintain them. Most of the Tide and
Current tracker requests are asking for greater functionality of some sort (including some of mine).
https://opencpn.org/flyspray/index.p...rom=&closedto=
BTW if someone wants to start a page on the way the tide harmonic file works, I am ready to make you an editor.
As you have noticed, tides are not a terribly high priority for programmers, so long as they are working. I will say there is considerably interest in adding functionality to calculate ETA from A to B including tide/currents, somehow. Rasbats has taken the first try at producing a
plugin that will do this. Those kinds of improvements may be more meaningful and better "programming bang for the buck".
Incidentally, the tracker program just assigned that particular task to me because I help to maintain Tracker, I did not pick it. We don't always use that field anyway, except when it gets up towards the top and is seriously being considered.
So perhaps users need to mount a "Tides and Currents" effort of their own,
learning more about how the actual tidal file works, publishing this information, and perhaps developing alternative files that are better. Also consolidating the list of features needed, discussing their merits, so as to come up with (by consensus) one or two very detailed and specific things that would improve Tide functionality. Then with wide user support, try to get those recognized as important To Do items.
That's my suggestion, raising what I would call a "complaint" is not going to help much, IMHO.
BTW your joint and focused effort with others to improve the icons in OpenCPN was methodical and planned and it has succeeded, making OpenCPN much better for everyone.