Y-path schedules
SimonAlexander
Peter Hicks
I can't see anything in the CIF, short of trawling through every location in every Y-path schedule for matching locations, that easily shows which schedules are related to each other. They don't have to have the same headcode, or even the same operator I don't think, to narrow it down.
SimonAlexander
Marsh Lane
Hi Simon,
I dont believe there is a direct link, however there is a BUT. Back in my days in train planning, we had Q and Y paths on the coal traffic. They could have different starting and ending points but shared a common element. An example would have been a Mossend to Drax Power Station path (lets say 6E09), via the ECML, for example. We may have had a Y path out of Thornton Yard to Eggborough Power Station, lets say 6E07. In both cases, the core part of the path was Millerhill Yard to Milford Junction - timing wise, that was identical for both paths, so obviously only one could run at the same time. Both were WTT paths, but the only way of identifying them would have been the core section (or our own train planning knowledge!) - obviously in our case they had the same TSCs as well.
We got more complicated, because we could request an STP path
from Ayr Falkland Yard, that was timed to Mossend, then picked up
6E09 to Milford, and ran in the path of 6E07 from Milford to
Ferrybridge, depending on customer requirements - but that was a
bespoke one day (or week-to-week) STP path rather than a Y. But i
put i forward to show just how things could work. I've been out of
train planning for a while now, but I suspect today's network is
simpler, given the loss of much week-to-week style traffic like
coal with multiple origins and destinations, and the move to
standard routes with things like intermodal.
Now for the BUT ... with Y paths, they are guaranteed WTT paths,
so logically in the above example, 6E07 would have been a path on
the ECML allocated to DB Cargo UK - ie they have access rights to
that path for the duration of the timetable. So to me, it would
follow that any Y path must be the same operator, otherwise a
different operator would be making use of guaranteed access rights
of some other company. It could happen, but would be week-to-week
STP arrangements - with the STP timings utilsing an part or all of
an unused WTT path, it would not be a WTT path itself. I do not
believe two operators can have absolute rights to use the same
path for obvious reasons.
Therefore, you should be able to search your database, for
locations where multiple paths for the same operator pass two or
more consecutive locations at the same time and then identify
those as Y paths. With your example, the core section appears to
be Calder Bridge Jn, Wakefield to Gun Lane Junction, Ipswich.
Rich
--
You received this message because you are subscribed to the Google Groups "A gathering place for the Open Rail Data community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openraildata-t...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/e5e35d2d-137e-411b-af9c-c01192e4198an%40googlegroups.com.
Marsh Lane
Hi Simon,
I dont believe there is a direct link, however there is a BUT.
Back in my days in train planning, we had Q and Y paths on the
coal traffic. They could have different starting and ending
points but shared a common element. An example would have been a
Mossend to Drax Power Station path (lets say 6E09), via the ECML,
for example. We may have had a Y path out of Thornton Yard to
Eggborough Power Station, lets say 6E07. In both cases, the core
part of the path was Millerhill Yard to Milford Junction - timing
wise, that was identical for both paths, so obviously only one
could run at the same time. Both were WTT paths, but the only way
of identifying them would have been the core section (or our own
train planning knowledge!) - obviously in our case they had the
same TSCs as well.
We got more complicated, because we could request an STP path
from Ayr Falkland Yard, that was timed to Mossend, then picked up
6E09 to Milford, and ran in the path of 6E07 from Milford to
Ferrybridge, depending on customer requirements - but that was a
bespoke one day (or week-to-week) STP path rather than a Y. But i
put i forward to show just how things could work. I've been out of
train planning for a while now, but I suspect today's network is
simpler, given the loss of much week-to-week style traffic like
coal with multiple origins and destinations, and the move to
standard routes with things like intermodal.
Now for the BUT ... with Y paths, they are guaranteed WTT paths,
so logically in the above example, 6E07 would have been a path on
the ECML allocated to DB Cargo UK - ie they have access rights to
that path for the duration of the timetable. So to me, it would
follow that any Y path must be the same operator, otherwise a
different operator would be making use of guaranteed access rights
of some other company. It could happen, but would be week-to-week
STP arrangements - with the STP timings utilsing an part or all of
an unused WTT path, it would not be a WTT path itself. I do not
believe two operators can have absolute rights to use the same
path for obvious reasons.
Therefore, you should be able to search your database, for
locations where multiple paths for the same operator pass two or
more consecutive locations at the same time and then identify
those as Y paths. With your example, the core section appears to
be Calder Bridge Jn, Wakefield to Gun Lane Junction, Ipswich.
Rich