Add Valmiera synthetic observations
This commit is contained in:
@@ -67,7 +67,7 @@ Fixed positions:
|
||||
|
||||
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.
|
||||
|
||||
Current staging limitation: the synthetic dataset has no Valmiera row, so that position is deliberately shown as missing and remains manually editable. Monta is the production typeface; Rubik remains temporary until the authorized Monta font files are supplied. The export dimensions are locked, but final pixel-level placement must still be compared against the production masters after Monta is installed.
|
||||
Valmiera is included in the development seed so all 13 fixed positions can be exercised. Monta is the production typeface; Rubik remains temporary until the authorized Monta font files are supplied. The export dimensions are locked, but final pixel-level placement must still be compared against the production masters after Monta is installed.
|
||||
|
||||
## Latvia overview
|
||||
|
||||
@@ -97,6 +97,6 @@ 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.
|
||||
- How Valmiera should be sourced when authorized provider data is available.
|
||||
- Confirm how Valmiera is named and sourced when authorized provider data is available.
|
||||
- Final Monta font files and a pixel-level export comparison against the production masters.
|
||||
- Required authentication and role separation for analytical, production, and administrative workspaces.
|
||||
|
||||
Reference in New Issue
Block a user