Render highways other than residential as areas

[newtestaccount4949]

Expected behavior

highway=secondary, highway=primary, highway=trunk and highway=motorway render when area=yes is in the tags

Actual behavior

nothing appears at all

Links and screenshots illustrating the problem

[jeisenbe]

@newtestaccount4949 thank you for opening this issue.

Could you provide a link to an example location where there is a highway=secondary or highway=primary with area=yes?

Usually the tag area=yes plus a highway area is used to represent a plaza, square or similar feature which allows travel in any direction. The most common use is with highway=pedestrian.

Note that there is also a key area:highway=* for mapping the area of linear highways. See https://wiki.openstreetmap.org/wiki/Key:area:highway - this is more common for roads which are used by motor vehicles.

[jeisenbe]

Related to #1967 and #699
Also see #180 about rendering area:highway=*

[IgorEliezer]

Could you provide a link to an example location where there is a highway=secondary or highway=primary with area=yes?

Not the OP, but I have an example of a would-be tertiary area: https://www.openstreetmap.org/way/664093445. Note that I put both area:highway and highway + area=yes because back then I wasn't sure of how to get it working, now I know they have different purposes (edit: fixed).

Perhaps big toll areas like this would look better if a single surface could be rendered instead of rendering individual ways.

[jeisenbe]

Here is aerial imagery of way 664093445 - where a highway=unclassified way meets a highway=tertiary:

It doesn't appear that drivers can use this as a multi-directional space, so area:highway would be more appropriate.

The rendering as an area is more confusing even at z19.

Re: https://www.openstreetmap.org/#map=19/52.33492/14.90347 - the second link - this currently looks odd because each lane has been tagged as a separate way:

But rendering the whole area as the same fill color would not be an improvement. We can get an idea of how this would look from the current rendering at z17:

[newtestaccount4949]

[jeisenbe]

@newtestaccount4949 thank you for the example. The object shown is appopriately tagged with area:highway=primary because it is a linear highway with one-way flow.

Rendering of area:highway was discussed in issue #180 and declined with this comment: #180 (comment)

[matkoniecz]

It doesn't appear that drivers can use this as a multi-directional space, so area:highway would be more appropriate.

I changed tagging to correct area:highway

@newtestaccount4949 thank you for the example. The object shown is appopriately tagged with area:highway=primary because it is a linear highway with one-way flow.

+1

highway=secondary, highway=primary, highway=trunk and highway=motorway render when area=yes is in the tags

Is there even single case where such tagging is a correct one?

[matkoniecz]

Looking at https://overpass-turbo.eu/s/PhV it seems clear that rendering of highway=unclassified + area=yes should be dropped as it encourages poor mapping with disjoint road graph like at https://www.openstreetmap.org/way/158049754 .

I went through several examples and every single one was incorrect (I fixed ones except this one linked above)

[jeisenbe]

@matkoniecz could you open a separate issue about removing the rendering of highway=unclassified + area=yes?

@newtestaccount4949 - thank you for bringing up this issue. So far it looks like area:highway=* is the accepted tagging for these features, and we have #180 for that tag, so I will close this issue.