# Montgomery County MD Police Dispatch - Calls & Response Times (`j0401/md-moco-police`) Actor

Every call Montgomery County, Maryland police responded to (public open data, 1.92M incidents, 2017-today): priority, call type as received and as closed, address and coordinates, police district and beat, and seven response-time intervals in seconds. Filter by type, district, city or response time.

- **URL**: https://apify.com/j0401/md-moco-police.md
- **Developed by:** [Wenhao Yang](https://apify.com/j0401) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.03 / 1,000 montgomery county police incident records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Montgomery County MD Police Dispatch - Calls & Response Times

Every call the Montgomery County, Maryland police responded to, straight from
the county's dispatch log. **1.92 million incidents**, from April 2017 through
the last completed call.

### Low cost

**From $0.00005 per record, down to $0.00003 at Gold.** Pay only for the
records you actually receive - the whole register stays queryable, you are
never billed for the scan behind it.

### What you get

One row per dispatched incident, with the full call timeline attached:

- **What** - the priority and the call type, both as first received and as
  finally closed, and the disposition
- **Where** - the block-level address, the city and ZIP, the coordinates, and
  the police district and beat
- **When** - the call start and end timestamps
- **The response-time chain** - **seven intervals in seconds**: call->call-route,
  call->dispatch, call->arrive, call->cleared, call-route->dispatch,
  dispatch->arrive, and arrive->cleared
- **Linked reports** - the crime report and crash report numbers, where one
  exists

### Filter it

- **Call type** - `initialType="TRAFFIC"` (as received) or
  `closeType="SUSPICIOUS"` (as closed). 234 and 238 types respectively.
- **Priority** - 0 through 5. Priority 1 is the largest group (~783,000 calls).
- **District and beat** - `district="3D"`, `beat="G1"`. 9 districts, 45 beats
  (plus an unattributed bucket).
- **City and ZIP** - `city="Rockville"`, `zip="20852"`. 97 cities (plus an
  unattributed bucket).
- **Response time** - `minResponseSeconds=900` finds every call a unit took
  over 15 minutes to reach.
- **Date range** and **last-N-days**.

### Example inputs

**Slow responses** - dispatch-to-arrival over 15 minutes, in seconds.

```json
{ "minResponseSeconds": 900, "maxResults": 50 }
```

**One city's serious calls** - combine city and priority.

```json
{ "city": "ROCKVILLE", "priority": "1", "maxResults": 50 }
```

**One type of call, newest first** - `initialType` is a substring match.

```json
{ "initialType": "DOMESTIC", "maxResults": 25 }
```

**Where the calls are** - `mode=aggregate` returns one count row per district;
every group comes back.

```json
{ "mode": "aggregate", "groupBy": "district" }
```

### Or roll it up

Set `mode=aggregate` and get a rolled-up count by **priority**, **district**,
**beat**, **call type** (received or closed), **disposition** or **city**.
Every group comes back - not cut off by `maxResults`.

### Then analyse response

- Which call types and districts take longest to reach.
- The full timeline of a single incident, interval by interval.
- Call volume by priority, district and beat, over any window.
- Domestic and traffic calls, with their dispositions.

### Example output

**One incident** - `city=ROCKVILLE`, `minResponseSeconds=600`:

```json
{
 "platform": "md-moco-police",
 "source": "montgomery-county-md-police-dispatch",
 "mode": "rows",
 "groupKey": "",
 "groupCount": "",
 "groupBy": "",
 "incidentId": "P2600291687",
 "startTime": "2026-09-29T11:32:51.000",
 "endTime": "2026-09-29T12:17:02.000",
 "priority": "2",
 "initialType": "TRESPASSING/UNWANTED",
 "closeType": "TRESPASSING/UNWANTED",
 "address": "16000 BLK  SHADY GROVE RD",
 "city": "ROCKVILLE",
 "state": "MD",
 "zip": "20850",
 "longitude": "-77.1826",
 "latitude": "39.11891",
 "policeDistrict": "1D",
 "beat": "A1",
 "crimeReportNumber": "",
 "crashReports": "",
 "pra": "439",
 "calltimeCallroute": "77",
 "calltimeDispatch": "277",
 "calltimeArrive": "1752",
 "calltimeCleared": "2650",
 "callrouteDispatch": "199",
 "dispatchArrive": "1475",
 "arriveCleared": "898",
 "disposition": "TRESPASSING",
 "sourceUpdatedAt": "2026-09-29"
}
```

**`mode=aggregate`, `groupBy=priority`** - one count row per priority:

```
1                               ~783,300
2                               ~456,400
4                               ~365,100
0                               ~179,200
3                               ~136,100
5                                     4
```

### Notes on the data, from the source

- **The intervals are in seconds.** `dispatchArrive` is the time from a unit
  being dispatched to its arrival; `calltimeArrive` is from the call coming in
  to the unit arriving.
- **A missing interval is a fact about the call, not a gap.** About a quarter
  of calls were handled without a unit ever arriving (a phone resolution, a
  cancelled call), so `calltimeArrive`, `dispatchArrive` and `arriveCleared`
  are empty on those rows - and a response-time query only matches calls that
  did have an arrival.
- **Addresses are block-level** (e.g. `900 BLK N FREDERICK AVE`), as the
  dispatch system holds them.
- **The register is updated daily**; `sourceUpdatedAt` carries the dataset's
  own refresh date.

# Actor input Schema

## `address` (type: `string`):

Substring match on the incident address (block-level, e.g. '900 BLK N FREDERICK AVE'). Blank = any.

## `city` (type: `string`):

Substring match on the city, e.g. 'ROCKVILLE', 'BETHESDA', 'GAITHERSBURG'. 97 cities in total (plus an unattributed bucket). Blank = any.

## `zip` (type: `string`):

Substring match on the ZIP, e.g. '20852'. Blank = any.

## `initialType` (type: `string`):

Substring match on the call type as first received, e.g. 'TRAFFIC', 'DISTURBANCE', 'CHECK WELFARE', 'DOMESTIC'. 234 types in total. Blank = any.

## `closeType` (type: `string`):

Substring match on the call type as finally closed, e.g. 'TRAFFIC', 'SUSPICIOUS'. 238 types in total. Blank = any.

## `disposition` (type: `string`):

Substring match on the disposition, e.g. 'OTHERMISCELLANEOUS', 'DISORDERLYCONDUCT', 'FAMILYTROUBLE'. 495 dispositions in total (plus an unattributed bucket). Blank = any.

## `beat` (type: `string`):

Substring match on the police beat, e.g. 'G1', 'A3', 'I1'. 45 beats in total (plus an unattributed bucket). Blank = any.

## `priority` (type: `string`):

Exact call priority. Priority 1 is the most urgent and is the largest group (~783,000 calls); priority 5 has only a handful. Blank = any.

## `district` (type: `string`):

Exact police district. Blank = any.

## `startFrom` (type: `string`):

Earliest call start date/time, YYYY-MM-DD. Blank = any.

## `startTo` (type: `string`):

Latest call start date/time, YYYY-MM-DD. Blank = any.

## `minResponseSeconds` (type: `number`):

Smallest dispatch-to-arrival time in SECONDS. Set 900 for calls a unit took over 15 minutes to reach. Note this only matches calls where a unit arrived; a missing arrival is excluded. Blank = no lower bound.

## `maxResponseSeconds` (type: `number`):

Largest dispatch-to-arrival time in SECONDS. Set 300 for a fast-response view. Blank = no upper bound.

## `recentDays` (type: `integer`):

Only calls whose start time falls within the last N days. Ignored when 'Call made on or after' is set. 0 = off.

## `mode` (type: `string`):

rows = incidents matching your filters (default). aggregate = one count row per group (see groupBy).

## `groupBy` (type: `string`):

Which dimension to aggregate over (mode=aggregate). Blank = priority. Every group is returned - aggregate mode is not cut off by maxResults.

## `maxResults` (type: `integer`):

Cap the number of records pushed in rows mode (0 = default 50; up to 2,000 per run). Each record is metered individually, so there is no per-run charge cap. Aggregate mode returns every group.

## Actor input object example

```json
{
  "address": "",
  "city": "",
  "zip": "",
  "initialType": "",
  "closeType": "",
  "disposition": "",
  "beat": "",
  "priority": "",
  "district": "",
  "startFrom": "",
  "startTo": "",
  "recentDays": 0,
  "mode": "rows",
  "groupBy": "",
  "maxResults": 50
}
```

# Actor output Schema

## `recordsUrl` (type: `string`):

Montgomery County police dispatch records - as JSON

## `datasetUrl` (type: `string`):

No description

## `runUrl` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("j0401/md-moco-police").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("j0401/md-moco-police").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call j0401/md-moco-police --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,j0401/md-moco-police"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/GIrJDU8K8UMfRzFWR/builds/NEGOyVfmWS7etzjSe/openapi.json