This document provides an overview of STC data types including static and real-time traffic and transit network data, usage data from API calls and trip tracking, and planned user survey data. It describes the types of data that will be collected and outlines the next steps of testing a mobile app with beta testers to integrate real-time data before a pilot test is conducted.

1. 1
STC Data Overview
Type Description
Static road/transit
network data
Road network data: Navteq digital map (link-node) for entire LA county
(freeway/arterial)
Transit network data: Lines, directions, stops, schedules, shapes for all
LA Metro buses and rails
Real-time traffic/transit
data
Real-time traffic data: 1) link-based average travel speed/time with
timestamp (freeway/major arterial), and 2) (freeway) traffic incident
data (timestamp, location, type (e.g., lane closure, accident, etc.),
severity, description (non-standard text))
Real-time transit data: 1) transit vehicle AVL and 2) predicted arrival
time at downstream stops/stations
Usage data 1) API calls to the server that are originated by the users (web/mobile)
will be recorded (e.g., trip planning, checking real-time transit arrival
information), and 2) trip tracking data when using mobile App
User survey data (survey
questions need to be
finalized so they can be
implemented in
database)
1) Actual trip made survey when a user closed the mobile App in the
middle of a trip, what else?
2) Web-based surveys (open to all users, how frequent, survey
questions?)
3) Focus group surveys (handouts?)

2. 2
Usage Data
Type Description
Trip planning Inputs: timestamp, user ID, origin and destination, expected mode to
travel and expected time to start travel
Returns: trip ID (associated with mode), trip comparison (total trip time,
costs, and additional CO2 when compared with taking transit), detailed
trip segment information (driving, walking, transit) (segment OD,
expected segment start and end times)
Checking trip information
(mobile, associated with
a confirmed trip)
Inputs: User ID, trip ID, user location array, timestamp
Returns: Updated ETAs for trip segments, relevant traffic incident
information
Checking transit
information without trip
planning (web/mobile)
Get nearby stops, get ETA at selected line/stop, timestamp
Post-processing data 1) Planned trip/segment start and end time vs. actual start and end
time
2) Missed transfers/connections

3. 3
User Survey Data
Type Description
Post-account creation
survey
Account creation will open to public, and we are intending to closely
follow the target participants of LA Metro/Caltrans District 7 employees
and UCLA students/staff. The post-account creation survey is to make
sure the target participants have input the correct contact information
(email, phone be optional)
Actual trip made survey When a user closed the mobile App after planning/confirming a trip, we
can not receive user location data to track the actual trip made. A
survey will be provided to the user the next time he/she opens the App
Web-based survey Users will receive an email with a web link to request participate the
survey for their comments and feedbacks (monthly?)
Focus group survey With handouts or can be done with web-based survey

4. 4
Discussion
• Current status
– Server APIs have finished
– Mobile App developers are working on the alpha release
(substantial changes in APIs)
– Web developers are working on web interface design
• From mobile App alpha release to beta release, we would like
to have 5 to 10 volunteers (preferable be UCLA students)
served as beta testers before the beta release
– Period I (2 weeks, starts 9/9/13) – test without real-time
data integration, to make comments on the mobile
interface flow , and make necessary changes
– Period II (4 weeks, starts 9/23/13) – test with real-time data
integration, to find bugs that could not be found in the lab
environment

5. 5
Discussion
• Pilot test
– Was scheduled for 4 months from 10/1/13 to 1/31/14
– Is 3 months (from 11/1/13 to 1/31/14) enough given that we
can have a more reliable beta release (tested with real-time
data)?