id | title | date | author | layout | guid | permalink | image | categories | tags | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
42097 |
Building Safety Data on the Open Data Portal |
2016-08-01 15:54:44 -0500 |
Tom Schenk |
post |
/index.php/building-safety-data-on-the-open-data-portal/ |
|
|
One of the most defining characteristics of any city is its buildings. They help define the physical character and aesthetic of any city. A USA Today reader poll put Chicago’s skyline as the second-best in the United States. Buildings go beyond the downtown and into our neighborhoods to serve a greater function to also house and shelter us. So it’s also important to make sure these buildings are safe and cared for, which is accomplished by the City of Chicago’s Department of Buildings which inspects and sometimes issues violations for buildings failing to meet a standard for quality and safety.
Several years ago, Chicago published building violations data on the data portal. Last year, the city began publishing a list of problematic landlords and a list of building code scofflaws. Today, we’ve expanded building safety data on the open data portal by releasing administrative hearings data for ordinance violations issued by the Department of Buildings on the open data portal.
These data detail the current and historical administrative hearing cases resulting from violations and tickets (notices of violations) issued by Department of Buildings. Administrative hearing records provide the status of the cases which result from violations issued to building owners. This is the same data that is used to help the city determine the aforementioned problematic landlord and building scofflaw lists. Updated each day, you can see whether someone was ultimately found liable for a violation or if the case was dismissed. Likewise, you can also see the status of cases that have yet to be decided.
As with any data, there is some nuance in understanding its structure. Often, a single building is issued a ticket (a notice of violation, which is abbreviated as NOV). In this data, each row represents a particular violation. Violations which were part of the same ticket are denoted by the same NOV NUMBER. The VIOLATION CODE indicates the unique code for a particular violation while VIOLATION DESCRIPTION gives a plain-language description of the VIOLATION CODE.
At times, a case may have multiple respondents. This field is pipe-delimited, so each respondent is separated by a “|” character.
Every morning, the data set is updated with the most recent information, including the stage for each case. For cases that haven’t been determined, it shows the current status, such as cases that have continuances (i.e., rescheduled). See the LAST MODIFIED DATE to see when the case status has been last updated. When a case has been decided as either a default or liable, information on the associated fines are also included.
This data set complements the building violations data already on the data portal. The building violation data set represents the inspections and violations issued by the Department of Buildings. Just like Law & Order, the violations data provides the citation (law), while this new ordinance violations provides the hearing (order).