Name: Stop Incidents 2010 - 2017

Display Field: INCIDENT_TYPE

Type: Table

Geometry Type: N/A

Description: Whenever a forcible stop or a frisk is conducted, MPD officers are required to submit an incident report which includes specific factors which supported the determination that reasonable suspicion was present to use the minimum amount of force necessary to stop or frisk a person. Although the primary purpose of the stop and frisk incident report is to collect information on forcible stops or frisks, officers frequently use this report to document non-forcible stops. Thus, the incident type “stop and frisk” may include non-forcible stops, forcible stops, and frisks. Each row of information in the attached dataset represents an individual associated with a stop and frisk incident. Not all individuals of an incident may have been stopped or frisked. For example, two individuals may have been associated with a stop or frisk incident but only one person may have been stopped. The other person may include a witness. Moreover, two individuals may have been stopped where only one person is frisked. A “stop” is a temporary detention of a person for the purpose of determining whether probable cause exists to arrest a person. A “frisk” is a limited protective search on a person to determine the presence of concealed weapons and/or dangerous instruments. https://mpdc.dc.gov/node/1310236

Copyright Text: N/A

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, PBF

Supports Advanced Queries: true

Supports Statistics: true

Use Standardized Queries: true

Extent:

Drawing Info:

N/A

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: false
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeNone

Type ID Field: null

Fields:

• INCIDENT_TYPE ( type: esriFieldTypeString, alias: Incident Type, length: 20 )
• REPORT_TAKEN_DATE_EST ( type: esriFieldTypeDate, alias: Estimated Report Taken Date, length: 8 )
• YEAR ( type: esriFieldTypeDouble, alias: Year )
• DATA_TYPE ( type: esriFieldTypeString, alias: Data Type, length: 10 )
• SUBJECT_RACE ( type: esriFieldTypeString, alias: Subject Race, length: 50 )
• SUBJECT_SEX ( type: esriFieldTypeString, alias: Subject Sex, length: 10 )
• SUBJECT_ETHNICITY ( type: esriFieldTypeString, alias: Subject Ethnicity, length: 25 )
• BLOCK_ADDRESS ( type: esriFieldTypeString, alias: Block Address, length: 50 )
• INCIDENT_LOCATION_DISTRICT ( type: esriFieldTypeString, alias: Incident Location District, length: 5 )
• INCIDENT_LOCATION_PSA ( type: esriFieldTypeDouble, alias: Incident Location Police Service Area )
• AGE ( type: esriFieldTypeString, alias: Age, length: 10 )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata