# Rogers LPR Locations Map `LPR locations.pdf` is the Department's answer to the camera-map category: **one page, 15,993,426 bytes, two embedded raster images, and 122 characters of extractable text.** The entire text layer reads: > "LPR Locations / Red=Current Flock Locations / Blue=Future Locations / 3 mi / N / Image © 2025 Airbus" It is a Google Earth screenshot of Rogers with dropped pins, each labeled with an intersection and a travel direction. Red pins mark current Flock locations; blue pins mark future ones. ## What the map shows Reading the rendered image, the pins carry named intersections with directions, among them **2nd/Hudson WB, Dixieland/Olive SB, 2nd/Locust EB, 21st/Walnut WB, 1st/New Hope, I49/Whitaker EB, and 26th/Pleasant Grove WB** in red, and **Hudson/Bekaert EB, I49/Olive EB, 8th/Olive SB, I49/Walnut EB, 26th/Water Park NB, Promenade/New Hope EB, I49/Whitaker WB, 1st/Chandler NB, Dixieland/Pleasant Grove NB, 8th/Pleasant Grove NB, and Mt. Hebron/Garrett NB** in blue. Several labels run off the image edge and are not fully legible, so this list is **not represented as complete**, and the red/blue counts are not treated as a device census. ## Why no coordinates entered the map **The file contains no latitude, longitude, address, or other machine-readable location data.** The pin positions exist only as pixels over satellite imagery. The corpus does not derive coordinates from imagery. Geolocating a pin by eye and publishing the result would manufacture a precision the record does not contain and attribute to the agency a coordinate it never stated. [[Arkansas Camera Map Data]] is therefore **unchanged by this file**. The only Rogers coordinate in the dataset comes from an ARDOT plan sheet ([[Rogers ARDOT Permit P1869 and Case 971374]]), and it is a Condor video camera rather than one of these LPRs. ## The disclosure posture this represents Rogers produced a camera map promptly and without objection on that category, which several custodians have not. The named intersections are genuinely informative, and the current-versus-future distinction is more than most have supplied. What it produced is a picture of one. The format is not queryable, cannot be reconciled by count against the ten contracted LPRs, and is not usable as coordinate data. Other agency productions show that Flock can generate devices-and-locations exports, and the [[Rogers Flock LPR Pilot Procurement]] invoice links to a Flock planner “Location of Services” page. This production does not establish whether Rogers generated, retained, or could export native coordinate values. This is a distinct produced format from the ones already catalogued: a visual answer without machine-readable coordinates. The record does not establish intent to withhold data. Compare Russellville, which produced a native CSV with coordinates, and Bentonville, which produced device-health screenshots with addresses but no coordinates. ## Cross-references - [[rogers-pd/2026-07-24-first-production/_overview|Rogers First Production Overview]] - [[Rogers ARDOT Permit P1869 and Case 971374]]; [[Rogers Flock LPR Pilot Procurement]] - [[Arkansas ALPR Camera Coordinates and Directional Nomenclature]]; [[The Disposition Is the Record]] ## Open questions / follow-ups - Whether an existing native devices-and-locations export with coordinates is retained or exportable for Rogers. - Reconciliation of the mapped pins against the ten contracted LPRs and against installation dates. - The full legible pin list, including labels cut off at the image edges. - Whether the blue "future" sites have since been installed.