[osmosis-dev] [patch] Merge command an resulting bounding box?

[Igor Podolskiy]

Hi everybody,

so now I implemented some bound handling in the --merge task we talked 
about a few days ago, which you will find in the attached patch.

The bounds are processed as follows:

1. If neither source 0 nor source 1 have a bound, the merged stream 
doesn't have a bound, either.

2. If both sources have a bound, then a bound corresponding to the 
unions of bounds 0 and 1 is emitted to the merged stream.

3. If source 0 does have a bound but source 1 hasn't (or vice versa):
    3a. If source 1 is empty (no entities whatsoever), the original
        bound of source 0 is passed through to the merged stream.
    3b. If source 1 is not empty, no bound is passed through.

In case 3b - when a bound is "removed" -, there are three possibilities 
controlled by the new boundRemovedAction keyword argument:

* ignore: don't do anything and continue
* warn: emit a warning to the log but continue (default)
* fail: stop processing altogether

The patch applies to current trunk and additionally includes a handful 
of test cases (MergeBoundTest.java) which test all those cases from 1 
through 3b :)

Let me know if there's something wrong with the patch, I'd be happy to 
fix it.

Best regards
Igor
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mergebounds.patch
URL: <http://lists.openstreetmap.org/pipermail/osmosis-dev/attachments/20110505/70ca93e8/attachment.ksh>