b0txec
87 lines
3.0 KiB
Markdown
87 lines
3.0 KiB
Markdown
# Product workflows
|
||
|
||
This document records the current understanding of the visible workspaces. It should be updated when workplace users clarify the real operational purpose.
|
||
|
||
## Home
|
||
|
||
Entry point and navigation overview. It identifies the development dataset and links to each workspace.
|
||
|
||
## Stations
|
||
|
||
Purpose: inspect station-focused observations, map values, and open detailed charts for a selected station.
|
||
|
||
Current status: inherited workflow; still requires detailed workplace validation and UI review.
|
||
|
||
## City Analysis
|
||
|
||
Purpose: compare historical observations across selected cities.
|
||
|
||
The operator chooses:
|
||
|
||
- cities;
|
||
- start and end time;
|
||
- weather field;
|
||
- aggregate key;
|
||
- granularity.
|
||
|
||
Results can be viewed as grid/list data or rendered into the familiar temperature-map formats. Weather-symbol authoring does not belong in this workflow.
|
||
|
||
## Faktiskā
|
||
|
||
Purpose: prepare the daily **faktiskā laika ziņu karte**—an actual-weather newsroom graphic containing:
|
||
|
||
- title;
|
||
- source;
|
||
- temperatures;
|
||
- weather conditions represented by the bundled weather-font glyphs;
|
||
- 1920×1080 or 3840×1440 output;
|
||
- optional wind layout where required.
|
||
|
||
Current operator flow:
|
||
|
||
1. Select cities.
|
||
2. Select resolution and optional wind layout.
|
||
3. Choose the temperature field, calculation, and time range.
|
||
4. Load map data.
|
||
5. Enter title and source.
|
||
6. Select a weather glyph.
|
||
7. Apply it to all selected cities when appropriate.
|
||
8. Assign different glyphs to the exceptions.
|
||
9. Review the canvas and download PNG.
|
||
|
||
The weather symbols are not automatically derived from the historical temperature query. They remain editorial/manual inputs until a reliable phenomena-data mapping is designed and validated.
|
||
|
||
## Latvia overview
|
||
|
||
Purpose: aggregate selected fields across Latvia for a selected time range.
|
||
|
||
Current status: inherited workflow; terminology, units, and workplace use still need validation.
|
||
|
||
## Data archive
|
||
|
||
Purpose: inspect available database dates and individual stored records/files.
|
||
|
||
Current status: inherited technical/administrative workflow. Access control and export correctness require review before production use.
|
||
|
||
## HARMONIE
|
||
|
||
Purpose: inspect and render forecast-model GRIB fields.
|
||
|
||
Development limitation: no representative HARMONIE GRIB fixtures are currently included, and valid external-provider access is not configured in staging.
|
||
|
||
## LVGMC forecast
|
||
|
||
Purpose: display prepared LVGMC forecast products and broadcast tables.
|
||
|
||
Development limitation: representative forecast CSV fixtures are not currently included, and valid external-provider access is not configured in staging.
|
||
|
||
## Decisions still required
|
||
|
||
- Exact workplace meaning and default query for Faktiskā temperatures.
|
||
- Which cities belong to each newsroom graphic by default.
|
||
- Default titles and source labels.
|
||
- Whether wind layouts belong to Faktiskā, City Analysis, or both.
|
||
- Whether weather conditions can eventually be populated automatically and which provider field is authoritative.
|
||
- Required authentication and role separation for analytical, production, and administrative workspaces.
|
||
|