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
We are working on collecting parking data for all of Berlin with a local community. And we are working on processing the OSM data to generate good parking data based on it as well. All this is WIP and documented at https://parkraum.osm-verkehrswende.org/. We use a modified version of the Zlant parking editor for this (Links below).
Based on this project, I have some input for the quest / overlay:
It need to show separately mapped parking areas of type lane and street_side (and possibly surface for those cases that are miss-tagged). Otherwise we will generate bad data by mapping the parking data twice. The zlant-Editor does that by showing the separately mapped areas on the map.
Right now, our project is focussed on just collecting "if and in which direction can be parked", eg parking:lane:left=parallel. To keep it simple, I suggest to focus on this, so the colors of the overlay could visualize "no parking:lane:<side> data" vs. "data present".
Side note: In the future, it would be gerat to be able to run the same quest for other sub-data like the parking-position (eg on_street), a simple condition check and mappging the surface below the cars (Topic of "Entsiegelung" (unsealing?))
Use case
![image](https://user-images.githubusercontent.com/4929752/176750285-ff1a7166-bd01-48f1-8da4-4fb98c2620bc.png)
There is a great editor for parking_lane tag here.
Proposed Solution
The same as the overlay sidewalk for pedestrians an overlay would enhance a specific editing for cars.
The text was updated successfully, but these errors were encountered: