GitHub

PlantMeteo

Stable Dev Build Status Coverage

PlantMeteo helps plant-model workflows move from raw meteorological inputs to model-ready weather tables. It is designed for two common starting points: you have coordinates and dates but no weather file yet, or you already have weather data but it needs to be standardized, checked, aggregated, or exported.

Start Here

  • Start with get_weather if you do not already have a cleaned weather file.
  • Start with read_weather if you already have station, archive, or project weather data.
  • Use to_daily when you want one row per civil day with standard daily summaries.
  • Use prepare_weather_sampler and sample_weather when your model needs rolling or calendar windows, custom reducers, or cached repeated queries.

Why This Package Exists

Plant models rarely receive weather in the exact format they need:

  • station files use different column names and units
  • downloaded weather often comes through provider-specific schemas
  • source timesteps rarely match the timestep expected by the model

PlantMeteo gives you a consistent weather table abstraction, a small API interface, and tools to aggregate or sample weather into the form your model actually uses.

Fastest Path: Get Weather From Coordinates And Dates

If your first problem is "I need usable weather quickly", start with get_weather and the built-in OpenMeteo backend. It is the earliest path in this documentation because it removes one of the most painful setup steps in many modeling workflows.

Open-Meteo is a practical default because it provides:

  • simple coordinate-based access
  • hourly meteorological variables
  • recent forecasts and older archive data through one interface
  • no API key friction for exploratory and research use

See Open-Meteo Guide for how PlantMeteo uses it, why it is useful, and where its limits are.

Second Path: Read And Standardize Local Files

If you already have weather data, read_weather maps source-specific column names and units to PlantMeteo's canonical variables and returns a typed weather table. This path is usually best for station exports, legacy project files, and curated datasets that you want to keep under your own control.

Main Capabilities

Installation

From the Julia package REPL, run add PlantMeteo. Then load it with using PlantMeteo.

Documentation Map