Best Tide Pool Days

Home › Corrections

Corrections

We want every figure here to be right. If something is wrong, out of date or should not be here, tell us.

Report an error

Use the form below or email corrections@besttidepooldays.com. Copyright notices can go to the same address.

Response times

TypeWe acknowledge withinWe aim to resolve within
Safety-relevant errorSame business dayThe item is hidden at once while we check
Data error5 business days10 business days
Park or reserve request (threshold change, removal)3 business days5 business days
Copyright notice2 business daysRemoved promptly once a complete notice arrives
Privacy request5 business days30 days

Business days are Monday to Friday, US Eastern, excluding federal holidays. If we made the error, we fix it, and once the fix changes a published figure we log it below. If the source is wrong, we say so on the page and tell the source where it has a public channel. We do not change a figure that correctly follows our published method, but we will explain the method.

Copyright. A notice should identify the work, the material and its address, your contact details, a statement of good-faith belief that the use is not authorized, and a statement under penalty of perjury that the notice is accurate and that you are authorized to act for the owner (17 U.S.C. § 512(c)(3)).

Contact

Orith Apps LLC
7965 N High St, Ste 350 #240
Columbus, OH 43235, USA
Phone: (614) 398-0845
Corrections: corrections@besttidepooldays.com
Privacy requests: privacy@besttidepooldays.com
Everything else: support@orithapps.com

Corrections log

DatePageWhat changedCause
Nov 2026Seal Rock and Strawberry HillBoth used the Waldport (Alsea Bay) station, inside the bay, so their lows were shown about 45 to 55 minutes late and 0.6 to 1.1 ft too shallow. They now use Southbeach, which matches the open coast; dates, heights and counts on both pages changed.Our error: a bay station was used for open-coast beaches
Nov 2026Home, method, about and two spot pagesBean Hollow and Sculptured Beach were counted as having a beach-specific low-tide line. Their cited figures cover a stretch of coast, so they are now counted as regional guidance (the split changed from 12 and 7 to 10 and 9).Our error: the source scope was misread
Nov 2026Home and year hubOregon’s deepest daylight low moved from −2.7 ft at South Beach to −2.9 ft at Otter Rock, once spot stations were included.Our error: only reference stations were read
Nov 2026King-tide pagesHeights above mean higher high water were rounded twice, so some were 0.1 ft off. They are now rounded once.Our error: double rounding
Nov 2026Every data page“Retrieved” and “checked” dates were UTC dates, so some read one day late. They are now Pacific dates.Our error: time zone
Nov 2026About 48 spot and region pagesSentences on what time of day the lows fall (for example “around the middle of the day”) did not match the listed times. They are now worked out from the times themselves.Our error: wording not tied to the data
Nov 2026Home pageThe “furthest above their normal high water” heights were heights above MLLW, not above mean higher high water (MHHW). They now give the height above MHHW.Our error: the wrong datum was subtracted
Nov 2026Home, year hub, AboutEach region’s deepest daylight low was taken from its first NOAA station only. It now uses the lowest of the region’s reference stations and its spots’ own stations; the region page names a spot’s deeper low separately.Our error: only one station was read
Nov 2026Spot and region pages“Longest stretch is N days in a row” counted low tides, not days. It now counts calendar days.Our error: a counting bug
Nov 2026Maine region pagePortland and Eastport were described as stations close together. They are about 294 km apart; the sentence now applies only to stations within a short distance.Our error: the distance check was missing
Nov 2026Year hubMaine was said to get its lowest lows in winter. The season is now worked out from every station’s monthly counts.Our error: the season used one month’s tie-break
Nov 2026Many pagesHeights that round to zero were printed with a minus sign. They now read “0.0 ft”.Our error: rounding

Sources.

Tide figures on this site: NOAA CO-OPS predictions, public domain; see the method page for how they are computed.

Report an error.