1. 4th Year Systems Design Workshop ROUTE System Workshop Group #24 Danny Ho Macy Lui Gegi Thomas Supervisors: Prof. Doug Dudycha (GEOG) Prof. Eric Kubica (SY DE) March 21, 2002

2. Overview 1. Introduction 2. The ROUTE System 3. Demonstration 4. Design Architecture - Client - Server 5. Conclusion 6. Future Considerations

3. Introduction Traffic congestion is a common societal problem Traffic congestion is a common societal problem Current navigation software assumes static traffic flow Current navigation software assumes static traffic flow Absence of link between road conditions and path calculation Absence of link between road conditions and path calculation Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

4. Problem Statement Provide motorists with efficient, accurate directions from origin to destination using user-position and coincident traffic delay information, to reduce traffic congestion, and its subsequent costs, in urban areas. Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

5. Our Solution ROUTE System = Route Optimization Using Traffic Events System ROUTE System = Route Optimization Using Traffic Events System Input: Input: –Live traffic data (road speeds collected via road sensors) –Desired destination (entered by user using front-end interface) –Current geographical location of vehicle (detected using GPS device) Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

6. Our Solution – cont’d Output: Output: –Optimized path of travel (displayed in GUI on a portable device) Scope: Scope: –Street network of Kitchener/Waterloo Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

7. Overall Design Goal Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations From Concept to Design…

8. Design Approach Evolutionary Prototyping Evolutionary Prototyping –Client feature development Rapid Prototyping Rapid Prototyping –Client interface development Use of Chunks Use of Chunks –Location acquisition –Client User Interface Module –Route optimization Module –Traffic network Database Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

9. Demonstration Path optimization with current location and destination Path optimization with current location and destination Update and re-optimize when traffic condition changes Update and re-optimize when traffic condition changes Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

10. Design Architecture Separation of Computing Responsibilities Separation of Computing Responsibilities –Client: User Entry Interface User Entry Interface Location Identification Location Identification Path Rendering Path Rendering –Server: Path Optimization Path Optimization Traffic Data Handling Traffic Data Handling Client / Server Paradigm Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

11. Design Architecture Client-Side Architecture Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

12. Design Architecture Location Processor Location Processor Route Handler Route Handler ESRI MapObjects map control ESRI MapObjects map control Street network data file Street network data file Introduction Business Objectives Demonstration Design Architecture Future Enhancements Conclusion Client – System Inputs/Outputs

13. Design Architecture Inputs Inputs –GPS coordinate from GPS device –Street network data file (shape file) –Edge list of optimized route from Server Outputs Outputs –Parameters for optimization –Onscreen map output to user Client – System Inputs/Outputs Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

14. Design Architecture Server Architecture Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

15. Design Architecture Requirements for optimization Requirements for optimization Decision: Dijkstra’s algorithm Decision: Dijkstra’s algorithm Advantages/Disadvantages Advantages/Disadvantages Server Side - Route Optimization Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

16. Design Architecture Data Investigation & Representation Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

17. Conclusions Successful implementation of core ROUTE System components Successful implementation of core ROUTE System components A robust, portable, client-server solution for traffic route mapping A robust, portable, client-server solution for traffic route mapping Positive societal implications: Positive societal implications: –Improved emergency vehicle response –Increased enjoyment of driving –Cleaner environment Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

18. Public policy to fully adopt traffic sensors in cities Public policy to fully adopt traffic sensors in cities Standardized data collection and map formats amongst cities Standardized data collection and map formats amongst cities Package this to popular devices Package this to popular devices Compatibility with any GPS and wireless devices Compatibility with any GPS and wireless devices Improved network performance & scalability Improved network performance & scalability Introduction The ROUTE System Demonstration Design Architecture - Client - Server Conclusion Future Considerations

19. Questions? Thank you for attending our presentation. Thank you for attending our presentation. Supervisor Acknowledgment: Supervisor Acknowledgment: –Prof. Doug Dudycha (GEOG) –Prof. Eric Kubica (SY DE) Other Acknowledgments Other Acknowledgments –Ian Mackenzie (GEOG) –Steve Kemp (City of Toronto) –Prof. Hallinga (Civil Engineering)

20. Design Architecture Location Processor Location Processor –Track route history –Perform bearing calculations –Perform position tracing –Determine source node for path finding –Determine destination node for path finding Client – Components

21. Design Architecture Route Handler Route Handler –Process routes returned by server –Detect deviations from best path Client – Components

22. Design Architecture Street network data file Street network data file –Shapefile format (industry standard) –Contains geographical vector data –Contains street info (names, etc.) –Commonly used dataset for any geographical system applications Client - Components

23. Design Architecture ESRI © MapObjects map control ESRI © MapObjects map control –Reads Shapefile of street network –Used to display all map features Client - Components

24. SCOOT Demand Responsive Demand Responsive Data Transmission in real-time Data Transmission in real-time Employed at intersections Employed at intersections 279 intersections in Toronto system 279 intersections in Toronto system Urban Traffic Control System

25. SCOOT

26. Design Architecture Server Architecture

27. IBM WebSphere Industrial Strength Server Industrial Strength Server 65% of the Fortune 500 companies 80% of the top US healthcare companies 75% of commercial banks worldwide 90% of the top commercial banks in the US 67% of the world's largest banks use IBM messaging servers 15 of the top Wall Street brokerage firms 7 of the 8 largest US telecommunications companies [Source : http://www-3.ibm.com/software/webservers/appserv/]

28. ESRI Geographical Product Line Geographical Product Line ESRI MapObjects, ArcView, ArcIMS ESRI MapObjects, ArcView, ArcIMS Consideration Factors: Consideration Factors: –Financial –Ease of Implementation / Time –Feasibility of Implementation

29. Design Methodology Design Trade-offs & Considerations - Server Implementation Logic - 3 rd Party vs. Proprietary - Server Connectivity - Protocols (HTTP vs. SMS) - Computing Design - Client vs. Server-centric

30. The Impedance Issue I - Impedance is measured in time taken to travel an arc (sec) I - Impedance is measured in time taken to travel an arc (sec) S - Average speeds of each road are sensed (meters/sec) S - Average speeds of each road are sensed (meters/sec) L - The lengths of the arcs are known and static (m) L - The lengths of the arcs are known and static (m) Impedance, I = S x L Potential optimizations include: Fastest/shortest/consistent travel speed

31. The TAXI Solution

32. Market Analysis Major contributors: Major contributors: –Digital map services MapQuest.com MapQuest.com –In-vehicle voice services OnStar OnStar

33. Screenshots

34. Screenshots