CSE 454 Jeff Beorse, James Lee, Bo Qin, Daniel Suskin TopoCycle CSE 454 Jeff Beorse, James Lee, Bo Qin, Daniel Suskin

CSE 454 Autumn 2009

pgRouting Set up pgRouting with PostgreSQL Import King County Tiger/Line Data Remove Highways and non-road lines Create Topology Use existing A* search Link with UI (front end) with PHP Looks up nearest node ID with given x’s and y’s Con: Slow (~5 sec per query) even with bounding box Pro: Easily scalable with more data

Custom route finding A* in 3D Slope times distance Optimizations to make database queries faster

Further Problem Statement If we wanted to find a route that we previously searched, how would we go about that? Route submissions! Why else are submissions a good idea? Share routes with buddies Have a community in which everyone can share routes online Etc..

Community system Highlights of our community system Searchable by: Tags, length, start and end locations, route name, and creator id. Large set of initial routes obtained from other communities

Back end implementation Process search queries Fetch single route track points Fetch single route meta data Submit single route

Showing the Map Google maps API version 3 Drawbacks Map Event Listener Geocode Addresses Reverse Geocode Points Markers with Custom Images Polylines Drawbacks Limited number of geocoding requests Subject to change

Testing and Evaluation TopoCycle vs pgRouting vs Google maps Riding the Routes User Testing Bikers compared against the routes they already used Usually matched the user's preferred route Sometimes elevation weighted too high User Interface Good: Large Map, Analogous design Google Maps, Click to add points, Delete Specific Points Bad: No directions, removing points doesn't update map immediately, more scope desired

Lessons Build upon previous work Government is behind the times We used: Google Maps, pgRouting, Bikely.com, the U.S. Geological Survey, the Census Bureau Government is behind the times Mmm, tape And check terms of use

Problems and Plans for the Future Bounding box Unreliable data No rigorous definition of success Future Better balance of elevation vs distance Scalability Mobile platforms Expansion of supported regions