3 ms·
I've lived here for a few years and the median income in Redwood City still surprised me. Wow. Click the Caltrain 'Local' route and see for yourself. I had to
by kevingadd 14y ago
I've lived here for a few years and the median income in Redwood City still surprised me. Wow.
Click the Caltrain 'Local' route and see for yourself. I had to double-check it since it seemed so implausible to me, but it seems to be roughly accurate.
- eande 14y agoI am not sure where their data is pulled from, but the numbers are not correct, at least for Redwood City. http://www.city-data.com/city/Redwood-City-California.html http://www.city-data.com/city/Redwood-City-California.html Redwood City median income in 2009 was $67,611.
- dangrover 14y agoData is for the census tracts where the stops are located, which admittedly makes more sense for subway/streetcar/bus stops than commuter rail stops (where people drive from other tracts and park at the stations). The BART is particularly troublesome because it takes on characteristics of both types of transit. A data science friend of mine said we should do a "watershed" model where we define an area where people flow into a stop, but I'm not sure how best to do that! Maybe someone smart can fork the project and improve on our methods.
- djcapelis 14y agoProbably you could just bunch census tracts within a certain distance of any stop and count them as being part of their nearest stop and then average them. (Weighing correctly for population differences.) If you wanted to do it better, you could have the weight for each census tract fall off with distance from the stop.
- jonemo 14y agoI also looked at the Redwood City data point and it's pretty clear that they are using incorrect data. Since I have been to Redwood City and am going to be living there permanently starting a few months from now, I was a little confused. Using this tool on ArcGIS [1] I was not able to find a single corridor that has such a low median household income anywhere near Redwood City. Note that they don't seem to use the most granular data level, but zoomed out I get the number as $45,568 for tract #060816102.02 as opposed to their $30,800. $45k is still low compared to the surrounding areas, but it's far away from $30k. [1] http://www.arcgis.com/home/webmap/viewer.html?services=da76de09076b4959ad005e1dc2c48049 http://www.arcgis.com/home/webmap/viewer.html?services=da76d...
- dangrover 14y agoHm, looking into that. I noticed that the lat/longs in the GTFS feeds can occasionally be off/inconsistent.