Update README.md
Browse files
README.md
CHANGED
@@ -52,17 +52,24 @@ English
|
|
52 |
|
53 |
### Data Instances
|
54 |
|
55 |
-
|
56 |
|
57 |
-
```
|
58 |
{
|
59 |
-
|
60 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
61 |
}
|
62 |
```
|
63 |
|
64 |
-
Provide any additional information that is not covered in the other sections about the data here. In particular describe any relationships between data points and if these relationships are made explicit.
|
65 |
-
|
66 |
### Data Fields
|
67 |
|
68 |
List and describe the fields present in the dataset. Mention their data type, and whether they are used as input or output in any of the tasks the dataset currently supports. If the data has span indices, describe their attributes, such as whether they are at the character level or word level, whether they are contiguous or not, etc. If the datasets contains example IDs, state whether they have an inherent meaning, such as a mapping to other datasets or pointing to relationships between data points.
|
@@ -71,10 +78,20 @@ List and describe the fields present in the dataset. Mention their data type, an
|
|
71 |
|
72 |
Note that the descriptions can be initialized with the **Show Markdown Data Fields** output of the [Datasets Tagging app](https://huggingface.co/spaces/huggingface/datasets-tagging), you will then only need to refine the generated descriptions.
|
73 |
|
|
|
74 |
|
75 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
76 |
|
77 |
-
|
|
|
78 |
|
79 |
### Curation Rationale
|
80 |
|
|
|
52 |
|
53 |
### Data Instances
|
54 |
|
55 |
+
Here is an illustrative example from the processed dataset (note that specific details are subject to change):
|
56 |
|
57 |
+
```json
|
58 |
{
|
59 |
+
"year": 2022,
|
60 |
+
"city": "Raleigh",
|
61 |
+
"crime_major_category": "Theft",
|
62 |
+
"crime_specific_category": "Vehicle Theft",
|
63 |
+
"latitude": 35.7796,
|
64 |
+
"longitude": -78.6382,
|
65 |
+
"start_time": "2022-05-15T14:00:00",
|
66 |
+
"end_time": "2022-05-15T16:00:00",
|
67 |
+
"clear_status": "Cleared by Arrest",
|
68 |
+
"incident_address": "123 Main St, Raleigh, NC",
|
69 |
+
"notes": "Weapon: None"
|
70 |
}
|
71 |
```
|
72 |
|
|
|
|
|
73 |
### Data Fields
|
74 |
|
75 |
List and describe the fields present in the dataset. Mention their data type, and whether they are used as input or output in any of the tasks the dataset currently supports. If the data has span indices, describe their attributes, such as whether they are at the character level or word level, whether they are contiguous or not, etc. If the datasets contains example IDs, state whether they have an inherent meaning, such as a mapping to other datasets or pointing to relationships between data points.
|
|
|
78 |
|
79 |
Note that the descriptions can be initialized with the **Show Markdown Data Fields** output of the [Datasets Tagging app](https://huggingface.co/spaces/huggingface/datasets-tagging), you will then only need to refine the generated descriptions.
|
80 |
|
81 |
+
A typical instance in the processed dataset can be represented in JSON format as follows:
|
82 |
|
83 |
+
- `year`: The year when the incident occurred.
|
84 |
+
- `city`: The city where the incident took place.
|
85 |
+
- `crime_major_category`: The broad category of the crime.
|
86 |
+
- `crime_specific_category`: The specific type of crime within the major category.
|
87 |
+
- `latitude` and `longitude`: Geographical coordinates of the incident location.
|
88 |
+
- `start_time` and `end_time`: The start and end times of the incident.
|
89 |
+
- `clear_status`: The status of the case (e.g., cleared by arrest, under investigation).
|
90 |
+
- `incident_address`: The detailed address where the incident occurred.
|
91 |
+
- `notes`: Additional information about the incident, such as weapon used, if any.
|
92 |
|
93 |
+
|
94 |
+
## Dataset Creation
|
95 |
|
96 |
### Curation Rationale
|
97 |
|