[PATCH] CrossingWays.java incorrectly showing errors

[delta_foxtrot2]

CrossingWays and OverlappingWays select ways like boundary=administrative and treat them like highways and railways and throw warnings as a result.

I'm currently trying to code a patch for this.

[delta_foxtrot2]

The overlap error after considering it further is probably valid, however to fix the crossingway error, CrossingWays.java file just needs the following line of code about line 109:

if(es2.ws.way.get("boundary") != null && es2.ws.way.get("highway") == null && railway2 == null && !isCoastline2) continue;

[stoecker]

I'm not sure you're right here. Show an example.

[anonymous]

A lot of ABS (Australian Bureau of Statistics) boundaries were imported earlier this year, ABS boundaries are for census and other statistic purposes and aren't ways of any sort and shouldn't be treated like a way.

However when you get one of their administrative boundaries crossing ways it's reported as a warning. I'm trying to locate the issue I saw before, I should have included it in the original bug report.

[anonymous]

If you don't want to exclude all boundaries, a boundary=administrative check would achieve the same thing that the code I posted previously does.

[stoecker]

Actually the code will not take "boundary" into account at all. There must be another issue which causes this problem.

[delta_foxtrot2]

I'm looking over areas I thought this warning was being triggered, but I'm unable to replicate it at the moment, as I said I should have posted the original URL in the ticket, I'll re-open if I find an example.