[OSM-dev] Osmosis Replication Statistics

[Tom Hughes]

In message <46D4A7A7.6040707 at bretth.com>
          Brett Henderson <brett at bretth.com> wrote:

> That's fair enough.  I'm trying to figure out what to focus on next.
> Currently on my list of potentials are:
> * An API download task.  Marcus Wolschon has already written this, I
> just have to make a couple of minor changes before applying it into the
> codebase.
> * An API upload task.  This will duplicate the functionality of
> Martijn's bulk_import.pl so has slipped in priority.  Once the kinks
> have been ironed out in that tool I'll re-use the ideas.
> * Create a new task for dumping "current" tables.  This might be useful
> in the short term to speed up planet creation.
> * Complete the changeset application code in --write-mysql-change and
> add "placeholder" functionality to allow new entities to be created.
> * Add referential integrity checking to database writing code.
> * Add a task for reading changes from JOSM style change files.
> * A new cron or daemon run osmosis-extract application for producing
> regular changesets (ie. daily snapshots or perhaps even less).
> * Add configurable logging (eg. -quiet or -verbose type switches) to
> customise osmosis output.
> * Add progress reporting features to osmosis tasks so you can tell where
> it's up to.
> * Enhance pipe connection code to be smarter in how it auto-connects tasks.
> * Re-think command line, it's fairly verbose at the moment.
> 
> Please feel free to provide suggestions on what is required or would be
> helpful.

A couple of things that came to mind over the weekend are:

  - A filter task to select only those objects bounded by a given polygon

  - A task to report the which users were involved in creating/editing
    a given set of objects

The motivation for these was a requirement to discover all the people
that had made edits in the Netherlands so we could email them before
uploading the AND data.

Tom

-- 
Tom Hughes (tom at compton.nu)
http://www.compton.nu/