Keep track of ways adjacent to bus stops and bus stops adjacent to ways

[PolyglotOpenstreetmap]

I would like to have the possibility to query which way is adjacent to a highway=bus_stop node. Is it possible to keep track of this information in a lookup? In Python I'd use a dictionary for this. I would also like to be able to do the reverse. For a given way, ask if a stop is near to it, and on which side.

If the highway=bus_stop node is not in the lookup yet:

• Look at the route relations it's a member of.
• For all the ways in the route relation, determine if a PT stop is in a rectangle near to it on either side.
• Look at the stop_area relations it's a member of

Same principle for the highway ways. Also update these lookup tables when performing validation tasks.

There are operations like splitting ways and moving/adding/removing bus stop nodes that would invalidate the entry in the lookup table. Not sure how to detect those.

[sonukushwaha403]

Hello ,sir I am facing difficulty / unable to find , where should I start my contributions, Can u please tell me what should I learn ,show that I could efficiently contribute to osm .

…

On Wed, 9 Sep, 2020, 2:20 PM Jo, ***@***.***> wrote: Please have a look at: https://josm.openstreetmap.de/ https://josm.openstreetmap.de/wiki/DevelopersGuide https://josm.openstreetmap.de/wiki/DevelopersGuide/DevelopingPlugins Don't hesitate to get back to me if you have any questions, Jo On Wed, Sep 9, 2020 at 10:25 AM Jo ***@***.***> wrote: > Hi Sonu, > > Sure, please go ahead. > > Jo > > On Wed, Sep 9, 2020 at 9:34 AM Sonu kumar kushwaha < > ***@***.***> wrote: > >> can i create an issue regarding readme ,which will include the process of >> installation of jsom, and Supplemental information for JOSM >> >> — >> You are receiving this because you authored the thread. >> Reply to this email directly, view it on GitHub >> <#24 (comment) >, >> or unsubscribe >> < https://github.com/notifications/unsubscribe-auth/AALBYVL6IAPO2PR6EDS47P3SE4VZ7ANCNFSM4QIYKGCQ > >> . >> > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP6IHA44EJ7S3Q62N73P7QTSE443ZANCNFSM4QIYKGCQ> .

[floscher]

@sonukushwaha403 Maybe you could start with one of the tickets about the validator, something like https://josm.openstreetmap.de/ticket/15415 or https://josm.openstreetmap.de/ticket/19474 . I think the validator hasn't seen many changes in quite some time and should be rather straightforward to get started with.

Quick explanation of the validator checks: The validator check classes all extend the abstract Test class. Therefore they have to implement the visit() methods. For each OSM object in the dataset one of the visit() methods is called and in that visit() method an error is added to the errors field, if that object fails the current check.

If you want, you could create one class that contains all possible error codes that the pt_assistant plugin can produce. Something like the class AllValidationTests in the wikipedia plugin, which I added a while ago.

Feel free to pick one to work on. As soon as you open a pull request, we could give you feedback on your work. If there's a need for a longer discussion or some troubleshooting we could probably arrange a video call / remote coding session.