Skip to content

CCTV cameras

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade D · dataset: Stream (a timestamped recording) · type cctv

What it is

IP cameras reached over RTSP or ONVIF. In the test estate there is one camera per dock, nine in all. The connector reference is CCTV and video.

Grade

D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typecctv
Other spellings that resolvevideostream, camera
Settingsendpoint_url, username, max_frames, transport, device_capture
Credentialspassword

The test connection

The test estate defines 9 connections of this type. The first is shown, and expected.json lists every one.

Dock camera CAM-NORTH-01

SettingTest value
endpoint_urlrtsps://cam-dock-north-01.quillmere.invalid:322/stream1
usernameviewer
max_frames12
transporttcp
device_capturefalse

Credentials: password. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. For a camera that serves its stream encrypted, over rtsps:// or https://, add one connection per camera in Settings › Integrations › Systems, with the settings above. FACE refuses an rtsp:// or http:// feed: the frames and the camera’s login would cross the network unencrypted.
  2. To watch a camera, open Surveillance from its connection’s card on Ask. It opens with that camera chosen and starts the live feed.
  3. The recording below holds each test camera’s frames under frames/<camera_id>/, with their timestamps in frames.jsonl. Open them next to expected.json to see what FACE builds from the frames.

What FACE finds

Against a camera, FACE asks it what it is (RTSP DESCRIBE, or ONVIF) and samples frames, up to max_frames, at fetch time.

DatasetKindDomainPrimary keyRowsFields
framesvideo_frame_sequencedock_visionnone737

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 3 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
deviceframes.camera_idbigquery, databricks, files, gps, iot, kafka, mqtt, postgres, rfid, servicenow
dockframes.dock_idexcel, files, kafka, logisticsapi, postgres, sensorgateway, whs, yms
trailerframes.trailer_iddatabricks, document, excel, iot, kafka, mqtt, postgres, servicenow, tms, yms

Evidence it holds for the planted anomalies:

  • ANOM-6, An RFID read with no matching ASN. streams/cctv/frames.jsonl, look for "camera_id":"CAM-EAST-03" (frame at the read time, no trailer_id).

See all connectors at once for the walkthrough across every source.

Download

Streams are dialled and held open, so their datasets are replay recordings under streams/cctv/, not a zip. Download the files, and use them as described above.

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.