← Previous Contents


Data refresh 2021-01-10

The data refresh available from https://flaterco.com/xtide/files.html#harmonicsfiles includes a large number of new currents because harmonic constants for currents are now available through MDAPI.

A corresponding update of the harmonic constants management package is available from https://flaterco.com/xtide/files.html#experts.

Minor updates 2020-06-28

The XTide, Congen, libtcd, and tideEditor packages have all been touched to perform some minor but messy maintenance.  Build scripts that were specific to particular flavors of Linux and to non-Unix platforms were moved into a new separate package, FunkyBuilds; configure scripts were patched to improve portability; old URLs were updated, and documentation nits were fixed.  XTide got a bugfix increment because some of the outdated URLs were in the source code; the other three packages are just re-releases.

FunkyBuilds includes a new build script for Ubuntu and an improved one for DOS.  A new DOS binary has been posted under Contrib.

All available from https://flaterco.com/xtide/files.html.

End of maintenance for non-free data

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.

Mailing list

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.

To do list


Major things to do in XTide 3 if life turns out not to be too short after all:


All the cheap and nasty reverse geocoding for the purpose of improving station descriptions is stupid and should be punted to QGIS.


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.


Purge antique portability workarounds from configure.ac.  Always just include stdint not inttypes.

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:

← Previous Contents