Finalize convective outlook rollout
This commit is contained in:
@@ -26,7 +26,10 @@ database credentials through your normal secret-management process.
|
||||
- Hourly and narrative forecasts
|
||||
- Forecast discussions
|
||||
- Weather stories
|
||||
- Convective outlooks
|
||||
- Convective outlooks:
|
||||
- `GET /outlooks/convective`
|
||||
- `GET /outlooks/convective/active`
|
||||
- `GET /outlooks/convective/location`
|
||||
|
||||
Common query parameters include `format`, `units`, and route-specific options
|
||||
such as forecast `precision`, timezone `tz` / `TZ`, and outlook filters
|
||||
|
||||
@@ -100,7 +100,7 @@ Outputs are HTTP responses in JSON, XML, or text format. All public endpoint han
|
||||
|
||||
`weatherapi` owns no durable weather state. Its runtime state is limited to process memory, loaded configuration, HTTP server state, template registry, renderer registry, and database connection pools. Durable weather data and schema creation are external concerns owned by `weatherfeeder` and Postgres.
|
||||
|
||||
The API currently serves latest-resource views: latest observation, current conditions, latest active alerts run, latest hourly forecast, latest narrative forecast, latest forecast discussion, latest weather story run, and latest individual weather story. Forecast `today` and `tomorrow` routes derive filtered copies from the latest run.
|
||||
The API currently serves latest-resource views: latest observation, current conditions, latest active alerts run, latest hourly forecast, latest narrative forecast, latest forecast discussion, latest weather story run, latest individual weather story, and latest convective outlook run. Forecast `today` and `tomorrow` routes derive filtered copies from the latest run. Convective outlook active and location routes derive filtered copies from the latest run.
|
||||
|
||||
## Configuration and CLI Boundaries
|
||||
|
||||
|
||||
@@ -1,5 +1,9 @@
|
||||
# SPC Convective Outlook API Implementation Plan
|
||||
|
||||
Status: implemented. This file is retained as planning history; current
|
||||
behavior is documented in [`docs/api.md`](../api.md) and the internal docs under
|
||||
[`docs/internal/`](../internal/).
|
||||
|
||||
## Summary
|
||||
|
||||
Implement the `weatherapi` SPC convective outlook API described in [`docs/roadmap/outlook.md`](outlook.md).
|
||||
|
||||
@@ -1,10 +1,15 @@
|
||||
# SPC Convective Outlook API Roadmap
|
||||
|
||||
Status: implemented. This file is retained as planning history; the current
|
||||
public HTTP contract is documented in [`docs/api.md`](../api.md).
|
||||
|
||||
## Summary
|
||||
|
||||
Add `weatherapi` support for SPC convective outlook data stored by `weatherfeeder`.
|
||||
|
||||
This is roadmap-only content. Do not document these endpoints in `README.md`, `docs/api.md`, or other current-behavior docs until the endpoints are implemented in the same change.
|
||||
This was roadmap-only content while the endpoint work was pending. Current
|
||||
behavior now belongs in `README.md`, `docs/api.md`, and the relevant internal
|
||||
and integration docs.
|
||||
|
||||
Target endpoints:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user