[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              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2009-03-26 10:17) wrote:

> I'm not 100% sure about where the prob should be, and also I'm not
> sure that the line break means anything

The line break absolutely means something.  Its part of the defined  
format for transmitting the "Meteorological Codes" data.  The weather  
service you are using might not display the line breaks to you in the  
format you are viewing it, but the raw weather data has them. It  
delineates groupings, and is required.  See  
http://adds.aviationweather.gov/metars/index.php?submit=1&station_ids=lfly&chk_tafs=on for the formatting. You could also poke around Metar.php in Services_Weather and see the full raw data string returned from the weather service (including the TAF and produced times  
etc...)

Anyway, I'm unable to reproduce your error even with the data from  
LFLY and it makes absolutely no sense to me why you would be seeing  
that exact same error with the new version of Metar.php.  Even without  
the fixes I just submitted to PEAR, the error would be different only  
a warning is produced while the forecast data displays correctly.

Please verify that you are, indeed, *using* the new Metar.php file.  
(Perhaps introduce a syntax error in the file so you can see that the  
file is indeed the one being used).