Picycle Cyclist Safety

To content | To menu | To search

Friday 19 August 2016

Whats next?

Focus has shifted slightly in the last few months. Whilst the prototype unit proved to be a valuable test for what the platform will become, it also had a couple of issues:

  • It was very power hungry. There was no sense in trying to power a full operating system (let alone a Raspberry Pi) when a simpler design would achieve the same end.
  • Size. The Zero is impressively small, but when combined with external sensors, it became quite bulky.

Therefore, the long term plan will be to open source the design for the "MK1" unit, as there is still a lot of value to be discovered in a design running a full OS (plus the ease of build and use). The back-end infrastructure will continue to be developed and supportedallowing anyone to build their own unit based off the original design to help build the concept. GitHub users will be able to commit to the source and Azure/CI will take care of the rest.

Our main focus will be to complete the development of the "MK2" design, more to come about this soon!

Friday 1 July 2016

The vision


I started this project with aim of capturing the safety conditions that cyclists encounter on the roads, with the vision to build a data set capable of guiding infrastructure planning decisions and other similar type work.
This is achieved through creating a large and constantly growing empirical data set, capturing data about the surroundings of the cyclist. The output from this used as an indicator of safety (as opposed to relying on accident statistics and perceived safety data).

Why Picycle? Because at the heart of the data capture is a Raspberry Pi!

Credit is given to Dr Rich Boakes for his support in cultivating the idea and the mentorship provided.

Not just another cycling blog

Enough blogs about people nearly getting run down or knocked off on the roads. Time to do something about it!

This blog is to discuss the work on the Picycle Cyclist safety project, and related matter...