Weather Write

WeatherWrite brings your local weather coverage to the cloud. It automatically captures real conditions and generates posts that highlight yesterday’s recap, today’s forecast, and tomorrow’s outlook — all written in the style you choose. Schedule posts to publish exactly when you want, with automated images matched to the weather. Customize as much as you like, or let WeatherWrite handle the heavy lifting. Your readers get weather that feels personal, and you stay in control while the work gets done for you.

Video walkthrough: https://youtu.be/4ZUW77WvSCc

Features:
– Generates a dedicated post for each weather report created, on demand or on a schedule.
– Scheduled auto-posting (up to 6 times per day and you control the schedule)
– Admin settings for API key, schedule, images, weather alerts, writing style, and defaults

External Services

This plugin connects to several external services to generate weather-aware content and visualizations. Details for each service are below.

• ManOverMachine API (text generation, weather images, official alerts, scheduling)

  • Endpoint: https://api.manovermachine.com
  • What it’s used for: Generates the narrative text for posts, generates weather-variant images from your uploaded base photos, retrieves official weather alerts (OpenWeather One Call 3.0), and schedules the external pings that trigger your posts at exact times.
  • What data is sent and when: On generation (manual or scheduled), the prompt text and selected options (e.g., location string, tone, length) are sent. For image generation, your selected base image is sent for transformation. For alerts, latitude/longitude. For scheduling, your site’s trigger URL, timezone, configured times, and webhook token. Requires your API key; the plugin does not store API responses beyond creating the post. To obtain your key, visit https://www.weatherwrite.com/ or email mike@weatherwrite.com.

• Open‑Meteo Forecast API

  • Endpoint: https://api.open-meteo.com
  • What it’s used for: Retrieves forecast and hourly data used in summaries, charts, and thresholds.
  • What data is sent and when: Latitude/longitude, desired variables, unit and language parameters on fetch.
  • Privacy: https://open-meteo.com/en/privacy

• Open‑Meteo Geocoding API

  • Endpoint: https://geocoding-api.open-meteo.com
  • What it’s used for: Resolves user-entered place names to coordinates.
  • What data is sent and when: Query string (place name), country hint, language.

• Nominatim (fallback geocoding)

  • Endpoint: https://nominatim.openstreetmap.org
  • What it’s used for: Fallback geocoding if Open‑Meteo geocoder cannot resolve.
  • What data is sent and when: Query string in the request URL. A User‑Agent header identifying the site is included.
  • Policy: https://operations.osmfoundation.org/policies/nominatim/

• GeoNames

  • Endpoint: http://api.geonames.org
  • What it’s used for: Looks up GeoNameID and region metadata for map embeds.
  • What data is sent and when: GeoNameID queries and/or name lookups; includes the configured username.

• OpenWeather (official alerts, proxied through the ManOverMachine API)

  • What it’s used for: When enabled in settings, retrieves official weather alerts via One Call 3.0 for the configured location.
  • What data is sent and when: Latitude/longitude when checking for alerts, sent via https://api.manovermachine.com.

• Meteoblue (map embed)

  • Website: https://www.meteoblue.com
  • What it’s used for: Optional iframe map shown in posts if enabled.
  • What data is sent and when: Parameters are included in the iframe URL (e.g., geonameId and/or lat/lon). No plugin-side requests are made; it is a browser iframe embed.