SydneyHack 2016

Generate insights (understand) -> predict

SIRA - greenslips
CRS crash locations etc
Event id: number from the police, manually input data, could be incorrect
Insight only useful if actionable.
Implementation of Solutions
-

Data must be placed in context -> add context i.e. roads: major roads?
Specific blackspot areas? Broader context they travel from A to B
Create a streetscape from data
Trace pedestrian/traffic movement
Look at behaviour of all road users (cars! Buses, public transport networks)
Look at movement of users to track interaction

What to do with data

-

City science group Monash university for inspo

Melbourne pedestrian crash animated heatmap
http://nearlykilled.me cyclists self-log near-accidents
o crowdsourced data
o combine with given data to enrich
data -> drive solutions, inspire a solution
who are we designing the solution for?
o Planning tool? Implementation for new safety measures?
o For drivers?
o For pedestrians?
Empathise, define, ideate, prototype, iterate

Sign in with a Hotmail account

Hotmail.com/email

Judging Process
Each team will have exactly two minutes to present the methods and solution.
The judging will take place in two tracks and the teams will be randomly
assigned to one of the tracks. The presentations will take place after lunch on
Sunday, 11 September, starting around 12.30 pm and will be held in the two
lecture theatres.
The criteria and weights for judging the work will be as follows:
Innovation (50%)
Is the solution novel? Does it solve a problem in a creative or never-seen-before way?

Solution is novel in that it compiles data into an accessible format in

which you can clearly see where the accidents are happening,
specifically in which areas, and specifically on which streets, as well as
the severity of such events
This historical data is then fed directly into an app on the users phone
which can then notify the user that they are in a historically hazardous
location/what hazards in particular to look for based on phone GPS
It essentially puts the data in commuters hands for easy access
o Are people really going to use this?
o What incentives are there for people to use this app?
o Are people motivated to use it simply to protect themselves?
What about people who travel to work every day and are
therefore already very familiar with the accidents which have
historically occurred?
Possible integration with Waze so then you could have both
historical and live data
How are we going to integrate historical data into the app
map?
The Map itself could possibly just be used by policymakers to identify
problem streets and areas to inform infrastructure development in public
transport or road-building/sky-bridge building etc.

Implementability (25%)
Is the solution implementable or likely to be implemented?
-

Very implementable
The map itself should be pretty likely to be implemented; it is likely that similar processes are
already being used by urban planners
As for the app, it should be implementable if the proper resources and expertise are supplied

Impact and likelihood of adoption (25%)

Will the application have real impact? Can it change the world, or at least help someone in the community?
-

Map created using this method can help inform policy to:
o isolate causes of crashes e.g. alcohol, fatigue, speeding
o assess the effectiveness of zoning regulations e.g. school zone speed limits
o identify particular problem areas
App can help the community via notification of hazards

Does it solve a stated goal of the hackathon?

The top four teams from each track will advance to the final presentation round in which the finalist teams
will have five minutes to make more detailed presentations. They will have 30 minutes to prepare the more
detailed presentation after the finalists are announced.

The judges will use the same criteria as above for assessing the final
presentations and the winners will be announced by the Chair of the Judging
Panel, Dr. Ian Oppermann. Prize Giving will follow.

SydneyHack (Pedestrian safety hackathon) is on this Friday, 9 September, commencing at

6pm.
Check-in will be open from 5.30pm. You will be required to sign the individual Non-Disclosure
Agreement (copy attached) prior to being checked in.
The labs will be open till 10pm on Friday, from 9am to 10pm on Saturday, and again at 9am on
Sunday. Breakfast will be served starting 8.45am and lunch starting 12pm on both days.
All work should be completed by 12pm on Sunday, 11 September.
Each team will have exactly two minutes to present the findings and outputs in two parallel tracks
(starting 12.30pm). The judging panel will select 8 teams (4 from each track) for final presentations of
5 minutes each following which the winners will be announced. Prize giving will follow.
For more information on the judging process please visit the SydneyHack website.
TEAMS
If you have formed a team since signing up, please login to your Eventbrite registration and add your
team information as soon as possible.
To do this login to Eventbrite, choose Tickets then click on the hackathon, then click Edit. If you scroll
down you will see the question are "Are you already a member of a team?", change this to "Yes" and
enter your team name in the text box.
You can do this also if you would like to change your team.
There are 9 persons registered as one-person teams and 7 registered as two-person teams.
Please note that all teams will have to have at least three and preferably four members. Please try
and find additional members for your teams to be eligible to participate.
There will be another opportunity after the presentations this Friday (which will finish by 7 pm) for
registered students without teams to form right size teams.

Structure
1) Factors
2) Hypothesis
3) Visualisation
a. Create tool
b. Something that works
c. Solve the issue e.g. create a map which shows dangerous places
Microstrategy
Map Process

Data based mainly on geographical -> use ArcMap for clear display
Take pedestrian casualty -> identify where accidents happened a lot
Joined this data to SA1 area so we could calculate density of accidents in
each SA1
Select SA1s with density >200 accidents per SQKM, clear that Sydney
CBD is very serious

Also analysed what type of vehicles caused these accidents -> bar chart
for each area which shows the composition comprised by each type
Therefore can identify most dangerous areas and most dangerous vehicles