Add rendering of aeroway=taxilane

[polarbearing]

We currently render aeroway=taxiway as the major aircraft paths, from zoom level 13 with increasing line width.
aeroway=taxiway has about 4k uses so far, for minor aircraft paths.
https://wiki.openstreetmap.org/wiki/Tag%3Aaeroway%3Dtaxilane
https://taginfo.openstreetmap.org/tags/?key=aeroway&value=taxilane

I propose to render, with the same colour, from zoom level 15 with a line, visibly narrower than taxiway.

[imagico]

There does not appear to be consensus on if and where to use aeroway=taxilane and not aeroway=taxiway. Also it seems to conflict with the use of aeroway=parking_position (https://wiki.openstreetmap.org/wiki/Tag:aeroway%3Dparking_position) on ways which according to the documentation and common practice is used "from the relevant taxiway and to the nose wheel position". See also #3869. So far the tag seems to be used mostly in Ukraine (more than half of the uses) and very sporadic outside. Documentation is poor and there are many cases where use is not according to the documentation or inconsistent within an airport (https://www.openstreetmap.org/way/500136192 https://www.openstreetmap.org/way/704711279 https://www.openstreetmap.org/way/756508406).

Therefore suggestion to close this.

[polarbearing]

I'm not pushing too hard for it. However, I've seen it being used by mappers in preparation of the BER airport opening (rumours say it might indeed happen this month). Usage seems plausible to me. Also, I'm always skeptical when a small number of incorrect use is taken as argument against rendering.

[imagico]

If i am linking to examples that does not mean these are all the cases i found. They are just meant to illustrate the kind of use i am talking about. You can easily find more cases using overpass.

I think this is a perfectly valid idea to try improving mapping of airports (though not without issues of course) but at this stage clearly not suitable for rendering here because of the mentioned reasons.

[polarbearing]

Could you please kindly elaborate what the specific inconsistency is for the example you gave, and what the proportion is in relation to consistent use? Your examples show different airports, so I cannot deduce inconsistency within one particular airport.

[jeisenbe]

The inconsitent usage is that features that small taxiways on the gate side of the airport are most commonly tagged aeroway=taxiway at most airports, but at some they are tagged aeroway=taxilane instead. In other cases, the way between the parking position and the nearest small taxiway is tagged as aeroway=taxilane, but at other airports these same features are tagged asaeroway=parking_position ways.

Perhaps someone can make a proposal to clarify when aeroway=taxilane should be used instead of the other two tags, and once that is clear we could support it.

[polarbearing]

Thanks. You used taxilane twice in the first sentence, is that a typo?

[jeisenbe]

Yes, I’ve fixed it.

[polarbearing]

Ok so taxiway is the older tag, taxilane the more recently introduced for a subset of the former. Thus naturally there is a situation when both tags are used for the minor way.

[dktue]

While taxiways have ref-Tags, taxilanes don't. Taxilanes connect the parking position to the taxiway. Taxilanes neither intersect multiple taxiways nor any other taxline.

I vote for rendering them.