MMM-aviationwx (Aviation weather)

Mykle1

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

@mkyle1 - Great job on the module, it looks superb. I’ll be adding it to my mirror very soon.

Thanks, I appreciate that. I did it as a request from a user so forgive my lack of aviation understanding.

Typically winds reported at xxx degrees at yy kts and shorthand would be 260/05 rather than @.

That’s easy enough to fix. I’ll take care of that. Maybe even as soon as tonight.

As far as the Statute Mile/KM situation is concerned. The API only provides Statute Mile (SM) in the data. I didn’t do any conversions because I was going to move to another API that provided both, making it easier to give you a config option and a whole lot less coding for me. However, I will look at it again and see what it involves. Worst case scenario you’d have to wait for my moving to the other API but I can’t tell you when that would be. :-)

Mykle1

@XT16Johnny

Just in case others want the @ symbol as a separator between wind speed and direction I made it a config option.

sym: "@",  // or sym: "/",

Result:

So, for those interested, you can do a git pull in the MMM-PilotWX directory to update or download and install as usual.
https://github.com/mykle1/MMM-PilotWX

Mykle1

@XT16Johnny

I wouldn’t have a clue what a Statue Mile looks like out of the window!

cowboysdude

Can it do this? ¿

Mykle1

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

Can it do this? ¿

HAHA :-)

cowboysdude

@Mykle1 IN PURPLE? BUT just on Fridays and Wednesdays…the other days I want it blue. Well unless the wind is blowing from the west then I need it hot pink or orange…no wait orange is for the days it’s blowing from the east at 2.2mph…

Can you do that? Thanks! LOL

Mykle1

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

Can you do that? Thanks! LOL

I can, but I didn’t. ;-)

However, I did make a config option for Kilometers if you would rather that than Statute Miles for Visibility. :-)

So, for those interested, you can do another git pull in the MMM-PilotWX directory to update or download and install as usual.
https://github.com/mykle1/MMM-PilotWX

I don’t know what the standard for this type of display is but it seems to me that 260/6kt is easily readable, whereas 3KM for visibility is not. Would not 3/km be better? Or is that not what you pilots are used to? Please clarify. Thanks. :-)

cowboysdude

@Mykle1 Why Thanks!

320fan

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

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.

My next proposal is to remove line “Station Conditions” for the Static view. It’s a little bit pointless ;)
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.

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.
Thanks for visibility in KM, thats very usefull. And to have a same view - please, change speed in knots as “KT”, not a “kt”.
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.

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

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?

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.

320fan

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.