Add LVGMC warning map workflow
This commit is contained in:
@@ -108,6 +108,20 @@ The renderer uses canvas `TextMetrics` visible-glyph bounds (`actualBoundingBoxL
|
||||
|
||||
Implementation status: both native exports are implemented and visually validated against the supplied production templates. Later newsroom feedback can still tune the per-template rectangles without changing the manual-entry workflow.
|
||||
|
||||
## Brīdinājumi
|
||||
|
||||
Purpose: prepare a newsroom map from the current LVĢMC open hydrometeorological-warning dataset without tracing warning areas manually.
|
||||
|
||||
Operator flow:
|
||||
|
||||
1. Open **Brīdinājumi**; warning metadata and ordered polygon coordinates load through the WeatherTool backend.
|
||||
2. Select the independent 1920×1080 or 3840×1440 production canvas.
|
||||
3. Optionally filter the current warning period by day and phenomenon.
|
||||
4. Enter the editorial title. Warning geometry, severity colors, legend, source data, and validity information remain data-driven.
|
||||
5. Preview and download the native-resolution PNG.
|
||||
|
||||
The two exports use separate geographic-to-pixel calibration and layout values. Neither output is produced by resizing the other. Upstream times are interpreted in the `Europe/Riga` timezone. Empty warning data is a valid state and produces an uncolored base map.
|
||||
|
||||
## Apskats
|
||||
|
||||
Purpose: aggregate selected fields across Latvia for a selected time range.
|
||||
|
||||
Reference in New Issue
Block a user