Diesel

I'd love to port it to Android... just no time for that in the foreseeable future. It was just the luck of the draw that the class was iPhone programming and not Android programming. I hear Android is much less code. The fact that your METARs are out of date is strange. That shouldn't be the case, and I'd really like to fix that if it is. Please message me your airfield and when it is happening. I suspect it's just a bad internet connection and not downloading the METAR and so you just have an old update (And my app doesn't give feedback if this happens, which is bad). I should put a "last updated" time on the METAR in addition to the METAR's effective time so you know if it actually successfully downloaded the METAR. I just simply grab the METAR from this site which I have found to be up to date: http://weather.noaa.gov/pub/data/observations/metar/decoded/

Thank you! Appreciate all the feedback, and I will try to make it better as time goes on and add features which people ask for. Yah, so I'm not sure if it's correct to accept a K in front of it, but the site of METAR text files has it. http://weather.noaa.gov/pub/data/observations/metar/decoded/ Thank you for this! I had introduced a bug which removed all IATA from my airfields databases, so when you searched 4M3 it did not show up. I fixed it and will put out a new database soon with the new App. You should be able to search 4M3 or K4M3 and get the same "airfield". I tried to create a database that relied only on the FAA NASR 56-day subscription to update US Airfields, but it was missing a lot of small airfields. So I think it will continue to populate with old airfields as well as new. I will add an error if the METAR is not current for the given date. What do you think? One day old? One week old? I will give a pop-up dialog on the METAR page when the airfield is opened, unless you have a better idea. That is a mistake as well... when coding I threw this error in because of how I used to get NOTAMs, but I changed this so an update would not be needed if the NOTAM server changed something, so this isn't a factor. I forgot to remove the error (Which is produced because the NOTAM site comes back with an error due to the airfield not existing). I think I will either just leave the NOTAM list blank or change the title of the field to NO NOTAMs instead of the time or add one NOTAM field which states that this airfield has no NOTAMs. I'm pretty sure it does pull FDC. I checked KOMN and got FDC 4/4947 NOTAM. I don't think it does Flight Restrictions though. I would like to add that! Thanks! You helped me find 2 bugs by using it in a way which I, and my friends, don't often use it. I'll put out an update in a week or 2 (depending on Apple's approval time) which will at a minimum let you search for IATA (Already fixed) and give you information on the expired METAR (waiting for feedback on that). New App is up to Apple for Review. Should fix your issues!