`streets_polygons_labels` and `street_polygons` tag-targeting differ in `area:` usage. impls only use `area:aeroway`
Hi, so the streets_polygons_labels and street_polygons tagging is different in terms of targeting:
- While
streets_polygons_labelsallows:aeroway=runway,taxiwayorhighway=pedestrian,service - While
street_polygonsallows:area:aeroway=runway,taxiwayorhighway=pedestrian,service
This means that it can be pretty confusing if a runway has or does not have a tag.
streets_polygons_labels also includes all laybels at zoom 14 while the polygons are not yet there, but that is something that might not be a bug.
Related PR adjusting planetiler to be "spec-compliant": https://github.com/onthegomap/planetiler/pull/1221
Interstingly, the tileserver impl does only look at area:aeroway:
https://github.com/shortbread-tiles/shortbread-tilemaker/blob/a92a462bc83dc7dc4910c90da4c236fee23b1b27/process.lua#L824
@msbarry raised in https://github.com/onthegomap/planetiler/pull/1221#discussion_r2024496226 that
Seems like a mistake... I see plenty of runway polygons tagged with
area=yesaeroway=runway(notarea:aeroway=runway(f. ex.way/997816571). Think it would make sense to support both in both layers
I am unsure how planetiler should go about this. Follow the spec or follow the implementation of the spec. Advice appreciated.
I'd go with the area:aeroway tag and would be okay changing it in 1.1. In most cases it's a moot point because you don't want to label runway and taxiway polygons, you want to label the lines.