Tides work again on new installs, from the nearest station within 100 km

This release fixes new installs and updates of 2.2.1, which stopped predicting tides and reported predictor.getExtremesPrediction is not a function. If you are on 2.2.1, update to get tides back. It also moves to the newer Slackwater station database, so the plugin now only uses a station close enough to stand in for your tide.

What changes when you upgrade

• The plugin picks the nearest station with tide predictions within 100 km of the vessel. Past that it publishes no tide, says so in its status, and clears the tide values it had published, rather than showing a tide from other water. A default station you chose in settings is used at any distance. (#178)
• Predicted heights change at some stations with the new data, by up to about half a metre at a few TICON stations. (#178)

Also in this release

• Near Canadian stations that list a name but no tide model, the plugin uses the nearest station that has one, instead of a flat zero tide. If such a station is saved as your default, the plugin falls back to the nearest station and logs an error. (#178)
• The settings list no longer offers stations with no tide model. (#178)
• A new path, environment.tide.stationDistance, gives the distance in metres to a station picked by position, and the plugin status shows it. (#178)
• Station data now loads the first time something needs it, rather than when the server loads the plugin. (#178)
• If station data fails to load, the plugin reports an error, and requests get an answer instead of hanging. (#178)