I don’t think that it would make sense to do that where I am (England), because (a) there’s considerable overlap between areas and (b) some information like this was imported years ago and was immediately out of date. See the discussion here on the local mailing list. Some still exist (example here) but add no value.
That is where I just learned something new about stops and routes. Those are tagged with “operator”. With a stop or a route having multiple networks or operators, that candidates are separated by semicolon.
How common is the practice of tagging all or several networks or operators at stops and routes?
I have imported an OSM extract into PostgreSQL using osm2psql . Has anyone experience how to filter stops or routes by operator or network?
I guess, in Germany, counties (Kreis/Landkreis/Stadt) (OSM: admin_level=6) are responsible for public transport, at least if they provide the (public) money/subsidies.
So, from my experiences, a set of counties get together and form a Verkehrsverbund (a public association, authority). As a consequence, the serviced area of such a Verbund (the boundaries) matches the outer boundaries of the counties.
So, the relations like the two above can easily be created.
Just zoom into the map and see the name of the counties along the line of the relation.
Here the boundary does not 100% fit with admin boundaries. Some stops are part of two different networks and not only the stop closest to the border. Additionally, there are some special cases like:
I try to tag all networks, except long-distances one, for the stops and routes and all operators for the routes. Operators for the stops won’t help much as the stop is usually only operated by one authority but used by several. In my home town a city department (Garten- und Tiefbauamt) is the operator which does not even run any public transportation.
In order to get the stops used by an operator I would suggest to take the stops from the route relations the operator runs.