@1ec5 commented on this pull request.
> + level3: "Administrative Boundary (Level 3)"
+ level4: "Administrative Boundary (Level 4)"
+ level5: "Administrative Boundary (Level 5)"
+ level6: "Administrative Boundary (Level 6)"
+ level7: "Administrative Boundary (Level 7)"
+ level8: "Administrative Boundary (Level 8)"
+ level9: "Administrative Boundary (Level 9)"
+ level10: "Administrative Boundary (Level 10)"
+ level11: "Administrative Boundary (Level 11)"
Not a bad idea overall, though the numbers probably aren’t as intuitive for
many mappers as designations coming from either `border_type=*` or `place=*`. I
had forgotten about the code to transform an unrecognized tag into a label. As
long as we have labels, we could fall back to a format string like “_Border
Type_ Boundary” if `border_type=*` is present but set to an unrecognized value.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5493#discussion_r1912585645
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/5493/review/2545580...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev
