<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Eric McWay</title>
    <description>The latest articles on DEV Community by Eric McWay (@ericmcway1).</description>
    <link>https://dev.to/ericmcway1</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4203498%2F65aab72e-ba72-49dd-a75b-5966c1f79144.png</url>
      <title>DEV Community: Eric McWay</title>
      <link>https://dev.to/ericmcway1</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ericmcway1"/>
    <language>en</language>
    <item>
      <title>Show DEV: when a station goes dark, what should the page say instead of a number?</title>
      <dc:creator>Eric McWay</dc:creator>
      <pubDate>Wed, 28 Oct 2026 16:48:07 +0000</pubDate>
      <link>https://dev.to/ericmcway1/show-dev-when-a-station-goes-dark-what-should-the-page-say-instead-of-a-number-k1g</link>
      <guid>https://dev.to/ericmcway1/show-dev-when-a-station-goes-dark-what-should-the-page-say-instead-of-a-number-k1g</guid>
      <description>&lt;p&gt;This is a follow-up to my earlier posts about labeling live sensor data. I run a small site that republishes coastal water readings, and this week two California stations I track stopped returning current values: Los Angeles Harbor and San Francisco Bay. The API still lists them, but there is no fresh temperature to show, so I am not going to quote an old one as if it were today.&lt;/p&gt;

&lt;p&gt;Right now my instinct is to leave the spot on the page with a plain "currently unavailable" note, keep the tide information that is still updating, and not fill the gap with a satellite estimate unless I label it clearly as a different kind of measurement. Hiding the spot entirely feels cleaner, but then a regular visitor might think I dropped the location. Showing the last reading with its age feels honest, but after a few days that number is just old news sitting where a current reading should be.&lt;/p&gt;

&lt;p&gt;Disclosure: I am the owner/builder of the site, and I used AI assistance to help draft this post. I am posting for feedback, not just traffic. The site is &lt;a href="https://watertemperaturelive.com" rel="noopener noreferrer"&gt;https://watertemperaturelive.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;One specific question for anyone who has shipped live data: if a station has been dark for more than a day, would you rather see the spot hidden until it returns, or a plain "no current reading" box left in its place?&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Show DEV: when tide predictions and observed water levels disagree, how do you label predicted vs observed?</title>
      <dc:creator>Eric McWay</dc:creator>
      <pubDate>Tue, 27 Oct 2026 16:57:18 +0000</pubDate>
      <link>https://dev.to/ericmcway1/show-dev-when-tide-predictions-and-observed-water-levels-disagree-how-do-you-label-predicted-vs-4aj2</link>
      <guid>https://dev.to/ericmcway1/show-dev-when-tide-predictions-and-observed-water-levels-disagree-how-do-you-label-predicted-vs-4aj2</guid>
      <description>&lt;p&gt;Disclosure: I run a small water-temperature site, watertemperaturelive.com. This post was drafted with AI assistance and edited by me. I am asking about a presentation pattern, not promoting the site.&lt;/p&gt;

&lt;p&gt;My earlier posts here were about labeling a temperature with its source, and about showing how old a reading is. This one is about a different confusion: predicted vs observed.&lt;/p&gt;

&lt;p&gt;A concrete example from today: Charleston Harbor. The station observation was 66.2°F at 12:30 PM EDT on Oct 27, 2026 (NOAA 8665530). On the same page, the tide table is explicitly astronomical predictions: next low tide 3:41 PM at 0.32 ft, next high tide 9:30 PM at 5.65 ft, relative to MLLW. Those heights are predictions, not measurements, and the page says so — but only if you read the note under the table.&lt;/p&gt;

&lt;p&gt;The problem I am weighing: when wind or surge pushes the actual water level away from the prediction, a casual visitor sees two numbers that look equally authoritative — a predicted height and an observed level — and may not notice which is which. If I put both on one page, how do I keep them from blending together?&lt;/p&gt;

&lt;p&gt;Options I am considering:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Keep prediction and observation in separate blocks with different verbs in the headings: "Predicted tides" vs "Observed water level."&lt;/li&gt;
&lt;li&gt;Show the difference explicitly when both exist, e.g. "Observed 0.4 ft above the predicted height at 2 PM," rather than silently replacing one with the other.&lt;/li&gt;
&lt;li&gt;Never overwrite a prediction with an observation in the same row; if the observed value is missing, say so instead of leaving the prediction standing alone.&lt;/li&gt;
&lt;li&gt;Use a neutral, non-alarm visual treatment for the gap, so a difference reads as "these are two different kinds of number" rather than "something is wrong."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What has worked for you on live-data pages that mix forecasts, predictions, and observations? Is there a labeling pattern you trust a casual reader to get right on first glance?&lt;/p&gt;

&lt;p&gt;For reference, the Charleston Harbor page is here: &lt;a href="https://watertemperaturelive.com/us/south-carolina/charleston-harbor/?utm_source=dev-community&amp;amp;utm_medium=community&amp;amp;utm_campaign=water_resources" rel="noopener noreferrer"&gt;https://watertemperaturelive.com/us/south-carolina/charleston-harbor/?utm_source=dev-community&amp;amp;utm_medium=community&amp;amp;utm_campaign=water_resources&lt;/a&gt; — the temperature and tide figures above are from that page today.&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Show DEV update: the hardest part of a live water-temperature site isn't the temperature — it's the timestamps</title>
      <dc:creator>Eric McWay</dc:creator>
      <pubDate>Mon, 26 Oct 2026 16:37:09 +0000</pubDate>
      <link>https://dev.to/ericmcway1/show-dev-update-the-hardest-part-of-a-live-water-temperature-site-isnt-the-temperature-its-the-49b</link>
      <guid>https://dev.to/ericmcway1/show-dev-update-the-hardest-part-of-a-live-water-temperature-site-isnt-the-temperature-its-the-49b</guid>
      <description>&lt;p&gt;Follow-up to my Show DEV post last week — I run &lt;a href="https://watertemperaturelive.com" rel="noopener noreferrer"&gt;https://watertemperaturelive.com&lt;/a&gt;, which republishes NOAA / NDBC / USGS water readings for about 20 U.S. coastal and Great Lakes spots.&lt;/p&gt;

&lt;p&gt;The thing I underestimated: the readings are the easy part. NOAA's CO-OPS API gives you a station reading every few minutes with an observation timestamp. The hard parts are everything around that:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Stations go quiet.&lt;/strong&gt; A pier sensor fouls or a storm knocks it out, and the API just stops returning new values. If you cache the last number without its age, your site happily shows a three-day-old temperature as "current."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Observed vs. analyzed.&lt;/strong&gt; For spots without a pier station I use NASA/JPL's MUR satellite analysis — a daily ~1km grid. It's an analysis of the surface, not a thermometer in the water, and it can disagree with a pier a few km away by a few degrees. Both are "right"; they're different measurements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Timezones.&lt;/strong&gt; Tide predictions share the page with the readings, so a timestamp rendered in UTC next to a tide table in local time confuses everyone.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;My current approach: every number renders with its station ID, its observation time in local time, and its age; if a station's newest reading is older than a threshold, the page says so instead of implying it's live, and a missing station is labeled missing rather than silently filled in from the satellite grid.&lt;/p&gt;

&lt;p&gt;Concrete example: the La Jolla pier station (NOAA 9410230) read 73.2°F at 9:24 AM PDT today (Oct 26) — well above that station's 2021–2025 October baseline on the site, which tops out at 67.8°F. The timestamp is what makes that claim checkable.&lt;/p&gt;

&lt;p&gt;Example page: &lt;a href="https://watertemperaturelive.com/us/california/la-jolla/?utm_source=dev-community&amp;amp;utm_medium=community&amp;amp;utm_campaign=water_resources" rel="noopener noreferrer"&gt;https://watertemperaturelive.com/us/california/la-jolla/?utm_source=dev-community&amp;amp;utm_medium=community&amp;amp;utm_campaign=water_resources&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Disclosure: I'm the owner/builder of the site — posting for feedback, not just traffic. (I used AI assistance to help draft this post.)&lt;/p&gt;

&lt;p&gt;Question for others publishing live sensor data: how do you label stale data — a visible age badge, grey it out, hide it entirely? And do you surface "station offline" as an explicit state, or just fall back to the nearest source?&lt;/p&gt;

&lt;p&gt;— Eric McWay&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>webdev</category>
      <category>api</category>
    </item>
    <item>
      <title>Show DEV: I built a water-temperature site that labels every number with its source — how would you do it better?</title>
      <dc:creator>Eric McWay</dc:creator>
      <pubDate>Sat, 24 Oct 2026 02:00:34 +0000</pubDate>
      <link>https://dev.to/ericmcway1/show-dev-i-built-a-water-temperature-site-that-labels-every-number-with-its-source-how-would-you-83l</link>
      <guid>https://dev.to/ericmcway1/show-dev-i-built-a-water-temperature-site-that-labels-every-number-with-its-source-how-would-you-83l</guid>
      <description>&lt;p&gt;Hi all — I built &lt;a href="https://watertemperaturelive.com" rel="noopener noreferrer"&gt;https://watertemperaturelive.com&lt;/a&gt;, a site showing current water temperatures and tide predictions for about 20 monitored U.S. coastal and Great Lakes locations. Data comes from official sources: NOAA CO-OPS pier/harbor stations, NDBC buoys, USGS gauges, and NASA/JPL's daily MUR satellite sea-surface analysis.&lt;/p&gt;

&lt;p&gt;The problem I'm trying to solve is provenance confusion. Most water-temp sites show one number. But a pier thermometer at La Jolla (NOAA 9410230) and a 1km satellite analysis pixel offshore are very different things. Right now, for example, the La Jolla pier reads 72.9°F (observed Oct 23, 3:24 PM PDT) — above the station's usual October 90th percentile of 67.8°F (2021–2025). A satellite pixel a few km offshore could easily read differently, and neither is 'wrong' — they're different measurements.&lt;/p&gt;

&lt;p&gt;So every number on the site carries a label: station ID, observation time, and whether it's a direct observation or a satellite analysis, plus a seasonal baseline band so you can tell when today's reading is unusual. Example page: &lt;a href="https://watertemperaturelive.com/us/california/la-jolla/?utm_source=dev-community&amp;amp;utm_medium=community&amp;amp;utm_campaign=water_resources" rel="noopener noreferrer"&gt;https://watertemperaturelive.com/us/california/la-jolla/?utm_source=dev-community&amp;amp;utm_medium=community&amp;amp;utm_campaign=water_resources&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Disclosure: I'm the owner/builder of the site — posting for feedback, not just traffic. (I used AI assistance to help draft this post.)&lt;/p&gt;

&lt;p&gt;My question: how would you label observed vs. analyzed values so a casual visitor (not a data person) instantly gets the difference? Right now I use badges like 'pier reading' vs 'satellite analysis' plus the station ID. Is that enough, or would you do something more explicit in the UI? Also curious how others handle mobile layout for data-dense pages — the tide tables get cramped.&lt;/p&gt;

&lt;p&gt;— Eric McWay&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
