Ready to begin
No records have been processed. Start with Next step.
SECTION 26 / 28
Identify the station’s role for each train
REAL COURSE DATA · SORT, GROUP AND VERIFY
Classify source, destination and intermediate stops
Follow the selected procedure. Change a field, tie rule or weekday and explain why the result changes.
Ready
What we remember
- Processed
- 0
Predict the next change. Keep track of which list level, field and position convention the procedure uses.
On the supplied cards, a source call has a departure but no arrival; a destination has an arrival but no departure; an intermediate call has both. Classify each train–station relationship separately. A station can be an endpoint for some trains and an intermediate stop for others.
Bhubaneswar is a source or destination for four of the six calling services in our verified subset, and an intermediate call for two. Bhopal is intermediate for the verified services shown there. These statements are limited to the records inspected, not universal classifications of the physical station.
The missing-field pattern is the clue in this dataset. In other data, a missing value may mean incomplete information rather than an endpoint, so use the schema contract. The role is attached to a service call, not inferred from whether the station name contains “Junction”.
Try it yourself
Can one station be both a terminus and a through stop?
Show explained answer
For different trains, yes. Classify each service call independently.
Try it yourself
What distinguishes a destination call here?
Show explained answer
An arrival time exists and the departure field is —.
Try it yourself
Should missing data in any arbitrary table always mean a terminus?
Show explained answer
No. That interpretation is specific to this dataset’s endpoint convention.