zwn22 commited on
Commit
0b74a2a
1 Parent(s): d5f8464

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +24 -59
README.md CHANGED
@@ -76,7 +76,9 @@ Note that the descriptions can be initialized with the **Show Markdown Data Fiel
76
 
77
  ### Curation Rationale
78
 
79
- What need motivated the creation of this dataset? What are some of the reasons underlying the major choices involved in putting it together?
 
 
80
 
81
  ### Source Data
82
 
@@ -98,76 +100,39 @@ I mainly uses 5 datasets as source data:
98
  'Total Incidents', 'Year'
99
  - **Charlotte**:
100
  - [Charlotte Open Data Portal - CMPD Incidents](https://data.charlottenc.gov/datasets/d22200cd879248fcb2258e6840bd6726/explore?showTable=true)
101
-
 
 
 
 
 
 
 
 
 
 
102
  - **Durham**:
103
  - [Durham Open Data Portal - DPD Incidents UCR/NIBRS Reporting](https://live-durhamnc.opendata.arcgis.com/documents/DurhamNC::dpd-incidents-ucr-nibrs-reporting/about)
104
-
 
 
 
 
105
  - **Raleigh**:
106
  - [Raleigh Open Data Portal - Police Incidents (1)](https://data-ral.opendata.arcgis.com/datasets/09af62a32ae8436bae6eda74aa7f172b_0/explore?location=35.785903%2C-78.643000%2C10.73&showTable=true)
 
 
 
107
  - [Raleigh Open Data Portal - Police Incidents (2)](https://data-ral.opendata.arcgis.com/datasets/693811eb361f4da286891eca1fae5943_0/explore?filters=eyJDcmVhdGlvbkRhdGUiOlsxNzA2Njk1MjUzMjA5LDE3MDY2OTUyNTk2MTddfQ%3D%3D&location=35.797935%2C-78.624284%2C9.84)
108
-
109
-
110
- #### Initial Data Collection and Normalization
111
-
112
- Describe the data collection process. Describe any criteria for data selection or filtering. List any key words or search terms used. If possible, include runtime information for the collection process.
113
-
114
- If data was collected from other pre-existing datasets, link to source here and to their [Hugging Face version](https://huggingface.co/datasets/dataset_name).
115
-
116
- If the data was modified or normalized after being collected (e.g. if the data is word-tokenized), describe the process and the tools used.
117
-
118
- #### Who are the source language producers?
119
-
120
- State whether the data was produced by humans or machine generated. Describe the people or systems who originally created the data.
121
-
122
- If available, include self-reported demographic or identity information for the source data creators, but avoid inferring this information. Instead state that this information is unknown. See [Larson 2017](https://www.aclweb.org/anthology/W17-1601.pdf) for using identity categories as a variables, particularly gender.
123
-
124
- Describe the conditions under which the data was created (for example, if the producers were crowdworkers, state what platform was used, or if the data was found, what website the data was found on). If compensation was provided, include that information here.
125
-
126
- Describe other people represented or mentioned in the data. Where possible, link to references for the information.
127
-
128
- ### Annotations
129
-
130
- If the dataset contains annotations which are not part of the initial data collection, describe them in the following paragraphs.
131
-
132
- #### Annotation process
133
-
134
- If applicable, describe the annotation process and any tools used, or state otherwise. Describe the amount of data annotated, if not all. Describe or reference annotation guidelines provided to the annotators. If available, provide interannotator statistics. Describe any annotation validation processes.
135
-
136
- #### Who are the annotators?
137
-
138
- If annotations were collected for the source data (such as class labels or syntactic parses), state whether the annotations were produced by humans or machine generated.
139
-
140
- Describe the people or systems who originally created the annotations and their selection criteria if applicable.
141
-
142
- If available, include self-reported demographic or identity information for the annotators, but avoid inferring this information. Instead state that this information is unknown. See [Larson 2017](https://www.aclweb.org/anthology/W17-1601.pdf) for using identity categories as a variables, particularly gender.
143
-
144
- Describe the conditions under which the data was annotated (for example, if the annotators were crowdworkers, state what platform was used, or if the data was found, what website the data was found on). If compensation was provided, include that information here.
145
-
146
- ### Personal and Sensitive Information
147
-
148
- State whether the dataset uses identity categories and, if so, how the information is used. Describe where this information comes from (i.e. self-reporting, collecting from profiles, inferring, etc.). See [Larson 2017](https://www.aclweb.org/anthology/W17-1601.pdf) for using identity categories as a variables, particularly gender. State whether the data is linked to individuals and whether those individuals can be identified in the dataset, either directly or indirectly (i.e., in combination with other data).
149
-
150
- State whether the dataset contains other data that might be considered sensitive (e.g., data that reveals racial or ethnic origins, sexual orientations, religious beliefs, political opinions or union memberships, or locations; financial or health data; biometric or genetic data; forms of government identification, such as social security numbers; criminal history).
151
-
152
- If efforts were made to anonymize the data, describe the anonymization process.
153
-
154
  ## Considerations for Using the Data
155
 
156
  ### Social Impact of Dataset
157
 
158
- Please discuss some of the ways you believe the use of this dataset will impact society.
159
-
160
- The statement should include both positive outlooks, such as outlining how technologies developed through its use may improve people's lives, and discuss the accompanying risks. These risks may range from making important decisions more opaque to people who are affected by the technology, to reinforcing existing harmful biases (whose specifics should be discussed in the next section), among other considerations.
161
-
162
- Also describe in this section if the proposed dataset contains a low-resource or under-represented language. If this is the case or if this task has any impact on underserved communities, please elaborate here.
163
 
164
  ### Discussion of Biases
165
 
166
- Provide descriptions of specific biases that are likely to be reflected in the data, and state whether any steps were taken to reduce their impact.
167
-
168
- For Wikipedia text, see for example [Dinan et al 2020 on biases in Wikipedia (esp. Table 1)](https://arxiv.org/abs/2005.00614), or [Blodgett et al 2020](https://www.aclweb.org/anthology/2020.acl-main.485/) for a more general discussion of the topic.
169
-
170
- If analyses have been run quantifying these biases, please add brief summaries and links to the studies here.
171
 
172
  ### Other Known Limitations
173
 
 
76
 
77
  ### Curation Rationale
78
 
79
+ ### Curation Rationale
80
+
81
+ The dataset, covering police incidents in select North Carolina cities from 2000 to 2024, aims to aid crime research. It provides a long-term view of crime patterns and trends, useful for criminologists, sociologists, and public policy researchers. The comprehensive data enables analyses of crime evolution and its socio-economic correlations. It also supports the development of predictive models for law enforcement and policy planning. Additionally, the dataset's multi-city scope allows for comparative studies to understand unique challenges and inform localized crime prevention strategies.
82
 
83
  ### Source Data
84
 
 
100
  'Total Incidents', 'Year'
101
  - **Charlotte**:
102
  - [Charlotte Open Data Portal - CMPD Incidents](https://data.charlottenc.gov/datasets/d22200cd879248fcb2258e6840bd6726/explore?showTable=true)
103
+ - Details:
104
+ - Size: 483632 rows * 30 columns
105
+ - Column names: 'X', 'Y', 'YEAR', 'INCIDENT_REPORT_ID', 'LOCATION', 'CITY', 'STATE',
106
+ 'ZIP', 'X_COORD_PUBLIC', 'Y_COORD_PUBLIC', 'LATITUDE_PUBLIC',
107
+ 'LONGITUDE_PUBLIC', 'DIVISION_ID', 'CMPD_PATROL_DIVISION', 'NPA',
108
+ 'DATE_REPORTED', 'DATE_INCIDENT_BEGAN', 'DATE_INCIDENT_END',
109
+ 'ADDRESS_DESCRIPTION', 'LOCATION_TYPE_DESCRIPTION',
110
+ 'PLACE_TYPE_DESCRIPTION', 'PLACE_DETAIL_DESCRIPTION',
111
+ 'CLEARANCE_STATUS', 'CLEARANCE_DETAIL_STATUS', 'CLEARANCE_DATE',
112
+ 'HIGHEST_NIBRS_CODE', 'HIGHEST_NIBRS_DESCRIPTION', 'OBJECTID', 'Shape',
113
+ 'GlobalID'
114
  - **Durham**:
115
  - [Durham Open Data Portal - DPD Incidents UCR/NIBRS Reporting](https://live-durhamnc.opendata.arcgis.com/documents/DurhamNC::dpd-incidents-ucr-nibrs-reporting/about)
116
+ - Details:
117
+ - Size: 149924 rows * 16 columns
118
+ - Column names: 'Case Number', 'Report Date', 'Report Time', 'Status', 'Sequence',
119
+ 'ATT/COM', 'UCR Code', 'Offense', 'Address', 'X', 'Y', 'District',
120
+ 'Beat', 'Tract', 'Premise', 'Weapon'
121
  - **Raleigh**:
122
  - [Raleigh Open Data Portal - Police Incidents (1)](https://data-ral.opendata.arcgis.com/datasets/09af62a32ae8436bae6eda74aa7f172b_0/explore?location=35.785903%2C-78.643000%2C10.73&showTable=true)
123
+ - Details:
124
+ - Size: 422975 rows * 6 columns
125
+ - Column names: 'LCR Code', 'LCR Description', 'Incident Date', 'Incident #', 'DISTRICT', 'Yesterday'
126
  - [Raleigh Open Data Portal - Police Incidents (2)](https://data-ral.opendata.arcgis.com/datasets/693811eb361f4da286891eca1fae5943_0/explore?filters=eyJDcmVhdGlvbkRhdGUiOlsxNzA2Njk1MjUzMjA5LDE3MDY2OTUyNTk2MTddfQ%3D%3D&location=35.797935%2C-78.624284%2C9.84)
127
+ * This dataset is updated daily. I will monitor these updates and continue collecting data until February 15th, 2024.
128
+
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
129
  ## Considerations for Using the Data
130
 
131
  ### Social Impact of Dataset
132
 
 
 
 
 
 
133
 
134
  ### Discussion of Biases
135
 
 
 
 
 
 
136
 
137
  ### Other Known Limitations
138