Skip to main content
Petanque Life

Weather & Conditions

F15.08 6 features Planned

At a glance

Weather and Conditions brings golf-and-sailing-grade outdoor intelligence to petanque: forecasts for every upcoming competition with hourly granularity, real-time venue conditions with wind direction overlaid on court orientation, crowdsourced terrain reports with photos, a "best time to play" playability score from 0-100, condition-triggered technique tips and historical weather analytics per club — because outdoor sport conditions decide outcomes.

How it works

Weather data is pulled from a commercial weather API and joined to every venue's geographic location. Each competition page shows a forecast strip for its scheduled days — temperature, wind speed and direction, humidity, precipitation probability, UV index — with hourly granularity for the day-of and three-hour blocks for upcoming days. Players checking in or planning travel see what to expect.

Real-time venue conditions show the same metrics for the present moment, refreshed every fifteen minutes. Wind matters disproportionately in petanque (a 6 m/s side wind shifts trajectories noticeably) so wind direction is rendered with a compass arrow over the court orientation when available. Humidity and recent rain forecast hint at terrain moisture.

Terrain conditions go beyond weather to the boulodrome itself, and they are crowdsourced. Members can post a terrain report: surface type (gravel, clay, packed dirt, sand), condition (dry, damp, soaked, frozen, dusty), hardness (soft to rock-hard), wind exposure, free-text notes and a photo. Reports decay after 24 hours so the displayed condition is always recent. A reputation system prioritises reports from active local players.

Playability score combines weather and terrain into a 0-100 number for each upcoming day, with recommended hours flagged in green and "avoid" hours in amber. The scoring engine considers temperature comfort, wind strength, precipitation and historical patterns. Weather-related tips are condition-triggered: high wind unlocks a tip on tirer technique adjustments; recent rain unlocks pointer-line advice for damp terrain; high temperature warns about hydration and equipment expansion. Tips are short, illustrated and dismissible.

Historical weather data linked to each venue powers club-level analytics: average wind by month, wettest months, typical playing-window hours through the year. Federation organisers use this when scheduling annual competition calendars, and clubs use it to plan when to invest in covered courts.

Key capabilities

  • Weather forecast for every upcoming competition with hourly granularity
  • Real-time venue conditions including wind direction overlaid on court orientation
  • Crowdsourced terrain reports with surface, condition, hardness and photos
  • Playability score 0-100 per day with recommended hours
  • Condition-triggered weather tips for technique and hydration
  • Historical weather analytics per venue for scheduling
  • Reputation-weighted terrain reports with 24-hour freshness decay

In practice

Saturday morning a player checks their afternoon competition. Forecast: 24 °C, 5 m/s south wind, no rain. Playability 82 — green.

They drive over and post a terrain report on arrival: gravel, dry, hardness firm, light dust, photo attached. Three more players arriving see the report and skip re-posting. A wind-tip pops up: "Side wind 5 m/s — tirer trajectories drift right; aim slightly left of jack on long shots." Mid-afternoon the wind picks up to 9 m/s; a fresh tip lands.

After the competition the club's home page reflects the day's conditions in its historical chart — June afternoons trending windier than the prior year.

Features in this subsystem

6
ID Status Features
F15.08.01 Shipped Weather forecast for upcoming competitions, block by block (the competition's timed schedule blocks, else morning/afternoon per day; beyond_horizon for days past the provider) with the federation's warning thresholds evaluated per block, plus the weather_forecast_warning notice (one per competition/day/threshold, measured outcome) sent by the sweep weather_forecast_sweep — GET /v1/public/competitions/{id}/weather-forecast ✅ 3e1559c7.m-1 (t-1)
F15.08.02 Shipped Weather conditions at a published place to play (temperature, feels-like, wind, gusts, humidity, rain risk — measured through the provider port, integers only, stale snapshot shown with its time) — GET /v1/discover/places/{slug}/conditions ✅ 3e1559c7.m-1 (t-1)
F15.08.03 Shipped Crowdsourced surface reports per place to play — a member's OBSERVATION (surface type, condition, hardness, wind on site, optional court, optional note and photo through the media port) in D-COURTSIDE's own table, never D-VENUE's register; name read at query time, 3/reporter/place/rolling day, own deletion within the freshness window, the fresh report weighed into playability — GET POST /v1/discover/places/{slug}/surface-reports, POST …:photo-grant, DELETE …/{id}, GET …/{id}/photo | ✅ 3e1559c7.m-2 (t-1)
F15.08.04 Shipped Playability score 0–100 per hour in the place's local time, every deduction in factors[], the recommended window and best hour — a pure function over the federation's weather_policy (GET/PUT /v1/tenant/weather-policy) — in the conditions response ✅ 3e1559c7.m-1 (t-1)
F15.08.05 Shipped Weather-related tips — a pure matching engine (MatchTips) over the current forecast hour and the fresh surface report against the federation's tip set (tenant data with a code-declared platform catalogue as source) — GET /v1/discover/places/{slug}/tips, federation management GET POST /v1/tenant/playing-tips, POST …:import-catalog, PATCH …/{id} | ✅ 3e1559c7.m-2 (t-1)
F15.08.06 Shipped Historical weather per place and calendar month from the platform's OWN daily records (weather_daily), with measured coverage (days + years) and no_data months — GET /v1/discover/places/{slug}/weather-history ✅ 3e1559c7.m-1 (t-1)

Stakeholders who need this subsystem

Surfaces in 1 stakeholder analyses