plepe / plepe/OpenStreetBrowser
PT: support "_entry_only" and "_exit_only" roles
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 113
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Per:
- OSM Wiki: https://wiki.openstreetmap.org/wiki/Tag:route%3Dbus#Members
- OsmAnd Guideline for public transport: https://osmand.net/blog/guideline-pt
OSB will not list stops and platforms assigned with the roles stop_exit_only, stop_entry_only, platform_exit_only and platform_entry_only. They work as the stop and platform roles, except they indicate the stop is only for getting on or off.
- Example: https://openstreetbrowser.org/#pt/r8864362&map=18/-23.03931/-47.89475&categories=pt
- Relation: https://www.openstreetmap.org/relation/8864362
In this example, the 1st stop and the last stop are not listed/highlighted in the route.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing relation 8864362 in the OpenStreetBrowser PT category and trace how its stop and platform members are selected and highlighted. The issue is done when members with stop_entry_only, stop_exit_only, platform_entry_only, and platform_exit_only roles appear with the corresponding stop or platform handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100