Routelandia – Project Introducton and Description – Data Available

View Github Repository Open presentation in a new window

Routelandia

See all presentation from Routelandia

Routelandia – Project Introducton and Description – Data Available

0 0

announcement_presentation

PSU Capstone 2014 Team B - Project Proposal Presentation (End of 1st quarter)

On Github Routelandia / announcement_presentation

Routelandia

Project Introducton and Description

By:Jesse Wagner, John Donahue, Josh Proehl, Loc Le, Nasim Sanati, Peter Gicking, Rob Werfelmann

Presenter: 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

Presenter: Rob Werfelmann We can put presenter notes for ourselves here

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)
Presenter: Loc Le Talk about some of our ideas.

What does it look like?

Presenter: Jesse Wagner and Nasim Sanati Talk about some of our ideas.

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
Presenter: Josh Proehl
  • Client sends time frame app server calculates traffic stats over that based on ODOT history
  • Client has segments between on/off ramps

Timeline and Schedule

Presenter: John Donahue Talk about some of our ideas.
  • 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

Presenter: Peter Gicking Talk about some of our ideas.
  • 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
    • WebDev experience lack: can lead to lots of little mistakes and efficiency problems

Stretch Goals

Presenter: Peter Gicking Talk about some of our ideas.
  • Error reporting
  • iOS Application
  • Data gathering from users phone
  • Error reporting: As you drive, inform if route is taking longer than average/predicted? | Ask user if it took longer, and report back -PG
  • TODO: Gathering what data from user's phone?
  • Time it takes to go between bluetooth arterials
  • GPS Data to verify calculations were accurate

DAS ENDE

Any questions?