Closed tordans closed 4 years ago
In https://github.com/britiger/bikeparkingberlin/issues/45 the idea is to have a osm-login and a feature in the app to call out data that is missing in the field.
My idea is, to first builds this as a csv (or yml or something like this) file that can be edited via Github/PRs.
I image this would be easier than adding the login + frontend UI.
The csv could be parsed as a last step of the data-update-process to update mark the given data as "non" existing.
Idea for a data structure of this csv:
Filename: https://github.com/britiger/bikeparkingberlin/tree/master/database/non_existing_data/neukoelln_fahrrad.csv
https://github.com/britiger/bikeparkingberlin/tree/master/database/non_existing_data/neukoelln_fahrrad.csv
"id";"comment";"osm-user" "s_Fahrradstaender.9023";"An diesem Ort ist eine Mietfahrrad-Station, keine öffentlichen Fahrradständer";"tordans"
In https://github.com/britiger/bikeparkingberlin/issues/45 the idea is to have a osm-login and a feature in the app to call out data that is missing in the field.
My idea is, to first builds this as a csv (or yml or something like this) file that can be edited via Github/PRs.
I image this would be easier than adding the login + frontend UI.
The csv could be parsed as a last step of the data-update-process to update mark the given data as "non" existing.
Idea for a data structure of this csv:
Filename:
https://github.com/britiger/bikeparkingberlin/tree/master/database/non_existing_data/neukoelln_fahrrad.csv