Data-driven transit planning?

[dankegel]

Does anybody know what data Metro uses to evaluate how well its lines are meeting demand? I see they have some information at
www.metro.net/about/metro-service-changes/guidelines/
but I don't see any mention of something comparable to the "transit analyzer"
described by Nashville's MTA in
www.nashvillemta.org/PDF/Part4_Appendix_A_C.pdf
It used census data to identify the "Top Fifty Work Flows Poorly Served by Public Transportation".
Is there anything like that for the Los Angeles MTA?

The census data in question is probably that linked from
www.fhwa.dot.gov/planning/census_issues/ctpp/

I've seen www.metro.net/about/library/library-research/research-tools/transportation/statistics/
and www.metro.net/news/ridership-statistics/
but I haven't heard about how they look for where new lines are needed
(e.g. whether they're using origin/destination matrices derived
from census data or roadside sensors or whatnot).

Oh yeah, I also see they did an origin-destination survey a year or two ago:
www.metro.net/board/Items/2009/03_March/20090318P&PItem%206.pdf
www.ptvnustats.com/fileadmin/files_ptvnustats.com/case_studies/Los_Angeles_System-Wide_Origin-Destination__On-Board_Survey.pdf
Does anyone know where the results are?

I don't see them at e.g. www.surveyarchive.org/archive.html

Um, and I see they're using TAP card to generate origin-destination info:
www.transitgis.org/conference2011/Paper7.doc
but I don't know if they've shared that data yet.

And I see they have more data available at developer.metro.net/
but no origin/destination data?

So many questions, so little time...