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.
|
||||
|
||||
+1
-1
@@ -6,7 +6,7 @@ This directory contains the working documentation for the WeatherTool modernizat
|
||||
|
||||
- Development source is edited and committed on Windows; Docker builds and runtime testing are performed on Rocky.
|
||||
- A production-like staging copy runs through Docker Compose on Rocky Linux at `http://192.168.1.101:9190`.
|
||||
- Staging uses deterministic synthetic station observations for all 33 stations.
|
||||
- Staging uses deterministic synthetic observations for the repository station set plus Valmiera, required by Faktiskā.
|
||||
- Scheduled external-provider jobs are disabled in development and staging.
|
||||
- PostgreSQL is private to the project Compose network; only the Scala application publishes a host port.
|
||||
- UI modernization is in progress. City Analysis retains custom analytical map outputs, while Faktiskā is a fixed 13-position, latest-temperature newsroom workflow with a locked 3840×1440 export.
|
||||
|
||||
@@ -28,7 +28,7 @@ Status: in progress
|
||||
- [x] Review backend, frontend, deployment, and security structure.
|
||||
- [x] Run the project locally through Docker Desktop.
|
||||
- [x] Add configurable host port and scheduled-job switch.
|
||||
- [x] Add deterministic synthetic station data for all 33 stations.
|
||||
- [x] Add deterministic synthetic station data for the repository station set and the Faktiskā-required Valmiera position.
|
||||
- [x] Create an isolated Rocky Linux staging deployment.
|
||||
- [x] Keep staging PostgreSQL private to its Compose network.
|
||||
- [x] Commit the baseline changes and establish the Git-over-SSH workflow.
|
||||
@@ -144,7 +144,6 @@ Status: pending
|
||||
- Existing automated test coverage is minimal.
|
||||
- Direct refreshes on newer frontend routes can return 404 until the backend gains a general SPA fallback.
|
||||
- Full Docker build context scanning on Rocky can fail on the container-owned `postgres/` bind directory; do not loosen its permissions.
|
||||
- The Faktiskā synthetic feed has no Valmiera observation; staging displays it as missing rather than substituting an unapproved station.
|
||||
|
||||
## Change log
|
||||
|
||||
|
||||
Reference in New Issue
Block a user