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

[Mikel Maron]

Right now, I'm in the middle of building a GeoRSS Aggregator and spatial search on aggregated feeds, by BBOX, is one of the features.

  http://mapufacture.com/georss/

Development is active right now, so it's pretty crufty, may not be running, only has a few feeds, and may be hazardous to your health   but
it seemed relevant to the thread, and basically works, so take a poke around. Though, ////Please don't redistribute the url////.


Definitely interested in standardized ways of querying GeoRSS, eventually .. right now simply focused on getting up and running. Perhaps
this can be an example and testing ground for methods to query spatially, by time, keywords, tags/categoriess..

..Mikel



----- Original Message ----
From: Raj Singh <raj at rajsingh.org>
To: Danny Ayers <danny.ayers at gmail.com>; georss at lists.eogeo.org
Sent: Tuesday, May 9, 2006 1:45:03 AM
Subject: [georss] What's next--a query API

What's the first thing you want to do after you have a GeoRSS feed?
Do a geographic query of course.

I'm sure we can think of all kinds of interesting and useful spatial
queries, like distance from something else or the overlap of two
geographies, but the thing people will probably want to do 95% of the time
is get only things in a specified bounding box.

How about we promote this as a recommended feature of GeoRSS-enabled
software? Here's the proposal:

1. A GeoRSS bounding box query consists of a feed URI plus a BBOX parameter,
consisting of minx,miny,maxx,maxy. This is the same as the WMS BBOX
parameter.

2. A service can optionally support multiple coordinate reference systems by
adding support for an SRS parameter, which would contain an EPSG code (once
again like WMS).

--
Raj


_______________________________________________
georss mailing list
georss at lists.eogeo.org
http://lists.eogeo.org/mailman/listinfo/georss