fix(weathermap): exclude faint returns and resize-inflated coverage - #733
wafflestomper08 wants to merge 4 commits into
Conversation
|
@tavdog Could you review this change when you have a chance? I added handling for intermittent provider HTTP failures: with significant-weather filtering ON, a failed metadata or radar-tile request now returns no content instead of displaying the error screen. OFF preserves existing behavior. Simulated HTTP 503 tests passed for both failure points with the toggle ON/OFF; lint, app check and a live render also passed. This remains draft for rollout safety: the intensity filtering still depends on tronbyt/pixlet#480 being released and included in the server. Thank you! |
|
Cheers, @tavdog . The new functionality is reliant on PR #480 being approved, merged, and bundled in an updated server release. I'm in Portland, too. I've got the changes live on my own server and it's much improved for this time of year when there's some light cloud cover in the area but no notable precipitation. |
Summary
Make the optional significant-weather filter discriminate between meaningful radar returns and faint clutter:
[]behavior. Recommend 5–20% and explain the exclusion of very faint returns/very light drizzle.Dependency / rollout
Depends on tronbyt/pixlet#480.
This is intentionally a DRAFT: the new
retain_originalandcolor_pixel_percentagePixlet API must be merged, released, and included in Tronbyt server before this app change is rolled out. The ON path requires that runtime; merging the app first could break filtering on older servers. This is a server/Pixlet requirement, not display firmware.Validation
pixlet check --max-render-time 3s apps/weathermappassed.Palette source: https://www.rainviewer.com/files/rainviewer_api_colors_table.csv
Radar reflectivity is not a guarantee of precipitation reaching the ground. This intentionally excludes very light drizzle, while retaining stronger rain and snow echoes.