In rfortherestofus/obtn: Oregon by the Numbers

knitr::opts_chunk$set(
  collapse = TRUE,
  comment = "#>"
)

library(obtn)

One of the small but annoying issues that we have seen with Oregon by the Numbers is inconsistent rounding. In the 2020 version, we had the following issue:

For job growth data for Malheur county, the raw value provided to me was 0.49084635. A problem arose because this was rounded differently in two places. In the county table, it was rounded to 0 because we were rounding to the nearest whole number.

However, on the measure tables, the value for Malheur showed up as 0.5 because we were rounding to 1 decimal place:

The obvious solution to this is to use 1 decimal place everywhere. However, we haven't done this because it looks better aesthetically to have whole numbers on the county tables. We've intentionally made the choice to have the county tables use whole numbers while the measure tables use 1 decimal place with the assumption that the latter is for those who really want to dig into the data, and thus want the additional precision.

rfortherestofus/obtn documentation built on Feb. 10, 2025, 1:30 a.m.