Some things I noticed while mapping Amtrak Cascades:

1) It's a pain in the butt to live-map when you're screaming along at 102 MPH, as we were for dozens of minutes at a stretch, barely slowing for curves and towns.

2) The existing railroad maps for Cascadia leave much to be desired.

3) Someone else in the region did a really half-assed job at mapping yards in the region. Lots of broken segments, duplicate nodes and just plain wrong turnouts fixed, but lots of updating still needs to be done. Unfortunately, the Amtrak Cascades system lacks wifi service, so OSB tagging was a nonstarter (there really needs to be a way to handle the OSB layer offline like there is with other layers in JOSM). This same someone seems to have the idea that railway=spur is a valid tag (it's not: you really want railway=rail, service=spur, and even then NOT ON THE MAINLINE!). Worst yet, a potlatch user joined completely different railways in a spot they don't connect, which seriously confused tags (mainline as a spur, and railways in identity crisis like Union Pacific lines being labelled as BNSF or vice-versa).

4) I'm surprised with as many tracks as there are in the White Rock/Blaine metroplex, I still had to fix names and insert border crossing gates, which are a major obstacle in that metroplex divided by stupid border placement. It wouldn't surprise me that it's twin just west, Point Roberts/Tsawassen suffers a similar plight, but I haven't been on the ground there in 10 years to know the actual lay...