LoginSign Up
← Back to all sparks
J

jmastats

ANALYTICS
Velocity0.0

Download Weather Data from Japan Meteorological Agency Website

github.com/uribo/jmastats ↗

A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.

r-packageweather-datajapandataset-refreshapi-client
◆Current state
jmastats pulls weather and climate data from the Japan Meteorological Agency into R, and most of its releases exist to refresh the station and reference datasets it ships. Three of the four versions on record are dataset updates, dated by the month they were cut. The exception is 0.3.0, which taught jma_collect() to retrieve climatological normals derived from past observations.
◆Where it's heading
The package treats bundled data as the thing that must not go stale, and the retrieval API as broadly finished. Where code does change, it is about being a well-behaved client — request intervals to reduce server load, messages when returned data contains missing values, corrected station coordinates. Capability growth happens in single steps, roughly once a year.
◆Prediction
The next release is most likely another dated dataset refresh; a further extension of jma_collect() to a new observation type is plausible but the entries show no specific one being prepared.

◆Recent moves

  1. 1y ago

    jma_collect() can now retrieve climatological normals

    Climatological normals computed from past observations become retrievable through the existing jma_collect() entry point, the only capability added across the package's recorded history. The customary dataset refresh ships with it.

    View source ↗
  2. 2y ago

    Station coordinates and prefecture codes corrected

    A dataset refresh plus corrections to coordinates and prefecture codes in the station table. Data accuracy work of exactly the kind that makes up most of this package's release history.

    View source ↗
  3. 2y ago

    Bundled datasets refreshed to March 2024

    A dataset-only release with no code changes. It is the clearest example of the maintenance rhythm that defines the package between capability releases.

    View source ↗
  4. 2y ago

    First CRAN release adds request throttling to jma_collect()

    The initial CRAN release, which is what made the package installable through the standard channel. It also establishes the good-client behaviour the package has kept since: an interval between requests to reduce load on the agency's servers, and a message when returned data contains missing values.

    View source ↗