When I review a report, I almost always zoom in on the map, then use the "streetview" feature to get a feel for the context (road width, presence of bike lanes, speed limits, line of sight visibility, general road conditions, etc). That helps me to get a better understanding of what the driver and the cyclist/s were experiencing when the incident occurred.
I might make the FAQ available to non-registered users . . . but in general, cyclists seem to "get it" or they don't. At this stage of development, I'm not really looking to "sell" the idea to fence-sitters, I want the core of the community built around experienced cyclists that have balanced perspective on what's happening out there on the roads.
Regarding social media, I have been reticent to engage for several reasons but now realize I probably have to . So I have started to include some of that information in the email notifications. And I am cleverly "hidden" at @eezis and @closecalldb and Kennett Peterson volunteers to keep a FaceBook page (and you might wish to follow his blog: https://kennettron.wordpress.com/2014/10/18/adelaide/).
Thank you @eezis for linking to Kennetts blogpost. What a painfully sad story. Lets hope that Adelaide recovers completely and the driver won't be allowed behind another steering wheel.
Just yesterday afternoon I had another reckless driver deliberately drive up close to a few centimeters behind my rear wheel because he saw me as an obstacle. This was just 30 Meters away from a red light. The argument through the driver window, as always in situations like this, lead nowhere. People like this know, that there will be no consequences to their behaviour, so they keep on risking other peoples lives...
You might be interested in the german project http://wegeheld.org, which mainly focuses on documenting parking offences. Sadly the interface of the app is not there yet.
Being able to use a phone to document and upload an incident report complete with pictures/videos and GPS location and GPS track info would be a great plus to any such app. Also being able to warn other cyclists of reckless drivers in a specific area or of an ongoing incident might be helpful (i.e. if witnesses are needed).
When I review a report, I almost always zoom in on the map, then use the "streetview" feature to get a feel for the context (road width, presence of bike lanes, speed limits, line of sight visibility, general road conditions, etc). That helps me to get a better understanding of what the driver and the cyclist/s were experiencing when the incident occurred.
Regarding the contact info, unregistered users can access it from the login/register drop down: http://closecalldatabase.com/contact-u
Registered users can access it via their account drop down or from the FAQ: http://closecalldatabase.com/contact-r/
I might make the FAQ available to non-registered users . . . but in general, cyclists seem to "get it" or they don't. At this stage of development, I'm not really looking to "sell" the idea to fence-sitters, I want the core of the community built around experienced cyclists that have balanced perspective on what's happening out there on the roads.
Regarding social media, I have been reticent to engage for several reasons but now realize I probably have to . So I have started to include some of that information in the email notifications. And I am cleverly "hidden" at @eezis and @closecalldb and Kennett Peterson volunteers to keep a FaceBook page (and you might wish to follow his blog: https://kennettron.wordpress.com/2014/10/18/adelaide/).
If you ride, you can find me on Strava as well.