[Woc-notify] [AWS 0011726]: Modify "Local Forecast" search form

Mantis Bug Tracker noreply at newadmin.awids
Wed Jul 25 15:33:36 UTC 2012


The following issue has been ASSIGNED. 
====================================================================== 
https://mantis.awids/view.php?id=11726 
====================================================================== 
Reported By:                Rob Sallee
Assigned To:                Dan Vietor
====================================================================== 
Project:                    AWS
Issue ID:                   11726
Category:                   22.1.1) ADDS
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             07-11-2012 20:19 UTC
Last Modified:              07-25-2012 15:33 UTC
====================================================================== 
Summary:                    Modify "Local Forecast" search form
Description: 
Need to come up with a join maybe?  Or a two-tier lookup?  Probably need to
put the NavAids Table back into the mix some how.

Scott Kimbro scott.kimbro at koride.com
	
2:48 PM (30 minutes ago)
		
to NCEP

Robert:

 

Thank you for the prompt response.  I went back and tried the large
airport codes and those do seem to be working.  However, up until
recently, the identifier for my local airport, Paul C. Miller Airport in
Sparta, MI (8D4) would work when typing the ‘K’ prefix for that code. 
For example, K8D4 would return the point forecast for “3 Miles SE of
Sparta, MI”, which is the location of the airport.  As I fly quite
frequently, I do not recall ever running into an airport for which this
did not work (until now).  In Michigan, I know that airport codes for West
Branch (Y31), Clare Municipal (48D), Greenville (6D6) and so on, all worked
without error.  As I mentioned, whether I was flying locally or several
states away, these codes previously functioned as expected (so long as the
‘K’ prefix was included).

 

I along with many, many other pilots I have spoken to would really like to
see this functionality returned to production.  This is an invaluable tool,
one for which the efforts of individuals such as yourself, are truly
appreciated.

 

I would be happy to assist in testing and/or troubleshooting if that would
be of benefit to you.  Just let me know.

 

Again, thank you for looking into this issue.

 

 

Regards,

 

Scott Kimbro
======================================================================



More information about the Woc-notify mailing list