[Tickets #7847] Re: TAF data issue in metar.php

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7847
------------------------------------------------------------------------------
  Ticket             | 7847
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | TAF data issue in metar.php
  Queue              | Horde Base
  Version            | 3.3.2
  Type               | Bug
-State              | Unconfirmed
+State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2009-01-14 13:13) wrote:

It's not quite that simple. The TAF format was changed to deal with  
the fact that high impact airports now require a 30 hour 'valid' time.  
The end result is that the portion of the TAF data representing valid  
times now includes a 4 extra digits (representing the day of month for  
both the start and end times).

I've made the change to the metar block to take care of the missing  
'time' index, so now at least the forecast itself will print - but  
until Services_Weather is updated to reflect the new TAF format, the  
forecast's valid times will remain blank.

See http://aviationweather.gov/notice/taf30.php for information  
regarding the TAF format and  
http://lists.horde.org/archives/cvs/Week-of-Mon-20090112/086173.html  
for a patch against the lib/Block/metar.php