Document localized workflows and water map calibration
This commit is contained in:
+13
-13
@@ -10,13 +10,13 @@ Operator-facing workspace names, map names, export names, and production labels
|
||||
|
||||
Entry point and navigation overview. It identifies the development dataset and links to each workspace.
|
||||
|
||||
## Stations
|
||||
## Stacijas
|
||||
|
||||
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
|
||||
## Kartes
|
||||
|
||||
Purpose: compare historical observations across selected cities.
|
||||
|
||||
@@ -85,9 +85,9 @@ Completed Faktiskā checkpoint:
|
||||
|
||||
Valmiera is included in the development seed so all 13 fixed positions can be exercised. Confirmed Monda Regular/Bold files are now bundled and used. The export dimensions are locked, but final pixel-level placement must still be compared against the production masters after the font change.
|
||||
|
||||
## Ūdens temperatūra
|
||||
## Ūdens
|
||||
|
||||
Purpose: prepare the fixed water-temperature newsroom map as a separate production workflow. It must not be mixed into Faktiskā or City Analysis.
|
||||
Purpose: prepare the fixed water-temperature newsroom map as a separate production workflow. It must not be mixed into Faktiskā or Kartes.
|
||||
|
||||
Authoritative references:
|
||||
|
||||
@@ -96,37 +96,37 @@ Authoritative references:
|
||||
|
||||
Required behavior:
|
||||
|
||||
1. Open the dedicated **Ūdens temperatūra** workspace.
|
||||
1. Open the dedicated **Ūdens** workspace.
|
||||
2. Display the fixed set of Latvian-named water-temperature fields.
|
||||
3. Enter or correct every water temperature manually.
|
||||
4. Place values automatically at their locked production positions.
|
||||
5. Preview and download either a 1920×1080 or 3840×1440 PNG.
|
||||
|
||||
The background, title, source, field set, and value positions remain fixed. Only the water-temperature values are routinely edited. Both output sizes are production requirements and must be validated independently; implementation must not assume that browser preview dimensions define export geometry.
|
||||
The 1920×1080 and 3840×1440 products are independent authoritative canvases. Neither is derived by resizing or reflowing the other. Each template contains the fixed newsroom artwork and six separately measured value rectangles.
|
||||
|
||||
When switching output size, the background may use the target canvas aspect ratio, but boxes, typography, and nameplate elements must scale uniformly. They must never be independently stretched on the horizontal and vertical axes.
|
||||
The renderer uses canvas `TextMetrics` visible-glyph bounds (`actualBoundingBoxLeft`, `actualBoundingBoxRight`, `actualBoundingBoxAscent`, and `actualBoundingBoxDescent`) to optically center Monda text inside each rectangle. The browser preview scales the complete canvas only; downloaded PNGs retain their native dimensions.
|
||||
|
||||
Implementation status: first working version implemented. The page provides six Latvian-named manual min/max controls, automatic fixed placement, Monda rendering, explicit resolution selection, completeness validation, and Latvian PNG filenames. Pixel-level comparison and independent calibration of both output sizes remain required.
|
||||
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.
|
||||
|
||||
## Latvia overview
|
||||
## Apskats
|
||||
|
||||
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
|
||||
## Arhīvs
|
||||
|
||||
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
|
||||
## 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
|
||||
## LVĢMC
|
||||
|
||||
Purpose: display prepared LVGMC forecast products and broadcast tables.
|
||||
|
||||
@@ -137,5 +137,5 @@ Development limitation: representative forecast CSV fixtures are not currently i
|
||||
- Whether weather conditions can eventually be populated automatically and which provider field is authoritative.
|
||||
- Whether Stende and Zīlāni remain the production feeds after users test real provider data.
|
||||
- Confirm how Valmiera is named and sourced when authorized provider data is available.
|
||||
- Final pixel-level Monda export comparison against the production masters.
|
||||
- Apply the same native-resolution production comparison to additional broadcast products as they are finalized.
|
||||
- Required authentication and role separation for analytical, production, and administrative workspaces.
|
||||
|
||||
Reference in New Issue
Block a user