Metreport & metsensor based on parsed METAR

[minsulander]

Metreport

This is a split from #11.
For non-AWOS airports.
The solution to #11 implements a METAR store and incorporates the metar-taf-parser library, so this should be doable using that.

See also #61 which is similar.

• Decoding of raw METAR ideally happening before being sent to Metreport/sensor window
• Calculating TRL depending on Airport and QNH (TopSkyAirspace.txt)

Maybe asking Juha for template how METARs are decoded in Topsky (as visible in MET messages window by right click)

Potential sources:
https://aro.lfv.se/Links/Link/ViewLink?TorLinkId=315&type=MET
https://aro.lfv.se/Links/Link/ViewLink?TorLinkId=314&type=MET
https://aviationweather.gov/cgi-bin/data/metar.php?ids=ESMQ,ESNQ&hours=3&order=id%2C-obs&sep=true
https://metar.vatsim.net/metar.php?id=all

(Faked) Metsensor

Possible data sources:

1. API: https://airportdb.io/ (limited number of calls, maybe storing information on server as with sun-met (with .json) instead, with possibility to manually trigger update data from API from admin panel?
2. Local DB: https://ourairports.com/data/

Inspiration for data parsing: https://github.com/epranka/runway-app

• Wind component
• QFE and QFETHR
• Winbox custom control button to switch between RWYs on airports with several RWYs (to show wind component etc for relevant RWY)