Name: Stop Incidents Field Contact 2012 - 2017

Display Field: REPORT_TAKEN_DATE

Type: Table

Geometry Type: N/A

Description: When a non-forcible stop is conducted, MPD officers may document it on a field contact report instead of an incident report. A field contact report is also used to record general contact with a citizen. This dataset only captures the field contact type where the officer has indicated it is a stop by classifying it as a “pedestrian stop”, “vehicle stop”, or “bicycle stop.”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. The Metropolitan Police Department (MPD) upgraded its records management system in 2012 and 2015. During each implementation, data collection processes may have changed. For example: - The date field for field contact reports prior to January 2, 2012 was not migrated to the current record management system. As a result, tens of thousands of records carry a date of January 1, 2012. Therefore, MPD is unable to provide field contact data prior to January 2, 2012. - With the implementation of the most recent RMS in 2015, MPD began collecting race and ethnicity data according to the United States Census Bureau standards (https://www.census.gov/topics/population/race/about.html). As a result, Hispanic, which was previously categorized under the Race field, is currently captured under Ethnicity. Race and ethnicity data are based on officer observation, which may or may not be accurate. Individuals are not required to provide their date of birth and/or age; therefore, there may be blank and/or unknown ages. 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:

• REPORT_TAKEN_DATE ( type: esriFieldTypeString, alias: Report Taken Date, length: 255 )
• YEAR ( type: esriFieldTypeInteger, alias: Year )
• BLOCK_ADDRESS ( type: esriFieldTypeString, alias: Block Address, length: 255 )
• DISTRICT ( type: esriFieldTypeString, alias: District, length: 255 )
• PSA ( type: esriFieldTypeString, alias: Police Service Area, length: 255 )
• FIELD_CONTACT_TYPE ( type: esriFieldTypeString, alias: Field Contact Type, length: 255 )
• REASON_FOR_STOP ( type: esriFieldTypeString, alias: Reason For Stop, length: 255 )
• DATA_TYPE ( type: esriFieldTypeString, alias: Data Type, length: 255 )
• RACE ( type: esriFieldTypeString, alias: Race, length: 255 )
• ETHNICITY ( type: esriFieldTypeString, alias: Ethnicity, length: 255 )
• SEX ( type: esriFieldTypeString, alias: Sex, length: 255 )
• AGE ( type: esriFieldTypeString, alias: Age, length: 255 )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )

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

  Iteminfo   Thumbnail   Metadata