Update README.md

README.md

@@ -29,7 +29,7 @@ For any issues related to the raw datasets, please reach out to the respective g
 
 ### Dataset Summary
 
-The dataset comprising public police incidents from various cities in North Carolina, spanning from the early 2000s to 2024, contains valuable information such as crime type, time, and location of occurrence. 
+The dataset, derived from public police incident reports from various cities in North Carolina, spans from the early 2000s to 2024. The source data originate from the open data portals of Cary, Charlotte, Durham, and Raleigh. The dataset underwent a process of merging data from these cities, followed by cleaning to remove incomplete rows. Additionally, the dataset focuses on extracting and categorizing major crime types, providing valuable information such as crime type, time, location of occurrence, and other relevant details.
 
 ### Supported Tasks and Leaderboards
 
@@ -72,24 +72,17 @@ Here is an illustrative example from the processed dataset (note that specific d
 
 ### Data Fields
 
-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.
-
-- `example_field`: description of `example_field`
-
-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.
-
-A typical instance in the processed dataset can be represented in JSON format as follows:
-
-- `year`: The year when the incident occurred.
-- `city`: The city where the incident took place.
-- `crime_major_category`: The broad category of the crime.
-- `crime_specific_category`: The specific type of crime within the major category.
-- `latitude` and `longitude`: Geographical coordinates of the incident location.
-- `start_time` and `end_time`: The start and end times of the incident.
-- `clear_status`: The status of the case (e.g., cleared by arrest, under investigation).
-- `incident_address`: The detailed address where the incident occurred.
-- `notes`: Additional information about the incident, such as weapon used, if any.
+The dataset contains several fields, each providing specific information about police incidents. Here is a list of these fields along with their descriptions and data types:
 
+- `year` (integer): The year in which the incident occurred. Used as input in temporal analysis tasks.
+- `city` (string): The city where the incident took place. This field is crucial for geographic analyses and comparisons between cities.
+- `crime_major_category` (string): A broad categorization of the crime, used as input for crime pattern analysis and categorization tasks.
+- `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.
+- `latitude` (float) and `longitude` (float): Geographical coordinates pinpointing the location of the incident. These fields are essential for geospatial analysis.
+- `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.
+- `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.
+- `incident_address` (string): The specific address where the incident occurred. This field adds a detailed spatial dimension to the data.
+- `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.
 
 ## Dataset Creation
 
@@ -99,8 +92,7 @@ The dataset, covering police incidents in select North Carolina cities from 2000
 
 ### Source Data
 
-I mainly uses 5 datasets as source data:
-
+Five datasets are primarily utilized as source data:
 - **Cary**:
   - [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)
   - Details:
@@ -173,12 +165,9 @@ Raleigh's Open Data Policy stipulates that by using data from their site, users
 
 Each city's portal reflects a commitment to transparency and public engagement, allowing unrestricted access and utilization of data for various purposes, with specific stipulations in Raleigh's policy and Cary's adoption of the CC BY-SA 4.0 license providing additional guidance on use and liability.
 
-### Citation Information
-
-
 ### Contributions
 
-Thanks to Town of Cary, City of Charlotte, and City of Raleigh for providing the raw dataset.
+Thanks to Town of Cary, City of Charlotte, City of Durham, and City of Raleigh for providing the raw dataset.