post_office=post_partner should NOT be used with amenity=post_office

[mnalis]

As noted by @Cj-Malone in https://github.com/Helium314/SCEE/issues/736#issuecomment-2841101689 👍

The wiki says post_office=post_partner should NOT be used with amenity=post_office.

Indeed.

That usage (using post_office=post_partner as property tag on existing shop=*) however is only useful for very small shops / offices mapped as nodes. In cases where e.g. shop=supermarket is mapped as a polygon, removing the node with exact position of such "Paketshop" and just tagging post_office=post_partner on that polygon would be unwanted loss of information)...

So, I'm unsure about what is the best way to proceed... Ideas?

0. do nothing (i.e. keep tagging post_office=post_partner on amenity=post_office)
1. remove post_office=post_partner answer
2. make post_office=post_partner leave a Note instead, asking the user to describe what type of shop/amenity/office is that post_partner inside?
3. keep the post_office=post_partner, but remove amenity=post_office (and hope some QA tool will flag it for fixing / improving).
4. keep the post_office=post_partner, but replace amenity=post_office with amenity=fixme like EveryDoor (see controversial https://github.com/Zverik/every_door/issues/880)
5. if post_office=post_partner is selected, have a sub-question asking if it is inside office, some amenity or a shop and tag that too (but that is not only complex, but might be creating duplicate shops/office etc if they already tagged on o polygon)
6. something else?

I generally lean toward 2. or 1.

[mnalis]

(after doing some research...)

---

or perhaps variant of 0:

7. keep tagging post_office=post_partner on amenity=post_office, but document it in a wiki with explanation, as it seems that ~42%+ of them are already tagged in such combination (and not mostly by SCEE, judging by few quick probes)

[Helium314]

-7. seems reasonable, but might also require quite a bit of work for documeting how it's used, and probably for a discussion in the OSM forum.

-1. could be a temporary solution, i.e. remove this answer until 7 is seen as acceptable.We could also do a variation of 5. where users (who had to enable expert mode to enable this quest) are informed about this and asked to fix it or leave a note. The note could be pre-filled with some text like "this is actually a post partner, not a post office".

[Cj-Malone]

(after doing some research...)

or perhaps variant of 0:

7. keep tagging post_office=post_partner on amenity=post_office, but document it in a wiki with explanation, as it seems that ~42%+ of them are already tagged in such combination (and not mostly by SCEE, judging by few quick probes)

This is based on 2 imports https://community.openstreetmap.org/t/post-partner-confusion/128321