4th Year Systems Design 4th Year Systems Design Workshop Workshop ROUTE System ROUTE System Workshop Group #24 Workshop Group #24 Danny Ho Danny Ho Macy Lui Macy Lui Gegi Thomas Gegi Thomas Supervisors: Supervisors: Prof. Doug Dudycha Prof. Doug Dudycha (GEOG) (GEOG) Prof. Eric Kubica (SY Prof. Eric Kubica (SY DE) DE) March 21, 2002
34
Embed
4th Year Systems Design Workshop ROUTE System Workshop Group #24 Danny Ho Macy Lui Gegi Thomas Supervisors: Prof. Doug Dudycha (GEOG) Prof. Eric Kubica.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
4th Year Systems Design 4th Year Systems Design WorkshopWorkshop
ROUTE SystemROUTE System
Workshop Group #24Workshop Group #24Danny HoDanny HoMacy LuiMacy LuiGegi ThomasGegi Thomas
Supervisors:Supervisors:Prof. Doug Dudycha Prof. Doug Dudycha (GEOG)(GEOG)Prof. Eric Kubica (SY DE)Prof. Eric Kubica (SY DE)
• Traffic congestion is a Traffic congestion is a common societal problemcommon societal problem
• Current navigation software Current navigation software assumes static traffic flowassumes static traffic flow
• Absence of link between Absence of link between road conditions and path road conditions and path calculationcalculation
Introduction
The ROUTE System
Demonstration
Design Architecture
- Client
- Server
Conclusion
Future
Considerations
Problem StatementProblem Statement
Provide motorists with efficient, Provide motorists with efficient, accurate directions from origin accurate directions from origin to destination using user-to destination using user-position and coincident traffic position and coincident traffic delay information, to reduce delay information, to reduce traffic congestion, and its traffic congestion, and its subsequent costs, in urban subsequent costs, in urban areas.areas.
Introduction
The ROUTE System
Demonstration
Design Architecture
- Client
- Server
Conclusion
Future
Considerations
Our SolutionOur Solution
• ROUTEROUTE System = System = RRoute oute OOptimization ptimization UUsing sing TTraffic raffic EEvents vents SystemSystem
• Input: Input: – Live traffic data (road speeds Live traffic data (road speeds
collected via road sensors)collected via road sensors)– Desired destination (entered by user Desired destination (entered by user
using front-end interface)using front-end interface)– Current geographical location of Current geographical location of
vehicle (detected using GPS device)vehicle (detected using GPS device)
Introduction
The ROUTE System
Demonstration
Design Architecture
- Client
- Server
Conclusion
Future
Considerations
Our Solution – cont’dOur Solution – cont’d
• Output:Output:– Optimized path of travel (displayed Optimized path of travel (displayed
in GUI on a portable device)in GUI on a portable device)
• Scope:Scope:– Street network of Street network of
Kitchener/WaterlooKitchener/Waterloo
Introduction
The ROUTE System
Demonstration
Design Architecture
- Client
- Server
Conclusion
Future
Considerations
Overall Design GoalOverall Design Goal
Introduction
The ROUTE System
Demonstration
Design Architecture
- Client
- Server
Conclusion
Future
Considerations
From Concept to Design…
Design ApproachDesign Approach
• Evolutionary PrototypingEvolutionary Prototyping– Client feature developmentClient feature development
• Rapid PrototypingRapid Prototyping– Client interface developmentClient interface development
• Use of Use of ChunksChunks– Location acquisitionLocation acquisition– Client User Interface ModuleClient User Interface Module– Route optimization ModuleRoute optimization Module– Traffic network DatabaseTraffic network Database
Introduction
The ROUTE System
Demonstration
Design Architecture
- Client
- Server
Conclusion
Future
Considerations
DemonstrationDemonstration
• Path optimization with Path optimization with current location and current location and destinationdestination
• Update and re-optimize Update and re-optimize when traffic condition when traffic condition changeschanges
Introduction
The ROUTE System
Demonstration
Design Architecture
- Client
- Server
Conclusion
Future
Considerations
Design ArchitectureDesign Architecture
• Separation of Computing ResponsibilitiesSeparation of Computing Responsibilities
• ESRI MapObjects map controlESRI MapObjects map control
• Street network data fileStreet network data fileIntroduction
Business Objectives
Demonstration
Design Architecture
Future
Enhancements
Conclusion
Client – System Inputs/OutputsClient – System Inputs/Outputs
Design ArchitectureDesign Architecture
• InputsInputs– GPS coordinate from GPS deviceGPS coordinate from GPS device– Street network data file (shape file)Street network data file (shape file)– Edge list of optimized route from Edge list of optimized route from
ServerServer
• OutputsOutputs– Parameters for optimizationParameters for optimization– Onscreen map output to userOnscreen map output to user
Client – System Inputs/OutputsClient – System Inputs/Outputs
TNODE_ LENGTH KWRDS_ ST_NAME TIME_IMP10 390.830 1 WEBER ST N 31.2668 208.501 2 KING ST N 16.680
994 61.251 3 REG RD 70 TO HWY 7/8 E_BND 4.009990 239.345 4 REG RD 70 TO HWY 7/8 E_BND 15.666994 105.104 5 REG RD 70 TO HWY 7/8 E_BND 6.880315 254.607 6 MARGARET AVE 16.665290 78.559 7 MARGARET AVE 5.142281 171.243 8 WELLINGTON ST N 13.699496 162.913 9 VICTORIA ST N 13.033496 149.292 10 WATER ST N 11.943493 18.505 11 VICTORIA ST N 1.480494 17.614 12 VICTORIA ST N 1.409910 246.562 13 STRASBURG RD 16.139936 199.060 14 BLOCK LINE RD 13.029
Introduction
The ROUTE System
Demonstration
Design Architecture
- Client
- Server
Conclusion
Future
Considerations
ConclusionsConclusions
• Successful implementation of Successful implementation of core ROUTE System componentscore ROUTE System components
• A robust, portable, client-server A robust, portable, client-server solution for traffic route mappingsolution for traffic route mapping
• Thank you for attending our Thank you for attending our presentation.presentation.
• Supervisor Acknowledgment:Supervisor Acknowledgment:– Prof. Doug Dudycha (GEOG)Prof. Doug Dudycha (GEOG)– Prof. Eric Kubica (SY DE)Prof. Eric Kubica (SY DE)
• Other Other AcknowledgmentsAcknowledgments– Ian Mackenzie (GEOG)Ian Mackenzie (GEOG)– Steve Kemp (City of Toronto)Steve Kemp (City of Toronto)– Prof. Hallinga (Civil Engineering)Prof. Hallinga (Civil Engineering)
Design ArchitectureDesign Architecture
• Location ProcessorLocation Processor– Track route historyTrack route history– Perform bearing calculationsPerform bearing calculations– Perform position tracingPerform position tracing– Determine source node for path Determine source node for path
findingfinding– Determine destination node for path Determine destination node for path
findingfinding
Client – ComponentsClient – Components
Design ArchitectureDesign Architecture
• Route HandlerRoute Handler– Process routes returned by serverProcess routes returned by server– Detect deviations from best pathDetect deviations from best path
Client – ComponentsClient – Components
Design ArchitectureDesign Architecture
• Street network data fileStreet network data file– Shapefile format (industry standard)Shapefile format (industry standard)– Contains geographical vector dataContains geographical vector data– Contains street info (names, etc.)Contains street info (names, etc.)– Commonly used dataset for any Commonly used dataset for any
geographical system applicationsgeographical system applications
• Consideration Factors:Consideration Factors:– FinancialFinancial– Ease of Implementation / TimeEase of Implementation / Time– Feasibility of ImplementationFeasibility of Implementation