MMM-aviationwx (Aviation weather)

[Mykle1]

@320fan said in MMM-aviationwx (Aviation weather):

https://avwx.rest/api/metar/uudd

Data before being displayed by MM

[320fan]

@Mykle1 Yea, I have seen these data for both METAR/TAF: it’s a pure JSON which may be (I hope) easily adopted for that module. If you may adopt initial module with a new data source, it will be very nice.

For the empty fields, which contains no data logic is very simple: no observation/forecast=no data in the fields.
For the TAF report it seems that you must follow all elements of the “Forecast” array and display it like:
“Start-Time”/“End-Time”, “Type” (in case of BECMG or TEMPO);
“Wind-Direction”, “Wind-Gust”, “Wind-Shear”,“Wind-Speed” - if they are presented;
“Visibility”;
“Cloud-List”;
and last but do not least:
“Icing-List”;
“Other-List”;
“Probability”.
Or you just can follow each “Raw-Line” element of “Forecast” array (this is ok for me, but I’m not sure about all others person, who would like to use this module).

[Mykle1]

@320fan said in MMM-aviationwx (Aviation weather):

it’s a pure JSON which may be (I hope) easily adopted for that module.

JSON data, for me, is most easily used. :-)

If you may adopt initial module with a new data source, it will be very nice.

I usually don’t take someone else’s module and modify it, preferring to create something of my own. Especially, as in this case, where the author has specific license requirements regarding the use of their code

Or you just can follow each “Raw-Line” element of “Forecast” array (this is ok for me, but I’m not sure about all others person, who would like to use this module).

Oh, I don’t think that is a problem. I don’t know any other pilots that have been asking for this type of module.

Question: Do you prefer the data to be displayed one object at a time, rotating through each? Or do you prefer all the objects displayed simultaneously (static)?

[320fan]

@Mykle1 I think that the best way to show all objects simultaneously. But that will be good only if all information can be fitted in the one screen.

[320fan]

So, I tried to make a “tech spec” for a new module. It’s very briefly and dirty, but we can start with that.

displaying of the METAR:

1. Symbol for the “Flight-Rules”: VFR/IFR/etc. You can take samples from MMM-aviationwx.css file of the MMM-aviationwx module.
2. IATA/ICAO Airport code. IATA - three symbols “Station”, ICAO - four. Best way to make that configurable (to show IATA/ICAO/Both). I think that the best way to put this conversion table inside new module.
3. Time of METAR observation. Be carefull, “Time” field is in Zulu time (GMT+0). Need to be cofigurable: to keep initial (Zulu time) or convert that to the local time based on timezone.

For the datafields below I propose to make a possibility to see a “brief format” or “full data” . It must be done via config.

For a brief format:
4.1) “Wind-Direction”,“Wind-Gust”,“Wind-Speed”,“Wind-Variable-Dir”: Best way to show that like “Wind-Direction”/“Wind-Speed"G"Wind-Gust” “Wind-Variable-Dir"V"Wind-Variable-Dir”…
Display of “Units”/“Wind-Speed” in current case is mandatory due to different units in different countries.
4.2) “Visibility” (with “Units”/“Visibility”)
4.3) “Cloud-List”: display all (or just first? make configurable?) layer of clouds. You can keep that “as is”, for example BKN030 means BroKeN clouds at 3000 ft.
4.4) “Temperature”/“Dewpoint” (with “Units”/“Temperature”)
4.5) “Altimeter” (with “Units”/“Altimeter”). Make that field configurable (show/do not show).
4.6) “Remarks”. Make that field configurable (show/do not show).

For a full data format - it must be done using “Raw-Report” fiels. In that case you just need to clean up ICAO 4 letter code and Time from “Raw-Report” and display the rest part of this field.

displaying of the TAF:

1. Showing of TAF must be configurable (show/do not show).
2. I propose to display TAF one line below METAR, without repeating of “Flight-Rules” and “Station”.

And here we can make a “brief format” or “full data” like it was above.

For a brief format:
3.1) Each time group of “Forecast” array must be displayed in the new string (tbd).
3.2) “Start-Time”/“End-Time”, “Type” (in case of BECMG or TEMPO);
3.3) “Wind-Direction”, “Wind-Gust”, “Wind-Shear”,“Wind-Speed”, so like it was above for METAR.
3.4) “Visibility” the same
3.5) “Cloud-List” the same
3.6) “Icing-List”,“Turb-List”, “Other-List”;
3.7) “Probability”

For a full data format - it must be done using “Raw-Report” field same as above.

[320fan]

+some ideas regarding layout may be taken here (this is my lovely AeroWeather app for iPad).

[Mykle1]

@320fan

Whoa!

You’re not asking for much. :-)

Let me be as clear as possible here. This is my hobby. I do this for the fun of it. I will see what I can do, as time allows. I make no promises, meaning it may never get done. If it gets done, it may not be to the small amount of specifics you outlined above.

[320fan]

@Mykle1 hi. Yea, I’m fully understand that. And same for me - it’s just a hobby. However, some posts above I’ve just shared my ideas/vision of this plugin (nothing personal ;). In any case, thanks for your support in advance. I’m especially push this topic to find a persons, who will be interested in that too.

[stephenmelody]

I’m interested!! I know what great work you do too @mykle1

I’m a private pilot so already have this module on my screen but I fly transatlantic quite often so seeing UK airports would also be helpful!

Cheers,

Steve.

[Mykle1]

@stephenmelody said in MMM-aviationwx (Aviation weather):

I’m interested!! I know what great work you do too @mykle1

Oh, you just had to get involved, Stephen? :-)
You know, there’s football on right now? :-)

Here’s a little something to wet your whistle. “Whet” your whistle is incorrect. Evidently, you can “whet your appetite” but not your whistle. :-)

From left to right:

• Flight rules
• ICAO
• Wind Direction/Wind Speed/units
• Cloud List (first element)
• Temperature/Units/Dewpoint
• Altimeter/Units

Under that

• Remarks