<?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: ISOTHERM</title>
    <description>The latest articles on DEV Community by ISOTHERM (@isotherm).</description>
    <link>https://dev.to/isotherm</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%2F4248174%2F1b246b4f-3ff4-4281-9d45-bb22e85c89d3.png</url>
      <title>DEV Community: ISOTHERM</title>
      <link>https://dev.to/isotherm</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/isotherm"/>
    <language>en</language>
    <item>
      <title>Three counting mistakes that put you in the wrong temperature bucket (checked on 1,153 resolved market-days)</title>
      <dc:creator>ISOTHERM</dc:creator>
      <pubDate>Mon, 16 Nov 2026 17:18:29 +0000</pubDate>
      <link>https://dev.to/isotherm/three-counting-mistakes-that-put-you-in-the-wrong-temperature-bucket-checked-on-1153-resolved-39ka</link>
      <guid>https://dev.to/isotherm/three-counting-mistakes-that-put-you-in-the-wrong-temperature-bucket-checked-on-1153-resolved-39ka</guid>
      <description>&lt;p&gt;Daily-high temperature markets look simple: one airport, one day, one number. But the market does not resolve on "how hot it was." It resolves on a specific set of airport reports, read by a specific rule. Count the reports a little differently and you land one bucket away, with a number that looks perfectly reasonable.&lt;/p&gt;

&lt;p&gt;I rebuilt the daily high for every city with a Polymarket daily-high market from public airport reports, then compared my number with the range each market actually resolved to. Period: markets that closed between 17 October and 16 November 2026. That is 1,153 city-days across 48 cities. I only read which range won. No prices are involved anywhere in this.&lt;/p&gt;

&lt;p&gt;Getting to 1,153 out of 1,153 took three corrections. Each one is a mistake I made first.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Counting only the top-of-the-hour reports
&lt;/h2&gt;

&lt;p&gt;Many airports outside the United States publish a routine report (METAR) every 30 minutes, not every hour. Some archives file the half-hour ones under a different report type, so a query for "routine reports" quietly returns only the hourly ones.&lt;/p&gt;

&lt;p&gt;If the day's peak falls on a half-hour report, you miss it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Hourly reports only: 1,102 of 1,153 city-days in the resolved range (95.6%)&lt;/li&gt;
&lt;li&gt;With half-hour routine reports: the 51 misses disappear&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. Counting US special reports
&lt;/h2&gt;

&lt;p&gt;So I included the second report type everywhere. That fixed the 51 and broke 7 others, all at US airports.&lt;/p&gt;

&lt;p&gt;US airports publish one routine report an hour. In between they issue special reports (SPECI) when conditions change quickly. Those specials can carry a higher temperature than any routine report that day, and they do not count. The trap: the archive I used strips the word SPECI from US reports, so "drop every line that starts with SPECI" removes nothing.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Both report types everywhere: 1,146 of 1,153 (99.4%)&lt;/li&gt;
&lt;li&gt;Half-hour reports outside the US, hourly routine reports only in the US: 1,153 of 1,153&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  3. Truncating instead of rounding
&lt;/h2&gt;

&lt;p&gt;A common explanation says the reading is truncated: 10.9 becomes 10. I tested it on the same days, using the 0.1 °C value from the report remarks where one exists, converting to °F first for °F markets.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Rounded half up: 1,153 of 1,153&lt;/li&gt;
&lt;li&gt;Truncated: 1,094 of 1,153 (94.9%)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Truncating put the number in the wrong range on 59 city-days, about one day in twenty. At airports that only report whole degrees the two rules give the same answer, so the gap is concentrated where 0.1-degree values exist.&lt;/p&gt;

&lt;h2&gt;
  
  
  The rule that matched every day
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Take the airport named in the market rules and its local calendar day.&lt;/li&gt;
&lt;li&gt;Count routine reports. Outside the US that includes the half-hour ones. In the US, hourly routine reports only. Special reports never count.&lt;/li&gt;
&lt;li&gt;Use the 0.1 °C remark value when the report has one, otherwise the whole-degree temperature.&lt;/li&gt;
&lt;li&gt;Take the highest value. Convert to °F first if the market is in °F. Round half up to a whole degree.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What this does not tell you
&lt;/h2&gt;

&lt;p&gt;Thirty days is thirty days. Rules change, archives get corrected after the fact, and a market can resolve on something other than what its rules suggest. So the comparison runs every week and every city-day is published, including any day that differs:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://isotherm-82f.pages.dev/check.html" rel="noopener noreferrer"&gt;https://isotherm-82f.pages.dev/check.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There is also a free single-file Python script and a 30-day Tokyo sample if you want to run the rounding check yourself:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://isotherm-82f.pages.dev/kit.html" rel="noopener noreferrer"&gt;https://isotherm-82f.pages.dev/kit.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is information about how numbers are counted. It is not financial or betting advice, and ISOTHERM is not affiliated with any exchange or prediction market.&lt;/p&gt;

</description>
      <category>predictionmarkets</category>
      <category>weather</category>
      <category>data</category>
      <category>python</category>
    </item>
  </channel>
</rss>
