@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)"
I noticed that other boundary types don’t say “Boundary”. For example,
`boundary=electoral` is just “Electoral”. We could shorten “Administrative
Boundary (Level 4)” to just “Administrative (Level 4)”, but I’m ambivalent
about similarly truncating the `border_type=*`-based labels, such as “City
~~Boundary~~”. That would easily get confused with the `place=*`-based labels,
which follow different criteria.
Another option would be to drop the level suffix, since @tomhughes doesn’t seem
enamored with including this information anyways. To the extent that this
introduces ambiguity in the search results, the solution would be to tag
boundaries with `border_type=*`, which is a good idea anyways.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5493#discussion_r1912562705
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/5493/review/2545550...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev
