1. Team Members Charles Dunbar Ben Kallal Ankit Patel Peter Purcell Kody Reynolds 1 IRP Presentation Client Lisa Hein-Iowa Natural Heritage Foundation Faculty Advisor Tom Daniels

2. Problem One of the Iowa Natural Heritage Foundation's major goals is to encourage the use of reclaimed railroads for use as bike trails. There is currently no such application specifically designed for cyclists to create routes that make use of the bike trails in IA. Solution An application where the user can plan out their own routes, taking in account different options such as traffic count and difficulty of the route. 2

3. 3

4. 4

5.  Create a safe and efficient route between two locations in Iowa  Will support online access through any operating system that supports application supported browser  Will support IE, Firefox  Will take a start and end location for routing  Will have consistent routing algorithm 5

6.  Will route cyclists using a graphical interface  Will display a route as an overlay of an Iowa map  Will allow the printing of a map with instructions  Will provide a code or URL that can be sent to another to exactly recreate the route  Mapping data can be updated and maintained 6

7.  Usability Must provide a positive service to the users to help accomplish their goals of finding the least-costly route  Reliability Users must be allowed to access the web service almost always without any downtime and get back the correct least-cost path from origin to destination 7

8.  Speed The algorithm and user interaction with the application must be reasonably fast and responsive under normal use conditions  Scalability Must be able to handle multiple requests at once – up to an upper limit MAX_NUM_USERS that is defined  Security The server module must be immune to attacks from external sources 8

9.  During our research we found that there are not many alternate applications in existence that INHF could use as a solution to this problem.  Google Maps Designed with similar data Has no options for user to change their ride preferences automatically. The routes given often do not take road type into account. Does not allow custom route generation based on INHF standards 9

10.  Limited web programming Mitigation: Learn from each other and utilize online resources (ie StackOverFlow)  Limited Knowledge of GIS Mitigation: Use resources from INHF and some other faculty members at ISU who can help us or refer to other resources that might.  Google changing the API Mitigation: Hope for backwards capability, and be as modular as possible. 10

11.  Google Maps  ArcGIS-Server server: ArcGIS Server 9.3.1 Red Hat Enterprise 5.4  Xenon X550 @ 2.67GHz CPU  3042MB Memory  10GB hard drive  ArcGIS Client server: Red Hat Enterprise 5.4  Xenon X550 @ 2.67GHz CPU  372MB memory  8GB hard drive 11

12. 12

13.  Routing Application Source Code for web client Code for edge weighting on the server Map Data  Documentation Design Document  ESRI wish list Operations/Set-up Manual  Setup for ArcGIS server  Merging data  Uploading data to the server correctly 13

14.  Communication with GIS (to server and client module) ESRI API  Developed ArcGIS  Associated Risk AJAX calls  Interactive web applications 14

15.  Web Client Google Maps Layout and Implementation ArcGIS JavaScript Integration Custom Waypoint Placement feature  Server Setup and maintenance and OS  GIS Merging of the data Custom Edge Waiting algorithms 15

16.  Google Maps Layout and Implementation Duplicating basic Google Maps functionality  ArcGIS JavaScript Addition of custom Geocoding Utilization of ArcGIS JavaScript API to retrieve routes from server Display of directions and retrieved layer Utilizing custom options for route generation  Creation of Printer Friendly CSS  Waypoint Generation  Create Link  Options Modal Dialog 16

17. 17

18.  Installing ArcGIS Server  Configuring of ArcGIS  Setup of network analyst toolkit  Setting up the web server  Uploading mapping data  Maintaining the server 18

19. 19

20.  Research of mapping data fields  Merging of bike trail and road data  Integration of bike trail and road data  Design algorithms for custom routing preferences 20

21.  Roadblocks: Acquiring the ArcGIS software Proper server setup Merging data Proper bike trail networking Server crashes Uploading data to the server  Planning, Mitigation, Solution 21

22. 22

23.  JavaScript Testing Basic unit tests  Requirements Testing Link logic, Printer friendly  General Route Testing Discussion with Dr. Daniels  Usability Testing Discussion about the application with cyclists during a scheduled testing time. 23

24.  How-to videos  Better Examples  A clearly labeled glossary  An ESRI MVP system  Pass in dynamic parameters via JavaScript API 24

25. Conclusion We came together well as a team and were able to overcome major roadblocks to successfully complete the project. Lessons Learned  Ask for help early  Don’t wait on others to get back to you  Don’t underestimate the complexity of learning a new software package  Anticipate major roadblocks earlier 25

26.  Streamline merging and joining of GIS data Possible to create a tool to automatically do this  Further routing algorithm refinement  Addition of user comment feature on the client module 26

27. 27 TO DO (piecart)

28. 28