Semicolons are not correctly handled on aeroway=runway

[sb12]

http://www.openstreetmap.org/way/31724226

Probably introduced by #750

[pnorman]

Hmm. There's also a data error here, runway refs should with a slash. For this particular bug, I don't see an obvious cause to why it would work on roads but not runways

[sb12]

You are right. This is probably in most of the about 60 cases in the world a data error. Not sure if there's any case where semicolons in runway or taxiway refs are valid.

The problem seems to be the text-placement=line for taxiways and runways.

[matthijsmelissen]

The problem seems to be the text-placement=line for taxiways and runways.

This probably means that aeroways should be excluded from the multi-line scheme.

[pnorman]

This probably means that aeroways should be excluded from the multi-line scheme

Yes - and the rendering probably isn't the most sensible for them either.

Perhaps we should make a new layer for them, and exclude aeroway=* from the shields query for roads? I'm thinking of the uncommon case where a runway is also a road.

[pnorman]

The problem seems to be the text-placement=line for taxiways and runways.

We should probably report this upstream, as it looks like a bug even if we don't want to be doing multi-line ref rendering from them.

[RobJN]

This bug was also raised in an OSM diary post:
http://www.openstreetmap.org/user/Vid%20the%20Kid/diary/25989

[pnorman]

The upstream bug with the unknown character is fixed

I'd like to not apply the ; newline logic to aeroways, but splitting that text rendering into its own layer is covered by #2169