My dataset is about railroad bridges from the Palouse River and Coulee City (PCC) rail system in Washington State. The data has information on each bridge, like where it is, what type it is, how long it is, the year it was built, latitude and longitude. There are both categorical and numeric variables in this dataset, so it works for this project.
For my project, I decided to explore the bridges to see if anything stood out in the data. I decided to focus on which bridge type is the longest on average because I wanted to compare the types of bridges. I also made a map to see where the bridges are located in the PCC system. I chose this dataset because it was different from what I am usually interested in.
library(tidyverse)
── Attaching core tidyverse packages ──────────────────────── tidyverse 2.0.0 ──
✔ dplyr 1.1.4 ✔ readr 2.1.5
✔ forcats 1.0.0 ✔ stringr 1.5.1
✔ ggplot2 3.5.2 ✔ tibble 3.3.0
✔ lubridate 1.9.4 ✔ tidyr 1.3.1
✔ purrr 1.1.0
── Conflicts ────────────────────────────────────────── tidyverse_conflicts() ──
✖ dplyr::filter() masks stats::filter()
✖ dplyr::lag() masks stats::lag()
ℹ Use the conflicted package (<http://conflicted.r-lib.org/>) to force all conflicts to become errors
Rows: 164 Columns: 20
── Column specification ────────────────────────────────────────────────────────
Delimiter: ","
chr (7): LineSegmentNumber, BridgeIdentification, Location, State, Types, C...
dbl (13): X, Y, OBJECTID, ID, Milepost, Latitude, Longitude, BridgeSectionNu...
ℹ Use `spec()` to retrieve the full column specification for this data.
ℹ Specify the column types or set `show_col_types = FALSE` to quiet this message.