-
Notifications
You must be signed in to change notification settings - Fork 120
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
Categorize regional & national public transit trains #471
Comments
minimum zoom of national trains should change to 5, and regional trains should stay at 6 |
Related service tag discussion on OSM transit relations: #548 (comment) |
From the discussion in #548: Says @zerebubuth: The transit layer currently contains the route / "line" relations, which cover the whole length of the route / named service / "line". The
99% of the features are covered by |
Looks like there is a similar tag to service called passenger. TagInfo says, but those look to be rarely applied to route_relations. One example is Amtrak California Zephyr.
|
In the
transit
layer, we just tossed in allroute=train
features. Let's characterize if it's a regional train or not so the styling and zoom ranges can be distinct.UPDATE: Once we add the
service
property from the route relation, we can make the following selection:service IN ('high_speed', 'long_distance', 'international')
. That set should have a min_zoom = 5, while the remainder should remain min_zoom = 6.service
intransit.jinja
layer selection SQLmz_calculate_transit_level
SQL function.apply-planet_osm_line.sql
?The text was updated successfully, but these errors were encountered: