Closed sladen closed 8 years ago
matkoniecz
commented
8 years ago http://taginfo.openstreetmap.org/tags/motorway=yes is used 98 times worldwide and is not documented on wiki. This is not a place to propose new tags.
http://taginfo.openstreetmap.org/tags/railway=rail#combinations - maxspeed on railway is potentially usable.
dieterdreist
commented
8 years ago sent from a phone
Am 05.11.2015 um 19:24 schrieb Paul Sladen notifications@github.com:
motorway=yes (grade-separated special-access roads)
the common tag is motorroad=yes http://taginfo.openstreetmap.org/keys/motorroad
sladen
commented
8 years ago @matkoniecz; thank you, I've corrected highway=motorway and @dieterdreist added your suggestion of motorroad!=no:
mboeringa
commented
8 years ago "To aid efficient long-distance road or rail planning at low-zoom levels" ... _"grade-separated bi-directional special-access railways"_
???
You've totally lost me with this last sentence... and that is coming from someone who developed his own style... Where do I input this information in e.g. http://www.yournavigation.org/?
On a more serious note: you are aware of OpenRailwayMap? (http://www.openrailwaymap.org/), that has layers displaying infrastructure classifications and max speeds for the rail network?
pnorman
commented
8 years ago We do have special rendering for highway=motorway.
sladen
commented
8 years ago @mboeringa, this bug description has tried to use careful generic descriptions: to allow space for thinking about how the default Openstreetmap visual representation could better support those use-cases. Rather than only presenting the case of special-access roads, the description tried to also show the generic case involving special-access railways too. Both follow similar construction techniques and are often found running parallel. Both tend to be routed away from population centres.
(I don't think the YOURS instance at yournavigation.org supports either case; but many other transport planners do support these common preference options. For clarity this bug description is about the default visual representation; the metadata and tagging itself already exists).
@pnorman, I think visually distinguishably at low-zoom is the key here.
matthijsmelissen
commented
8 years ago As @pnorman mentions, we have the case for highways already covered with highway=motorway.
For railways, unfortunately there is not much we can do with the current data. The number of switches / ingress won't help us, because double-track long-distance railways do often have a large number of switches to allow switching between the two tracks.
As I don't see a way we can currently implement this, I will close this issue. @sladen Thank you for your suggestion though!
sladen
commented
8 years ago @math1985, could you try another form of wording, the sentences about points/switches seem to be somewhat unrelated/off-topic to the core issue of visually separating long-distance routes (motorways, high-speed railway lines, airports). High-speed lines are usually bi-directional (with odd small exceptions such as the CTRL Waterloo link) and dual track (with exceptions in Scandinavia and Iberia).
The suggested matching based on the value of railway=rail && maxspeed>=x doesn't require anything else, but of course oneway=no could be validated in addition.
littlebtc
commented
7 years ago My two cents.
Since Lua transform is now available, can we write a Lua transform to add highspeed=yes when railway=rail and maxspeed>=200?
Edited: I will try to investigate maxspeed and highspeed use in railway and make another issue.
kocio-pl
commented
7 years ago Even if we can use lua, next database reload is possible not sooner than 6 months from previous one, so it's about 5 months of waiting for database reload opportunity.
sommerluk
commented
7 years ago @littlebtc Probably it’s possible to do this in the SQL querry…
littlebtc
commented
7 years ago After some investigation:
Maybe we can start by adding highspeed and usage to the import tag list in osm-carto.style, then after the refresh, investigate styles to make high-speed rail and railway main lines more prominent.
2017年7月23日 下午5:03，"Lukas Sommer" notifications@github.com寫道：
@littlebtc https://github.com/littlebtc Probably it’s possible to do this in the SQL querry…
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gravitystorm/openstreetmap-carto/issues/1959#issuecomment-317239226, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFB85Zz0MhdCsaM6lb__D1PvSZSf2Xqks5sQwxygaJpZM4Gc1ZZ .
sommerluk
commented
7 years ago As of version 4 of openstreetmap-carto, we have hstore in the database, so no reload is necessary. But it cannot be backported to version 3…
2017-07-23 9:16 GMT, Hsiao-Ting Yu notifications@github.com:
After some investigation:
- According to OpenRailwayMap, use highspeed=yes may be more reliable and easier than dealing with maxspeed=?
- But it is still requires osm2pgsql database refresh as we have to edit openstreetmap-carto.style.
Maybe we can start by adding highspeed and usage to the import tag list in osm-carto.style, then after the refresh, investigate styles to make high-speed rail and railway main lines more prominent.
2017年7月23日 下午5:03，"Lukas Sommer" notifications@github.com寫道：
@littlebtc https://github.com/littlebtc Probably it’s possible to do this in the SQL querry…
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gravitystorm/openstreetmap-carto/issues/1959#issuecomment-317239226, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFB85Zz0MhdCsaM6lb__D1PvSZSf2Xqks5sQwxygaJpZM4Gc1ZZ .
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/gravitystorm/openstreetmap-carto/issues/1959#issuecomment-317239873
-- Lukas Sommer
djakk
commented
6 years ago Hello ! There is the motorroad=yes tag, there is also this tag I’ve just discovered and adopted : expressway=yes which can be used to describe physically a road (not all motorroads are expressway with interchanges). I think both of them should be rendered as I-don’t-know yet :)
dieterdreist
commented
6 years ago sent from a phone
On 11. Sep 2018, at 19:49, djakk notifications@github.com wrote:
Hello ! There is the motorroad=yes tag, there is also this tag I’ve just discovered and adopted : expressway=yes which can be used to describe physically a road (not all motorroads are expressway with interchanges).
yes, motorroads are legally defined (signs), like motorways, whereas trunks are physically defined (at least in germany and italy). Expressway is an almost unused tag (compared to the other 2 tags I mentioned), with current usage numbers we are likely not going to render it.
djakk
commented
6 years ago "Trunk" is sometimes used to describes physically the road (Germany, Italy, France) and sometimes used as a super-primary road type (Japan, UK). For France, I want to switch to the latter (I've started a thread on the French mailing list). Thus, I'll suggest to use the expressway tag, its usage will increase ;)
To aid efficient long-distance road or rail planning at low-zoom levels, long-distance grade-separated roads and railways (having infrequent ingress/egress connections) should ideally to be visually distinguishable from the general road and rail networks (having frequent ingress/egress connections). These road and rail routes are generally available only to certain classes of equipment and have significantly differing operation rules and requirements, making them unsuitable for general or local travel covering distances of under one hundred kilometres.
Extant database tagging schema:
In the default rendering, ideally the special case of grade-separated dual-carriageway special-access roads, should be immediately visually distinguishable from long-distances routes normally open to general traffic and which have frequent connections to the main or destination travel network. As the present low-zoom rendering is saturated red, this is likely to require a variation in the Hue; another option would be use of a central border.
In the default rendering, ideally the special case of grade-separated bi-directional special-access railways, should be immediately visually distinguishable from long-distance railways normally open to general traffic and which have frequent connections to the main or destination travel network. As the present low-zoom rendering is saturated black, this is likely to require a variation in Width; another option would be the use of a central border.