dee

Fort_Worth_Codebook3.docx

Codebook

Fort Worth Code Violations Dataset

Dataset overview This dataset contains administrative records related to Fort Worth code violations and complaints. Each row appears to represent a violation record rather than a unique case, because one case may contain multiple violations. Records: 230,708 Variables: 22

Variable codebook

Variable Name	Type	Description	Example / Notes
Complaint_Type_Description	Text	Type or category of complaint or violation.	Examples may include property maintenance, multi-family, vehicle, health hazard, or zoning-related issues.
Location_1	Text	Geographic location stored as a text coordinate pair.	Often appears as a latitude/longitude pair in parentheses.
Count	Numeric (integer)	Count field included in the export.	Appears to function as a record counter and is commonly 1.
Case_ID	Text	Unique identifier for the case.	A single Case_ID may appear in more than one row.
Violation_ID	Numeric (integer)	Unique identifier for a specific violation record.	Most useful row-level identifier in this file.
CFWLand_ObjectID	Numeric	Parcel or land-related object identifier used in the city system.	Contains some missing values.
Violation_Address	Text	Street address associated with the violation.	Useful for sorting, filtering, and location review.
Case_Created_Date	Date/Time	Date and time when the case was created.	Can be used to create year or month variables.
Code_Officer	Text	Name of the code officer associated with the record.	Useful for counts by staff member.
Violation_Current_Status	Text	Current status of the violation.	Observed values include Open and Closed.
Case_Current_Status	Text	Current status of the overall case.	Not necessarily identical to violation status.
Next_Activity_Due_Date	Date/Time	Next scheduled activity date for the case or violation.	Contains many missing values.
Violation_Created_Date	Date/Time	Date and time when the violation record was created.	May differ from the case creation date.
Update_Date	Date/Time	Date and time when the record was last updated.	Useful for measuring recency or approximate case age.
GeoCodeScore	Numeric	Score reflecting geocoding match quality or location confidence.	Higher values generally indicate better geocoding confidence.
X_Coordinate	Numeric	Projected X coordinate for the location.	May be blank when the record was not geocoded.
Y_Coordinate	Numeric	Projected Y coordinate for the location.	May be blank when the record was not geocoded.
Location 1	Text	Additional text-based location field.	Appears similar or overlapping with Location_1.
City	Text	City name for the violation location.	Appears to be Fort Worth in this dataset.
State	Text	State abbreviation for the violation location.	Appears to be TX in this dataset.
Longitude	Numeric	Longitude of the violation location.	May be missing for ungeocoded records.
Latitude	Numeric	Latitude of the violation location.	May be missing for ungeocoded records.

Unit of analysis

The likely unit of analysis is the violation record, not the case. A single case may contain multiple violation records, which is why Case_ID can repeat.

Location fields

The file includes several overlapping location variables, including text coordinates, projected coordinates, longitude, and latitude. For introductory Excel work, students usually only need Violation_Address, Longitude, and Latitude.

Missing data

Some variables contain substantial missing data, especially Next_Activity_Due_Date and several coordinate fields. This is common in real administrative datasets.

Limited-variation fields

Some fields appear to have little variation, such as Count, City, and State. These may be less useful for comparison but still help students understand the structure of the file.

Recommended variables for beginner Excel analysis

For an introductory Excel assignment, the most useful variables are: Complaint_Type_Description, Case_ID, Violation_ID, Violation_Address, Case_Created_Date, Code_Officer, Violation_Current_Status, Case_Current_Status, and Update_Date.

This dataset contains administrative records related to code violations and complaints in Fort Worth, Texas. Each row represents a violation record and includes information such as complaint type, case number, violation number, address, dates, assigned code officer, case status, and geographic location. Because this is a real-world administrative dataset, some values may be missing or repeated, and one case may include multiple violation records.