planner: add the Wind data layer - #2349
Merged
Merged
Conversation
The Wind layer reads the shared climate archive. The map colours each cell by the mean daytime speed of the week and draws one arrow per cell for the most frequent direction of the month: thicker when the wind is steady, double-headed for two opposite winds. Arrows thin out at low zoom. The year slider and the profile strip show the chance of headwind for the travel direction; the point chart shows ten years of weekly speeds and the wind rose. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
A route now reads only overview tiles. The point chart reads the detail tile of its point through a reactive cache in the shared climate source, and its weekly grid appears when the tile arrives. A failed tile load while drawing the map sets the layer error and retries on the next move. The map paints a cell only from a mean of 2.5 m/s, so calm weeks show the arrows on the plain map. The arrows are slim and white on a thin dark halo. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Weather now reads detail tiles on demand through detailCell as well, so a route of either layer reads only overview tiles. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Wind layer reads the shared
climatearchive. It follows the owner decisions in #2329.windRow), with the label line. Without a route, the track is empty.WindRose.sveltein theextraslot). The headline and the rose read the overview tile. The weekly grid appears when the detail tile of the point arrives.Legend.marks).openClimatekeeps one source per archive URL for Weather and Wind.detailCellreads a detail cell from a reactive cache of decoded tiles and starts the load of a missing tile. Both layers now use it for the point chart (and Weather for the night labels), so a route reads only overview tiles.specTilemoves totest-support/planner/climate-tiles.tsfor the climate and wind tests.Measurements
Local preview of the Baden-Württemberg data with the BW climate archive:
test:plannerbudget: unchanged (the request test has no climate archive).Checks
npx vitest run src/lib/planner/ src/components/planner/: 202 tests pass.svelte-check: no new findings (the 15 remaining errors are the unbuilt wasm packages).npm run test:planner: pass.obc suites check,obc prose --check: pass.Pending owner choice, not in this PR: branch
claude/planner-wind-straight-doubledraws a double arrow as one straight line on the mean axis of its two directions.Public docs changed: no
Requirements: none
🤖 Generated with Claude Code