| queries | |||
|---|---|---|---|
| region status | train location/status table | interactive dynamic map | |
| rail line | traffic graph | route map | details |
| place | find | lineup | |
| train schedule | find | route map | details or
|
the existence of published train schedule information makes it possible to predict where trains are at any given time. to do this we've combined schedule and geospatial information from a variety of sources into a regional database. the query tools on this page are designed to facilitate access to this information, and to present it in ways we hope you will find interesting and useful.
to check the reliability of this information in predicting actual train operations see our Regional Train Performance page.
we're always curious to know what you might think of these tools:
these queries are intended to give a broad-scale picture of the rail network.
the geographic scope is loosely defined as anything in Maryland, its neighbouring states or the District of Columbia for which both geospatial and schedule information is available.
this query returns a table with the location and status of scheduled train movements:
|
| ||||
this query returns the same information, presented in the form of a simple map:
| ||
these queries return information about the scheduled train movements on a particular rail line, and about the lines themselves.
this query generates a Time/Location (string line) diagram for scheduled train movements on any rail line, plotting the milepost location of trains against a 24-hour day:
| ||
this query returns a map tracing the route of a rail line:
| ||
any rail line is an ordered series of locations. this query returns a table showing the places by which any line is defined, including junction points with other lines:
| ||
these queries help you find places along the rail lines and to display associated scheduled train movements.
this query will help you determine along which lines a place might be found, and the associated milepost location:
| ||
this query returns a table listing a lineup of train movements scheduled to pass any location.
| ||
| ||
if you already know a train's symbol, this query returns a map tracing its route.
| ||
if you already know a train's symbol, these queries return its schedule information, including computed junction pass times and a simple performance profile giving end-to-end and segment velocities and dwell times (within the current geographic coverage area) presented in tabular form or
as a simple bar chart:
|
|
| Q: | Sometimes a train symbol is followed by a number in parentheses. What does it mean? | ||
| A: | when a train's schedule passes midnight, it becomes the previous day's train (and it needs to be considered separately from the following day's train with the same symbol).
a train with (-1) following the symbol is yesterday's train; one with (-2) started out the day before yesterday, und so weiter.
| ||
| Q: | Whey is there no information for (specific train) or (particular line)? | ||
| A: | these tools display only lines for which geospatial information and at least one schedule is available.
we always welcome any authenticated schedule information within the region, particularly for the short lines (e.g., ESHR, M&D, MMID, SBV or W&W). if you are in a position to share this information, or can direct us to a source, please advise us at webmaster@pacerfarm.org. | ||
| Q: | Why do some lines seem to have junctions with themselves? | ||
| A: | this occurs where there's a discontinuity in mileposts (referred to also as a "milepost equation").
for instance, Point of Rocks MD is milepost 64.7 (west from Baltimore on the CSX Old Main Line subdivision) but also milepost 42.8 (west from Union Station in Washington DC on the CSX Metropolitan Subdivision). the line runs west from there as the Metropolitan Subdivision, but with its mileposts numbered from Baltimore. it's just a conceptual simplification to treat the milepost discontinuity as a junction with another line which happens to have the same name. for an amusing example, see a segment of the Norfolk Southern Blue Ridge District with discontinuity-induced junctions with itself on each end. | ||
| Q: | What about train movements that aren't scheduled? | ||
| A: | they abound, but in the absence of a way to deal with them we have no choice but to exclude them.
extra movements include most unit trains (in this area, primarily coal and grain) as well as helpers, second sections of regular trains, detours, work trains ... the list goes on and on.
on some lines these movements constitute a majority of the traffic.
some trains operate on an "as needed" basis -- they have a schedule but do not necessarily operate on any particular day. we're gradually enhancing the query tools above with options for filtering such movements. | ||
| Q: | What is the origin of the string line diagrams? | ||
| A: | string line charts have been used for constructing railway schedules since the 1880s, and the same basic methods are still in use today.
one might expect to see more online references to the practice, but after querying several search engines the only resources that turned up (other than this page) were Systra Consulting's Rail Sim software and a press release cached at Google mentioning string line charts as an output option of ALK's Line Capacity Analysis System (LCAS) software. those interested in the subject might wish to check out these treeware resources:
| ||
| Q: | After visiting this site I took my train-crazed four-year-old (nephew, son, grandson) down to milepost (whatever) on the (whichever) line at (whenever - hour, minute, second) but no train appeared. What happened? | ||
| A: | we're sorry.
your experience provided a good object lesson in distinguishing between precision and accuracy.
see also "disclaimers", below.
| ||
| Q: | The schedule is interesting, but does it get any better: is real-time information available? | ||
| A: | railroads, unlike other modes of transportation, do not incorporate GPS-type locators into their operations control systems.
railcars and locomotives do carry equipment identification tags which trigger wayside readers, but in its raw form this information may or may not correlate to train symbols, service plans or schedules.
railroads share shipment tracing information (by waybill or freight car/trailer/container) with shippers and consignees, but its availability to the general public varies from carrier to carrier.
in the case of CSX the data provided appears to come from crew origin and destination reports rather than from the tag readers; we presume this to be a least-effort way to capture train symbols.
Norfolk Southern's trace data clearly comes from the equipment tag readers, with a latency that seems to run anywhere between a couple of hours and a few minutes.
when trace information is aggregated over time, the results can be interesting -- see our Regional Train Performance page. | ||
| Q: | Does NS local HA13 really manage to be in two places at once? | ||
| A: | no.
it just looks that way because it has a different schedule on different days of the week, and queries that specify "all possible days" or "all weekdays" will return both variants. this can be solved with day-specific queries (e.g., "Monday", "Tuesday", etc.). | ||
| Q: | Why is so much of this page in lower case? | ||
| A: | well, actually, the whole site's that way.
it's just an idiosyncracy.
and no, we're not related to e. e. cummings (at least not of which we are aware).
|
this information is deemed reliable but not guaranteed. your mileage may vary. some settling may occur.
these schedules are repackaged and presented strictly for our own amusement, and for yours.
the information returned by the queries on this page is the result of farm hand compilation and analysis of published timetables and of schedule and geospatial information from other sources including current and historical employee timetables (the term is somewhat of a misnomer in that these documents don't contain schedule information -- but they do contain the mileposts and place names used to define rail line segments), track charts and roadway or ZTS maps. for passenger carriers (Amtrak and the commuter and excursion railroads) the schedule information shown here was obtained from their published timetables. freight railroads generally do not publish schedule information, but some of the service plan information upon which their operations are based is available on the public internet and from other sources.
in going past the limits of the material in our personal collection for the acquisition and cross-checking of data, we have found the following to be of great assistance:
any errors are, of course, our own.
the author of the analysis and presentation of this information is available for hire or rent. click here for our webmaster's resume.