Somaliland National Police · National checkpoint command
PIN is not checked. Your scope (regions & checkpoints) is enforced after sign-in.
Capture who was stopped, where, vehicle details, ID, outcome, and free-text notes. Data stays in this browser session until you connect a live backend.
An extra lane into the same national stop record. Officers keep using this form exactly as today. When you deploy a Google Cloud Run endpoint and connect ANPR cameras, each camera POSTs a read to your API; your backend stores events in Firestore (or your DB) with a flag such as source = ANPR. The dashboard, All Stops, warrants, and Vehicle Lookup stay the same screens — they also show rows that arrived from cameras.
The camera software reads the plate at the lane, then sends HTTPS POST to your URL (plate, checkpoint code, time, confidence, optional snapshot URL). Your service validates an API key, normalizes the plate string, and writes one document per read.
Backend creates a pending or ANPR stop record (plate + checkpoint + time). An officer opens Log New Stop; the plate may be pre-filled from the queue. They complete driver, ID, outcome, and notes — same fields as now.
The same warrant and history checks run against your registry. High-risk or warrant hits can trigger the same alert path as a manual lookup — no separate "camera-only" workflow.
Design rule: manual and ANPR are parallel — both write compatible stop/event records; nothing in this form is removed when cameras go live.
| Stop ID | Time | Plate | Driver | Checkpoint | Region | Dur. | Outcome | Warrant |
|---|
| Warrant ID | Name | Plate | Offence | Issued | Last Seen | Crossings | Priority | Action |
|---|
Search by plate. The registry shows vehicle class (private, business, government, or military) plus crossing history scoped to your posting where applicable.
Use alongside the lookup result: occupant count, visible items, travel purpose, and documents. In production this ties to your stop record; here it is a local worksheet only.
General Police units support national mobility: highway patrol, cross-regional response, and liaison with Kaantroolada commanders. This brief is a placeholder for orders of the day, corridor priorities, and contact chains that your organisation would publish from a live server.
Use the same national dashboard and stops feed as command staff, but operational discipline still follows posting: when you log a stop, select the Kaantroolada post where the encounter occurred. Patrol units do not replace checkpoint registers — they supplement them.
Each role maps to different tasks: who may edit checkpoints, who may manage all users, and who may reset credentials.
Assign commanding officers and review posting strength. Actions respect the simulated role above.
| Checkpoint | Region | Commander | Staff | Status | Actions |
|---|
| Name | Badge | Role | Checkpoint scope | Status | Actions |
|---|