Data on the Open Data Network

Publishers

Refine by:Found 311 results

public safety Close
data.austintexas.gov Close
dashboard.hawaii.gov Close
data.cdc.gov Close

public safety - The Public Safety category contains data, from across the Open Data Network™ of publishers, related to public safety, 911 data, ambulance, emergency, fire, police, prison, evacuation, arrests, and crime.

API
EMS - Total Patient Transports
data.austintexas.gov | Last Updated 2019-11-28T14:31:37.000Z
This table contains data that describes monthly patient contacts. It includes all incidents with a response priority between 1 and 5, inclusive.
API
EMS - Response Interval Compliance: County P2 v2018
data.austintexas.gov | Last Updated 2019-12-01T14:30:11.000Z
This table contains data describing requests for assistance received by ATCEMS. Incident counts are broken out by location, and priority for City of Austin and Travis County incidents. See document attached to metadata for more details. When using this data for research or other purposes, please cite it as: Austin-Travis County Emergency Medical Services (2014). EMS – Incidents by Month [data set]. City of Austin, Texas Open Data Portal. Retrieved from https://data.austintexas.gov/Public-Safety/EMS-Incidents-by-Month/gjtj-jt2d. Since this table is updated on a monthly basis, include the date that the table was accessed in the citation.
API
EMS - Trauma Activation Specialty Center Transport Rate v2018
data.austintexas.gov | Last Updated 2019-10-07T13:30:15.000Z
This table contains data describing ATCEMS management of Trauma Alert patients. In this setting, “Trauma Alert” refers to injured patients who meet Physiological or Anatomical criteria for transport to a Trauma Center per City of Austin/Travis County EMS System Clinical Operating Guidelines.
API
Chromatograms GC2010 2012-04-04
data.austintexas.gov | Last Updated 2015-08-17T17:23:10.000Z
Chromatograms GC2010 2012-04-04
API
Chromatograms GC2010 2014-03-09
data.austintexas.gov | Last Updated 2015-08-17T17:23:07.000Z
Chromatograms GC2010 2014-03-09
API
Graffiti Abatement SRs by Council District FY 2015-2016
data.austintexas.gov | Last Updated 2019-12-05T11:20:05.000Z
View created from 311 Unified Data. Additional filters may be added to filter requests by data or specific council district. Note:Socrata automatically groups data points when zoomed out
API
Downtown Austin Community Court (DACC) FY 2018 Caseload information
data.austintexas.gov | Last Updated 2019-12-02T16:10:07.000Z
Displays FY 2018 issued citation offenses in DACC jurisdiction for informational purposes
API
2015 RP Warnings + Field Observations
data.austintexas.gov | Last Updated 2019-03-13T22:57:42.000Z
This Racial Profiling dataset provides the raw data needed to identify trends in traffic stops. It is used to help identify potential improvements in department policy, tactics, and training. This data is used to produce the annual Racial Profiling report, posted on APD's website here: http://www.austintexas.gov/page/racial-profiling-reports AUSTIN POLICE DEPARTMENT DATA DISCLAIMER 1. The data provided are for informational use only and may differ from official APD crime data. 2. APD’s crime database is continuously updated, so reports run at different times may produce different results. Care should be taken when comparing against other reports as different data collection methods and different data sources may have been used. 3. The Austin Police Department does not assume any liability for any decision made or action taken or not taken by the recipient in reliance upon any information or data provided.
API
Top 10 Dispatch Problems
data.austintexas.gov | Last Updated 2018-10-17T17:34:29.000Z
This table shows the 10 most frequently recorded incident problem types as recorded by communications personnel for each fiscal year presented.
API
2017 Contours
data.austintexas.gov | Last Updated 2019-08-15T19:04:52.000Z
This layer represents contour elevation lines as of the spring of 2017. The contours are derived from LiDAR data, collected in the winter of 2017/2018. Contours were generated using Global Mapper, sample spacing used to create the contours is consistent with the Nominal Point Spacing (NPS), of the source LiDAR dataset from which it was derived. Lines were automatically smoothed while being generated by Global Mapper.