How do the JSON output and object table of 911 calls API created by Crimeometer function?

In this article, we will review the object table and JSON output specifically of Crimeometer 911 calls API. I will focus on providing a clear understanding of the structure and contents of the object table and JSON output, and how they relate to the data provided by the Crimeometer 911 calls API. Understanding the object table and JSON output is important for properly using and interpreting the data provided by the API.

Object and Description table

• total_incidents: The total number of incidents recorded in the API.

• total_pages: The total number of pages of incident data available in the API.

• incidents: An array of incident objects, each representing a single incident recorded in the API.

• call_city_key: A unique identifier for the city in which the incident occurred.

• call_code: A code representing the type of incident that occurred.

• call_date: The date and time at which the incident occurred.

• call_type: A description of the type of incident that occurred.

• call_description: A more detailed description of the incident.

• call_latitude: The latitude of the location at which the incident occurred.

• call_longitude: The longitude of the location at which the incident occurred.

• call_address: The address of the location at which the incident occurred.

The information in the table is useful because it provides a detailed breakdown of the data provided by the Crimeometer 911 calls API. The object table lists all of the different data points that are available for each incident, including the date and time of the incident, the location, and the type of incident that occurred. This information is important for understanding the context of each incident and for analyzing trends and patterns in the data. Additionally, the object table provides a clear and concise summary of the data that is available, making it easier for users to understand what is available and how to access it. Overall, the information in the table is essential for anyone looking to use or analyze the data provided by the Crimeometer 911 calls API.

JSON REST output

This JSON output represents data from a collection of 911 calls, with information about each call contained in an "incidents" array. The output includes the total number of incidents recorded in the collection ("total_incidents"), as well as the total number of pages of incident data available ("total_pages"). Each incident is represented as an object within the "incidents" array, with properties such as "call_city_key" (a unique identifier for the city in which the incident occurred), "call_code" (a code representing the type of incident), "call_date" (the date and time at which the incident occurred), and "call_type" (a description of the type of incident). Other properties such as "call_description", "call_latitude", "call_longitude", and "call_address" provide additional details about the incident, such as a more detailed description, the location of the incident, and the address of the location. Overall, this JSON output provides a comprehensive overview of a collection of 911 calls, with detailed information about each individual call.

{
"total_incidents": 2,
"total_pages": 1,
"incidents": [
{
"call_city_key": "AUS",
"call_code": "20191010131",
"call_date": "2019-04-11T01:40:00.000Z",
"call_type": "Alcohol-related offense",
"call_description": "DWI at 816 LAVACA ST",
"call_latitude": 30.27146322,
"call_longitude": -97.74426176,
"call_address": "816 LAVACA ST"
},
{
"call_city_key": "AUS",
"call_code": "20183640046",
"call_date": "2018-12-30T02:48:00.000Z",
"call_type": "Alcohol-related offense",
"call_description": "DWI at W 9TH ST / LAVACA ST",
"call_latitude": 30.27154076,
"call_longitude": -97.74415195,
"call_address": "W 9TH ST / LAVACA ST"
}
]
}

Conclusion

In this conversation, we discussed the object table and JSON output specifically of Crimeometer 911 calls API. The object table provided a list of all the data points available for each incident, including the date and time, location, and type of incident. The JSON output provided a more detailed representation of this data, with each incident represented as an object within an "incidents" array. The JSON output also included information about the total number of incidents and pages of data available. Understanding the object table and JSON output is important for properly using and interpreting the data provided by the Crimeometer 911 calls API.

Footnote

The Crimeometer 911 calls API is a data source that provides information about 911 calls made to emergency services. If you would like to access this data, you can request access to the Crimeometer 911 calls API through the third party data marketplace of Worldindata. Worldindata is a platform that connects data providers with users who are interested in accessing various types of data. By requesting access to the Crimeometer 911 calls API through Worldindata, you will be able to access the data provided by this API and use it in your own projects or analyses. Please note that access to the Crimeometer 911 calls API may be subject to certain terms and conditions, and you may be required to pay a fee in order to use the API.