Opened 8 years ago

Closed 5 years ago

#3654 closed enhancement (wontfix)

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

Reported by: Michael Zajac Owned by: mapnik-team@…
Priority: major Milestone:
Component: mapnik Version:
Keywords: Cc: michael@…

Description

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.

Change History (8)

comment:1 Changed 8 years ago by Michael Zajac

Cc: michael@… added

comment:2 Changed 8 years ago by Ldp

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

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

comment:3 Changed 8 years ago by Michael Zajac

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 Rail Yard is sparse.)

comment:4 Changed 8 years ago by Ldp

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. :)

comment:5 Changed 8 years ago by Ldp

ambiguate -> clarify

Duh @ me.

comment:6 Changed 8 years ago by Michael Zajac

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.

comment:7 Changed 5 years ago by math1985

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

comment:8 Changed 5 years ago by math1985

Resolution: wontfix
Status: newclosed

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.

Note: See TracTickets for help on using tickets.