The data refresh available from https://flaterco.com/xtide/files.html#harmonicsfiles includes routine updates and corrections. Please note that the SQL dump now includes the database creation commands, and it is no longer necessary or advisable to createdb harmbase2 before loading it.
A corresponding update of the harmonic constants management package is available from https://flaterco.com/xtide/files.html#experts.
XTide 2.15.5 restored compatibility with recent gpsd. XTide 2.15.4 fixed a FTB with libXaw 1.0.14 and assorted minor issues. Get the latest from https://flaterco.com/xtide/files.html and see the changelog for details.
The archive is at https://flaterco.com/files/xtide/. Old links pointing to ftp://ftp.flaterco.com/xtide/... should be redirected to https://flaterco.com/files/xtide/....
For various reasons, I have ended maintenance of the non-free data set. Anyone interested in generating new harmonic constants from published data can find information and a list of data sources here.
There is an announce-only mailing list to which I send notices of each update to XTide or the harmonics data. You can subscribe or read the archives at https://pairlist10.pair.net/mailman/listinfo/xtide-announce.
Please note: If an announcement to you gets bounced by your mail server, you fall off the list. Some long-time contributors have fallen off because, unbeknownst to them, their ISPs subscribed to a spam blackholing service that blackholed all pair.com-hosted domains after one of them sent out spam.
XTide
Major things to do in XTide 3 if life turns out not to be too short after all:
harmbase2
All the cheap and nasty reverse geocoding for the purpose of improving station descriptions is stupid and should be punted to QGIS.
harmgen
It should be possible to link directly with liboctave to avoid the very inefficient conversion of input data from binary to text and back again that currently is done. However, this would be fixing something that is not broken, and is neither important nor urgent.
libtcd
Purge antique portability workarounds from configure.ac. Always just include stdint not inttypes.
In signed_bit_unpack, extend_mask << numbits uses undefined behavior.
In the documentation section on inference, cite NOAA SP NOS CO-OPS 3 Sec. 4.2.3 explaining how bogus it is.
Things to do in the next major revision, if there ever is one: