Category Archives: hackathon

Can Police BodyCam Video be Public while protecting Privacy?

Seattle Mayor Ed Murray

Seattle Mayor Ed Murray launches bodycam Workshop

You have a serious car accident. The police arrive and investigate. They issue a citation and write a report. The officers are wearing body-worn video cameras and their cars have dashcam video. At the end of the event the officer gives you a code. The next day you go online to the police department’s website, key in the code and all the materials regarding the collision are available to you – the videos, with a written transcript, the officers’ reports, the citation, the sketches and photographs of the accident scene, witness statements, and perhaps a history of other collisions and problems at that intersection.

That’s one vision laid out at a body-cam video workshop hosted by the Seattle Police Department on Tuesday, June 23. The event included officers from the Orlando, Louisville and Dallas police departments, plus representatives of the Police Foundation, Code for America and Socrata, the Seattle company which powers open data portals such as data.gov and data.seattle.gov. These organizations are all participating in the White House sponsored Police Open Data initiative, announced last month by the Obama Administration.

“Policing is in a crisis,” said Seattle Police Chief Operating Officer (COO) Mike Wagers several times during the workshop. “Police are not necessarily using more force or making more mistakes,” he added, but there’s been a change in the technology available to the general public. “Two-thirds of adults in the United States will own a camera-capable smartphone by the end of this year.” Those smartphones mean there is more video than ever being taken of police-citizen encounters and uploaded to YouTube and similar sites.

What’s the real future for police video?   Can the privacy of victims, children and witnesses be protected while at the same time making this video public?   Is it possible to “redact” or blur the faces and audio of such people to protect them yet release the video to the public?

The rest of this article is on GeekWire here.

See also the previous article discussing how Seattle Police held a hackathon in December, 2014, to find ways to redact video.

Implementing a body-worn video camera program requires much more than just buying the cameras themselves – there is storage and indexing and search and making the video public and much more – here is a previous blog post discussing these issues.

1 Comment

Filed under 911, hackathon, Law Enforcement, Seattle Police, video

Inside the First-ever Seattle Police Hackathon

Henry Kroll Demonstrates Redaction

Henry Kroll Demonstrates Redaction

The Seattle Police Department (SPD) held its first-ever hackathon on Friday, December 19th. The event was focused on a single problem: How to redact the video streams recorded by police officers from their dashcams and (soon) body-worn video cameras.

More than 80 people filled the room from 10 a.m. to 3 p.m. About one-third were technology professionals or part-timers like Henry Kroll, who makes a living as a salmon fisherman but focuses on video and other technology issues in his spare time.  The remainder were Seattle police and other public officials, a few members of the community, and a number of people from local companies such as Amazon Web Services and Evidence.com, plus a substantial media presence from local television stations and newspapers.

Seven teams made presentations and demonstrations …

Read the rest of this article on Geekwire here.

1 Comment

Filed under government operations, hackathon, Law Enforcement, Seattle Police, video

Apps Contests are Stupid

Hackathons and App ContestsIt seems like apps contests and apps challenges and hackathons sponsored by governments have been all the rage over the last couple of years.

They were kinda cool when they were new, in 2008, such as Washington DC’s original “Apps for Democracy“.   Vivek Kundra, then CTO of the District, valued the apps developed there at $2.3 million, although how he arrived at that number is unknown.

But now apps contests are not just overdone – there are just so many of them – but actually are becoming counterproductive, turning off developers and governments.   In fact, they are stupid.

Why?

First, the data sources are not standardized between different cities, counties and states.   This leads to myriad problems.

One of the great breakthrough ideas in the government of the District of Columbia in 2008 was the concept of a “data catalog“.   Governments have always had masses of data which they crunched to produce reports and insights and to support policy development.  But they also kept such data under lock-and-key.   The District’s government made some of those datasets open and available for citizens, academics, researchers and app developers to use.   Kundra’s successors in D.C., Bryan Sivak and Rob Mancini, extended the District’s data catalog to 507 datasets.   Kundra ported the idea to the federal government with data.gov, and a whole industry – including Seattle startup Socrata, is now built on opening up data.

But very few “normal” citizens are interested in this stuff.  Many of them don’t have the skills or interest to spend a lot of time loading thousands of rows of data into a spreadsheet or some statistics program and crunching the data.  Most non-policy-wonk citizens, if they have an opinion on a policy issue at all, have that opinion based on a logical or emotional basis and don’t generally want it polluted or confused by facts.  As an example many people feel “crime is rampant in our city, we need more cops”, when, actually, violent crime has dropped steadily in almost every US City for the last 20 years.

Nevertheless, the open data catalog is a brilliant idea because it allows developers to build apps using that data and display it in new and interesting ways.

My favorite example of this from the Apps for Democracy days is the “stumble safely” app.

This app used the crime dataset from the DC government.  It took your location, as determined from the GPS on your smartphone, along with the time of day, day of the week and other information.    It mashed that data against the crime dataset.   And it showed the safest path for you to “stumble home” from a night of eating or drinking.

It no longer works.

Stumble SafelyA primary reason:  “stumble safely” used the DC crime dataset, but was useless outside the District of Columbia.   Few other cities – even today – have put their crime datasets in an open data catalog.  And the formats of those datasets vary widely from place to place.   So “stumble safely”, written for the District of Columbia, won’t work anyplace else unless it is modified for each individual city or government.

This is a common problem with almost all government open data on the web.

In fact, the only commonly used data which is standardized – as far as I know – is transit data with the GTFS standard promulgated by Google.  Transit data is widely standardized because transit agencies are like private companies.  They have to market and sell their services – ridership on buses and trains – or they will run budget deficits and cease to exist.

Few other government organizations are in the same situation – there is little incentive for police departments or fire departments or building inspectors or water departments or electric utilities to standardize their datasets and make them open.  Indeed, most of them fear (wrongly so), that exposing data will open them to criticism for problems with the data or bad comparisons with other agencies, e.g. being less efficient or more expensive at delivering service than the same agency in a nearby city.   And every agency will say “we don’t have the time or money to standardize our data.”   It takes strong leadership (aka “arm twisting”) by an elected official or extraordinary leadership by a CIO to push an open data initiative forward.

Yelp, Code for America and the City of San Francisco are trying to standardize restaurant inspection data with the LIVES specification, an effort I applaud.    But I predict this will be a slow slog – slow adoption – for the reasons mentioned above.

A second major reason apps contests are stupid is the lack of monetization.   Apps developers need to eat, too, and put a roof over their heads and a Porsche in their garage.  They’re all looking to create that “killer app”  which will be downloaded a million times at a $9.99 per download.

But how many apps created from hackathons or apps challenges or contests are monetized?   How many of them are still active and downloaded and used?

My answer:  few, very few.

Stumble safely, alas, is dead (just click on the link here). Most of the apps on Apps for Democracy and other apps contest sites are dead.

A few are living and continuing to develop because their creators are passionate about them (Living Voters Guide by Travis Kriplean) or they do have a monetized component (Seattle Emergency Radio by Brian Adams, monetized via advertising).

One Bus AwayAnother potential avenue for monetization is for a City/County/State government to take over the use, care and feeding of an app after an apps contest.   That sometimes happens, but often can be a dicey proposition.  Brian Ferris, a Ph.D. student at the University of Washington in Seattle, wrote One Bus Away, an extraordinarily innovative transit application to track, in real time bus arrival times without using GPS (since Seattle buses at that time had no on-board GPS).  It has a 100,000 users each week.  Brian now works for Google in Zurich, and the area’s four transit agencies are trying (and fighting with each other) on how to keep the app going.

Evergreen Apps CompetitionAnother possible solution to the monetization problem is offering prize money to encourage participation such as the $100,000 offered this summer by Battle Hack.  When we did the evergreen apps challenge last year in Seattle, the three governments involved were able to offer some prize money funded by federal grants and local innovation funds.  But that’s rare – taxpayers will quickly wonder why we’re offering money to hackers when potholes are still jarring their cars.

One potential exception to the hackathon/monetization problem is New York City.  New York City has its “Big Apps” competitions, 8 million people, hundreds of thousands of businesses and innovative Mayoral leadership with Michael Bloomberg.   It represents an “apps ecosystem” which might survive and thrive despite the other hurdles.

If most apps contests are stupid, where do we go from here?

I’m not sure how to get datasets standardized across 3000 counties and 18,000 or more cities and 50 states.   Perhaps private companies such as Socrata, a premier provider of data catalog services such as data.gov, or a company which has monetized data such as CrimeReports.com can figure that out.   Or – and this is a long shot – perhaps the Mayors’ Innovation Task Force of the US Conference of Mayors would take this on, but I’m not holding my breath.

Perhaps an innovative state government will take leadership and build a data catalog with its cities and counties and standardize the data on the catalog.  This presents a great economic development opportunity – think of all the startup companies in that state which might develop statewide apps, or mash up the government open data against data from other sources such as the census or sales data from, say, Amazon.

The second problem – monetization of apps – will be hard to solve unless and until data is standardized so a single app – a crime reporting app, for example – can be downloaded and used across an entire state or the nation with the potential for millions of users.

In the meantime, we’ll have to rely on the kindness of friends to the government community like Travis Kriplean, innovative leaders like Jay Nath in San Francisco and Mark Headd in Philly, plus the ongoing attempts to standardize data like GTFS and LIVES to carry us forward.

But proliferating these stupid apps contests sure ain’t going to do it.

23 Comments

Filed under apps, hackathon, open data