[Talk-us] Coconino National Forest boundary isn't rendering anymore?

[stevea]

On Jul 16, 2020, at 10:13 AM, Joseph Eisenberg <joseph.eisenberg at gmail.com> wrote:
> It's not the tagging. Other relations with boundary=protected_area + protect_class=6 are rendering fine in the OpenStreetMap Carto style. The code is here: https://github.com/gravitystorm/openstreetmap-carto/blob/5724017f5b549ba954d9d645c0b2383dd16237d1/project.mml#L1132-L1149 - boundary=protected_area + protect_class=6 is enough.

To repeat myself, I believe Joseph and I agree / are saying largely the same thing here:  there isn't anything to "fix," as boundary=protected_area + protect_class=6 renders fine in Carto, and that is how Coconino is now (more correctly) tagged.

Given the recent history of this multipolygon's tags being changed from national_park to protected_area (both of which render, but slightly differently), if original poster Paul wants to add clarity to why he believes this "isn't rendering anymore" I welcome what he might add or additionally ask.  However, I believe the relevant issues to be addressed have been.  The answer is "Coconino's boundary IS rendering, but with more accurate tags, and differently than a national_park, which is how it was previously though incorrectly tagged."

SteveA