On Thu, Apr 23, 2009 at 1:36 AM, Frederik Ramm <frede...@remote.org> wrote:
> Hi, > > Eugene Alvin Villar wrote: > >> Getting RSS/Atom feeds for these seems to be the logical next step. (I >> prefer Atom 1.0 + GeoRSS extension instead of RSS 2.0, by the way.) I >> assume >> that it'd be *extremely* easy to do this: just reformat the current >> changeset list page's output. >> > > Yes, but as you have perhaps seen, this is sub-optimal in that it gives you > many false positives. > > The bounding box stored with a changeset is a quick indicator about the > extents of changes but not so suitable for alerting people or monitoring an > area because if someone makes an edit in Madrid and one in Moscow then > basically everyone who monitors some place in Europe will have that change > on his radar. > > A proper monitoring function has to use the changeset bbox as an index only > and then check whether the changeset *really* contains something in the area > of interest to the subscriber. This is more expensive in terms of CPU power > and I'm not sure if we want to burden the API with it. It could be done > externally if changesets are distributed as OSM diffs are today. > > Bye > Frederik > I view the web page and the feed of the changeset/history as simply two different container formats for the same underlying data. So, fixing the bbox problem should be at the source side (before the web page or the feed is generated) instead of as an additional step just for the feed.
_______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
