On Mon, Oct 8, 2012 at 3:00 PM, Paweł Paprota <ppa...@fastmail.fm> wrote:
> > Now, OWL fits into this picture very nicely because implementing a > proper Changeset Publisher is going to be a PITA and also why reinvent > something when there's something that already works. So my idea was to > write a very simple Activity Publisher that pulls the data from OWL and > pushes it into AS. Then the Rails Port pulls the activities from the AS > and voila - TTT done! :-) > > At this point I would be interested in learning about OWL status - what > needs to be done to get it up and running, what are the current > challenges, whether there is an API that can be used to pull the data > from OWL etc. > A few months ago Matt rewrote OWL so it wouldn't use a single monolithic table that had all changes ever in it. This table got too big and too hard to index and query. His table rewrite required a change in the rails app that is used to query it. I made some of those changes a while ago but decided that some of the queries we wanted to support became really hard with the schema change and have abandoned improving it. The change to multiple tables improves spatial queries (because it splits changes out into buckets based on location), but makes querying across all changes (e.g. finding changes for a particular changeset or user) significantly slower. I'll let Matt comment on the status of the DB, but last I checked (before redaction started) it was staying up to date but didn't have a public-facing interface yet.
_______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
