Today’s post is not super complex, but we all know I am a sucker for transit. Especially Amtrak. Back home on the East Coast, it runs both quickly and reliably along the Northeast Corridor and the Keystone Corridor. But as this graphic from the Wall Street Journal shows, that does not quite hold up for the longer distance Amtrak routes. Why? Freight trains.
Credit for the piece goes to the Wall Street Journal graphics department.
Yesterday I took a look at the Alaskan Airlines and Virgin America merger. Part of the disappointment on the internets centres around the service and experience delivered by Virgin. I mean who doesn’t like mood lighting, right? Well the Economist took a look at international airlines by both price and service. And if we use Virgin Atlantic as the best proxy for Virgin America, you can see why people prefer it over American carriers.
Alaska Airlines and Virgin America made some news the past few days when they announced Alaska would purchase Virgin America for $2.6 billion. I mapped out the flight routes of the two carriers to see where they overlapped. You can see the results in my piece for the blog today below.
Credit for the work is mine, except the underlying map, which I sourced from Brigham Young University Geography Department.
As I mentioned earlier this week, I visited London for work for a week and then took some rollover holiday time to stay around London and then visit Dublin. But now I am back. And this week that has meant all the jet lag. And while everybody experiences jet lag and recovers from it differently, I wanted to take a look at my experience. The data and such is below. But the basic point, it is about four days before I return to normal.
What is missing, unfortunately, is the Chicago-to-London data. Because anecdotally, that was far, far worse than the return flight.
I just spent the weekend back in my hometown of Philadelphia and while we walked most places, there were a few Uber rides. As someone who doesn’t use the app and normally will hail a taxi when necessary, I had been looking forward to posting this piece. FiveThirtyEight looked at data for New York comparing Uber to taxis.
Transport for London (TfL), the organisation that runs the London Underground or Tube, has announced a nighttime service called Night Tube. It is not for the entire system, but only a few specific lines. That means that TfL needed a new map. And that means that everyone will want to create their own version of the Night Tube map. So this article at City Metric looks at just that. The TfL version is shown below.
Credit for the original goes to Transport for London.
If you remember a little while back, Amtrak No. 188 derailed in North Philadelphia at Frankford Junction. I covered it here and here. Well, the New York Times has analysed the Northeast Corridor to identify the curviest segments of track, excluding entrances and exits from stations. Perhaps as no surprise, Frankford Junction is right among the top segments.
Credit for the piece goes to the New York Times graphics department.
Today’s post looks at an illustration from the BBC about aircraft cabin flow. As I have flown on four aircraft in the last month—quite a lot for me—I do recall thinking during one particular flight just where the air intakes were on the aircraft. It never dawned on me that they were in the actual engines themselves.
I think from a design side the only thing I would change is the width of the line for the airflow. That would show how while some is released, replacement air comes from the air mixing unit.
Credit for the piece goes to the BBC graphics department.
Let’s face it, lots of people think tables are boring. They convey data very quickly and very efficiently. But they often don’t look “pretty” enough. So, today, I just wanted to show a table from the Washington Post from last week.
It does nothing fancy. Nor do the illustrations actually communicate the information more quickly or more clearly. But, look! Green clocks and charging stations!
Credit for the piece goes to the Washington Post’s graphics department.
Tuesday I posted my late-night work on Amtrak No. 188’s derailment, (now with a few minor updates, including the speed information released this afternoon) so you could all get a sense of what happened yesterday. Of course, in the last 24 hours, we have seen a lot of news outlets covering the story.
The New York Times has a nice piece mapping out the details of the accident. Of particular interest, they included a map showing the parts of the Northeast Corridor equipped with positive train control. That is a system designed to prevent trains from exceeding their speed limits.
The Washington Post has two nice pieces. The first, below, incorporates both illustration to simplify the wreck site for the audience and then photographs to provide context of just how destroyed some of the train cars are, the first in particular.
The Post, however, also has a supplemental piece that looks at Amtrak’s accidents over the last ten years. This is the most data-centric piece of all that we are looking at, but that is okay. Most of the story is not reliant on data, but rather illustrations and diagrams trying to piece everything together.
Lastly, the BBC has an article with several small graphics looking at US train risks. Spoiler, American trains, while safe, are far less safe than those in Europe and Asia. Here, though, the map looks at accidents along the Northeast Corridor.
Credit for the New York Times piece goes to Gregor Aisch, Larry Buchanan, Bill Marsh, Haeyoun Park, Sergio Peçanha, Julie Shaver, Joe Ward, and Karen Yourish.
Credit for the Washington Post piece on the derailment goes to Bonnie Berkowitz, Patterson Clark, Alberto Cuadra, Todd Lindeman, Denise Lu, Katie Park, and Gene Thorp.
Credit for the Washington Post piece on Amtrak accidents goes to Dan Keating and Lazaro Gamio.