Openstreetmap-carto: Render capacity of amenity=bicycle_rental and amenity=bicycle_parking nodes

Created on 5 Oct 2018  路  11Comments  路  Source: gravitystorm/openstreetmap-carto

It would be nice to see the capacity tag of bike sharing stations and bicycle parking places rendered as text.

The capacity text should probably only be visible at at z>=18, so there will be enough free space around the node (bicycle_parking is only rendered at z=18 and above).

I will try to submit a PR with this change when I have time, but if someone beats me to it, I won't mind.

amenity-points

Most helpful comment

I'm cycling a lot (1000-1500 kilometers/ year) and I find this information useless. I don't care what is the capacity of the parking, because it could be very big but fully loaded. Maybe in veeery late future there will be possibility of live-rendering for free stands on certain parking at the moment, that would be useful and great. In current situation I find it more as map cluttering.

All 11 comments

I would rather not render anything other than names/refs on general style.

Perhaps we could copy OpenCycleMap, which shows the capacity number only when it's >=20. https://www.opencyclemap.org/docs/ (and a bigger icon)

Or if you don't want to show the capacity at all, how about rendering bicycle parking at z17 (same as bicycle rental) when it has a capacity >=20?

I try to focus on some other non-obvious things, so it's hard for me to imagine all the aspects here. What do other people think about it?

It would be cool if there was a specific zoom level dedicated to other information for things besides name that can't be shown in an icon. Like restaurant style, materiel, capacity, elevation, etc. I forget which zoom level it was now, but one of them is almost exactly like the next zoom down and would probably work for it. I don't how it work for things that are only rendered below that zoom level, but whatever.

Outside of that, if an exception is made for bike parking capacity by itself, then it might open the doors to people wanting a bunch of other similar tags being rendered later on, which has the potential to add a massive amount of clutter if not done right. So, if it is rendered, it should be a part of wider design goal and not done individually. That's not to say id be against it. Id just like to see that kind of information rendered on its own zoom level, as a standard or something though. Maybe by tag type. Instead of making an exception for one tag or subset.

I think that it makes more sense to use the car parking approach: if they are big enough, they should be tagged as an area and then we could show the symbol earlier.

I'm cycling a lot (1000-1500 kilometers/ year) and I find this information useless. I don't care what is the capacity of the parking, because it could be very big but fully loaded. Maybe in veeery late future there will be possibility of live-rendering for free stands on certain parking at the moment, that would be useful and great. In current situation I find it more as map cluttering.

I made a PR which renders the capacity as a superscript to the *parking and bicycle_rental markers, resembling an exponential.

Undoubtedly this increases 'clutter', but at z>=18 I don't think this is that much of a problem. As for the benefit of this change, the larger the size of the parking place, the bigger the chance of finding a free parking place soon.

Z18 was the zoom level I was thinking of. I think its currently under utilized as its own zoom level. Maybe it could be the "extra information" zoom level or something.

I think there's something to be said for @Tomasz-W's point though. Either you get a space or you don't. The capacity doesn't really matter without the added information of how many of the spots are currently being used. Unless your in a bike gang or something where your specifically looking for bike parking with the increased capacity.

Also, 99% of the time different bike parking spots in the same area will have the same amount of parking spaces. Since they are usually the same type. So your probably not going to be cruising around the map looking for the perfect capacity parking. In my area most bike parking is installed by the county. So I can go three towns over and it will probably still be the same pole in the ground with only two parking spots. very rarely is it different.

So ultimately, I just don't think capacity is important or something anyone considers. I've never seen it displayed on any OSM based map, including the cycling map on the main site. Which would be a better place for it, IMHO.

I've never seen it displayed on any OSM based map, including the cycling map on the main site.

https://www.openstreetmap.org/way/352186626#map=19/52.25611/20.98316&layers=C

However the same place on OSM Carto shows the space in a visual way:

https://www.openstreetmap.org/way/352186626#map=19/52.25620/20.98316

I agree with the comments above. As there seems to be no support for the proposal, I'm going to close this issue. Thanks for the idea though!

Just to agree with the issue being closed, the capacity tag is used on many objects, from parking spaces over hotel beds to size of schools. Thus it is useful for evaluating a particular POI as in the database, but not useful for rendering on the general map.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

polarbearing picture polarbearing  路  5Comments

boothym picture boothym  路  5Comments

Thorwynn picture Thorwynn  路  3Comments

wielandb picture wielandb  路  3Comments

Vort picture Vort  路  3Comments