The Protest Route in the Dataset

The transport department published daily cycling routes as part of an open-data programme. Analyst Corin checked the latest release before a public workshop and noticed a dense line ending outside a private house. It came from a peaceful protest ride whose organiser had invited participants to meet at her home. Their route had been recorded by a city-funded app.

The public file contained no names, but local social media posts made the destination easy to interpret. Corin worried that combining two ordinary sources could expose someone more clearly than either source alone. His colleague argued that the route had happened in public and that withholding data because it involved a protest could look politically motivated.

Corin proposed a rule that applied to all journeys: remove precise beginnings and endings and publish only combined street-level counts where enough journeys existed. The department would still show transport patterns without presenting individual trips as reusable traces. Because the release was already online, he also contacted the organiser to explain what had happened, acknowledging that earlier downloads could not be recalled with certainty.

The organiser was angry, particularly because she had supported the open-data programme. She nevertheless helped test the revised format. It showed that the protest had increased cycling along the main road without drawing a line to her door. Corin published a change note explaining the general rule, not the private reason that had prompted it. Openness remained the programme's purpose, but he no longer treated every missing detail as a failure to be transparent.