zwn22 commited on
Commit
95e5010
1 Parent(s): 5c0f39d

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +3 -18
README.md CHANGED
@@ -13,8 +13,6 @@ tags:
13
  - [Cary Open Data Portal - CPD Incidents](https://data.townofcary.org/explore/dataset/cpd-incidents/information/?disjunctive.crime_category&disjunctive.crime_type&disjunctive.crimeday&disjunctive.district&disjunctive.offensecategory&disjunctive.violentproperty&disjunctive.total_incidents&disjunctive.year&sort=date_from)
14
  - **Chapel Hill**:
15
  - [Chapel Hill Open Data Portal - Police Incidents](https://opendata-townofchapelhill.hub.arcgis.com/datasets/a761c9be03ef474bbbf4a114778623c5/explore?filters=eyJEYXRlX29mX1JlcG9ydCI6WzEyNjIzMDYxNjAwMDAsMTY5ODcwOTA4MDAwMF19&showTable=true)
16
- - **Charlotte**:
17
- - [Charlotte Open Data Portal - CMPD Incidents](https://data.charlottenc.gov/datasets/d22200cd879248fcb2258e6840bd6726/explore?showTable=true)
18
  - **Durham**:
19
  - [Durham Open Data Portal - DPD Incidents UCR/NIBRS Reporting](https://live-durhamnc.opendata.arcgis.com/documents/DurhamNC::dpd-incidents-ucr-nibrs-reporting/about)
20
  - **Raleigh**:
@@ -70,7 +68,7 @@ The dataset contains several fields, each providing specific information about p
70
  - `crime_major_category` (string): A broad categorization of the crime, used as input for crime pattern analysis and categorization tasks.
71
  - `crime_specific_category` (string): More detailed classification of the crime, falling under the major category. This field allows for a finer-grained analysis of crime types.
72
  - `latitude` (float) and `longitude` (float): Geographical coordinates pinpointing the location of the incident. These fields are essential for geospatial analysis.
73
- - `start_time` (datetime) and `end_time` (datetime): The beginning and end times of the incident, providing temporal context. These fields are used in analyses that require time-based information.
74
  - `clear_status` (string): The resolution status of the case, such as whether it was cleared by arrest or remains under investigation. This field can be used to understand case outcomes.
75
  - `incident_address` (string): The specific address where the incident occurred. This field adds a detailed spatial dimension to the data.
76
  - `notes` (string): Additional remarks or details about the incident, like weapon usage or other relevant factors. This field provides supplementary information that may be relevant for certain analyses.
@@ -103,19 +101,6 @@ Five datasets are primarily utilized as source data:
103
  - Details:
104
  - Size: 101828 rows * 19 columns
105
  - Column names: 'Incident ID', 'Agency', 'Offense', 'Street', 'City', 'State', 'Zipcode', 'Date of Report', 'Date of Occurrence', 'Date Found', 'Reported As', 'Premise Description', 'Forcible', 'Weapon Description', 'Victim Age', 'Victim Race', 'Victim Gender', 'Latitude', 'Longitude'
106
- - **Charlotte**:
107
- - [Charlotte Open Data Portal - CMPD Incidents](https://data.charlottenc.gov/datasets/d22200cd879248fcb2258e6840bd6726/explore?showTable=true)
108
- - Details:
109
- - Size: 483632 rows * 30 columns
110
- - Column names: 'X', 'Y', 'YEAR', 'INCIDENT_REPORT_ID', 'LOCATION', 'CITY', 'STATE',
111
- 'ZIP', 'X_COORD_PUBLIC', 'Y_COORD_PUBLIC', 'LATITUDE_PUBLIC',
112
- 'LONGITUDE_PUBLIC', 'DIVISION_ID', 'CMPD_PATROL_DIVISION', 'NPA',
113
- 'DATE_REPORTED', 'DATE_INCIDENT_BEGAN', 'DATE_INCIDENT_END',
114
- 'ADDRESS_DESCRIPTION', 'LOCATION_TYPE_DESCRIPTION',
115
- 'PLACE_TYPE_DESCRIPTION', 'PLACE_DETAIL_DESCRIPTION',
116
- 'CLEARANCE_STATUS', 'CLEARANCE_DETAIL_STATUS', 'CLEARANCE_DATE',
117
- 'HIGHEST_NIBRS_CODE', 'HIGHEST_NIBRS_DESCRIPTION', 'OBJECTID', 'Shape',
118
- 'GlobalID'
119
  - **Durham**:
120
  - [Durham Open Data Portal - DPD Incidents UCR/NIBRS Reporting](https://live-durhamnc.opendata.arcgis.com/documents/DurhamNC::dpd-incidents-ucr-nibrs-reporting/about)
121
  - Details:
@@ -149,13 +134,13 @@ Cary's Open Data Portal operates under the Creative Commons Attribution-ShareAli
149
 
150
  Chapel Hill's Open Data Portal is governed by the Open Database License (ODbL) 1.0 License. This license permits both commercial and non-commercial use, distribution, and modification of the data. Users are required to attribute the data appropriately and, if the data is altered or transformed, or if new datasets are built upon it, the resulting work must be distributed under the same ODbL 1.0 License.
151
 
152
- While Durham and Charlotte's Open Data Portals do not specify a particular license, their websites state that the data is publicly accessible and can be freely used. Charlotte's portal serves as a resource for the public to explore, visualize, and download data, facilitating the creation of new applications and maps. Similarly, Durham's portal is dedicated to making all government data available for public use without restrictions.
153
 
154
  Raleigh's Open Data Policy stipulates that by using data from their site, users agree to the terms and conditions described under the City of Raleigh Open Data Privacy Policy. The City of Raleigh makes no warranties regarding the completeness, accuracy, or timeliness of the data, and disclaims all express or implied warranties, including those of merchantability or fitness for a particular purpose. Users should be aware that the data format or schema may change as updates are made, and they use the information at their own risk.
155
 
156
  ### Contributions
157
 
158
- Thanks to Town of Cary, City of Chapel Hill, City of Charlotte, City of Durham, and City of Raleigh for providing the raw dataset.
159
 
160
 
161
 
 
13
  - [Cary Open Data Portal - CPD Incidents](https://data.townofcary.org/explore/dataset/cpd-incidents/information/?disjunctive.crime_category&disjunctive.crime_type&disjunctive.crimeday&disjunctive.district&disjunctive.offensecategory&disjunctive.violentproperty&disjunctive.total_incidents&disjunctive.year&sort=date_from)
14
  - **Chapel Hill**:
15
  - [Chapel Hill Open Data Portal - Police Incidents](https://opendata-townofchapelhill.hub.arcgis.com/datasets/a761c9be03ef474bbbf4a114778623c5/explore?filters=eyJEYXRlX29mX1JlcG9ydCI6WzEyNjIzMDYxNjAwMDAsMTY5ODcwOTA4MDAwMF19&showTable=true)
 
 
16
  - **Durham**:
17
  - [Durham Open Data Portal - DPD Incidents UCR/NIBRS Reporting](https://live-durhamnc.opendata.arcgis.com/documents/DurhamNC::dpd-incidents-ucr-nibrs-reporting/about)
18
  - **Raleigh**:
 
68
  - `crime_major_category` (string): A broad categorization of the crime, used as input for crime pattern analysis and categorization tasks.
69
  - `crime_specific_category` (string): More detailed classification of the crime, falling under the major category. This field allows for a finer-grained analysis of crime types.
70
  - `latitude` (float) and `longitude` (float): Geographical coordinates pinpointing the location of the incident. These fields are essential for geospatial analysis.
71
+ - `occurance_time` (datetime): The beginning time of the incident, providing temporal context. These fields are used in analyses that require time-based information.
72
  - `clear_status` (string): The resolution status of the case, such as whether it was cleared by arrest or remains under investigation. This field can be used to understand case outcomes.
73
  - `incident_address` (string): The specific address where the incident occurred. This field adds a detailed spatial dimension to the data.
74
  - `notes` (string): Additional remarks or details about the incident, like weapon usage or other relevant factors. This field provides supplementary information that may be relevant for certain analyses.
 
101
  - Details:
102
  - Size: 101828 rows * 19 columns
103
  - Column names: 'Incident ID', 'Agency', 'Offense', 'Street', 'City', 'State', 'Zipcode', 'Date of Report', 'Date of Occurrence', 'Date Found', 'Reported As', 'Premise Description', 'Forcible', 'Weapon Description', 'Victim Age', 'Victim Race', 'Victim Gender', 'Latitude', 'Longitude'
 
 
 
 
 
 
 
 
 
 
 
 
 
104
  - **Durham**:
105
  - [Durham Open Data Portal - DPD Incidents UCR/NIBRS Reporting](https://live-durhamnc.opendata.arcgis.com/documents/DurhamNC::dpd-incidents-ucr-nibrs-reporting/about)
106
  - Details:
 
134
 
135
  Chapel Hill's Open Data Portal is governed by the Open Database License (ODbL) 1.0 License. This license permits both commercial and non-commercial use, distribution, and modification of the data. Users are required to attribute the data appropriately and, if the data is altered or transformed, or if new datasets are built upon it, the resulting work must be distributed under the same ODbL 1.0 License.
136
 
137
+ While Durham's Open Data Portals do not specify a particular license, its website states that the data is publicly accessible and can be freely used. Durham's portal is dedicated to making all government data available for public use without restrictions.
138
 
139
  Raleigh's Open Data Policy stipulates that by using data from their site, users agree to the terms and conditions described under the City of Raleigh Open Data Privacy Policy. The City of Raleigh makes no warranties regarding the completeness, accuracy, or timeliness of the data, and disclaims all express or implied warranties, including those of merchantability or fitness for a particular purpose. Users should be aware that the data format or schema may change as updates are made, and they use the information at their own risk.
140
 
141
  ### Contributions
142
 
143
+ Thanks to Town of Cary, City of Chapel Hill, City of Durham, and City of Raleigh for providing the raw dataset.
144
 
145
 
146