Metadata for Reported Crime Open Data Download
Cases deemed sensitive due to the nature of the crime, victim, victim/offender relationship, or investigation status may contain data that cannot be shared openly at this time. Case numbers and specific location information for sensitive cases are not included in the open data.
|Case Number||The case year and number for the reported incident (YY-######).
Sensitive cases have been randomly assigned a case number and are denoted by an X following the case year (YY-X######).
|Occur Month Year||The Month and Year that the incident occured.|
|Occur Date||Date the incident occurred. The exact occur date is sometimes unknown. In most situations, the first possible date the crime could have occurred is used as the occur date. (For example, victims return home from a week-long vacation to find their home burglarized. The burglary could have occurred at any point during the week. The first date of their vacation would be listed as the occur date.)|
|Occur Time||Time the incident occured. The exact occur time is sometimes unknown. In most situations, the first possible time the crime could have occured is used as the occur time.
The time is reported in the 24-hour clock format, with the first two digits representing hour (ranges from 00 to 23) and the second two digits representing minutes (ranges from 00 to 59).
Note: By default, Microsoft Excel removes leading zeroes when importing data. For more help with this issue, refer to Microsoft's help page.
|Address||Address of reported incident at the 100 block level (e.g.: 1111 SW 2nd Ave would be 1000 Block SW 2nd Ave).
To protect the identity of victims and other privacy concerns, the address location of certain case types are not released.
X / Y
|Generalized XY point of the reported incident. For offenses that occurred at a specific address, the point is mapped to the block's midpoint. Offenses that occurred at an intersection is mapped to the intersection centroid. To protect the identity of victims and other privacy concerns, the points of certain case types are not released.
XY points use the Oregon State Plane North (3601), NAD83 HARN, US International Feet coordinate system.
Lat / Lon
|Generalized Latitude / Longitude of the reported incident. For offenses that occurred at a specific address, the point is mapped to the block's midpoint. Offenses that occurred at an intersection is mapped to the intersection centroid. To protect the identity of victims and other privacy concerns, the points of certain case types are not released.|
|Neighborhood||Neighborhood where incident occurred.
If the neighborhood name is missing, the incident occurred outside of the boundaries of the Portland neighborhoods or at a location that could not be assigned to a specific address in the system (e.g., Portland, near Washington Park, on the streetcar, etc.). Note: Neighborhood boundaries and designations vary slightly from those found on the Office of Neighborhood Involvement website.
|Crime Against||Crime against category (Person, Property, or Society)|
|Offense Category||Category of offense (for example, Assault Offenses)|
|Offense Type||Type of offense (for example, Aggravated Assault)
Note: The statistic for Homicide Offenses has been updated in the Group A Crimes report to align with the 2019 FBI NIBRS definitions. The statistic for Homicide Offenses includes (09A) Murder & Non-negligent Manslaughter and (09B) Negligent Manslaughter. As of January 1, 2019, the FBI expanded the definition of negligent manslaughter to include traffic fatalities that result in an arrest for driving under the influence, distracted driving, or reckless driving. The change in definition impacts the 2019 homicide offenses statistic and the comparability of 2019 homicide statistics to prior year.
|Offense Count||Number of offenses per incident. Offenses (i.e. this field) are summed for counting purposes.|