How Safe is Your Suburb
- Created by
- Space-Time Research (Karl Ots, Jo Deeker, Ray Thornhill)
- data.australia.gov.au datasets used
- Other datasets used
- 2006 Population Census (from CDATA Online) - Australian Bureau of Statistics; LGA Map Boundary Shape File - Australian Bureau of Statistics
How Safe Is Your Suburb is an easy- to-use interactive web application that allows the public to gain greater awareness and insight into crime statistics in Local Government Areas (suburbs) in New South Wales. The tool can be used by residents, local governments, state and federal government, researchers, non-government agencies, and crime and policy makers to better understand the meaning of the statistics produced by the NSW Bureau of Crime Statistics and Research, and how the statistics can be applied to their lives.
How Safe Is Your Suburb embraces the Gov 2.0 philosophy by opening up a static dataset to the public in a useful way. The user can analyse and play with the data, comment on data, and then share their data with others.
For example, the user can choose different ‘reports’, make selections within each report to compare different types of crime over time, and then see which types of crime are more prevalent in their area. They can view an interactive thematic map of crime that provides a spatial visualisation of crime types across LGAs for a given year. They can also identify which suburbs have higher crime rates in total and in per-head of population. (It makes sense that there is more crime in more populous areas). Users can make comments on each visualisation they are working on.
The application mashes up NSW crime data with LGA boundary files and Census data from ABS. Space-Time Research has classified each offence into different categories to enable simpler analysis. More detail could be added to the application at a later date.
The application is built using Space-Time Research’s SuperVIEW product, and is hosted on the Google App Engine. In the spirit of a govhack style competition, our team of three (one database builder, one programmer, one analyst / writer) started working on the application just over 24 hours before it was due.