After the most recent presentation to the class, I've decided to focus on using the first solution. So from today onward, my system will include designs for the bike beacons, and an iphone application with different views between cyclists and Department of Transportation users. Here's that system as a reminder.
It will use beacons and a smartphone application to track routes. The routes will be sent to a satellite and collected back in the application. Department of Transportation users can then log in and view that mapped information around the city for safety adjustments.
To better structure my progress and my understanding of how the system and application will work, I've started a rough application map. This way I can visually see the links between navigation and different parts of the system.
The believe that application should first start with the option to immediately track your route or to continue to the home map screen. Cyclists that are in a hurry to start their commute shouldn't have to navigate though an application when they are in a time crunch to get somewhere. So with a simple tap on that screen option, they should be able to start their ride right away. Should the user decide to continue into the application, they will be greeted with a map of their surrounding area.
There will be three main icons to continue to the next level into the application. The first one will pertain to the map, and contain a variety of sorting options to view the map including: time, area, bike lanes, and roads. Time will sort the viewed map by time of day, week, month, or year and display the number of riders on those roads accordingly. This is particularly useful for Department of Transportation users to monitor cyclist activity around Kansas City. Area will adjust the map to the local area around the user, an area of so many miles around the user, parts of town, or the entirety of Kansas City. Bike lanes will be a safety section, letting users see not only where bike lanes exist around the city, but where DoT is putting new ones in. Finally, the roads option will let the user filter the map to show only major or minor roads, or both at once.
The second icon will be the tracking icon. This will be the manual option, usable perhaps to the cyclist already in the application or for users who missed the option at the starting screen. It lets the user turn on the gps route tracking at the beginning of their route, and then turn it off at the end. The user is then taken to the route they finished displayed on the map without any other information from other users. Once the route is complete the user might get a notification, asking them if they encountered any dangerous areas or hazardous obstructions along they way. The user could continue if their ride was fine, or input the safety issue for DoT to view. For those that continue, it will take them directly to the next icon, which can also be entered on the home screen.
The third icon will be for the user's routes. By touching this icon, the user will enter their route map, able to view any route they've logged into the site. These can be viewed all at once on a map, or arranged by date and area. Date will be the default sorting state, but the area option would bring up routes closest to the user's current location. The map view would show the same route ridden many times in the form of density. Perhaps using color. The user could also touch another option to the side, containing routes recommended to the user via DoT. These routes might be safer than their current route, or new routes that they have ridden that have recieved safety changes.
There will be three main icons to continue to the next level into the application. The first one will pertain to the map, and contain a variety of sorting options to view the map including: time, area, bike lanes, and roads. Time will sort the viewed map by time of day, week, month, or year and display the number of riders on those roads accordingly. This is particularly useful for Department of Transportation users to monitor cyclist activity around Kansas City. Area will adjust the map to the local area around the user, an area of so many miles around the user, parts of town, or the entirety of Kansas City. Bike lanes will be a safety section, letting users see not only where bike lanes exist around the city, but where DoT is putting new ones in. Finally, the roads option will let the user filter the map to show only major or minor roads, or both at once.
The second icon will be the tracking icon. This will be the manual option, usable perhaps to the cyclist already in the application or for users who missed the option at the starting screen. It lets the user turn on the gps route tracking at the beginning of their route, and then turn it off at the end. The user is then taken to the route they finished displayed on the map without any other information from other users. Once the route is complete the user might get a notification, asking them if they encountered any dangerous areas or hazardous obstructions along they way. The user could continue if their ride was fine, or input the safety issue for DoT to view. For those that continue, it will take them directly to the next icon, which can also be entered on the home screen.
The third icon will be for the user's routes. By touching this icon, the user will enter their route map, able to view any route they've logged into the site. These can be viewed all at once on a map, or arranged by date and area. Date will be the default sorting state, but the area option would bring up routes closest to the user's current location. The map view would show the same route ridden many times in the form of density. Perhaps using color. The user could also touch another option to the side, containing routes recommended to the user via DoT. These routes might be safer than their current route, or new routes that they have ridden that have recieved safety changes.
No comments:
Post a Comment