You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Toronto has an iconic and standardized bike parking -- Post and Ring. It is so widely deployed that I feel it would be nice to have a preset for it.
Is it OK to add it to name-suggestion-index? Maybe there are tag suggestions?
amenity=bicycle_parking
bicycle_parking=stands
operator=City of Toronto
operator:wikidata=Q172
support=post
access=yes
description=Post and Ring
The text was updated successfully, but these errors were encountered:
skfd
changed the title
Qestion: Toronto-specific bike parking preset, is it a right place to add?
Question: Toronto-specific bike parking preset, is it a right place to add?
Nov 4, 2024
This would be difficult to add to the NSI if "post and ring" is just a common name and not a formal brand. From an operator angle, we do have data/operators/amenity/bicycle_parking.json, but adding the above tags (plus operator:wikidata=Q172) to that file would mean that the tags would be suggested for every amenity=bicycle_parking with operator=City of Toronto. If the post and ring is all Toronto has, it might work, but if the city operates any other types of bike parking amenities, then that approach would run into problems.
I would say 95% of bike parkings in the city are those. Name is probably not well known; I would give it a nice description if a shape and surveyors will understand. Just because of statistics I feel it makes more sense to default/strongly suggest it when people add new bicycle parkings.
Toronto has an iconic and standardized bike parking -- Post and Ring. It is so widely deployed that I feel it would be nice to have a preset for it.
Is it OK to add it to name-suggestion-index? Maybe there are tag suggestions?
The text was updated successfully, but these errors were encountered: