Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove entries of route=railway with DB as operator #9017

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Nakaner
Copy link
Contributor

@Nakaner Nakaner commented Dec 7, 2023

I would like to ask to remove the entries of Deutsche Bahn and its subsidiaries for routes with route=railway completely. The assigned operators do not make any sense. These route relations are used to model the route of a timetable sheet. There are multiple companies involved in operation. The routes usually use infrastructure by DB Netz AG but sometimes DB RegioNetz or other infrastructure operators (e.g. AVG, SWEG, WEG). The services operated on the infrastructure are operated by lots of different companies. Many are still served by DB Regio but long distance trains by DB Fernverkehr, local trains are often operated by non-DB companies. It makes no sense to provide defaults for this relations. It requires mappers experienced with public transport issues to decided in each inidividual case. Deriving any common values from that is like deriving a list operators from land registry (i.e. worthless).

The existing entries of Name Suggestion Index are based on existing OSM data but mappers sometimes do things wrong. The numbers of OSM objects backing these NSI entries are low.

These route relations are used to model the route of a timetable sheet.
There are multiple companies involved in operation. The routes usually
use infrastructure by DB Netz AG but sometimes DB RegioNetz or other
infrastructure operators (e.g. AVG, SWEG, WEG). The services operated on
the infrastructure are operated by lots of different companies. Many are
still served by DB Regio but long distance trains by DB Fernverkehr,
local trains are often operated by non-DB companies. It makes no sense
to provide defaults for this relations.
@LaoshuBaby
Copy link
Collaborator

I understand what you mean. To put it simply, there are multiple operators in a network (German railway?), right?

Are you interested in removing the operator and creating a network that does not record operator information?

Because the current network also records operator information

https://github.com/osmlab/name-suggestion-index/blob/main/data/transit/route/train.json#L419-L430

@Nakaner
Copy link
Contributor Author

Nakaner commented Dec 7, 2023

route=railway is not part of any public transport mapping. It is operator-less.

@Robot8A
Copy link
Collaborator

Robot8A commented Dec 14, 2023

route=train should have the public transport routes (with pt operators)
route=railway and route=tracks should have the infra (with infra operators)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants