Actually, English is required around the world for civilian flying.
Further, there is nothing which states that the METAR in the computer cannot stay OVC003 and then translate to the local dialect (which per ICAO is supposed to be English everywhere anyways)
Which can be done today, so I don't see the problem.
A lot. Currently there is a very limited set of categories for NOTAMs. Second, many NOTAMs which are geographic in nature (e.g. tower light out) are tied to an airport. In this day and age, NOTAMs should be tied to GPS coordinates. You also should support multiple NAVAIDs. I am sorry, but I do not want to read about VOR and NDB issues when flying WAAS. If WAAS is down, I am going to dial in a VOR and it is good enough to get me somewhere VMC or I am getting radar vectors.
That is just one example.
Go ahead and come up with some more then, because that's not a tech problem. That's a category problem. Publish a spec and add a category and give a little lead time and it's done. The underlying tech for transporting the data doesn't care, and the database schema is all that has to change.
Maybe a professional pilot and a few others can, but no GA pilot who does not fly for a living that I know can do what you are describing.
I know I sure as heck cannot do what you are describing, I also do not want to waste the years of mental energy learning how to do it. Foreflight based on you description makes a decent dent into it, but the reality is this should be built into the system.
I was no pro a little over a year ago and could do it, and it certainly didn't take me "years of mental energy" to accomplish it. I had to read the format to pass my Private exam just like anyone else does, back when nobody was making "translators" so you just did it. Instructor would sit during ground school and print off the stuff for a flight and you'd go over it, and they'd show you how to scan down a page of them quickly and effectively, and it's not that hard. Slide finger down page if you're lost I suppose, but you'd analyze a page full of them for winds (what's the general direction and highest speeds?), ceilings (it's easy to see where they're low in a page full of them), temps, etc. The old joke was the longer the line the more bad weather was happening at that station, but it's true. Extremely easy to see. I'd even go so far as to say if someone can't figure out how to scan a page of METARs for a route of flight in 30 seconds for the "interesting" weather, they're pretty darn lazy.
Lastly, I am pretty sure NOTAMs are not international standards. METAR and TAF yes, but not NOTAM.
Tim
Don't know. Doesn't matter much to me.
Still not seeing a "tech" problem. Seeing a human problem of entitlement attitude that scanning a page of data printed in text that's well-delineated with exactly the information you need, is somehow some sort of major "hardship", but completely in disagreement with that. It isn't that hard.
Yeah, if I see "GR" I'll probably have to look it up, but that station and surrounding station info is likely to look bad enough I can probably guess I don't want to fly in it if I don't need to, anyway. The first pass at a page full of METARs is just a go/no-go decision. You only need to focus in on a few stations out of an entire page for details after you've decided the weather is "go" or you know it's "go" only if a couple of stations don't have criteria behind the aircraft capabilities or yours.
If the entire page has piles of OVC and a bunch of those start with "00" there's a good chance I'm not taking that IFR flight for example. I'm not a fan of widespread weather that will force approaches to minimums at every airport within an hour of the destination airport in a no ice capability single. Others may do it all day and not care. Scan down the temp/dew points... yup, confirmed... they're all within a degree or two and temps are all just above freezing. Done. No-go. Took 20 seconds. Didn't have to decode squat. The numbers have away the end game before you even needed more information.