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.

Hi all.

Just want to recall that old topic, which still actual for some of us
So, I made iCloud sync with calendar and birthdays (the second point was a little bit tricky, but it works now).
But, the last stone still without any movement - iCloud reminders:

• tried to do that with vdirsyncer: as result, I got an empty file without any reminder (tried many different setup)
• tried to search for any other suitable ways: different scripts, etc. Nope.

Maybe Is there any options to do it now?

Thanks in advance.

@Mykle1 Okay, no problem. Thanks.

@Mykle1 Hi again.

Yea, 29.91Hg.

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

pressure must be like xx.xx (not like xx as it is)

Tell that to the API. That’s the data being given. I just display it.

For example:

https://aviationweather.gov/adds/dataserver_current/httpparam?dataSource=metars&requestType=retrieve&format=xml&stationString=UUDD&hoursBeforeNow=1

altim_in_hg 29.911417/altim_in_hg

I think that this API converts pressure in hPa from raw_data (like Q1013) into hg by simply dividing by coefficient.

• one moew issue:
  

Datas from: https://aviationweather.gov/adds/dataserver_current/httpparam?dataSource=metars&requestType=retrieve&format=xml&stationString=UUDD&hoursBeforeNow=1

raw_text
UUDD 071630Z 34005MPS 9999 BKN022 M04/M08 Q1009 R88/520295 NOSIG
/raw_text

sky_condition sky_cover="BKN" cloud_base_ft_agl="2200"

It must be BKN022, not BKN2200.

@Mykle1 Hi again.

As I can see you continue to improve your mode - thats fine, thanks. Now I’ve some time for tests of this updated module. My points are:

1. No possibility to set custom number of airports for the “Static” view: for example, line like:

ICAO: "UUDD,UUWW,UUEE,UUOO,UWKD,URMT,ULLI,UWWW",  // separated by comma only

works fine (8 ICAO codes), but when I’m decrease/increase number of ICAO codes it doesn’t work: “Loading PilotWX…” and thats all.

2. My next proposal is to remove line “Station Conditions” for the Static view. It’s a little bit pointless

3. For the “Rotating” view: the whole text alltime yellow. How I can change that?
   

3.1) For the “Rotating” view: pressure must be like xx.xx (not like xx as it is). In aircraft you must use all four digits for all the time. But for me - pressure in hectopascals (like 1019, without digits after comma) better in any case. Hovewer, in any case 1 hg = 33.863886666667 hPa. hg used for US airports at all the time, for EU/RU airports - hectopascals are the standard.
3.2) And the last one regarding pressure - it’s nice to have it for a “Standard” view too - it’s a really important information.

4. About time, which I can observe in the end of the line (tt:tt): I would ask you to display a UTC (Zulu) time, not a local time. So, thats the standard of METAR/TAF In that case you display it like (ttttZ) or (tt:ttZ), and Zulu will be a remider for that.

5. Thanks for visibility in KM, thats very usefull. And to have a same view - please, change speed in knots as “KT”, not a “kt”.

6. For the “Loading PilotWX…” message - I would like to propose next code:

        if (!this.loaded) {
            wrapper.classList.add("wrapper");
//            wrapper.innerHTML = "Loading PilotWX . .";
//            wrapper.className = "bright light small";
              wrapper.innerHTML = (this.loaded) ? this.translate("EMPTY") : this.translate("LOADING");
              wrapper.className = "small dimmed";

            return wrapper;
        }

In that case this module will take into account locale settings for correct displaying of “Loading” message.

7. In case of no cloudbase layer classification (like "BKN/OVC/etc.) you may see a OVX text:
   
   Thats not correct; the reply from server in that case is: sky_condition sky_cover=“OVX” cloud_base_ft_agl=“0”

The right way - to display data directly from a string, as example:
raw_text> URMT 071330Z 32006MPS 0650 0550NE R25/0800N +SHSN VV002 M01/M01 Q1010 R25/290255 NOSIG RMK QBB080 OBST OBSC QFE719 raw_text>

• VV002 means vertical visibility in hundred of feets or QBB080 means vertical visibility in meters (this code not applicable for all airports).

8. And if case of aligment to the right:

               {
                        module: 'MMM-PilotWX',
                        header: 'Aviation weather',
                        position: 'bottom_right',
                        disabled: false,
                        config: {

the whole layout is shifted to the right; Is it possible to align/to stretch all elements like for the “Weather forecast” plugin?

9. Is it possible to use a same font/font size, like for standart modules (like "calendars, “weather”, etc.) to keep a same view for the whole mirror? It’s not a big deal, but in that case we can make a mirror looks more “arranged”.

And last, but do not least: @Mykle1, thanks again for your job.

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

Hi again,

Sorry for my long absence, I had really tough week of flights,and now I’m have 1 day off Seem that you made a very good job with new module and I have seen that some questions were in place. So, just some of my opinions on these questions:

1. Remove C from temperature? - yes, indeed. We just need to be sure that all data in C.

2. Remove the kt from wind speed? The best way to keep initial units of measure (m/s in RU, kts in other contries from example). But, as I undestood, thats depends on API…

3. About remarks: first, just to recall - best way to have them to be configurable (to have options to display them/not display them at all). And for me - best way to keep the whole RMK field. Is there any possibility to align it by the next way:
   ?

4. Also, I would ask you to keep digits after OVC/FEW/etc - it’s a important information, which means a top of clouds. I’ve just seen that on the last screenshoots this information is missing.

If you have any additional questions - please, let me know.
And thanks you again for your job.

And that for a detail view:

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

Sooooo, you’re NOT a pilot?

I’ve just mean that building of the MagicMirror is my hobby, but the aviation is my profession ;). I’m the Airbus driver in our real world.

This is a bit of a cheat (at the moment) but here are two instances of the module at the same time, one showing UUDD data and the other showing KJFK data.

It’a good step forward in the right direction!
So, just some comments from my side:

1. Using of colored dot before ICAO code is a best solution (It’s more user-frendly than just a IFR/VFR etc.)
2. For the remarks - I’m agree that the best way to remove that.
3. About different units - it’s nice to have a possibility to convert all units in the one base, but that request is not mandratory. In any case I can provide simple formulas for coversion of hPa into Hdg, F to C, kt to m/s and etc.

And if we going back to beginning: could you please make for the brief data format something like that from my lovely iPad AeroWeather application? This app is very popular for the pilots and it wiil be nce to keep more-less same base:

@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.