posted by Joe
Jonathan has posted analysis of data from the first month. Over 100 reports were filed in the Portland region during the first month, and that was with very little publicity. Even at this rate, at year's end B-SMaRT would generate 6 reports for every DMV cyclist crash report.
While the data analysis is very preliminary, I was surprised to see that only 2 of the 15 reported collisions will be reported to the DMV and make it into the official stats. It will be interesting to see how this trend holds up over the year.
Zooming way out in the report viewer, you notice reports are being filed in other regions as well. At least a dozen other regions from Tucson to Halifax have expressed interest in adopting the B-SMaRT system, and some of them are trying it out in real time! The next update will limit reports to the Portland-Vancouver metro region, but a new B-SMaRT will be offered (free of charge) to other regions.
As Jonathan mentioned, I hope to include Google Street View in the next update as well. That should help visualize problem and incident reports in the viewer. If you have any other feature requests, feel free to send them my way.
posted by Joe
UPDATE: See the launch story at BikePortland!
The tool is now open for early adopters. There is also a new option to try out the reporting tool without registering. Just click on either of the reporting links in the menu bar, and choose Take the system for a test ride. Your reports will not be saved, but this way more folks can put the tool through its paces and let us know what they would like to see.
The most recent 3 months or so of close calls from bikeportland.org have been added to the database. You can view them (and the first user-submitted reports!) in the View Reports section. Feel free to try everything out, and let me know if you find bugs or have suggestions.
posted by Joe
What is it? A way to collect and organize Portland area cyclists' experiences with risk on the roads.
How does it work? The locations of close calls, collisions, and problem areas are submitted using a map-based interface along with some information about them. Each report becomes immediately viewable and searchable. Users have the option of being contacted when a safety project is planned for locations they've reported on.
Why? The collected data could point to locations where design, maintenance, or enforcement improvements are needed. The database could also tap user knowledge to help craft such improvements.
How do I use it? Click on one of the links in the menu bar above to get started. Close Call/Collision reports can be filed for specific incidents. Problem location reports are appropriate for general concerns about trouble spots you are familiar with. The report viewer allows you to browse, search, or download submitted reports.
What about non-cyclists' experiences? While the experiences of motorists, pedestrians, and other non-cyclists are certainly valuable, their inclusion would make the data much more difficult to interpret. If there were enough interest, separate databases for other groups would be possible in the future.
Could the tool be used outside of Portland? Yes, but a few changes might be needed to better match local conditions and crash reporting standards.
What if I have trouble with the tool? If you find bugs or have suggestions, you can send them to Joe or post them in the comments section of the bikeportland.org release story.