3 ms·
Beautiful, yes, but I'm a form follows function guy, and at least from looking at their screenshots of the Chicago Loop, I'm left thinking their version of the
by bunderbunder 10y ago
Beautiful, yes, but I'm a form follows function guy, and at least from looking at their screenshots of the Chicago Loop, I'm left thinking their version of the map is quite a bit less useful than the (admittedly unsightly and cluttered) official one[1].
Some things that are iffy or missing from a functional perspective:
• Any indication that the red and blue line stations are connected by tunnels at Lake/Washington and Jackson.
• For that matter, the fact that the Jackson blue line station exists in the first place - it's obscured by the B in the street label for Jackson Boulevard. Same goes for the LaSalle blue line and State red line stations, and the Washington blue line station is also iffy. That's over 1/4 of the stations in the map's area hidden under
street labels.
• Which stations have elevators? Most of the ones downtown don't.
• Which directions are the trains traveling in? With the exception of the green line, all of the elevated trains go only one way around the loop.
• Color matters, especially on a system where all the trains are identified by color. Why did they use a dark mauve to indicate the pink line? In the real system it's indicated by a bright bubblegum pink. They've created a big opportunity for confusion with the purple line.
• A human touch might be able to make some better arrangement choices. The CTA map crosses the blue line over the green and pink lines a little outside of the loop, at the point where it diverges from the other two. That's a much better choice than trying to do it right in the middle of the already jumbled mess that is the confluence of all of the trains in Chicago's transit system (save one small spur line out in the suburbs) along a three block section of Lake street.
• Clearly indicating that the purple line operates differently from the others is also useful, and might save someone who's unfamiliar with the system from a lot of time spent waiting on the wrong side of the station while watching a bunch of brown lines pass by.
I'll grant the loop section of the L system may well be the most fiddly, nit-picky light rail mapping problem in the world, and the datasets they were working with might not have given all the detail they needed. (On the other hand, that thing with hiding stations under street names feels pretty egregious to me.) I guess what I'm really going for here is, when it comes to drawing maps, I still think involving a human hand in the process can make an enormous difference in the quality of the final product.
[1]: http://www.transitchicago.com/assets/1/clickable_system_map/200806d.htm http://www.transitchicago.com/assets/1/clickable_system_map/...
- maxerickson 10y agoHere, use this to make a bulleted list •, there's no markup support for it. Leading whitespace triggers the code formatting that breaks wrapping so remove that too.
- Kiro 10y agoWhat's wrong with the way it is now? Wrapping looks fine to me.
- bunderbunder 10y agoI had to go through several rounds of edits to get the wrapping right - HN doesn't automatically wrap code blocks. Still, I prefer using code blocks to do bulleted lists on HN. Not sure why. Maybe its that thing I just confessed to having for laborious hand editing. Probably does mean I'm being a jerk to mobile users, though. Eh, I can go change it.
- samstave 10y agoGreat points... It would be great if the system could take other data inputs (from trusted sources) to say that point X on open map has [service] And illustrate it - [escalator, elevator, tunnel, handicap, food, coffee, restroom] etc... and make it so that it would accept updates from users.... ie users travel along a line, and they report what services/things/shops/what-not are available... in the same logic that WAZE uses user input for traffic incidents - but this for infra/social-stuff