Name: Officer Traffic Stops

Display Field: Month_of_Stop

Type: Table

Geometry Type: N/A

Description: CMPD conducts an average of 120,000 traffic stops per year. Under North Carolina state law (G.S. 143B-902-903), the CMPD as well as other law enforcement agencies in the state are required to collect information on all traffic stops, the reason for the stop, and the type of enforcement action taken. Information on the driver’s sex, race, ethnicity, and age is collected, compiled, and reported to the NC Department of Justice. Information on whether the driver or passenger(s) were searched is also collected. For more information, please visit http://charlottenc.gov/CMPD/Pages/Resources/OpenData_Source.aspx CMPD is committed to deploying traffic officers to areas where we experience high crime and victimization. Our focus is also in the geographical areas where concerns are reported by community members. We as a police department have a responsibility to those communities, to address their concerns and take appropriate enforcement action in an effort to keep their neighborhoods safe. Additionally, we are not only reacting to crime but proactively engaging in strategies that are intended to prevent criminal activity from occurring by placing officers in areas with a greater statistical history of crime.

Copyright Text: N/A

Default Visibility: false

MaxRecordCount: 2000

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:

• OBJECTID ( type: esriFieldTypeOID, alias: ObjectID )
• Month_of_Stop ( type: esriFieldTypeString, alias: Month_of_Stop, length: 7 )
• Reason_for_Stop ( type: esriFieldTypeString, alias: Reason_for_Stop, length: 25 )
• Officer_Race ( type: esriFieldTypeString, alias: Officer_Race, length: 30 )
• Officer_Gender ( type: esriFieldTypeString, alias: Officer_Gender, length: 10 )
• Officer_Years_of_Service ( type: esriFieldTypeDouble, alias: Officer_Years_of_Service )
• Driver_Race ( type: esriFieldTypeString, alias: Driver_Race, length: 20 )
• Driver_Ethnicity ( type: esriFieldTypeString, alias: Driver_Ethnicity, length: 12 )
• Driver_Gender ( type: esriFieldTypeString, alias: Driver_Gender, length: 8 )
• Driver_Age ( type: esriFieldTypeInteger, alias: Driver_Age )
• Was_a_Search_Conducted ( type: esriFieldTypeString, alias: Was_a_Search_Conducted, length: 3 )
• Result_of_Stop ( type: esriFieldTypeString, alias: Result_of_Stop, length: 20 )
• CMPD_Division ( type: esriFieldTypeString, alias: CMPD_Division, length: 50 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

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

  Iteminfo   Thumbnail   Metadata