It would be nice to see biking times in addition to car/public transit, however.
Interactive visualization of commute times for all US cities
51–60 of 88 posts
Re: Interactive visualization of commute times for all US cities
#52This is the most worthless chart I've ever seen. When would this be useful? It's roughly the same everywhere. Before I am downvoted into oblivion... honestly can someone explain to me when they would ever reference this chart? Give me one good example.
Re: Interactive visualization of commute times for all US cities
#53Earlier quoted context omitted.
Is this the absolute worst-case commute times? It never takes me that long to commute into/out of miami, or baltimore, or fort lauderdale. More like half the time. DC actually seemed like it went the opposite way as it usually takes an hour and a half to get from VA through the beltway into DC while the map showed only an hour for as far out as Dale City. A half hour (or more) from Petworth into Downtown during rush…
Agreed on DC - the places that I plugged in from northern va. (22102, 22213, 22046, etc.) all seemed to be showing the best-case times. Some places that it says are a 5-10 commute are more like 30-45 minutes at rush hour. Also, not related to the commute times, but the crime rates look strange. At least, it's showing Arlington, VA as almost completely red (very high crime). Maybe the data is right, but that would be…
Re: Interactive visualization of commute times for all US cities
#54Hi, Sha from Trulia here. I worked on some of the frontend aspects of this visualization and would be happy to answer any questions. We're pulling in OSM road data and published GTFS files for public transit routing. I just linked to SF but you can also search for other cities: http://www.trulia.com/local#commute/new-york-ny http://www.trulia.com/local#commute/miami-fl http://www.trulia.com/local#commute/austin-tx
Is this the absolute worst-case commute times? It never takes me that long to commute into/out of miami, or baltimore, or fort lauderdale. More like half the time. DC actually seemed like it went the opposite way as it usually takes an hour and a half to get from VA through the beltway into DC while the map showed only an hour for as far out as Dale City. A half hour (or more) from Petworth into Downtown during rush…
Re: Interactive visualization of commute times for all US cities
#55Hi, Sha from Trulia here. I worked on some of the frontend aspects of this visualization and would be happy to answer any questions. We're pulling in OSM road data and published GTFS files for public transit routing. I just linked to SF but you can also search for other cities: http://www.trulia.com/local#commute/new-york-ny http://www.trulia.com/local#commute/miami-fl http://www.trulia.com/local#commute/austin-tx
However the main problem I have during my real estate search has nothing to do with UI. It seems like for every home I find through the site that I contact a realitor about the home is already "under agreement". If your site could find a way to be more up to date about those things, it would really stand apart.
Re: Interactive visualization of commute times for all US cities
#56Fire up the app, let it run in background, and it logs everything passively and adds it to global data set. Feasible?
Re: Interactive visualization of commute times for all US cities
#57Hi, Sha from Trulia here. I worked on some of the frontend aspects of this visualization and would be happy to answer any questions. We're pulling in OSM road data and published GTFS files for public transit routing. I just linked to SF but you can also search for other cities: http://www.trulia.com/local#commute/new-york-ny http://www.trulia.com/local#commute/miami-fl http://www.trulia.com/local#commute/austin-tx
Times seem inflated in Austin, too. The smaller the time, the greater the error. The ten-minute area should be two or three times larger, but the 45-minute area bears some resemblance to rush-hour reality. Also, every route seems to be treated the same. In the morning, the road I live on is always empty in one direction and congested in the other. I used to commute against traffic and now go the same way as everybody…
For example, Beaverton, OR, into Portland. Where I live it's at most, even at rush hour, 15 minutes to one of the two freeways near my house and this is estimating 30-35 minutes. The entire (house -> downtown) calculation is close (about 45 minutes downtown) but only for rush hour. Other than if there was an accident on I-5, there isn't a possibility of taking 50-55 minutes to get from my house to Tigard or Tualatin without spending 30 minutes lounging at Starbucks along the way.
Looking at the data a little more, surface streets seem to simply be an estimate outward radially, with what appears to be very little taken into account otherwise. The freeways seem to be good, educated guess estimates.
Re: Interactive visualization of commute times for all US cities
#58Hi, Sha from Trulia here. I worked on some of the frontend aspects of this visualization and would be happy to answer any questions. We're pulling in OSM road data and published GTFS files for public transit routing. I just linked to SF but you can also search for other cities: http://www.trulia.com/local#commute/new-york-ny http://www.trulia.com/local#commute/miami-fl http://www.trulia.com/local#commute/austin-tx
Re: Interactive visualization of commute times for all US cities
#59Thinking out loud: In an attempt to vastly improve the data, could a mobile app be written that can "detect" if you are driving (exact location, speed, alignment/frequency to your past paths, etc), in such a way that the data could be automatically collected and crowdsourced? Fire up the app, let it run in background, and it logs everything passively and adds it to global data set. Feasible?