Asbjørn Ulsberg wrote:
Hi.
I just wonder if anybody have any experience with either producing or
consuming weather (meteorological) data through Atom? Would WeatherML be
worth looking at, or are there simpler and more light-weight
vocabularies that might express the data satisfyingly?
How do you think such data should be expressed through Atom? How should
the basic Atom entry look like, which basic Atom constructs would be
useful to utilize for the entry to give as much meaning as possible to
non-meteorological consumers like ordinary feed readers?
Since weather measurements are timely events, they fit rather well into
Atom's feed structure, but there are lots of metadata (like longitude,
latitude, wind speed, humidity, etc) that would need extensions of some
sort to be expressed properly.
Anyone?
Sure, put meteorological markup of observations (or grid point data) in
an entry's content element. Use standard Atom elements for the
observation metadata (time, id), and a georss:where element for position
(see GeoRSS). I haven't found any evidence that the US National Weather
Service uses SensorML or WeatherML in its existing feeds. For example,
http://www.weather.gov/xml/current_obs/KCCU.rss
has HTML markup meant for humans. The NWS is experimenting with "ATOM"
for its next generation of alerts. See
http://www.weather.gov/alerts-beta/
The current Colorado one
http://www.weather.gov/wwarss-tst/co.php?x=0
demonstrates some "cap" and "ha" namespace elements. Seems like most of
the cap elements could be replaced with Atom categories, or GeoRSS for
the areal element, but cap:expires at least is new and useful.
Cheers,
Sean
