MMM-aviationwx (Aviation weather)

Mykle1

@stephenmelody

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

EDIT> My bad, that’s miles

Mykle1

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

Is it outside of the US where viz is usually XXSM?

I thought that was the whole idea for this module, that it would be international, yes?

stephenmelody

Russian Viz is in metres, so they’d want to see 1500m I’m guessing.

That’s the problem, you’re creating the ability to call weather from international airports but each country / region reports differently. The good thing with AVWX is it tells you the unit to use, so you could just append after the value the unit identifier, so in your example you have:

 "Visibility": "9999",

and in the units section:

"Visibility": "m",

so you could concatenate it to be:

visibility: 9999m

Does that make sense? Have I answered the question?

stephenmelody

The three main differences I know of are:

USA reports altimeter in inHg, rest of the world is hPa (or mb, which is the same thing).

USA Reports viz in Statute Miles, rest of the world in Kilometers

Russia reports wind speeds in Metres/Second, rest of the world in Knots. (they also report altitude in meters above the ground and the rest of the world uses feet above the ground (or sea level, that also depends…)

That’s when flying becomes fun, so in the UK, you fly at an altitude in feet, a speed in knots (nautical miles per hour) and with a visibility in kilometers… talk about mixing up units!!!

Mykle1

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

Does that make sense? Have I answered the question?

Yup, I’m on it

Mykle1

So, it just dawned on me that the Raw-Report data looks pretty much like what I’ve been trying to achieve piece by piece, according to all of the wishes in this topic, aside from the order and the formatting. Shrug

Raw-Report: UUDD 220230Z 32003MPS 9999 OVC014 00/M02 Q1005 R32L/520295 NOSIG

Anyway, the flight rules have been converted to alternative color coding and are working. I can add the standard color coding at another time, via config option, so you can choose one or the other. The units will also will come from the data. The only time coming from the data is in Zulu time. It does not say if that is the time of the report.

Do you want a second line of data? Would you rather a single line as you’ve shown above?

Most importantly:

Someone needs to figure out how to call multiple ICAO’s in a single request. This would make my job a whole lot easier. Do I have to do everything? ;-)

@allebone said:

This is amazing collaboration.

So, collaborate already! ;-)

https://avwx.rest/api/metar/uudd only gets data for a single ICAO, uudd.

EDIT
I contacted the API. Only one station per request. Of course! I’ll think of something.

Mykle1

Here we encounter another problem with the “Remarks” line. It is not always the same length. When it is longer it wraps and looks messy. I could trim the data but that defeats the purpose. How set are we with having the remarks line?

Mykle1

Standard and Alternative color coding is now a config option

Mykle1

So, I keep flip-flopping with API’s. I’m not thrilled with aviationweather.gov but it does allow me to call multiple international stations in one request. However, there are differences in what each API offers. Until I can figure out how to make multiple requests to avwx.rest/api then this will have to do. When I do figure that out I intend to use the avwx.rest/api

Caveat

You can enter up to 8 international station ICAO’s. However, only stations with observation times within the last hour will be displayed. For instance, if KJFK has 2 observations within the last hour, then both observations will be displayed if there is an older observation among your other stations. In any case, the stations will order themselves by observation time starting with the most recent at the top.

Question: Remove the kt from wind speed? This API only provides kt.

Question: Remove the C from temperature? This API only provides C

Question: Any desire to have this module occupy the bottom or top bar where each station (one at a time) will span the entire width of your display? Ex, below the newsfeed module. I’m thinking a single line that can contain ALL of the data (raw data included) and you choose the amount of time each is displayed. Just a thought.

stephenmelody

I’d be surprised if the gov api is converting reported units to kts… I can have a look at this later and see if that’s really the case, or if it’s just providing values.

C can go as all temps are reported in celcius, that’s the only bit that I think is common!!

Have you tried emailing the guy at avwx?

https://avwx.rest/contact

He might be able to help

Mykle1

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

Have you tried emailing the guy at avwx?

I did. That’s how I know I can’t use a single url for multiple stations (as in aviationweather). It’s my own lack of coding capability that prevents me from making multiple calls to that API from within the module. Help with that will have to come from this forum or somewhere else, not the API.

I’d be surprised if the gov api is converting reported units to kts

The data says, wind_speed_kt

Mykle1

“C” removed

Individual coloring of each line made easy for easier viewing.

Still trying to work out the problem with /avwx.rest/api

320fan

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

Remove C from temperature? - yes, indeed. We just need to be sure that all data in C.
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…
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:
?
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.

Mykle1

https://youtu.be/zAImRnR9HsM

Mykle1

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

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.

I think, in the interest of mirror real estate, I will leave out the raw data for now. IMHO, an MM module is not meant to occupy all, or much of the display, as an iPad app would do.

Is there any possibility to align it by the next way:

I am not using a table in the module (I don’t know how) so alignment is tricky. I’m doing the best I can.

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.

Agreed, and it will remain, as long as the data provides it.

Eventually, I’ll learn how to make multiples calls within the module. Then I can use the API of choice. For now I am battling with xml data of aviationweather.gov

Mykle1

Ok, time for testing. Both of these modules are using aviationweather.gov for reasons explained above. I will learn how to make multiple requests within the module and move to avwx.rest/api, eventually.

Most like original in appearance and does allow for international ICAO’s.
https://github.com/mykle1/MMM-Pilot

{
	disabled: false,
	module: "MMM-Pilot",
	position: "top_left",
	config: {
		ICAO: "KJFK,EGLL,UUDD,EDDT,RJAA,ZBAA,LFPG,LIRF", // Any 8 International ICAO's
		colorCode: "Alternative", // Standard or Alternative
		updateInterval: 10 * 60 * 1000,
		useHeader: false,
		header: "",
		maxWidth: "400px",
	}
},

Mykle1

A new spin on the display and does allow for international ICAO’s.
https://github.com/mykle1/MMM-WISP

{
        disabled: false,
	module: "MMM-WISP",
	position: "bottom_bar", // you could try top_bar and thirds
	config: {
	        ICAO: "KJFK,EGLL,UUDD,EDDT,RJAA,ZBAA,LFPG,LIRF", // Not limited to 8 International ICAO's
		colorCode: "Alternative", // Standard or Alternative
		useHeader: false,
		header: "",
		maxWidth: "100%",
	}
},

Area 49

@Mykle1,

Thanks for your work on this!

I just installed Magic Mirror and started looking around for an aviation weather module that included Alaska. I just now stumbled on this thread, and see that your work should include the airports that I want in my list. I’ll install and test it as soon as I get a chance.

Mykle1

@Area-49 said in MMM-aviationwx (Aviation weather):

I’ll install and test it as soon as I get a chance.

Great! Let me know how things go. Use the four letter ICAO for each station you want to see

Area 49

@Mykle1,

Looks like there is a dependency required - from my PM2 error log file: Error: Cannot find module ‘xml2js’

I’m just getting started figuring out Linux, Git repository, and Javascript, so I’m not sure where to find - and under what directory to install this dependency.

Is this the one to install? https://github.com/Leonidas-from-XIV/node-xml2js

Thanks