-
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 rendering for amenity=parking_space #776
Comments
"i suggest to render it as the same yellow area as amenity=parking" - what would make it completely invisible |
Can we even zoom in enough to make this sensible? Z19 is a possibility if people have micromapped into this much detail for individual spaces. Maybe I misunderstand but this just seems to be for individual spaces but I think Math you are reading it differently. |
It's also not clear to me. Apparently you can have multiple places in one amenity=parking_space: http://www.openstreetmap.org/way/102292048 |
As I understand http://wiki.openstreetmap.org/wiki/Tag:amenity=parking%20space?uselang=en-US - it is area on amenity=parking with place marked for a single vehicle. Example of proper use: https://www.openstreetmap.org/way/164408278 (edit to see more) (IMHO 102292048 is a clear mistagging) IMHO it is near bottom on the list of things deserving to be rendered. |
Sorry math I though you wrote that but you we cutting and pasting from trac. We can just park this issue for now and do it in version 5.x. :) |
Once we have zoom level 25 :) |
Exactly, so I think parking_space should just be rendered with a small, maybe white, border at the highest zoom levels. |
Skeptical about the value of rendering individual spaces. Maybe if we had vector tiles and could do >z19, but we don't. |
Rendering individual parking spaces does seem a bit overkill, except for special-purpose spaces like handicaped, familly, electric, etc. See issue #81. Having for example a wheelchair icon on individual spaces is actually usefull. Not sure wether we want to render the area in addition to the icon. And I agree that z19 is the earlyest we want to render this. |
On z19, one could make out a single parking space. Maybe just a small P-with-wheelchair as icon, or even just the wheelchair in blue (since it's on a parking in yellow anyhow). I wouldn't do family & women's parking yet, for lack of a good small icon idea. Electric vehicle parking has usually got a charging station next to it. We should render the charger. |
Now http://parking.openstreetmap.de doesn't exist anymore I think we need render for parking spaces and also parking tags as parking:condition (ticket,free,disc...) |
As this map style supports zoom levels up to 22, I think that thsi feature request should be rejected. |
There's no layer about parking features (very important information when you go to a strange city).Also if information is given why not P symbol give us the amount of parking spaces you will find in that parking ? |
It is not valid reason to show too many details in general map style. The question is not whatever it displayed somewhere, but whatever it should be displayed in general purpose map style.
(1) see above |
The following issue has been moved over from trac:
now that the proposal for parking_spaces has been approved with 94%, mapnik should add a style for areas tagged with amenity=parking_space. i suggest to render it as the same yellow area as amenity=parking, but without the blue P, since such areas are relatively small and often occur in groups. the blue P could later be rendered through evaluation of the type=site + site=parking relation, which is also part of the proposal (but that would be a separate ticket).
i know, that this tag is brand new and you normally don't add features, that aren't heavily used, but this tag has potential to supersede the amenity=parking tag. but i fear, as long as it doesn't get rendered, people won't start mapping it.
for more information, you can find the proposal under http://wiki.openstreetmap.org/wiki/Proposed_features/parking
The text was updated successfully, but these errors were encountered: