Arlington civic telemetry coverage
Public service SOL Civic Telemetry. Source review began November 16, 2026 in America/Chicago.
| Source | Collection | What the records establish |
| --- | --- | --- |
| Arlington PD active calls | Delayed, transient police dispatch | The city displayed a call with this classification. The feed omits calls outside its time and status rules. |
| Arlington Fire GIS | On-demand archival adapter | Direct ordered queries returned May 5, 2016 through June 5, 2017. The collector excludes the archive from current telemetry. |
| Arlington Fire Department and Open Data Center | Manual records and announcement review | The Fire catalog search exposed station, battalion, and district datasets. No current public machine-readable incident feed was identified. |
| Arlington PD rolling crime layer | Reference | A rolling release of police reports with different identifiers, timing, and coverage from the active dispatch feed. |
| Broadcastify Arlington Fire | Listed playlist. Calls ingestion disabled | Collection requires authorized API access. The playlist listing provides no proof of a recording for a particular event. |
| OpenMHz | Manual reference. Ingestion disabled | No Arlington archive was verified for the period reviewed. |
| SOL Radio Observatory | Local 22-channel FRS receiving | The receiver status and worker units were active. Arlington P25 talkgroup capture was unverified. Storage telemetry showed routine recording disabled and no available emergency-audio disk space during the review. |
| Weatherford PD releases | Delayed PDFs | Daily media release narratives are parsed when their incident times can be identified. Partial parsing stays visible in source health. |
| Parker County Alert Center and NWS | Episodic announcements and alerts | These sources publish updates when issued. Empty snapshots and no-recent-event periods are tracked separately. |
Collection and privacy
The Arlington map itself calls the PoliceExternal layer. The PoliceIncident layer is a separate service with different documented hours and a different observed call set. The collector follows the display's district filter. It requests only call facts, omitting address, unit and coordinate attribute fields. The city documents a minimum 60-minute delay and a 15-minute refresh cycle. SOL enforces the one-hour delay and polls no faster than once every 15 minutes. Failed Arlington collections back off to 30 minutes, then one hour. The municipality polygon is cached for a week.
The City website terms describe restrictions on protected site materials, while the Open Data Policy addresses catalog licensing. The collector uses factual call identifiers, timestamps and category labels. It does not mirror the police website, precise addresses, apartment fields, maps, or recordings.
ArcGIS transforms source WKID 102738 (EPSG:2276) to EPSG:4326. SOL checks the returned CRS and tests membership in the Arlington municipal polygon before assigning Arlington and Tarrant. The Census boundary map identifies Tarrant County. Unknown or outside points retain unknown city/county. Accepted public points are rounded to 0.01 degree with 1 km uncertainty. No addresses or private investigation notes enter the collector. Bounding box and radius filters operate on these published points.
One source and call number identify one dispatch. The SQLite evidence table retains immutable revisions of the selected upstream facts and their SHA-256 hashes. The public incident preserves the initial call classification and reports the last observation separately. Candidate associations require another source, matching city, county and category, proximity in time and at the published map precision, plus overlapping descriptions. The association table records evidence for manual review. Candidates never merge incident rows or change verification status.
API and operation
- Existing routes and response envelopes remain supported. Incident lists, exports, summaries and context reports accept
county,city,agency,category,start,end,source,verification_status,event_id,bboxandradiuswhere compatible.bboxuses west,south,east,north.radiususes latitude,longitude,kilometers. Use ISO 8601 date/time with an explicit offset for portable queries. GET /api/crime/sources/healthreports interval, last successful collection, newest source event, newest stored incident, failures, archival coverage and current availability.SOL37_CRIME_COLLECT_ARLINGTON=1andSOL37_CRIME_COLLECT_PARKER=1opt the existing API service into collection. The latter runs the existing Parker-area sources on a daily schedule. Arlington is excluded from the public pull route to preserve its rate limit.- Parker-area collection was request-driven before this change. No scheduled civic collector was found during service inventory. The database had 234 Parker records and its newest event was July 10, even though the Weatherford site and Parker Alert Center contained newer material. The November Weatherford PDF format also used punctuation and clock formats the previous parser missed.
- New Weatherford records retain generalized incident facts and source links. New imports omit individual narratives and residential address fields. Legacy records are preserved. The Weatherford index is a recent release list, so it cannot establish continuous coverage back to July.
- The API provides stored date windows with limited record counts. Data absence can reflect delayed coverage, a closed call, archive boundaries, parser limits, or an unavailable source.
- Audio workflows remain disabled for Arlington. Reports use deterministic summaries and preserve dispatch labels with unverified outcomes.
Verification
Run python3.11 -m unittest discover -s tests -p test_arlington_civic.py -v and python3.11 bin/check_parker_crime_api_contract.py from the SOL random workspace. Compare all incident rows in a pre-change database copy against the post-change database. Verify the browser in Parker County, Arlington, and Combined scope, and check exports. To pause scheduled collection, remove its environment overrides and restart the API. The migrations and new incident records are additive.