Consider normalizing object to be the same shape regardless of endpoint#6

first off: nice job, thank you for making this data way more accessible! I understand part of this issue is likely from just how amtrak is making the data available. ## Viewing train from `/trains/{number}` endpoint notice estArr, estDep included.  ## Viewing train from `/stations/{code}` endpoint notice estArr, estDep not included  It would be nice if in the /stations/{code} endpoint, the shape was the same. ## My use case Simply get my train and see when it's Amtrak-reported estimated arrival is. Not sure how to query that robustly yet. The /trains endpoint has the nice info but I'd likely have filter by station/date in some (totally possible) way. deeper use case: omg I love amtrak but the chicago bound train is scheduled to slide through at 3:20am and is usually 1 to 5 hours late. Gotta pipe this data into a cron script that tells Twilio to spam my phone an hour before the train is about to arrive so that I can get the maximum amount of sleep. Open for collab on that :)