Parking alongside streets (parking:lane)

[tordans]

This ticket is about the parking:lane tag on highway.

ATM its more of a collection of references and thoughts to start a discussion.

I see a push in the community to add those details more to maps. I wanted to start the talk about how to add this to iD.

Articles about curb data

• https://geoawesomeness.com/curbs-openstreetmap-sideline-center/ is an article about the richness of data that is between the car-lane and the building and a call to mapping to add those data. I think the article mixes the concept of the kerb-tag with the area of the "curb" which has information that OSM stores in multiple tags (like the parking tags on highway); see also https://twitter.com/mapillary/status/1095997095352373248.
• https://medium.com/coord/behind-the-curbs-building-the-curb-map-883bab281feb builds a curb map without the specific kerb-tags on the map
• https://www.coord.co/surveyor is building a business case around the curb and its data

A great micro-editor for parking-tagging

• https://zlant.github.io/parking-lanes/#18/52.48050/13.44234
• https://github.com/zlant/parking-lanes

Those are the thinks I like the most about this editor: a. It combines the visualization of data as one mode with an editing mode. Which pulls you right into editing, since you see what is there and what is missing. b. It highlights the curb-side by color (edit mode) which is an easy reference to the input sidebar. c. The sidebar only shows the parking-related tags, so nothing else needs to be understood; and also the UI can be smart for just this use case.

Some Screenshots: (Location/Link)

Visualization mode:

Editing mode:

Editing UI:

Possible OSM Keys to support

• https://wiki.openstreetmap.org/wiki/Key:parking:lane
• parking:lane:{left/right/both} = parallel, diagonal, perpendicular, …
• parking:lane:{left/right/both}:{parallel/diagonal/perpendicular} = on_street, half_on_kerb, on_kerb, …
• parking:condition:{left/right/both} = free, customers, private, …

Solution in iD

ATM, I don't see an easy way to add those presets. With the current preset interface the sidebar would be too cluttered after adding all those (empty) fields. Also the highlighting (left curb, right curb) is non-standard ATM. Also the tags have a lot of interaction.

A first step could be to have presets that only show, once some info is there, like with the cycleway fields referenced in https://github.com/openstreetmap/iD/issues/1762#issuecomment-242025240.

Another take could be to duplicate the turn-lane UI for such usecases. So there is one box for turn tagging, one for parking, one for sidewalks …

[1ec5]

Another take could be to duplicate the turn-lane UI for such usecases. So there is one box for turn tagging, one for parking, one for sidewalks …

The turn lane UI is still being discussed in #387. Some of the proposed designs don’t really lend themselves to details other than turn lanes.

There are some similarities between parking:lane/parking:condition and cycleway. iD already has a field that differentiates between cycleway:left and cycleway:right:

This field is far from ideal; mental gymnastics are required to tell which side is left and which is right. But a winning design for #387 need not block a very rudimentary field for parking:lane and parking:condition.

With the current preset interface the sidebar would be too cluttered after adding all those (empty) fields.

A field can be marked “optional”, which hides it by default unless the field has a value or the user explicitly adds it using the “Add field” dropdown.

[tordans]

Another take could be to duplicate the turn-lane UI for such usecases. So there is one box for turn tagging, one for parking, one for sidewalks …

The turn lane UI is still being discussed in #387. Some of the proposed designs don’t really lend themselves to details other than turn lanes.

To clarify, since I might be using the wrong terms here. I am not referring to #387, but this UI:

I agree that #387 should do one thing great, which is handling the (car-)lanes. Parking, Sidewalks, maybe even bike lanes should go into dedicated UIs.

[bhousel]

Oh yeah what @1ec5 is correct. We ideally want to consolidate all of the "stuff tagged on a street" into a single place. I don't really want to build separate fields for each thing.