HISTORICAL SURVEILLANCE MAP

How did the archived system fit together?

This map presents a Behind the Shield MJ research extract derived from archived upstream device data. It separates Wing-integrated video-feed records, Flock ALPR devices, PTZ/video devices, approximate Wing gateway relationships, and other device types associated with Mt. Juliet.

Dataset records—Not necessarily physical cameras

Wing feed records—Not gateway appliances

Researched Wing sites—Grouped by cameraSiteId

Unmapped Wing records—No guessed map points

Historical data - not a current inventory

This map is based on an archived late-2025 Flock Safety device dataset. The Behind the Shield MJ cleaned research extract carries a November 2025 project-snapshot label, while preserved source-record timestamps extend into December 2025; the exact relationship between those dates has not been independently established. Devices, feeds, facilities, statuses, assignments, and configurations may have changed.

Wing camera location notice: The historical dataset confirms that Wing-classified camera-feed records with the listed names existed in the archived Flock dataset. What it does not independently confirm is the exact physical location of each camera. Camera/site locations shown on this map are approximate and were inferred from camera names, publicly available information, and location research. A dot on the map should not be interpreted as confirmation that a camera is mounted at that exact point. Some names identify locations very clearly, such as "CDP - Pavilion 5," while others are more ambiguous.

For some Wing-integrated records, the upstream dataset plotted a gateway-area point rather than the physical camera. Researched camera/site and gateway points are therefore approximate; unresolved or mobile records remain unmapped rather than receiving guessed coordinates.

METHOD & LIMITS

How to read this map

The map combines preserved source fields with clearly separated Behind the Shield MJ research fields.

Historical, not current. The extract is a late-2025 record and cannot establish the current device or feed inventory.
Records are not physical-camera counts. One dataset row may describe a device, video feed, integration record, or other system component.
Three coordinate meanings remain separate. A Flock-mapped coordinate is the upstream plotted point; a camera/site coordinate is a Behind the Shield MJ researched approximate facility or area, not a verified exact camera mount; and a gateway coordinate is an approximate visualization point, not a verified exact gateway mount. None establishes an exact field of view.
Wing sites are semantic groups. Each site node represents one researched cameraSiteId grouping, not a generic geographic cluster.
Relationship views are selection-specific. A selected site shows one line per distinct gateway represented by its currently matching feeds; a selected feed narrows to its single gateway relationship; a selected gateway shows one line per distinct currently matching researched site.
Gateway relationships use stable identifiers. Feeds resolve through gatewayHubId, and duplicate feed relationships at the same site and gateway are collapsed. Lines show integration/data relationships—not cables, network routes, wireless paths, line of sight, or exact technical data flow.
Sensitive context is narrowly labeled. The visible “S” treatment identifies cleaned-research contexts such as restroom-adjacent areas, playgrounds, or school-associated locations; it does not establish exact field of view, exact mounting position, or who was recorded.
Unresolved stays unresolved. Mobile trailers and insufficiently resolved feeds are listed in text without invented map points.
Wing integration is not per-feed FreeForm confirmation. The archived extract establishes Wing-classified feed records. The separate implementation SOW describes gateway architecture intended to enable Flock AI/FreeForm Search, but reviewed evidence does not establish FreeForm enablement on every feed.
Picard is shown separately. The historical deviceType value identifies Picard systems but, by itself, does not establish the function of every individual Picard record. Picard PTZ records remain in the PTZ/video layer.
Filters also govern selection. Markers, selected highlights, detail content, and relationship lines are recomputed together; a selected item clears when it no longer matches.
Source and research fields are distinct. Device type, status, source timestamps, and Flock-mapped coordinates originate in the historical dataset; site groupings, sensitive-context research, and approximate camera/gateway points are Behind the Shield MJ derived fields.

PROVENANCE & DOWNLOADS

Review the map data

The three downloadable Mt. Juliet CSVs are cleaned or derived Behind the Shield MJ research artifacts. They are not presented as files published by FlockSurveillance.org or Flock Safety.

Canonical upstream source

An upstream researcher-published historical device table is the provenance source modeled in the Source Library. Behind the Shield MJ used that material to create the Mt. Juliet-specific files below; the upstream source identity and observed archive context are documented separately from these local artifacts.

View canonical source

Behind the Shield MJ data files

Derived record-level CSVAuthoritative record-level Mt. Juliet map dataset combining preserved source fields with Behind the Shield MJ research fields.
Derived Wing-sites CSVDerived Wing site index grouped by stable cameraSiteId for site-level visualization.
Derived gateway CSVDerived approximate Wing gateway visualization points and stable gatewayHubId relationships.