[georss] "When" information in georss

Knoth, Brian D. bknoth at mitre.org
Mon Jul 30 16:53:01 EDT 2007


Hi Andrew:

You may remember during discussions of when and where, that I had
limited time to figure out a solution in order to get requirements
drawn up in time to meet development schedules. Anyhow, I did decide to
draft the requirements in terms that I had last posted to this
newsgroup, namely, to use an associated gml:TimePeriod element outside
of the georss:where element (as recommended by yourself and others),
utilize a gml:multipoint object to represent multiple locations during
time period and, finally, use the gml:ID attributes of TimePeriod and
Point to associate and actual point of the multipoint with a time. 

The approach has the advantages of being representable within the
georss v1.0 application schema and GML profile. I only hope that it
does not get wiped out by any newer versions of the profile (ie, I hope
the newer version are backward compatible).

brian




-----Original Message-----
From: ajturner at gmail.com on behalf of Andrew Turner
Sent: Sun 7/29/2007 13:05
To: Knoth, Brian D.
Cc: Holmes, Charles V.; georss at lists.eogeo.org
Subject: Re: [georss] "When" information in georss
 
Hi Charles & Brian - did you ever resolve this question?

I'm curious in particular in light of how best to support responses
from OpenSearch Geo and Time queries

OpenSearch Time makes it easy to request a feed with a begin/end time
points or periods - and then would be nice to support the response in
the RSS/Atom (which with pubdate et al. only nominally support "end
dates" (last updated))

http://www.opensearch.org/Specifications/OpenSearch/Extensions/Time/1.0
/Draft_1

By having a time period for items as well as the overall feed would
let consumers/aggregators understand the time period that the feed is
valid for.

thanks,
Andrew

On 7/19/07, Knoth, Brian D. <bknoth at mitre.org> wrote:
>
>
> Charles,
>
> You should probably contact me because a) we work for the same
company  b)
> the feeds you are accessing are the feeds from the system I work on
and c)
> this topic has been discussed through this community many times
before. If
> you are interested in the history, you can probably start here and
work
> backwards:
> http://lists.eogeo.org/pipermail/georss/2007-March/001258.html
>
> brian
>
>
>  ________________________________
>  From: georss-bounces at lists.eogeo.org
> [mailto:georss-bounces at lists.eogeo.org] On Behalf Of Holmes, Charles
V.
> Sent: Thursday, July 19, 2007 8:57 AM
> To: georss at lists.eogeo.org
> Subject: [georss] "When" information in georss
>
>
>
> In the effort of simplicity, I'm designing a system that only knows
how to
> handle one flavor of GeoRSS (currently simple).  There are layers
between
> the system and actual georss feeds that convert from whatever format
the
> feed is in into a simple georss feed.
>
> I'm currently looking at a feed with information such as:
> <gml:TimePeriod>
>   <gml:relatedTime>
>     <gml:beginPosition/>
>     <gml:endPosition/>
>   </gml:relatedTime>
> ...
> </gml:TimePeriod>
>
> Is there any construct in simple georss to represent this
information?  It's
> basically a LineString and the position of each point is only at the
> corresponding time in the TimePeriod.  Or should I make my understood
flavor
> of GeoRSS more complex?
>
> Thanks,
> Charles
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss
>
>


-- 
Andrew Turner
ajturner at highearthorbit.com      42.2774N x 83.7611W
http://highearthorbit.com              Ann Arbor, Michigan, USA
Introduction to Neogeography - http://oreilly.com/catalog/neogeography

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.eogeo.org/pipermail/georss/attachments/20070730/c8f48395/attachment.html 


More information about the georss mailing list