The weather applet uses the METAR format, which provides current conditions reports for airports. The applet itself fetches data from a number of different sources depending on where you're located.
The analog of this is the TAF format, which provides airport forecasts. Unfortunately, TAF doesn't contain temperature forecasts, since those are relatively unimportant in the context of aircraft. I'm not sure about other countries adopting CCF. It was mandated to the NWS stations that they provide it, but of course NOAA doesn't have control over most countries. Because of this, I was going to implement an abstract "source" class that gets passed a buffer from the web fetch and provides a list of weather report structures containing the actual data. Individual formats could then be accomodated with their own source class and URI scheme. Is this acceptable? Thanks, -David On Thu, 2004-09-16 at 20:44 +0200, Rodrigo Moya wrote: > On Wed, 2004-09-15 at 17:54 -0600, David Trowbridge wrote: > > I've begun to look at the weather calendar bounty today, since it looks > > like noone has made any progress on it. > > > > It seems to me that the new CCF (coded cities forecast) data is probably > > the best option, at least for those of us in the USA. Is it acceptable > > to implement this data format only but do it in a way that would be > > properly extensible to additional formats so as to accomodate other > > countries and services? > > > if that does not complicate too much the code for the backend, I'd say > it's ok, although of course it would be better to use a single method > for all countries. > > The weather panel applet works for me in Pamplona (Spain), not sure > about other countries, but what about using the same, whatever it is, as > that applet? _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
