Police Dispatched Incidents — Montgomery County

This dataset contains a list of Police Dispatched Incidents records. Update Frequency : 4 Times. This Actor returns it as one flat JSON row per record, with 26 declared fields — typed, named and documented in the dataset schema, so a spreadsheet or an agent can use it without guessing.

What you get

Field	Type	Meaning
disposition_desc	string	Disposition Desc
priority	number	Priority
incident_id	string	Incident_ID
calltime_dispatch	number	Calltime Dispatch
geolocation	string	Location
pra	number	PRA
state	string	State
police_district_number	string	Police District Number
end_time	string	End Time
start_time	string	Start Time
city	string	City
calltime_arrive	number	Calltime Arrive
crash_reports	string	Crash Reports
zip	number	Zip
calltime_callroute	number	CallTime CallRoute
close_type	string	Close Type
longitude	number	Longitude
address	string	Address
latitude	number	Latitude
calltime_cleared	number	Calltime Cleared

The output schema lists all 26 fields; the table above is the first twenty.

Every row also carries sourceRowId, sourceUpdatedAt and scrapedAt, so a pipeline can tell one record from another and know exactly when it was read.

{
  "disposition_desc": "OTHERMISCELLANEOUS",
  "priority": 3,
  "incident_id": "P2600319943",
  "calltime_dispatch": 2536,
  "geolocation": "{\"type\":\"Point\",\"coordinates\":[-77.2439,39.1272]}",
  "pra": 449,
  "state": "MD",
  "police_district_number": "6D"
}

Inputs

Field	What it does
Filter (SoQL)	Applied at the source, so a narrow question fetches a narrow page instead of downloading everything.
Order	Empty keeps the publisher's own order; set a column to sort, for example amount DESC.
Maximum rows	Hard cap. The source is paged 1,000 rows at a time.
Time budget	Stops cleanly and reports how far it got.
Pause between pages	Keeps the run inside the publisher's rate limits.

Limitations

• This is one dataset, from one publisher. It is the Police Dispatched Incidents dataset as Montgomery County, MD publishes it — not a national or cross-city equivalent, and not a merge with other sources.
• The publisher can change it. Columns are added, renamed and retired upstream; the field list here is the schema the Actor was generated from. A renamed column arrives as a new field only after the Actor is updated.
• Fields are typed from live records. A column that was empty in the sample is declared as text; a value that does not fit the declared type comes back null rather than being coerced into a wrong number.
• Records are what the publisher publishes. No geocoding, no de-duplication across datasets, no enrichment.
• Freshness is the publisher's. The data was last changed upstream on 2026-10-25. Where the publisher supplies a row timestamp it appears as sourceUpdatedAt; scrapedAt records when this Actor read the row.

Why this is different

• Police Dispatched Incidents — Montgomery County declares all 26 of its output fields in the dataset schema, each with a type, a description and an example.
• The Actor reads the Police Dispatched Incidents dataset directly from Montgomery County Open Data; no key, login or account is needed.
• Filters run at the source with SoQL, so a narrow request returns a narrow page rather than a full download.
• Every row is flat JSON: nested location objects become latitude and longitude, and no field holds a nested object.
• The row id is stable, so the same request de-duplicates instead of returning the same record twice.

FAQ

Do I need an API key? No. Montgomery County Open Data publishes this dataset openly.

How fresh is it? The Actor reads the dataset live. scrapedAt records when each row was read, and sourceUpdatedAt carries the publisher's own row timestamp where it supplies one.

Can I filter by date or status? Yes — use the Filter field with SoQL, for example status = 'Active'.

What happens if my filter is wrong? The run stops with the portal's own message and the hint to check SoQL, rather than returning an empty dataset that looks like "no data".

Is this the whole dataset? Up to your row cap, paged 1,000 at a time. Raise the cap to read more.

What is sourceRowId? The publisher's own row id when it supplies one, otherwise a stable hash of the row. Either way it is what makes de-duplication and joins possible.

Pricing

Pay per result: $0.0005 per row. Each stored dataset row is billed, including any diagnostic row returned instead of results.

An Actor-start event is also charged at $0.0001 per GB of allocated memory (minimum one event), even if no rows are returned. At 1 GB or less, 1,000 result rows cost $0.5001 before any applicable Store discount.

Data source

Montgomery County Open Data — Police Dispatched Incidents, published by Montgomery County, MD. Public data under the portal's open-data terms.