@stephenmelody I should clarify… do you have this working on a raspberryPi? I think I saw that your device isn’t Pi based…?

@cowboysdude Do you have this working? I’ve been using AlexaPi but it’s not really been that effective. It’s very slow and doesn’t always listen…

@Mykle1 I don’t know what’s going on with it, I’m not Linuxy enough to work out how to find the problem. It’s basically ok for a day and then I come down stairs in the morning and it’s unresponsive, no ping, ssh, anything on the screen so I have to pull the power.

I’m wondering if I’ve got it doing too much, it’s got MM, Alexa and Face recognition all going on. I’m also slightly suspect about the power supply to it being part of the issue.

If you have any hints of where I could start, please let me know… I don’t fancy rebuilding it from scratch… :(

I’m planning on pulling this down at some point soon… just having some stability issues with my raspberry pi at the moment. It keeps crashing on me every 12-24 hours…

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

@Sean Thanks!! I’ve just emailed you the details!

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!!!

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?

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

the format on that image is:

Wind direction @ wind speed: 220@05kt
Visibility: 10SM 10 statute miles
Sky Coverage: OVC - overcast, BKN - broken etc…
Cloud base: 150(00)ft
Temp: 10 degrees C
Dewpoint: -1 degrees C
Time of the report in 24 hour clock: 20:51

I’d say (personal opinion) that the pressure/altimeter setting isn’t that important. I’d prefer to keep the additional information, if you look at FDY and TBR above, they have:

-RA which is showers of rain
BR - which is fog (or haze, I can’t remember… 70% sure it’s fog, either way you can’t see through it well)

That to me is more important that the altimeter setting.

I can look for other examples if that would help?

10 degrees C temperature / -1 degrees C dew point (time of report)

Is it in a CSS file? That way I’m guessing people could self-configure?

Here’s what the original module is using and it looks like the below.

.vfr {
  color: green;
}

.mvfr {
  color: blue;
}

.ifr {
  color: red;
}

.lifr {
  color: #f0f;
}

Blue looks ok through my glass, so I don’t see any issue with that.

@sean do any of your modules cater for events created in other timezones than the calendar?

I’m using a ICS from Office365.

@allebone @Mykle1

This would give you the NOTAM information…
https://www.npmjs.com/package/notams

METAR / TAF:
https://www.npmjs.com/package/metar-taf

https://www.npmjs.com/package/metar-js

Don’t know if they help…?

@allebone - what colour scheme do you use for IFR/VFR/MVFR/LIFR? Personally I prefer the alternative one that I have called out above.

@Mykle1 - no problem, always here to make life harder :-D

Here’s another option that might be of interest, as it’s JSON format…

https://www.icao.int/safety/iStars/Pages/API-Data-Service.aspx

@Mykle1 It’s not great in that it doesn’t have full global weather either, so to the original requester’s requirements, it wouldn’t do the job anyway. the AVWX API looks to be better in that regard.

WRT flight conditions, this differs from country to country, the UK typically only reports 2, VFR or IFR. The US seems to have 4 (which is what I’d go with, i’ve never seen anything more that these 4):

VFR
MVFR
IFR
LIFR

There’s also two types of colour schemes, many pilots use the Alternative (I fly on alternative), so being able to configure this would be perfect…

Standard: VFR-Blue MVFR-Green IFR-Yellow LIFR-Red Unknown-Grey

Alternative: VFR-Green MVFR-Blue IFR-Red LIFR-Magenta Unknown-Grey

Would the text coloured per the rules work the same as a coloured circle? Yes - although a circle would be better for screen real estate I would imagine…

I’m also having this issue. Meetings organised in different timezones appear as if they were organised in my timezone.

So if a meeting was scheduled at 17:00 GMT, it should be 12:00 EST, but it’s showing as 17:00 on my calendar.

I’m using an ICS file from our company office365 account.

@michmich - perhaps you have some insight?

@Mykle1 Here…

https://aviationweather.gov/gis/scripts/MetarJSON.php

or maybe this:

https://aviationweather.gov/gis/javascript/Metars.js

However - the php file only seems to give North American and some random METARs, not the same coverage as that webpage gives… weird I know right?!

Also - the us gov doesn’t give local units like the avwx api does, so you have to make a leap of faith as to what it’s showing.

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

Anything I can to help? Im actually an Air Force aviator trying to get a module like this for our Operations Center.

There is a universal coding standard for METARS in the Flight Information Handbook (FIH).

Also, I’d stick to ICAO identifiers as they automatically include international.

If you use the API from NOAA: https://aviationweather.gov/metar/data?ids=Rodn&format=raw&date=0&hours=0, the results always come imperial.

Bryan

Hey Bryan,

That last bit isn’t strictly true… the NOAA API will give you locally used units, not always imperial.

for example, pull the NOAA API for EGNX (UK), you’ll get:

EGNX 201650Z 25012KT 9999 BKN042 12/10 Q1010

Windspeed is in Kts, viz is in Metres (9999m or 10km+), Pressure is in hPa (Q for QNH 1010hPa).

UUDD (Russia):
UUDD 201700Z 13002MPS 9999 OVC025 01/M02 Q1011 R88/190095 NOSIG

wind is in m/s (130 degrees at 02m/s) and viz in metres, pressure in hPa (Q1011).

KPIT (USA):
KPIT 201651Z 21012G18KT 10SM SCT250 02/M06 A3013 RMK AO2 SLP221 T00221056

Wind in kts (210 @ 12kts, Gusting to 18kts), viz is statute miles (10SM), pressure in inHg (A3013).

So you do need to know the units you’re dealing with, which is nice with the avwx api, as it gives you the units.

I don’t know of anywhere that uses F for temperatures, it always seems to be Celcius, with M indicating minus so for PIT above, Temp = 02 degrees C, dew point Minus 06 degrees C.

Here’s my thoughts, but they’re just preferences.

RMK stands for Remarks, so having it show “Remarks: RMK…” is a little redundant. AO2 just means it’s automated. Also, this info differs from country to country, so I’d say keep it.

Flight rules tend to be a coloured dot (as per the original code) so it’s often common for that to be first, at least in the US.

You know my coding skills… but I was wondering if there might be any hints in the original module, as that pulls multiple codes.

What does a UK airport give you? Maybe EGLL or EGNX as the codes?