How does the JSON and Object and description table of crime incidents API created by Crimeometer work?

In this article, we will be clarifying the object table and JSON output of Crimeometer's crime incidents API. Specifically, I will explain the fields and data types included in the object table and how the JSON output is structured to represent this information. It is important to understand the structure and contents of the object table and JSON output in order to effectively utilize the data provided by the Crimeometer API.

Table

ObjectsDescription
total_incidents
total_pages
incidents
city_keyCity code in UN/LOCODE standard
incident_codeIncident code provided by the source
incident_dateIncident occurred date (approximate in some cases)
incident_offenseIncident offense type using FBI-NIBRS standard
incident_offense_codeIncident offense code using FBI-NIBRS standard
incident_offense_descriptionIncident offense sub type using FBI-NIBRS standard
incident_offense_detail_descriptionIncident detail description
incident_offense_crime_againstIncident against Person/Property/Society/Not a Crime
incident_offense_actionIncident action status (Commited/Attempted)
incident_source_original_typeType of incident from the original source
incident_source_nameIncident source name
incident_latitudeLatitude value of the incident
incident_longitudeLongitude value of the incident
incident_addressIncident address
  1. total_incidents: The total number of incidents in the API.

  2. total_pages: The total number of pages in the API.

  3. incidents: An array of objects representing individual incidents.

  4. city_key: A code that represents the city where the incident occurred, using the UN/LOCODE standard.

  5. incident_code: A code that represents the incident, as provided by the source.

  6. incident_date: The date when the incident occurred. In some cases, this date may be approximate.

  7. incident_offense: The type of offense committed during the incident, using the FBI-NIBRS standard.

  8. incident_offense_code: A code representing the offense committed during the incident, using the FBI-NIBRS standard.

  9. incident_offense_description: A description of the offense committed during the incident, using the FBI-NIBRS standard.

  10. incident_offense_detail_description: A more detailed description of the offense committed during the incident.

  11. incident_offense_crime_against: The target of the offense, which could be a person, property, society, or something else.

  12. incident_offense_action: The status of the offense, which could be "committed" or "attempted".

  13. incident_source_original_type: The type of incident, as reported by the original source.

  14. incident_source_name: The name of the source that reported the incident.

  15. incident_latitude: The latitude of the location where the incident occurred.

  16. incident_longitude: The longitude of the location where the incident occurred.

  17. incident_address: The address of the location where the incident occurred.

The information in the table is useful because it provides a comprehensive overview of the data contained in the Crimeometer crime incidents API. By understanding the objects and their descriptions, users can accurately interpret and utilize the data provided by the API. For example, the incident_offense object can be used to classify incidents by the type of offense, and the incident_date object can be used to filter incidents by the date they occurred. The incident_latitude and incident_longitude objects can be used to plot the locations of incidents on a map, while the incident_address object can be used to display the specific address of an incident. Overall, the information in the table is essential for effectively using the Crimeometer crime incidents API.

JSON output

This JSON output represents data from the Crimeometer crime incidents API. It contains information about two incidents that occurred in Austin, Texas. The total_incidents field is set to 2, indicating that there are two incidents in the incidents array. The total_pages field is set to 1, indicating that there is only one page of incidents. Each incident is represented by an object in the incidents array, with each object containing a variety of fields that provide details about the incident. For example, the incident_offense field describes the type of offense that was committed, while the incident_date field provides the date when the incident occurred. The incident_latitude and incident_longitude fields give the location of the incident, and the incident_address field gives the specific address. Overall, this JSON output provides a detailed record of two incidents that occurred in Austin, Texas.

[
{
"total_incidents": 2,
"total_pages": 1,
"incidents": [
{
"city_key": "AUS",
"incident_code": "20191101137",
"incident_date": "2019-04-20T15:53:00.000Z",
"incident_offense": "Driving Under the Influence",
"incident_offense_code": "90D",
"incident_offense_description": "Driving Under the Influence",
"incident_offense_detail_description": "Driving Under the Influence at 5309 E RIVERSIDE DR",
"incident_offense_crime_against": "Society",
"incident_offense_action": "C",
"incident_source_original_type": "DWI",
"incident_source_name": "Austin_Police_Department_Crime_Reports",
"incident_latitude": 30.2292141,
"incident_longitude": -97.71322768,
"incident_address": "5309 E RIVERSIDE DR"
},
{
"city_key": "AUS",
"incident_code": "20191101207",
"incident_date": "2019-04-20T16:54:00.000Z",
"incident_offense": "Assault Offenses",
"incident_offense_code": "13A",
"incident_offense_description": "Aggravated Assault",
"incident_offense_detail_description": "Aggravated Assault at 5809 SWEENEY CIR",
"incident_offense_crime_against": "Person",
"incident_offense_action": "C",
"incident_source_original_type": "AGG ASSAULT FAM/DATE VIOLENCE",
"incident_source_name": "Austin_Police_Department_Crime_Reports",
"incident_latitude": 30.30535921,
"incident_longitude": -97.67908217,
"incident_address": "5809 SWEENEY CIR"
}
]
}
]

In summary

In this article, we have discussed the object table and JSON output of the Crimeometer crime incidents API. The object table lists the various objects and their descriptions that are included in the API, and the JSON output provides a detailed example of how this data is structured and formatted. We have also discussed the availability of the Crimeometer crime incidents API through the third party data marketplace of Worldindata. By understanding the object table, JSON output, and access to the API, users can effectively utilize the data provided by Crimeometer to gain insights into crime incidents.

Note

To access the Crimeometer crime incidents API, you can request access through the third party data marketplace of Worldindata. Worldindata is a platform that allows users to browse and purchase data from a variety of sources, including APIs like Crimeometer. To request access to the Crimeometer crime incidents API, you will need to create an account on the Worldindata platform and follow their instructions for requesting access to specific datasets. Once you have been granted access, you will be able to use the Crimeometer crime incidents API to retrieve data about crime incidents from a variety of sources. It is important to note that the availability and pricing of the Crimeometer crime incidents API may vary depending on the specific terms of the data marketplace.