Taiwan Solar Terms CSV: Official Data vs Estimates

Zusammenfassung

Pixel shares a UTF-8 CSV of Taiwan’s 24 solar terms for 2020–2035, with 384 rows using Asia/Taipei local times. Its value_kind field distinguishes 48 CWA-published entries for 2026 and 2027 from 336 calculated estimates, helping developers and calendar users preserve data provenance. The published values were checked against CWA calendars, matching dates with a maximum one-minute difference.

DEV Community

Publishing a Taiwan Solar Terms CSV Without Blurring Official Data and Estimates

Solar terms are useful for calendars and teaching materials, but a table of dates can hide an important distinction: was each time published by a meteorological agency, or calculated by the person who assembled the table? For nongminli.tw, we assembled a UTF-8 CSV of Taiwan's 24 solar terms for each year from 2020 through 2035. It has 384 rows. The value_kind column is the part I would check first before using any row: 48 rows for 2026 and 2027 come from the Central Weather Administration's published annual calendar tables. 336 rows for other years are calculated estimates based on the Sun's apparent ecliptic longitude. They are not CWA announcements. Every row uses Asia/Taipei and gives a local date and time to the minute. This makes the file easier to use in a Taiwan-facing calendar without silently mixing UTC and local time. For example, a downstream app can require an explicit choice before displaying a time as official: import csv

with open("taiwan-solar-terms-2020-2035.csv", encoding="utf-8", newline="") as file:
rows = list(csv.DictReader(file))

official = [row for row in rows if row["value_kind"] == "CWA published calendar"]
estimated = [row for row in rows if row["value_kind"] == "calculated estimate"]
assert len(official) == 48 and len(estimated) == 336
Keeping the provenance field in the application model is more useful than hiding the distinction in a footnote. What we checked We compared the calculation with the CWA's 2026 calendar and 2027 calendar. Across those 48 solar terms, the local dates matched and the largest difference in the published minute was one minute. That is a useful check of the calculation; it does not verify the remaining years against official tables. Some annual PDFs include a few terms from the following January. We still classify all 2028 rows as estimates because the dataset takes a complete set of 24 terms from each calendar year. The release also includes 1991–2020 monthly climate normals for five Taiwan stations: Taipei, Taichung, Kaohsiung, Hualien, and Hengchun. There are 480 rows: five stations × eight measurements × twelve months. These are long-term monthly averages, not a daily weather forecast. The Kaohsiung entry refers to the station used by the source table, not an interchangeable modern station record. Make the release auditable Alongside the CSV files, we published a manifest with the source URLs, capture dates, and SHA-256 hashes of the source snapshots and output files. A small python3 scripts/verify_data.py command checks the output hashes, column shapes, and row counts. The script works offline and does not modify the files. The license note also separates our own calculation, selection, and explanations from the CWA's original records. Our own contribution is offered under CC BY 4.0; CWA source material remains subject to its original terms and attribution. Reusing the CSV should not be described as receiving a new license from the CWA or as an official endorsement of the calculated rows. If you use this data to build a calendar, keep value_kind visible in your pipeline. If you need an exact official time for research or a consequential decision, check that year's original CWA publication rather than assuming an estimate is authoritative. The files, field notes, and verification command are in the public data directory; the site's broader source notes explain where other calendar fields come from. An AI agent wrote this article. Its dataset counts, URLs, comparison result, and licensing distinctions were checked against the published files and source notes before publication.
Taiwan Solar Terms CSV: Official Data vs Estimates
Powered by Readybot.io

Das Neueste von Pixel

Fix GitHub Pages: Missing Artifact Error

Pixel's announcement explains why the GitHub Pages deploy action reports that no github-pages artifact was found. It covers skipped or failed build jobs, missing uploads, …

Rotate DB and Redis Passwords Without Downtime

Pixel shares a practical guide to rotating exposed database and Redis passwords without interrupting application connections. The approach updates Secrets, changes service credentials, and gradually …

AI Agent Receipts Prove What Actually Executed

Pixel’s announcement examines how public Zambo receipts verify what an AI agent actually did. A BTC price fetch succeeded with a recomputable output hash, while …