This is a Just the Facts (JTF) post: generated by AI from my own raw material (voice memos, session notes) and a short outline I wrote, then checked by me. What's a JTF?
Reading local crime stories on ARLnow, I kept wanting more detail than the articles gave. So I built two command-line tools that pull Arlington's police scanner traffic from Broadcastify, transcribe it, and let me read or play the calls for any time window. They're fun to use. I'm less sure they're useful: across three incidents, the radio traffic filled in details the news stories left out, but none of it contradicted them.
A creative angle for digging deeper on local stories
- Reading ARLnow stories like this one about gunfire in North Arlington, I had questions. For example, were Flock cameras or other AI tools involved? Almost certainly not Flock: the county ended its Flock contract in September. The article doesn't address this.
- So I wondered: what if I could get the original police scanner traffic? Maybe it would show details the story left out.
- Digging around, I found that Arlington's main police dispatch channel isn't encrypted, and Broadcastify Calls archives it. Broadcastify also has a developer program with an API for those archives. So I built a tool.
Bringing scanner traffic to the Unix command line
- broadcastifyassist is a thin shell wrapper around the Broadcastify Calls API endpoints. Broadcastify's developer terms restrict sharing tools built on its API, so this one stays private. If you write your own, the interface scannerassist expects is in the resources below.
- One thing it adds is aliases. Instead of using raw talk group IDs like
5000-1, I can ask forarl-police. An alias can also name several talk groups at once. - scannerassist sits on top of it and adds transcription and caching, which makes the raw audio much easier to work with.
- It downloads and transcribes every call in a time window, with chatgptassist doing the transcription.
- The audio and transcripts are cached, so running the same query again doesn't download or transcribe anything twice.
- Both tools are friendly to the command line and to AI agents: plain text output, one call per line.
- Claude used scannerassist to find the radio traffic for the shooting I was curious about, and for the other incidents I gave it.
- These tools are a lot of fun. They connect the command line to real events as they happened, and I can read the transcripts and play the audio with equal ease.
OK, they're cool tools. But are they useful?
- True: it's impressive that I can read an article and, a few minutes later, hear the officers talking about that incident.
- True: the radio fills in details the news story left out. For the shooting above: about a dozen calls from across North Arlington, a 9mm shell casing, a Ring camera, and an officer posting video of a possible getaway car.
- But none of it contradicted ARLnow. Across three incidents, the ARLnow stories held. The radio added texture, not corrections.
- I'm not yet ready to call this a game-changer, but I'm glad it's in my local news toolkit.
- Below are some examples of using the tools to explore this incident.
Code
$ # scannerassist's settings live in a small config file:
sed -e 's#^S3_CACHE=.*#S3_CACHE=s3://your-bucket/cache/scannerassist#' \
-e 's#^AWS_PROFILE_NAME=.*#AWS_PROFILE_NAME=your-aws-profile-name#' \
$HOME/.config/scannerassist/default.config
## Where audio and transcripts are shared across machines. Leave S3_CACHE
## empty to keep the cache on this machine only.
S3_CACHE=s3://your-bucket/cache/scannerassist
AWS_PROFILE_NAME=your-aws-profile-name
## How many calls to download and transcribe at once.
PARALLEL=6
## Passed to chatgptassist -a transcribe -m / -p. The context names the
## vocabulary to expect, which keeps the model from mishearing local names.
TRANSCRIBE_MODEL=gpt-transcribe
TRANSCRIBE_CONTEXT="Arlington County, Virginia police and fire radio dispatch traffic. Unit call signs, street addresses, 10-codes. Some transmissions are only a few words or static."
$ # https://www.arlnow.com/2026/11/07/man-arrested-after-gunfire-reported-in-parts-of-north-arlington/
# reports the shots were fired 'late Friday night'.
# Let's find the radio traffic:
scannerassist -a transcript -g arl-police \
-s '2026-11-06 23:45' -e '2026-11-07 01:30' |
grep -i shots | head -5 | block
2026-11-07 00:20:35|arl-police-dispatch|18|514|5000-1/1794028854.mp3|To the area around 3100 block of North Taylor Street, from before report of shots heard. Repeat, advised they heard four or five rapid gunshots from the area of 31st Street North. Also heard the same about 30 minutes ago. 3100 block of North Taylor Street.
2026-11-07 00:21:58|arl-police-dispatch|14|514|5000-1/1794028932.mp3|Pingo 11, 812, we advise we have a second caller calling in about shots, also 31st Street North, saying they heard four shots about four minutes ago.
2026-11-07 00:23:08|arl-police-dispatch|29|514|5000-1/1794029018.mp3|Type area, 4100 block of 4th Street North. Going to be for a report of shots heard outside of this building. RP is advising calling on app of appearance. They advise they heard four gunshots, then heard a man scream very loudly. Stated that it sounded like it came from nearby, possibly from near the trash can area in front of the building. Nothing else seen. 4100 block of 4th Street North.
2026-11-07 00:24:40|arl-police-dispatch|9|514|5000-1/1794029090.mp3|Oh eleven and twelve, you guys, we've got third caller for those gunshots. They heard two shots two to three minutes ago in the area of Military Road.
2026-11-07 00:29:57|arl-police-dispatch|7|3135091|5000-1/1794029406.mp3|27, I'll be available shortly. I'm out on that shots fired call, 4th Street. I'm talking with three behind the building.
$ # The fields are time, channel, seconds, radio ID, audio file and
# transcript. Here I capture the entire night, and then use awk
# to extract lines after the incident
scannerassist -a transcript -g arl-police \
-s '2026-11-06 23:45' -e '2026-11-07 01:30' > night.txt
awk -F'|' '$1 >= "2026-11-07 00:46" && $1 < "2026-11-07 00:59" && $6 != "" {
print $0
}' night.txt |
tee incident.txt |
awk -F'|' '{
print substr($1, 12), $6
}' | block | head -5
00:46:13 251, I've got a shell casing here.
00:46:19 251, what's your exact location?
00:46:41 It's gonna be 5500 block of 15th Street. It's gonna be a 9 millimeter.
00:46:50 Supervisor direct.
00:46:53 Or is anybody on that call with Crooked?
# extracting the audio files it's possible to # listen to the incident cat incident.txt | head -5 | cut -d'|' -f5 | scannerassist -a file | xargs -n1 afplay
$ # The shooting was one of many calls that night. An LLM can sort the
# whole night into incidents
PROMPT="This is police scanner traffic from one night: one radio call
per line, as time|channel|seconds|radio id|audio file|transcript.
Transcripts are machine-made and can garble words. List the distinct
incidents police handled, one line each, as: first time (HH:MM), then
a short plain description (no addresses, names, plates or descriptions
of people). Group the shots-fired reports as one incident. Skip
routine chatter."
chatgptassist -a ask -f night.txt -p "$PROMPT" | block
23:50 - Wanted-person arrest and transport from a business.
23:55 - Loud party with people drinking outside a building.
00:01 - Theft of a bag and belongings from a parking area.
00:08 - Loud-noise complaint at a park.
00:08 - Suspicious vehicle investigation.
00:20 - Multiple reports of gunshots across the area; officers later found a shell casing.
00:21 - Possible assault with an injured person and missing wallet.
00:54 - Welfare check on a person on a sidewalk; person was okay.
01:06 - Report of threats to kill and rob someone outside a venue.
Resources
Behind This Post
The outline I wrote
- A creative angle for digging deeper on local stories
- Reading ARLnow stories like [[https://www.arlnow.com/2026/11/07/man-arrested-after-gunfire-reported-in-parts-of-north-arlington/][this one about gunfire in North Arlington]], I had questions, like: were Flock or other AI assets involved? (Almost certainly not Flock cameras: the county [[https://www.arlnow.com/2026/10/29/removal-of-flock-cameras-in-arlington-draws-criticism-from-all-sides-at-town-hall/][ended its Flock contract in September]].) The article doesn't address this.
- I wondered: what if I could get hold of the original police scanner traffic? Maybe it would reveal details missing from the story.
- Digging around, it turned out Broadcastify offers an API to do this, so I built a tool.
- Bringing scanner traffic to the Unix command line
- broadcastifyassist: a thin shell wrapper around the API endpoints
Broadcastify offers. Broadcastify's developer terms restrict
sharing tools built on its API, so this one stays private. If you
write your own, the interface scannerassist expects is in the
resources below.
- One improvement it offers: aliases. Rather than making requests with talk group IDs like =5000-1=, I can query =arl-police=.
- scannerassist: adds transcription and caching, so it's easier to work with the raw audio.
- Both tools are command-line friendly and AI-agent friendly.
- Claude was able to use scannerassist to find the radio traffic for the incident I had in question, and others I threw at it.
- These tools are so cool: they bridge the command line to real-life, in-the-moment events. It's easy to both read the transcripts and play the audio.
- OK, they're cool tools. But are they useful?
- True: it's impressive that I can read an article and, a few moments later, hear the officers talking about that incident.
- True: the radio fills in details the news story left out. For the
shooting above: about a dozen calls from across North Arlington, a
9mm shell casing, a Ring camera, and an officer posting
video of a possible getaway car.
- But none of it contradicted ARLnow. Across three incidents, the
ARLnow stories held. The radio added texture, not corrections.
- I'm not yet ready to call this a game-changer, but I'm glad it's in my local news toolkit.
- Below are some examples of using the tools to explore this incident.



































































