Routelandia
Project Introducton and Description
By:
Jesse Wagner, John Donahue, Josh Proehl, Loc Le, Nasim Sanati, Peter Gicking, Rob Werfelmann
Where did we start?
- Interested in the data
- Team wanted experience with web app developlemt
- Lots of freedom to make what we wanted
- Interesting puzzle/problem to solve
- Experienced and available sponsor
Data Available
- Highway traffic data from the last 20 years
- Detectors along the highway and on/off ramps
- Data on arterials throughout portland
- Bike Traffic data
- Very little data but expanding
- Transit bus data
- How busy busses are at specific stops
- How many people got off or on at specific stops
Highway Detectors
Segments
Transit Data
So what are we going to build?
- Travel time prediction based on highway ODOT data
- Select a highway and app will tell you when to leave
- Select highway in segments that you plan to travel on
- Can't predict off highway (Initally)
What does it look like?
Architecture
- Sponsor's DB
- Postgres with PostGIS plugin
- Read only from our perspective
- Application Server
- PHP based REST API
- (Restler framework chosen)
- May or may not have it's own database for user created data
- Client Applications
- Consume our REST API
- Draw data from API onto map provided by Google
Timeline and Schedule
- Early January - Determine in detail the structure of data between front-end and back-end will be communicated. (API Doc)
- Late January - Determine statistics for at least one stretch of freeway and have app draw lines on a map.
- Early February - Add more freeways to calculations. Add route chaining to statistics.
- Late February - Implement all freeways to application.
- March - Touch ups, implement strech goals if time permitting.
Anticipated Problems
- Wanted to do route calculation
- Quickly discovered even in concept it would be difficult
- Decided to avoid doing any route calculation
- Most team members not experienced with app/API dev
Stretch Goals
- Error reporting
- iOS Application
- Data gathering from users phone