-
Notifications
You must be signed in to change notification settings - Fork 822
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 icon for amenity=animal_boarding #3966
Comments
We have 720 nodes and 1195 ways with this "pet hotel" feature.
There is no such thing since a many years. You probably found a combined building with amenity object, which rendered the name because of the building. |
@HolgerJeromin, yes, it is when the amenity is combined with a building, but ultimately that really shouldn't matter. If there is an amenity attached to the building the name of the amenity shouldn't render the same as a building name. Since they are separate objects IMHO.
That seems close enough to the threshold to me. There's actually about a thousand more uses of amenity=animal_shelter. Which I find interesting. |
The tag amenity=animal_boarding is slightly less common than the two other animal-facility tags which were approved around the same time: amenity=animal_shelter and amenity=animal_breeding Numbers:animal_boarding - 1933 uses (taginfo) Maps:Animal shelter is more common in North America and Australia, animal breeding is more limited in extent. Here in Indonesia animal_boarding is the only one of the 3 that is common. History chartUsage is growing for all (not sure why the dotted line for animal_shelter isn't available, but it should meet up at 3000) But these are still only the 98th, 99th and 125th most common values of amenity: https://taginfo.openstreetmap.org/keys/amenity#values - there are a number of more common features which are not yet rendered in this style. For example, amenity=watering_place is also related to animals (a place where "animals such as horses can drink") and is used 7371 times, but not yet rendered. |
Here's the graph for amenity=animal_shelter by itself. Seems like it's on a good, consistent upward path.
Obviously. My main impetuous for favoring rendering of this is that the names already render when they tagged on buildings and my guess is that the vast majority of them are. So it wouldn't be a "new object" being added to the map per say. I'd perfectly fine with just a dot and label rendering (by itself if need be) in a unique color if nothing else. Then people will at least know the name is related an amenity and not just the name of the building (that could go for all three tags or just one of them. I don't really care). |
@jeisenbe, amenity=watering_place was declined by @matkoniecz in #3703, 8 months before your comment. Perhaps you could revive it. As his reason for the decline wasn't clear and @imagico said it might possibly be rendered if #1224 is worked out. |
+1 for rendering animal_*, especially animal_shelter, especially when they are areas. We have the municipal dog pound here: https://www.openstreetmap.org/way/827434380#map=18/45.12975/7.70202 and there is no way to find it on the map because it is not rendered at all - only the various buildings it is made of. Now, I could assign the "dog pound" name to one (or each) of the buildings, but that would be tagging for the renderer... The clean solution is just to draw the area and render the name over it. |
I wouldn't do that. |
Or in the meantime use landuse=commerical with whatever animal tag. It wouldn't be 100% correct, but it wouldn't be totally wrong either. |
It would be cool if there was an icon for animal boarding facilities. As it is their name's are already rendered in a generic text label color. So it wouldn't be that much of a leap to also add an icon (whatever clutter by rendering it is pretty much already there by the name being rendered IMHO). My suggestion is going with paw icon of amenity=veterinary, but without the cross in the middle. Since there is some overlap there and it makes sense. Maybe it could be added for amenity=animal_shelter also.
The text was updated successfully, but these errors were encountered: