Read the statement by Michael Teeuw here.
MMM-aviationwx (Aviation weather)
-
@stephenmelody said in MMM-aviationwx (Aviation weather):
I’m interested!! I know what great work you do too @mykle1
Oh, you just had to get involved, Stephen? :-)
You know, there’s football on right now? :-)Here’s a little something to wet your whistle. “Whet” your whistle is incorrect. Evidently, you can “whet your appetite” but not your whistle. :-)
From left to right:
- Flight rules
- ICAO
- Wind Direction/Wind Speed/units
- Cloud List (first element)
- Temperature/Units/Dewpoint
- Altimeter/Units
Under that
- Remarks
-
@320fan said in MMM-aviationwx (Aviation weather):
And same for me - it’s just a hobby.
Sooooo, you’re NOT a pilot?
However, some posts above I’ve just shared my ideas/vision of this plugin (nothing personal ;).
I get it. I just hope you understand the magnitude of what you are asking for. :-)
In any case, thanks for your support in advance. I’m especially push this topic to find a persons, who will be interested in that too.
You’re welcome, and while I’m not that interested in aviation (although it is interesting) I am interested in learning new things and challenging myself by making MM modules.
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.
-
@Mykle1 I like how it’s switching between hectopascals and inches of mercury, as well as m/s and knots!
That was always the one thing missing on this module for me, international airports
-
@stephenmelody said in MMM-aviationwx (Aviation weather):
I like how it’s switching between hectopascals and inches of mercury, as well as m/s and knots!
According to @320fan, "Display of “Units” is mandatory due to different units in different countries. Happily for me, there was no conversion necessary on my part. Included in the data for each station are the units that apply for that station. And good thing, too, as I have no idea what the hell hectopascals are. :-)
That was always the one thing missing on this module for me, international airports.
Well, we aim to please. :-)
And just for the record, this is not that module. I chose to create my own rather than fork and edit the existing one.Ok, time for the two of you to contribute to the cause.
- Does the “Remarks” line need the word “Remarks”? Is it preferred or not?
- Flight Rules come before the Station, or after? Seems odd to me.
- Find/create/make/conjure me a url from the API that can fetch multiple ICAO’s in a single GET request.
That’s all, for now. :-)
-
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?
-
@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:
