-
Notifications
You must be signed in to change notification settings - Fork 819
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
Add special rendering for shop=travel_agency #1409
Comments
I'm againt rendering this until there is a clear agreement on the tagging. Currently office=travel_agent is also used. http://wiki.openstreetmap.org/wiki/Proposed_features/office%3Dtravel_agent |
that is not a travel agency where the clients walk in to book a trip but a back office, or it is mistagging ;-) I'm opposing the palm tree icon as this seems Europe-centered, won't work in countries where palms are part of the flora. |
Sounds like that's exactly what it is. |
2015-05-14 11:06 GMT+02:00 AndiG88 [email protected]:
See shop: "A place selling retail products or services." (SERVICES) Still, it doesn't make sense to have 2 tags for the same thing, and remain |
That's exactly why I proposed 2) - a palm picture is nice, but I want OSM to be more universal whenever it's possible. Is it working or maybe different metaphore or visual details could be used instead? Travel agency is not less a shop than a ticket shop (shop=ticket): you also buy tickets, but they are just a convenient way for selling services (like concerts or other venues) really. I find it not a tagging issue (and if yes, it's rather compulsive categorizing, because we rather don't tag "travel_agent=yes"), it's just the twisted fact of life. =} I guess "shop" is a namespace including all the retail, so it should be as good as the office. I would render both then, since none of them is an error. |
We should start rendering shop=travel_agency, probably with this icon from osmfr-cartocss fork:
https://github.com/cquest/osmfr-cartocss/blob/master/symbols/travel_agency.svg
[It was proposed in meta-issue #1402]
The text was updated successfully, but these errors were encountered: