In addition to the API (using the API) there should be a simple web dashboard. Of course, with the API, people should be able to build their own (e.g., in Node-RED), but this is how I'll build mine.
quick list of stations heard recently (callsign-SSID)
map of stations heard recently (break out to new issue)
table of recently heard packets
filter by type (object, message, etc.)
table of recently sent packets
originated at digipeater
repeated by digipeater
plot (or at least table) of packets received/hr
any special info that will help people troubleshoot their RF issues?
heat map of received packets
may need to keep packets longer/periodically count by grid square to reduce data kept in the database
In addition to the API (using the API) there should be a simple web dashboard. Of course, with the API, people should be able to build their own (e.g., in Node-RED), but this is how I'll build mine.
- quick list of stations heard recently (callsign-SSID)
- map of stations heard recently (break out to new issue)
- table of recently heard packets
- filter by type (object, message, etc.)
- table of recently sent packets
- originated at digipeater
- repeated by digipeater
- plot (or at least table) of packets received/hr
- any special info that will help people troubleshoot their RF issues?
- heat map of received packets
- may need to keep packets longer/periodically count by grid square to reduce data kept in the database
Can take inspiration from https://www.prinmath.com/ham/talks/BPQ.pdf and other APRS clients.
Something like this (in current dw log going to frontail), but more interactive (sorting and filtering):
Something like this (in current dw log going to frontail), but more interactive (sorting and filtering):

Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In addition to the API (using the API) there should be a simple web dashboard. Of course, with the API, people should be able to build their own (e.g., in Node-RED), but this is how I'll build mine.
Can take inspiration from https://www.prinmath.com/ham/talks/BPQ.pdf and other APRS clients.
Oops, this is a duplicate of #10. Maybe this issue could be refocused on digipeater health and troubleshooting rather than replicating aprs.fi?
Something like this (in current dw log going to frontail), but more interactive (sorting and filtering):

Got index/status page stubbed out, and lists recent packets.