City level VMT dataset, VMT data updates

[eroten]

New dataset - CTU level VMT for Minnesota

CTU data limitations

• 2015 is interpolated due to underlying system changes, like with county level data
• VMT data at the CTU level is not as stable and reliable as county level data. I discussed these limitations with Christy Prentice and Scott Patnode at MnDOT before determining reliable CTUs.
• Some cities have centerline miles that appear to be in the incorrect county. This is a geographic data issue. To get the city total, we just group by ctu_name alone.
• MnDOT does not currently collect any data on townships. I double checked that all our townships were not present in MnDOT online documentation of cities.
• Due to data limitations, only a subset of CTUs can be reliably used for VMT. These are 110 of our 188 CTUs.
  • Sampling percentage
    • Starting in 2017-2019, MnDOT began reporting CTU level percent sampled data. Percent sampled indicates the proportion of total vehicle miles where the AADT data is sampled vs the AADT data is un-sampled. Sampled AADT can be sourced from counts, annually adjusted past AADT, modeled AADT from probe data or location specific AADT estimates.
    • A percent sampled greater than 0 indicates that there has been a sample at some point.
    • A percent sampled of 0 indicates that there has never been a sample. This indicates that the reported values are default values. Default values will not respond to actual changes in VMT, unlike sampled data. Though the defaults take into account things like rural/urban and route system, they are standardized values that have not been regularly updated.
    • Sampling is not an issue for trunk highways and interstates where sampling takes place regularly, but lower level systems like municipal streets and alleys, are less likely to be sampled regularly.
    • In fact, route systems Unorganized Territory Road, National Forest Road, State Forest Road, State Park Road, Military Road, Bureau of Fish and Wildlife Road, Other Local Road and Alleyway have never been sampled in our region.
    • Route systems "01", "02", "03", "04", "07", "52", "32", "53" are considered Trunk highway and county systems. All other are considered local systems. Note that route system "05" (Municipal State Aid Streets) is classified as LOCAL.
    • For our purposes, we are including CTUs that have sampled data on local systems, based on percent sampled data for any year in 2017-2023.
  • Availability
    • Some smaller CTUs and those that have been newly formed over the time series (2001-2023) do not have data for all years. For consistency, CTUs with fewer than 9 years of data are removed.

Other

• Made some object names easier to follow across scripts
• New clean route system index, used in both county and city MnDOT VMT
• Added 2023 WisDOT VMT to DOT VMT dataset
• Added colors to cprg_colors. A couple of them are still needed in data_dot_vmt.qmd
• Updated documentation on DOT VMT, specifying CTU limitations
• I was having difficulty with all our "Saint" CTUs, so I made a small helper in meta/data-raw/ctu_saint_names.R. This might be overkill and useful for no one else. Reviewer, let me know.

Testing updates

• Additional tests for ctu_population, checking for bad CTU names, CTU/county combinations
• New tests for on-road emissions compilation
• Additional, updated test for county level DOT VMT
• New tests for CTU level VMT

Checklist

Please complete this checklist as a courtesy to the PR reviewer.

Code and styling

• All of the files/scripts I added are in the right place and named appropriately. See the README for details.
• I have not used setwd()
• I have used file.path(here::here(), "file_name")) to source any scripts or read in data
• I have not added any large datasets, unless absolutely necessary (explain)
• I have commented my code, particularly in hard to understand areas
• I have added additional package dependencies as necessary with renv::install()
• I have run styler::style_dir(".", recursive = TRUE, filetype = c("R", "qmd"))
• Plots
  • If plotly, use source = "chunk-name" in plot_ly()
  • Use formatting with councilR::plotly_layout()?
• Chunk formatting
  • All chunks named
  • All figure or table chunks have caption
  • out.width: "95%". If a specific height is needed, use pixels. and/or out.height: "500px"

Document editing

• I have ensured that modified documents knit successfully from render_for_publication.R
• I have fixed any missing citations, cross references, hyperlinks
• I have reviewed my contributions for typos and misspellings.

GitHub and project management

• I have identified and assigned at least one Reviewer (Liz, Sam, Laine) to this PR
• I have assigned myself to this PR
• I have updated the status in the GitHub Project

[pawilfahrt]

Everything ran really smoothly Liz. Thanks for pulling this together so quickly.