[georss] What's next--a query API

Tue May 9 09:40:18 EDT 2006

I agree that the priority is examples, although I feel the next  
significant task is to converge on a recommendation for tagging XHTML.

We should provide examples of using WFS for managing GeoRSS entries.  
It would just be another feature format but we could help by  
describing a best practice of a GML feature schema for storing GeoRSS  
(<dullTech>GeoRSS GML is "not" itself a GML feature schema, but a  
separate schema which incorporates a GML geometry profile</ 
dullTech>). I am hoping GeoServer will implement this before long.

It would be practical to have a WMS GetMap extension to render GeoRSS  
entries on top of other map layers, modeled on remoteWFS. This gets  
into a bit of a standards quagmire, though, and it might be best to  
describe use of a FeaturePortrayalService for rendering just the  
layer of GeoRSS entries, which can then be overlain on other map layers.

Implementers of the Atom API can use that right now for GeoRSS- 
enabled Atom feeds, but sometime in the next 6-12 months we should  
describe an extension to that API for spatial (e.g. BBOX) queries.***

***Probably have to wait on that last, as the latest draft of this  
API seems to have dropped search capabilities. Is there collaborative  
scope here to help put it back in?

Josh

On May 9, 2006, at 9:00 AM, Allan Doyle wrote:

> I'm on the side of the "don't add any more" until things are a  
> little more stable and in use. If you look at what's going on with  
> RSS, most feeds are either chosen by the provider or are the result  
> of some kind of query you set up through some other mechanism  
> (generally a GUI/web page of some sort).
>
> I can see it being easy enough to set a WMS to return GeoRSS with  
> some MIME type hack or the same for WFS. However, I don't think it  
> makes sense to add the hack for WMS/WFS return of GeoRSS into the  
> GeoRSS spec.
>
> We need more examples, running applications, and clearly we need a  
> FAQ. That's where the energy needs to go.
>
> 	Allan
>
> On May 9, 2006, at 08:38, Andrew Turner wrote:
>
>> FoFRedux supports tagging, categories, and reading in the subject
>> fields from an RSS feed and GeoRSS feed. It can then put out feeds
>> based on tag or category. We're also adding complex search RSS
>> aggregated output so that you could, for example, have a GeoRSS  
>> output
>> of all feeds that are about weather and use the words "California,
>> Oregon, or Washington" in them.
>>
>> So doing what you're suggesting is already possible and
>> straight-forward to implement for RSS applications.
>>
>> Adding some BBOX, within distance, and simple geo queries would be
>> great and straight-forward. But the backend can either be MySQL or
>> PostgreSQL, so doing "complex" queries is more difficult to wrap up.
>>
>> And if you're seeking widespread adoption of GeoRSS for both hard- 
>> core
>> GIS, as well as "neographers", hobbyists, and the general public,  
>> then
>> I wouldn' toss too much in too quickly.
>>
>> Andrew
>>
>> On 5/9/06, Gregor J. Rothfuss <gregor at apache.org> wrote:
>>> Mike Liebhold wrote:
>>>> Jeff Harrison wrote:
>>>>
>>>>> it might be simpler (at least initially) for content providers to
>>>>> break thematic geoRSS content into separate feeds (Weather,  
>>>>> Traffic,
>>>>> Yard Sales, etc.).
>>>>
>>>> Interesting thought Jeff.
>>>>
>>>> Heirarchical and  thematic browsing of GeoRSS will demand  
>>>> enormous back
>>>> end semantic processing to structure metadata  into content  
>>>> categories -
>>>> given the viral popularity of unstructured plain language tags  
>>>> people
>>>> will inevitably use, are already using on social knowledge sites  
>>>> like
>>>> del.icio.us, and flickr.com,  and at least one social mapping  
>>>> site -
>>>> platial.com which already enables users' own key word tags of  
>>>> GeoRSS points
>>>
>>> both atom and rss have the category element, which can optionally be
>>> used with the domain attribute:
>>>
>>> <category domain="http://del.icio.us/tag">yardsales</category>
>>>
>>> this makes it possible to have multiple themes in one feed, and  
>>> filter
>>> by them. maybe there could be a couple such examples on the site to
>>> encourage such usage?
>>>
>>> -gregor
>>>
>>> --
>>> http://43folders.com/2005/09/19/writing-sensible-email-messages/
>>> _______________________________________________
>>> georss mailing list
>>> georss at lists.eogeo.org
>>> http://lists.eogeo.org/mailman/listinfo/georss
>>>
>>
>>
>> --
>> Andrew Turner
>> ajturner at highearthorbit.com        42.4266N x 83.4931W
>> http://highearthorbit.com              Northville, Michigan, USA
>> _______________________________________________
>> georss mailing list
>> georss at lists.eogeo.org
>> http://lists.eogeo.org/mailman/listinfo/georss
>>
>
> -- 
> Allan Doyle
> +1.781.433.2695
> adoyle at eogeo.org
>
>
>
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss