While waiting for interminable parade of yuppie to collect their stream of wet/dry/half-caf/whatever espresso drinks from the coffee shop, (come on people! life is too short to order anything other then “coffee, black”) I had an idea, and scribbled a few notes down on a napkin. (I think thats the first time I’ve ever done that napkin thingy)
Its not really a very exciting idea, but what I was thinking about was an RSS namespace for describing weather syndication. Not much use with the current crop of aggregators, but the next gen like Newsmonster, and Shrook give you much greater access to items outside the core. (and then of course there is the radical idea of using RSS for inter-website syndication!)
As I started thinking about it, I decided that weather doesn’t really fit neatly into one namespace, but wants 3 namespaces: weather, forecast, and storm.
I know that seems kind of excessive, and its possible they could be rolled into a single namespace, but I think a nice hybrid spec, that clearly laid out the relationship between the namespaces, and defined some common practice for temperature and such (more on that later) wouldn’t really be too complicated.
And looking at the data weather reports really come in 3 separate types: current conditions, forecasts, and hazardous weather/storm warnings.
weather: Current Conditionsweather: might include:
- sky – a prose description of current conditions
- temp – the current temperature
- humidity – the percent humidity
- windspeed – wind speed
- dewpoint – another temperature
- heatindex – relative heat, another temp
- windchill – relative cold, another temp. visibility
It’s Raining FurlongsOne of the first things you notice with weather is people (ahem, the U.S.) like to use their annoying, region specific measurements. Are temperatures in Fahrenheit or Celsius? Is windspeed miles per hour? kilometers per hour? knots?
Sometimes visibility is noted as “10 miles”, other times as “very good”.
To paraphrase Rich Bowen, “The person who came up with [this system] needs to be taken out an beaten with a yardstick”.
There are a number of potentially complex solutions we could come up with, involving sub-elements, or attributes, or what not, but I thought the easiest would be to require measurements of temperature and distance to be marked unambiguously. So valid temps are 32F or 5C, and a valid windspeed is 13MPH.
One nice thing is none of these scales are all that hard to convert between, but if for example you’re going to calculate windchill, you’ll need to make sure you know if you’re working in Farenheit & miles, or celcius and kilometers.
forecast: Is it going to rain on Tuesday?Forecast will generally be simpler as there is rarely much info available, still any element from current should be valid in forecast. The idea behind having forecast in a separate namespace is two-fold; forecast has a slightly different set of date, and it provides a simple way to determine whether one is talking about now or the future.
Forecast adds to the elements defined in weather
- period – prose description, “Today”, “Thursday”, “Tuesday Night”
- date – the day the forecast is for should one be able to represent a range of dates here? often you’ll see something like “Monday Night – Friday, Partly Cloudy”
- hi – forecasted high/max temperature for a period
- lo – forecasted lo/min temp for a period
StormI haven’t really thought about the Storm namespace yet. The data hear is most radically different then the other two, and I haven’t spent enough time looking at it to determine if there is an underlying set of structured data we can extract or not. But I think something good can be done.
Good idea?What do you think, seem like a good idea? Sound interesting? Did I miss something obvious?
update [2003/7/2]: Phil pointed out a prototype XML weather service for Medford Country, OR. Very high quality of data. Example output. Too bad this isn’t more widely available.
update [2003/7/3]: Quicktopic discussion on mod_weather