Why we use OpenStreetMap

When I created DeFlock back in October of 2024, I set out to find the best way of creating a massive database of Automated License Plate Readers (ALPRs). I considered reinventing the wheel and starting my own database, but that seemed to have more downsides than the other options. Before DeFlock was launched, OpenStreetMap already contained thousands of ALPRs added by mapping enthusiasts, so it only made sense to make use of existing crowdsourced data for a new crowdsourced map. OSM also offers greater protection than simply using our own database. There is a large community built around OSM who monitor changesets for vandalism and revert anything that appears as such, much like Wikipedia.

Beyond that, decoupling the map data from the website turned out to be a smart move. DeFlock has been under attack since it was established. Less than a year after its launch, we got a Cease & Desist from Flock with a bunch of bogus trademark claims. We believe this is an effort to make our site harder to find, not a legitimate claim. If anything does happen to this site, whether it’s changing names or even shutting down completely, the data doesn’t go with it. DeFlock is open source, and anyone can spin up another instance or even create their own website entirely with the same data.

From a technical perspective, OSM also has a powerful API for querying data. Their Overpass API allows us to query any feature in OSM through their robust DSL. This even allows the site to be expanded to other surveillance features that are mapped in OSM, such as gunshot detectors or police observation devices.

For all these reasons, we’ve decided to use OpenStreetMap as the database for our map. While there is still some friction having to use an OSM editor rather than being able to place a pin directly on the site, that’s something we hope to change eventually with a custom editor.