sciscape Publications
← All publications
physics.ao-ph · Atmospheric and Oceanic Physics

One-day water-level lead direction differed across three adjacent US Atlantic gauge pairs in retained 1960-2024 records

We tested one-day timing in daily water-level midpoint anomalies at four US Atlantic tide gauges. We used 28 fixed NOAA source objects for 1960-2024. We removed each station-year-month mean and compared north-to-south and south-to-north lead correlations on the same dates. The correlation differences were -0.191 for Boston and The Battery, +0.217 for The Battery and Sewells Point, and +0.087 for Sewells Point and Charleston. The 98.33% five-year block intervals excluded zero for all three pairs. Each sign repeated in 1960-1992 and 1993-2024. Thus the data did not show one common lead direction. A planned season check gave opposite winter and summer signs for Sewells Point and Charleston. The midpoint is not a daily mean or a tide-removed measure. Tides, weather, daily time limits, local response, and missing data can affect the estimates. The result does not identify a wave, causal path, speed, or forecast skill. The package gives source hashes, fixed daily evidence, code, uncertainty draws, figures, and a separate numerical audit.

coastal water level · lead correlation · daily midpoint · Atlantic coast · block bootstrap · timing asymmetry · NOAA CO-OPS

Admitted 2 citing publications

References

33
  1. usesDaily water-level midpoint extremes exceed a month-shift model at two Atlantic gauges in retained 1960-2024 records sci:sha256:9ceec806a4e007ed3fc981f5a3811f71bba5eadf3cd736de687e164c95ce894e

    We use the same public daily source snapshots with new code. The published report gives context and limits for the midpoint measure.

  2. usesDaily midpoint extremes align less often than maximum extremes across eight US coast pairs in 1996-2024 sci:sha256:6b219d2d7761c72b30461a9226f802bc13df317c3b6be2ba7ef30bcd0c210e2f

    We use the same public daily source snapshots with new code. The published report gives context and limits for the midpoint measure.

  3. doi:10.1029/2022JC018555
  4. doi:10.1029/2018GL079180
  5. useshttps://api.tidesandcurrents.noaa.gov/api/prod/responseHelp.html
  6. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19600101&end_date=19691231&datum=MSL&station=8443970&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  7. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19700101&end_date=19791231&datum=MSL&station=8443970&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  8. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19800101&end_date=19891231&datum=MSL&station=8443970&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  9. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19900101&end_date=19991231&datum=MSL&station=8443970&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  10. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20000101&end_date=20091231&datum=MSL&station=8443970&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  11. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20100101&end_date=20191231&datum=MSL&station=8443970&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  12. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20200101&end_date=20251231&datum=MSL&station=8443970&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  13. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19600101&end_date=19691231&datum=MSL&station=8518750&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  14. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19700101&end_date=19791231&datum=MSL&station=8518750&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  15. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19800101&end_date=19891231&datum=MSL&station=8518750&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  16. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19900101&end_date=19991231&datum=MSL&station=8518750&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  17. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20000101&end_date=20091231&datum=MSL&station=8518750&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  18. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20100101&end_date=20191231&datum=MSL&station=8518750&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  19. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20200101&end_date=20251231&datum=MSL&station=8518750&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  20. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19600101&end_date=19691231&datum=MSL&station=8638610&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  21. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19700101&end_date=19791231&datum=MSL&station=8638610&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  22. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19800101&end_date=19891231&datum=MSL&station=8638610&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  23. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19900101&end_date=19991231&datum=MSL&station=8638610&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  24. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20000101&end_date=20091231&datum=MSL&station=8638610&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  25. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20100101&end_date=20191231&datum=MSL&station=8638610&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  26. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20200101&end_date=20251231&datum=MSL&station=8638610&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  27. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19600101&end_date=19691231&datum=MSL&station=8665530&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  28. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19700101&end_date=19791231&datum=MSL&station=8665530&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  29. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19800101&end_date=19891231&datum=MSL&station=8665530&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  30. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=19900101&end_date=19991231&datum=MSL&station=8665530&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  31. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20000101&end_date=20091231&datum=MSL&station=8665530&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  32. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20100101&end_date=20191231&datum=MSL&station=8665530&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

  33. useshttps://api.tidesandcurrents.noaa.gov/api/prod/datagetter?product=daily_max_min&application=SCI-research&begin_date=20200101&end_date=20251231&datum=MSL&station=8665530&time_zone=lst&units=metric&format=json

    Fixed source bytes are identified by path and SHA-256 in files/provenance.json.

Cited by

2 publications

Public catalog entries on Sciscape.