cpedw
Well-known member
Looking forward to late summer, Tides Planner shows unusual behaviour at Oban on 30/9/2021, I found:
▼ 06:10 2.1m▲ 12:00 2.8m▼ 12:30 2.8m▲ 13:40 2.8m▼ 19:30 2.3m. My UKHO paper table gives
06:14 2.1m 13:09 2.8m 19:11 2.3m
and for 13/10/2021:
▼ 04:40 1.5m▲ 10:40 3.1m▼ 17:20 1.6m▲ 23:40 2.7m▼ 23:50 2.7m▲ 00:00 2.7m
UKHO 4:40 1.5m 10:41 3.1m 17:23 1.6m 23:36 2.7m
There are similar results for 18/9/2022,19/9/2022,17/10/2022, 18/10/2022 and 1/11/2022.
This was using the Android app on a Galaxy Tab S2, Android version 7.0.
It seems wrong to have 3 successive identical height tides less than 2 hours apart in Oban.
Can anyone tell me if the Apple version is similarly afflicted and do any other ports (apart from Portsmouth where they tell me that such things really happen) show this odd behaviour?
I did approach support@imray.com and they eventually conceded that "there may be an error". That was over a month ago and there's no sign of an update to the app.
Derek
▼ 06:10 2.1m▲ 12:00 2.8m▼ 12:30 2.8m▲ 13:40 2.8m▼ 19:30 2.3m. My UKHO paper table gives
06:14 2.1m 13:09 2.8m 19:11 2.3m
and for 13/10/2021:
▼ 04:40 1.5m▲ 10:40 3.1m▼ 17:20 1.6m▲ 23:40 2.7m▼ 23:50 2.7m▲ 00:00 2.7m
UKHO 4:40 1.5m 10:41 3.1m 17:23 1.6m 23:36 2.7m
There are similar results for 18/9/2022,19/9/2022,17/10/2022, 18/10/2022 and 1/11/2022.
This was using the Android app on a Galaxy Tab S2, Android version 7.0.
It seems wrong to have 3 successive identical height tides less than 2 hours apart in Oban.
Can anyone tell me if the Apple version is similarly afflicted and do any other ports (apart from Portsmouth where they tell me that such things really happen) show this odd behaviour?
I did approach support@imray.com and they eventually conceded that "there may be an error". That was over a month ago and there's no sign of an update to the app.
Derek