Let's do some architecture and modelling, shall we?
From what I can tell, the classes in your system are TrainSchedule and ScheduleLocation. Right off the bat these aren't clear to me. What are the responsibilities of each class? I can get a pretty good guess at TrainSchedule easily, but not ScheduleLocation. Is schedule location a train schedule taylored to a particular location?
A model should exist to provide allow a set of messages. What do your models need to do and know? It's very useful to think of things in terms of a set of things that you can send to your model (its messages) because this gives you an interface to deal with as a user of this model.
So it's good to describe what each class is for... and to deeply ask yourself what each class *is*. From your initial modelling, I'm not 100% sure what you want to put in and get out of the system.
Do you want to put in a series of locations (which know the distance between themselves along the trainline), and from there, you can build a schedule dynamically? That sounds like a great way to do it, however it's very different than what you've proposed.
Or do you simply want a schedule to hold a list of locations and the times that the train will arrive at a certain stop at? This seems more in line with what you've described already exists.
How you architect the internal workings of your classes & system should be dictated to by the external requirements on that system and if you're not telling us what those requirements are, we cannot help you architect the organisation of the internal workings of your classes to best obtain those outcomes or requirements.
Julian