#11491 closed enhancement (fixed)
Remove "place together with addr:*" for places with only addr:postcode
Reported by: | anonymous | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 15.09 |
Component: | Core validator | Version: | latest |
Keywords: | postal code postcode place address | Cc: |
Description
Please add exception for addr:postcode because we are using it in Poland for places (mainly villages) where is only one postcode. Thank you.
Attachments (0)
Change History (12)
follow-up: 10 comment:1 by , 9 years ago
follow-up: 3 comment:2 by , 9 years ago
(I am not the reporter)
Couldn't JOSM fix addr:postcode
→ postal_code
for cases like this?
I use a rule to change this in streets here in Brazil (and after reading this bug report I will also add another one for areas with place
)
comment:3 by , 9 years ago
Keywords: | postal code postcode place address added |
---|---|
Milestone: | → 15.06 |
Type: | defect → enhancement |
Replying to naoliv:
Couldn't JOSM fix
addr:postcode
→postal_code
for cases like this?
I use a rule to change this in streets here in Brazil (and after reading this bug report I will also add another one for areas withplace
)
Agreed. Can you please share these rules so we will include them in core?
comment:4 by , 9 years ago
What we use:
way[highway]["addr:postcode"], area[place]["addr:postcode"] { throwWarning: tr("improper use of {0}", "{1.key}"); suggestAlternative: "postal_code"; fixChangeKey: "{1.key} => postal_code"; }
But I see some possible issues/improvements:
- we are not testing for this, but an area or highway could be possibly (and erroneously) tagged with both
addr:postcode
andpostal_code
:- remove
addr:postcode
if both values are the same - just warn when the values are different
- remove
- likewise, !area and !highway with both keys:
- remove
postal_code
if the same - warn if different
- remove
Should area[landuse]
also be tested for this?
comment:7 by , 9 years ago
Milestone: | 15.08 → 15.09 |
---|
comment:9 by , 9 years ago
A test for place
together with addr:postcode
with autofix addr:postcode=>postalcode
is risky, because in some cases not the addr:postcode
tag is wrong, but the place
tag. See e.g. way/233908425 or node/439184883.
comment:10 by , 9 years ago
Replying to Klumbumbus:
I think Key:postal_code is the correct key to use on place nodes or relations.
I think not. wiki(Key:place) says: "Probably better to use the Karlsruhe Schema instead of this tag." so why not? De facto people using same tag for same meaning entity, either on buildings and on places/their boundaries.
comment:11 by , 9 years ago
Russia(and some rus-speaking exUSSR) are de-facto using addr:postcode on place. Pls see ru-wiki for tag "place":
http://wiki.openstreetmap.org/wiki/RU:Key:place#.D0.98.D1.81.D0.BF.D0.BE.D0.BB.D1.8C.D0.B7.D1.83.D0.B5.D1.82.D1.81.D1.8F_.D0.B2.D0.BC.D0.B5.D1.81.D1.82.D0.B5_.D1.81
I think Key:postal_code is the correct key to use on place nodes or relations.