Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Incorrect train fares for City destinations #2
One more: Ashfield to Town Hall is quoted as:
whereas, Sydney Transport fare calculator says the weekly ticket cost $35.00 and I pay $4.10 each way peak with Opal, so lets say $32.80 per week (though I actually get a fair number of off-peak discounts per week).
Artarmon-Town Hall: Google reports 9.2 km (zone 1), Sydney Trains 11.5 km (zone 2), diff 2.3 km.
So looks like Sydney Trains is arbitrarily adding ~2 km to all fares to the city! Will adjust calculator to do the same.
Digging into this a bit deeper, it looks like Sydney Trains applies a reality distortion field to Town Hall!
Artarmon-Wynyard: Google 8.4 km, Sydney Trains 8.3 km
Mortdale-Central: Google 17.5 km, Sydney Trains 17.1 km
So I'll apply the 2 km bonus to Town Hall only. WTF.
added a commit
Feb 24, 2014
If you have a look at the "CityRail Passenger Fares Handbook" it contains the following clauses which help explain this:
You can read a copy and example here: http://www.shittytrains.info/tickets/pdf/Passenger_Fares_Handbook.pdf
Yep was just going to chime in about the passenger fares handbook too. It also gives you the official distance between stations. Which is going to be a bit of an effort to program if you want to be 100% accurate, due to the number of possible transfer points for certain trips. For example, travel from Strathfield to Chatswood - you have to consider via Macquarie Park and via the City. Or trips like Glenfield to CIty there are about four or five different routes (via East Hills, via Granville, via Liverpool/Regents Park/Stratfield, via Liverpool/Bankstown/Sydenham, etc.)
Fares are always calculated by the shortest route (not counting the distortion field around the City Railway previously discussed.)