#18094 closed enhancement (fixed)
display addr:flats / addr:unit
| Reported by: | richlv | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | 20.05 |
| Component: | Internal mappaint style | Version: | tested |
| Keywords: | addr:flats addr:unit address | Cc: |
Description
Currently addr:flats values are not shown - it would be great to have them both to identify mapped/unmapped places, and to make catching mistakes easier.
I accidentally mapped a few addr:flats as addr:housenumber and was happy to see them :)
As for the style, perhaps similar to addr:housenumber but a different colour? Probably not worth bikeshedding on it much, personally I'd be happy with anything readable.
Attachments (1)
Change History (11)
comment:1 by , 6 years ago
| Component: | Core → Internal mappaint style |
|---|---|
| Summary: | display addr:flat → display addr:flats |
comment:2 by , 6 years ago
comment:3 by , 6 years ago
| Keywords: | addr:unit address added |
|---|---|
| Summary: | display addr:flats → display addr:flats / addr:unit |
we should also display addr:unit I guess
comment:4 by , 6 years ago
Both keys are used quite often though both are not well explained in the wiki and addr:unit still has no own wiki page.
I am wondering, e.g., how to handle addr:housenumber in combination with them.
For addr:flats, I guess, entrance=* is needed and it showed be a replacement for addr:housenumber.
comment:5 by , 6 years ago
My usecases are all entrance=* + addr:flats, no addr:housenumber on those - don't have an opinion on how to best handle such a combination.
comment:6 by , 6 years ago
Now that addr:flats is rendered on osm.org, perhaps there's some simple way to show it in JOSM, too? :)
comment:8 by , 6 years ago
| Milestone: | → 20.04 |
|---|
by , 6 years ago
| Attachment: | Screenshot 2020-04-14 at 23.58.38.png added |
|---|
comment:9 by , 6 years ago
This is wonderful, thank you so much :)
Can confirm "latest" version showing addr:flats.



Seeking rendering of addr:flats on osm.org at https://github.com/gravitystorm/openstreetmap-carto/issues/3988 .