MMM-aviationwx (Aviation weather)

Mykle1

@stephenmelody

How would I denote visibility if this is the data ?

Visibility:1500

Simply 1500? v1500? vis? other?

stephenmelody

Do you have an example airport you’re getting that from? Is it outside of the US where viz is usually XXSM?

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