Read the statement by Michael Teeuw here.
MMM-aviationwx (Aviation weather)
-
@stephenmelody said in MMM-aviationwx (Aviation weather):
Also, this info differs from country to country, so I’d say keep it.
But you, as an interested user, would know those were the remarks, regardless? And by the format of the module itself, that line would always be the remarks. For the sake of space, I’m going to remove it. Let’s see if you miss 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.
Understood, but does the data (ex. IFR) tell you the same thing as the colored dot? Less coding for me if “IFR” is immediately recognizable and understandable by you.
You know my coding skills… but I was wondering if there might be any hints in the original module, as that pulls multiple codes.
Only what you’ve told me. :-) API’s don’t conform to one protocol when it comes to formulating a url for data. This is a different API. I was hoping you guys would do some of the leg work. :-)
What does a UK airport give you? Maybe EGLL or EGNX as the codes?
I was going to test those but at the moment, the API is down.
I hope this is not a sign that this API is unreliable.
However, I get the rest of the night off! :-)
-
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
-
Thanks for the work on this - I am a pilot in Europe so very interested in seeing the outcome.
Unfortunately like many others, my coding is useless to everyone ;-)
Thanks again.
Johnny -
@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:- Using of colored dot before ICAO code is a best solution (It’s more user-frendly than just a IFR/VFR etc.)
- For the remarks - I’m agree that the best way to remove that.
- 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:
-
And that for a detail view:
-
Finally a reasonable request…and an offer to help…
-
@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 NOSIGwind 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 T00221056Wind 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.
-
@stephenmelody said in MMM-aviationwx (Aviation weather):
What does a UK airport give you? Maybe EGLL or EGNX as the codes?
-
@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.
Not at the moment but I’ll let you know. Would I then be employed by the USAF? How big is their budget? ;-)
There is a universal coding standard for METARS in the Flight Information Handbook (FIH).
Uhh, I won’t be reading that. I’m just trying to make heads or tails of the requests being given here and the amount of data I have to deal with. FYI, I’m not a pilot. I’m a programming hobbyist.
Also, I’d stick to ICAO identifiers as they automatically include international.
Point taken.
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.
This url encourages me, although it brings me to a web page displaying the data instead of the API data itself. Can you find me a url that brings me to the actual API data?
This is what your url gives me
This is what I need
-
@320fan said in MMM-aviationwx (Aviation weather):
Using of colored dot before ICAO code is a best solution (It’s more user-frendly than just a IFR/VFR etc.)
Read what I asked of @stephenmelody regarding this. Allow me to start off simply, without having to code a colored dot for each Flight Rule. User friendly, sure, but I’m doing this on my own time.
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.
Again, I’m not willing, at the moment, to code every conversion. If the units are included in the data, that’s what you will get.
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:
If we’re going back to the beginning then this is what you asked for initially. With the exception of the green icon, that’s what I’ve done so far.
