Actuar

Ask the office that pays the bill

A request sent to a police department's public information officer competes with press calls and lands with the people most practised at narrowing it. The same purchase appears in the procurement, purchasing, finance, or accounts payable records of whoever actually buys the equipment — a county board, a city finance office, a joint powers authority — and those offices process records requests as routine paperwork. Purchase orders, requisitions, and a vendor payment history for a fiscal year will show you what was bought, when, with whose money, and often what has been deployed without any public announcement.

Be specific enough to be inconvenient

Broad requests get delayed, estimated at an implausible fee, or refused as burdensome. Narrow ones are harder to wave away. The useful vocabulary is the vendor's own: a system's documentation will name its "user access logs", "network audit logs", or audit report exports, and asking for a record by the name its own software gives it removes the argument that no such record exists. Published audit logs from other jurisdictions are a good place to learn those names — the Have I Been Flocked project archives Flock audit logs released to other requesters. (It also offers a personal plate lookup; this project does not do that, and does not hold data about anybody's vehicle.)

Carve out the active investigation

The most common refusal is that data are part of an active criminal investigation, which Minn. Stat. § 13.82, subd. 7 does protect. Policies, contracts, inventories, audit logs, and aggregate counts are not investigative data, so say so in the request and exclude that category explicitly. It costs you nothing you wanted and takes away the easiest denial. Two further provisions are worth quoting when you meet resistance:

• § 13.82, subd. 31 makes public "the existence of all technology maintained by a law enforcement agency that may be used to electronically capture an audio, video, photographic, or other record of the activities of the general public." An agency may argue about the data a system collects; whether it owns the system is public.
• § 13.05, subd. 11 keeps data subject to the Act when a private contractor performs a government function. "The vendor has it" and "the vendor calls it proprietary" are not exemptions.

Follow the physical installation

A camera on a pole is construction. Permanent installations generally leave a trail of right-of-way, building, or electrical permits, and pole attachment agreements, held by a building or public works department that has no stake in the surveillance question. This works best as a cross-check: if procurement shows forty cameras bought and permits show twelve, the gap is the next question.

One caveat specific to Minnesota. Excavation notices go through Gopher State One Call , which is a private non-profit rather than a government entity, so it is not itself subject to ch. 13. Request locate and excavation records from the city or county in its role as a facility operator, where they are government data.

Check what is already published

Some of this does not need a request at all. Every Minnesota law enforcement agency operating a drone must report its warrantless deployments and total programme cost to the Commissioner of Public Safety each January under Minn. Stat. § 626.19, subd. 12, and the compiled statewide result is published by June — UAV annual reports, Minnesota BCA . Read that first, then request the agency's own submission, which is more granular than the compilation.

Watch the commercial pipeline

Records can leave a public agency by agreement rather than by breach. State driver and vehicle record systems disclose data to commercial brokers and to federal systems under standing agreements; in Minnesota those disclosures run through Driver and Vehicle Services under Minn. Stat. § 171.12, subd. 7 and the federal Driver's Privacy Protection Act, and subd. 7b requires a requester to certify the data will not be used for immigration enforcement. The agreements, and the record of how that certification is checked, are the thing to ask for — not anybody's driver record.

Do not do this alone

Local journalists can escalate a refusal in a way an individual requester cannot. University geography and data science departments will often take on the mapping and analysis as coursework. Historical and civic groups hold the context that makes a current map mean something — surveillance infrastructure laid over historically redlined neighbourhoods is a different argument than a dot map of cameras. This site ships redlining and racial covenant layers for exactly that comparison — turn them on alongside the camera layer on the map, and see the explainer for what the redlining grades mean and what they do not.

This is the ordinary case outside a city with its own police force, and it is the thing that most often stalls a local effort. A township has a board, an agenda, and an election behind it — and the readers inside its borders were bought by a county sheriff, mounted on a county road, on a county contract. Every lever the board can reach is real; none of them is the one attached to that camera.

Two questions decide what instrument you actually need, and it is worth settling them before drafting anything:

• Whose equipment is it? The camera layer records an operator where somebody mapped one, and leaves it null where nobody did — look your location up under what is around this place, which now names the operators of the cameras near a point and flags the ones that are not your own government. Where the operator is blank, that gap is itself the first records request: § 13.82, subd. 31 makes the existence of the technology public.
• How far do your town's powers reach? Minnesota towns hold the powers that ch. 365 and § 366.01 give them, and the broader ordinance powers under § 368.01 are available only to towns meeting a population or proximity threshold. Whether a given town's authority extends to equipment another government owns is a question for your town attorney and the Minnesota Association of Townships , not one this site can answer for you. Ask it first: the answer decides whether you are drafting a town ordinance or asking the county board for a resolution.

Whatever the answer, three things are open to a local board immediately and none of them depends on owning the equipment. It can file the records request itself — a government entity asking another government entity tends to get a faster and more complete answer than a resident does. It can put the item on a published agenda, which creates a public record and a date. And it can ask the county for the audit that § 13.824, subd. 6 already requires every ALPR operator to commission every two years, along with the public log under subd. 5 and the audit trail under subd. 7. Those documents exist whether or not anyone has ever asked for them, and reading them is usually what turns a general worry into a specific one.

Most of what is on this map is decided locally — by a county board that approves a jail contract, a city council that grants a data-centre abatement, or a sheriff who signs an agreement. These are the offices that can undo those decisions.

• Who represents me — Minnesota Secretary of State — your state legislators and districts.
• Directory of Minnesota city officials — League of Minnesota Cities.
• Minnesota county directory — county boards and sheriffs, who hold most of the authority on this map.
• Information Policy Analysis Division (IPAD) — the state office that issues advisory opinions when an agency refuses a data request. Free, and their opinions carry weight.

• Ask for the statute. An agency withholding data has to identify the specific provision that classifies it as not public. "It's law enforcement data" is not a citation.
• Ask for a fee estimate in writing before any work begins. Inspection of public data is free under Minnesota law; you only pay for copies.
• Request an IPAD advisory opinion. It costs nothing and often resolves a refusal without litigation.
• Narrow, then re-ask. A request refused as unduly burdensome will frequently succeed when scoped to one system, one quarter, or one contract.

Found a camera that is not here, or a community campaign we have missed? The camera layer is built on OpenStreetMap, so adding one there improves this map and every other project built on the same data. See how to contribute.