Police Transparency - Arrests - All Data (main table / denormalized)

<p><strong>Main Table / Denormalized Version</strong></p><p>This dataset provides demographic information related to arrests made by the Tempe Police Department. Each record represents an individual charge associated with an arrest and includes details about both the person arrested (arrestee) and the arresting officer. Demographic fields include race and ethnicity, age range at the time of arrest, and gender for each party.</p><p>The data is sourced from the Police Department’s Records Management System (RMS) and supports analysis of patterns related to arrests, enforcement activity, and demographic trends over time. This information is a component of ongoing efforts to promote transparency and provide context for law enforcement within the community.</p><p>For detailed guidance on interpreting arrest counts and demographic breakdowns, please refer to the <a target='_blank' href='https://tempe.gitbook.io/data-user-guide/arrests-demographics-hub-page/understanding-the-arrest-demographics-datasets' rel='nofollow ugc noopener noreferrer'><span style='color:#0000ff;'>User Guide: Understanding the Arrests Demographic Datasets</span></a>.</p><p><strong>Why this Dataset is Organized this Way?</strong></p><p>The main arrests open data table includes key information from each arrest event, along with associated person and charge details in one place. This format is ideal for quick viewing and simple analysis.</p><p>Providing this format supports a wide range of users, from casual data explorers to experienced analysts.<br /><br /><strong>Understanding the Arrests Open Data (main table / denormalized version)</strong></p><p>Each row in this dataset represents a single charge, which means a single arrest event may appear multiple times if multiple charges were filed. To determine the number of unique arrests, users should perform a distinct count of the rin field, which serves as the arrest incident identifier.</p><p>Likewise:</p><ul><li>To count unique arrestees, use a distinct count of the pin field (person identifier).</li><li>To count unique arresting officers, use a distinct count of the arrest_officer field.</li></ul><p>&nbsp;</p><p>This structure enables users to explore charge-level detail while maintaining the ability to summarize demographic data by arrest event, arrestee, or officer as needed. Visit the <a target='_blank' href='https://tempe.gitbook.io/data-user-guide/arrests-demographics-hub-page/understanding-the-arrest-demographics-datasets' rel='nofollow ugc noopener noreferrer'><span style='color:#0000ff;'>User Guide: Understanding the Arrests Demographic Datasets</span></a> for more details.</p><p style='background-color:rgb(255, 255, 255); border:0px solid currentcolor; box-sizing:border-box; color:rgb(74, 74, 74); font-family:&quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px; font-style:normal; font-variant-caps:normal; font-variant-ligatures:normal; font-weight:400; letter-spacing:normal; margin:0px 0px 1.5rem; text-align:start; text-decoration-color:initial; text-decoration-style:initial; text-indent:0px; text-transform:none; word-spacing:0px;'><br /><a style='border:0px solid currentcolor; box-sizing:border-box; color:rgb(0, 97, 155); font-family:inherit; line-height:1.5; text-decoration:none;' target='_blank' href='https://tempe.gitbook.io/data-dictionary/arrests-data-dictionary' rel='nofollow ugc noopener noreferrer'><span style='color:rgb(0,0,255); font-family:inherit; font-size:18px;'><span style='border:0px solid currentcolor; box-sizing:border-box; line-height:1.5;'><strong>Data Dictionary</strong></span></span></a><br /><br /><span style='font-size:18px;'><strong>Additional Information</strong></span></p><p><strong>Contact Email:</strong> <a href='mailto:PD_DataRequest@tempe.gov' rel='nofollow ugc'><span style='color:#0000ff;'>PD_DataRequest@tempe.gov</span></a><br /><br /><strong>Contact Phone:</strong> N/A</p><p><strong>Link:</strong> N/A</p><p><strong>Data Source:</strong> Versaterm RMS</p><p><strong>Data Source Type:</strong> SQL Server</p><p><strong>Preparation Method:</strong> Automated process</p><p><strong>Publish Frequency:</strong> Daily</p><p><strong>Publish Method:</strong> Automatic</p>

[
  "geospatial"
]