[osmosis-dev] Improve relation extraction handling

Frederik Ramm frederik at remote.org
Mon Nov 22 23:52:11 GMT 2010


Brett,

Brett Henderson wrote:
>>     I'm thinking of adding a "cascadingRelations=yes" flag to
>>     the --bp/--bb tasks that would
>> 
>>     * process relations not containing other relations as usual,
>>     * throw all other relations onto a stack and process them in a
>>     suitable order afterwards

> I'd try to use the existing completeXXX options as a starting point.  

I have done that now and committed the enhancements in r24342. I ran 
some tests of my own and I think everything works as desired.

I'd love to amend the tests as well but it seems I am lacking either the 
proper system or the proper brains to run the existing tests at all. The 
BoundingBoxFilterTest and PolygonFilterTest work in 0.38 and they now 
fail in trunk; the AreaFilterTest fails in 0.38 as well as in trunk:

test:
     [mkdir] Created dir: 
/home/fred/svn.openstreetmap.org/applications/utils/osmosis/tags/0.38/areafilter/report/test
     [junit] Running 
org.openstreetmap.osmosis.areafilter.v0_6.AreaFilterTest
     [junit] Tests run: 5, Failures: 5, Errors: 0, Time elapsed: 0.348 sec

How do I find out why exactly these tests fail? Running ant with -v only 
gives lines like

     [junit] junit.framework.TestListener: 
startTest(testProcessBoundContainer1)
     [junit] junit.framework.TestListener: 
addError(testProcessBoundContainer1, 
org.openstreetmap.osmosis.areafilter.v0_6.PolygonFilter.<init>(Lorg/openstreetmap/osmosis/core/filter/common/IdTrackerType;Ljava/io/File;ZZZ)V)
     [junit] junit.framework.TestListener: 
addError(testProcessBoundContainer1, null)
     [junit] junit.framework.TestListener: 
endTest(testProcessBoundContainer1)

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"



More information about the osmosis-dev mailing list