The fallback palette used for channels that are not Meshtastic presets was
built out of pastels, which are unreadable against the light OSM tiles. Six
of the nine entries scored under 1.6:1 contrast on the map: #fffac8 at
1.06:1 and #aaffc3 at 1.18:1 were effectively invisible, leaving only the
white marker outline showing.
The underlying issue is that one color feeds two opposite backgrounds. The
marker fill sits on light map tiles, while the filter label is text on the
dark Bootstrap panel. The old palette was calibrated only for the panel.
Replace it with 12 colors chosen by a search over HSL, constrained to clear
3:1 contrast against both backgrounds, stay at deltaE >= 30 from every
channelColorOverrides preset, and deltaE >= 20.9 from each other. Saturation
is capped at 80% to keep out neon tones that would collide with ShortTurbo.
Growing the palette from 9 to 12 entries is safe: the index is derived from
palette.length rather than a fixed number.
NODEINFO_APP is the better / authoritative source for a nodes primary channel.
MAP_REPORT_APP packets can arrive on a different MQTT uplink channel and
are unconditionally overwriting the channel set by NODEINFO, causing
nodes to appear on the wrong channel in the map and channel filters.
now MAP_REPORT_APP only sets Node.channel when it is not (yetw) known,
making it a fallback rather than an override.
* add world meshview tag
* small map change
* Add relay_node field to PacketSeen model and update template for display
* Add migration script to introduce relay_node column in packet_seen table
* Adapt PR 102 relay node display to packet page
* Added DB configuration and snapshot for basic detaisl
* update schemma
* fix ingestion error
* fixed the db and added more reporting
* 1
* Fix MQTT store bug.
* changes to reports
* more changes to report
* update latest list of instances
* Update protobuf
* remove file
* add channel to firehouse
* Add filter to firehose
* filter at chat.html
* remove duplicates from nodes in net.html
* add note bottom of page
* fixed issue reported on issue #143
---------
Co-authored-by: Paul Picazo <paul@picazo.com>
