Hi, Stefan, two steps required. The second is a lot easier than the first. 1) curate a database of exiting nodes. Choosing a unique key usually isn't difficult, especially if you are using GTFS data (stop_id is a good choice). Cross-check against routes already mapped. 2) write a proposal. You might want to wait till the feedback here is addressed! :)
Cheers, John On Tue, Jun 5, 2018 at 8:57 AM, Stefan de Konink <ste...@konink.de> wrote: > If this will be allowed, I would want to do the same for The Netherlands. > > Stefan > > > On dinsdag 5 juni 2018 06:45:22 CEST, Mateusz Konieczny wrote: > >> "Summary: Adding values for two existing tags to bus stops" >> >> example edit changes three tags. >> >> The same in the proposed changes etc comment. >> >> "This provides a link between the OSM node and the STIF stop_id." >> >> And how this match is obtained? >> >> Is source code of program generating matches and making edit published >> somewhere? >> >> How edits will be split to avoid mega-edit changing thousands of objects >> with massive bounding box? >> >> I see no mention of changeset tags - and wiki recommends adding some. >> >> 5 Jun 2018, 00:15 by ok...@johnfreed.com: >> I am planning an automated edit to improve our coverage of two existing >> tags in the Paris region. The data source is the regional transit >> coordinating agency, Île-de-France Mobilité, formerly STIF. >> >> There is a question about wheelchair access that I would like feedback on. >> >> If there is no need for a significant change, I plan to implement this >> around June 20. >> >> Please make comments here or on the Discussion page attached to the >> proposal: >> >> https://wiki.openstreetmap.org/wiki/Automated_edits/johnparis >> >> Thanks, >> >> John >> >> !DSPAM:1,5b16340e79641880612683! >> > > -- > Stefan > >
_______________________________________________ Talk-transit mailing list Talk-transit@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-transit
