Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

[roads] Render wildcard service=* for railway=rail, extending service=spur/siding/yard #3654

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 6 comments

Comments

@openstreetmap-trac
Copy link

Reporter: Michael Zajac
[Submitted to the original trac issue database at 7.53pm, Wednesday, 6th April 2011]

Render other service=* types in a lighter weight, just like service=spur/siding/yard. There could be more valid service types such as service=crossover, service=interchange, and potentially others. There's also the possibility of finer-grained classification, e.g., different tracks within a yard.

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 9.41pm, Thursday, 7th April 2011]

Why don't you get these documented first? Are they in use much?

Not sure what you meant by 'different tracks within a yard'.

@openstreetmap-trac
Copy link
Author

Author: Michael Zajac
[Added to the original trac issue at 4.56pm, Saturday, 9th April 2011]

These tags are currently in use, possibly applied to railways:

spur 51733, yard 30207, siding 17935, express 108, crossover 104, mainline 91, regional 88, Bahn 82, industrial 48, High_Speed 30, spur;yard 27, stub 22, main 16, tie_line 15, high_speed 15

Source: http://taginfo.openstreetmap.de/keys/service#values

(Anyone know a way to search for railway=rail AND service=* ?)

Different types of service track within a yard could be the lead/drill track, car sorting/switching, gravity hump, car storage, transfer, locomotive storage, turnaround, wye, and turntable, workshop/maintenance, loading/transloading, etc. (Caveat: I'm no expert, and Wikipedia's [http://en.wikipedia.org/wiki/Rail_yard Rail Yard] is sparse.)

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 6.29pm, Saturday, 9th April 2011]

I'm not convinced by the numbers, yet. The way I see it, all yard tracks not part of a main line going through are all service=yard. If you want to ambiguate that further, introduce a yard=* tagging. By deviating from the simple service=yard tagging, you're making life a lot more difficult for data users. The mapnik map is just one of those data users.

Definately don't want to show mapping errors like "spur;yard".

How one can even consider high_speed a service=*, I don't know. :)

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 6.30pm, Saturday, 9th April 2011]

ambiguate -> clarify

Duh me.

@openstreetmap-trac
Copy link
Author

Author: Michael Zajac
[Added to the original trac issue at 12.25am, Sunday, 10th April 2011]

The list above documents usage; I'm not espousing all of the tagging in use. yard=* sounds like a very good idea.

But still, I have added a number of crossovers and interchange tracks to the map, and they are neither spurs nor sidings.

@openstreetmap-trac
Copy link
Author

Author: math1985
[Added to the original trac issue at 4.07pm, Monday, 19th May 2014]

There does seem to be not much demand for this, given both the numbers and the lack of discussion about/requests for particular service values. I will therefore close this issue as wontfix.

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

No branches or pull requests

1 participant