The group_id field will be populated if there is only a single report of an issue or if there are multiple reports. The ID of the first ticket to arrive for a given issue is used as the group_id.

The total number of requests for a given issue (parent + child tickets).

Families of tickets (children and parent tickets) should be closed simultaneously. In some edge cases, prior to August of 2021, this did not always occur. This dataset is maintained with the understanding that all ticket statuses should be updated on the parent ticket and cascade to the entire family of tickets.

This field is useful for aggregating tickets for progress metrics such as the ticket closure rate.

This field is interchangeable with status_name (0 = open; 1 = closed; 3 = in progress; 4 = on hold).

The department assigned to handle the ticket.

Category that the request falls under. This is interchangeable with request_type_id.

ID for the category that the request falls under. This is interchangeable with request_type_name (e.g., potholes = 484).

See general notes section for more information.

The UTC datetime that the issue/request was created for the parent ticket.

Updates are always made on parent tickets. See description of parent_closed for more information.

The UTC datetime that an action was last taken on the parent ticket.

Closures are always made on parent tickets. See description of parent_closed for more information.

The UTC datetime that the parent ticket was closed.

Method used to submit the 3-1-1 request (e.g., 'Call Center' for requests by phone and 'Email' for requests by e-mail).

This is the street that the request location is on, as input by a 311 operator or the resident who submitted the request.

Note that for some locations, it is irrelevant to list a cross street, and this field may be missing.

Streets are assigned a string representation of a numeric code. Note that this value is set to 0 for instances where streets are not entered. This code may be useful for types of analyses in which street name is an unwieldy datapoint and a more concise representation is helpful.

See street_id field description for further information.

The city field is extracted from the location that the user enters. (Requests/issues are occasionally submitted for locations outside of the city limits. The city of Pittsburgh cannot address these tickets.)

The name of the neighborhood containing the latitude and longitude for the location in question.

The Census tract containing the latitude and longitude for the location in question.

The council district containing the latitude and longitude for the location in question.

The ward containing the latitude and longitude for the location in question.

The police zone containing the latitude and longitude for the location in question.

The latitude of the request's location, subject to possible obfuscation as described by the geoaccuracy field.

The longitude of the request's location, subject to possible obfuscation as described by the geoaccuracy field.

This field describes the nature of the latitude and longitude values, indicating whether 1) they match those attached to the original request (EXACT), 2) they've been modified (APPROXIMATE) or removed entirely (REDACTED) to obscure the location for privacy reasons, 3) they are out of the 3-1-1 service area (OUT_OF_BOUNDS), or 4) they were missing from the original request or removed in cases where the location is not germane to the request (NULL_COORDINATES).