-
Notifications
You must be signed in to change notification settings - Fork 820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Render operator on amenity=post_box and amenity=post_office #1023
Comments
2014-10-07 9:02 GMT+02:00 Minh Nguyễn notifications@github.com:
I think this would indeed be a valueable amendment, but it should not |
for displaying brand see #698 |
While I can see the sense of the basic idea you are proposing, I don't think this is a really big issue in reality. Many of the non-traditional parcel service providers, are not located within city centres where traditional post offices are often found. The commercial parcel service providers more often than not, have their base within some industrial zone, where you don't go for posting your typical vacation card... |
This is probably region specific - there are plenty of FedEx and UPS drop boxes in areas with post boxes, and there are similar overlaps for the offices. This being said, I see one FedEx and one UPS drop box mapped in the Pacific Northwest, so these things are hugely undermapped or not tagged with operator. |
You may be right. Here in the Netherlands, these parcel service providers almost exclusively operate on the basis of pick-up of parcels at the sending address. Therefore, there is not much use of having a "post office" type facility in a city centre, which just incurs high costs. I can see the sense of such a facility though, in dense urban financial or commercial districts, like the Manhattan you are showing. |
Just for the record,
|
Hm, "United States Postal Service" is a bit long for a little box. |
No. USPS is the most common anyways. |
What about amenity=post_office, because I think this issue is more about a confused tourist with his holiday card ending up at a parcel processing station, instead of a traditional post office, than necessarily about a different type of post_box and its rendering, considering the OP's first post here. |
Post box: there are hardly any postboxes in the database by an operator other than the national carrier. Rendering a few operators that are not the national carrier is not worth having to render the national carrier name under almost all mailboxes. Post office: duplicate with #840. |
@math1985 How should collection boxes for UPS, FedEx, DHL, and the like be tagged? They probably have more collection boxes than the national carrier in my city and probably many others. |
@1ec5 I'm not sure. I suppose this is in the US? Perhaps ask on the US mailing list what the tagging standard is? |
This issue grew out of a talk-us thread, actually: https://lists.openstreetmap.org/pipermail/talk-us/2014-October/013661.html |
I see, I missed that in your first post. I can re-open this issue, but I'm still not sure of what the best solution would be. |
Compounding the problem, many private carriers put their boxes right next to their competitors’ (maybe due to city ordinance; I’m not sure). It might be difficult to cram three carriers’ labels right next to each other. |
The best solution to me, especially taking into account this last raised issue, is not rendering this on the standard style, but on a dedicated site with togglable overlays depicting per layer each carrier's boxes. E.g.: This site by Marc Zoutendijk is an excellent example, that can display multiple backgrounds for the overlays, including OSM Standard: Taglocator |
Is anybody still interested in this? I think it would clutter the map with needless information. |
I see no good reason to render this particular part of OSM data. |
According to the wiki,
amenity=post_office
andamenity=post_box
can be used for facilities operated by either (quasi-)government agencies or commercial parcel services (UPS, FedEx, DHL, etc.). But if you come across a brown ✉︎⃝ icon on the map, you’re going to assume initially that it’s a traditional post office rather than something like a UPS Store. To reduce confusion, the renderer should place a small label underneath the icon indicating theoperator
. (But only if there isn’t already aname
on the feature, since the name would probably indicate the type of facility.)According to taginfo,
operator
is used on 27,965 post offices and 75,760 postboxes. (brand
is used on 6,309 postboxes.)(This issue was inspired by this talk-us thread.)
The text was updated successfully, but these errors were encountered: