South Dakota/Railroads

From OpenStreetMap Wiki
Jump to navigation Jump to search

Do we need to renew an API license or something? Andy, am I making a slippymap call I'm not allowed to do right now? Thanks for the tiles, I want to do the right thing.

Introduction

This is an evolving stub of South Dakota/Railroads.

Segments of railway=rail with similar tagging (especially name=* and usage=*) should be collected into a route=railway relation, developing these is an important "early task." (Subdivisions as relations makes them much easier to work with as single items. JOSM is a recommended editor as it has an excellent relation editing dialog window). For known active rail, this is largely done, but remains incomplete for Disused and Abandoned rail in the state. Primary focus now should be on TIGER Review of mainline, branch and industrial rail in South Dakota, the moderate amount of work required to improve these already-entered TIGER rail data and documenting in this wiki how we must and do improve them. Please update color-coding-status here as our map data get better!

Overpass Turbo (OT) queries can be useful as they geocode well, their bounds easily define as geographic names (like "South Dakota") and are easy to modify (e.g. change the value "disused" to "abandoned" or "BNSF" to "CP"). A few OT examples are sprinkled into this wiki where sensible.

Here is a link to the South Dakota Department of Transportation's official rail map. It is believed that both OSM and this wiki incorporate those data, however, they may not be fully recent or may update newer than what is in our map or what we document here. That official rail map states there are 1968.41 miles of (active?) railroad in South Dakota, 406.01 miles of state-owned active rail (May, 2018 data). Discrepancies between OSM data and the state official rail map are noted if/as they are discovered.

Editing Railroads starting from TIGER data

Like highways, railroad tracks have been imported from TIGER data and they share the same problems like unconnected segments, wrong tagging, missing bridges and railroad crossings and positions that are frequently off quite a lot. So a review is necessary as it is for highways. Please read WikiProject_United_States_railways#Editing_Railroads_starting_from_TIGER_data.

Active lines

Lines that see regular rail traffic whether freight, passenger, industrial, military, whatever. If they are active, they go here. If they are not, they are placed into the Disused or Abandoned sections below.

Burlington Northern Santa Fe Railway (BNSF)

A Class I major railroad in the USA. Here is an OT query, but it will match only BNSF railway with the exact value for its operator key of "BNSF" (none of the variations of spelling of that company now entered in OSM).

Main

Here is an OT query which returns South Dakota railways in OSM now tagged usage=main.

Subdivision Operator Relation Route TIGER Review Notes
BNSF Black Hills Subdivision BNSF relation 3793071 Edgemont - Wyoming Line - Newcastle, Wyoming - Osage, Wyoming - Upton, Wyoming - Moorcroft, Wyoming - Orin Subdivision (southwards) - Campbell Subdivision (northwards) - Gillette, Wyoming - Big Horn Subdivision (further westward) Done 34 km (21 miles) total in South Dakota, then meets Butte Subdivision in Edgemont. For disambiguation purposes, an exception to the rule "don't prefix Subdivision names with Operator," this has BNSF in front of its name because there is RCPE Black Hills Subdivision so close-by and almost parallel to this. (Between Edgemont and east of Hot Springs, the distance between the two same-named subdivisions is only 45 km / 28 miles).
Butte Subdivision BNSF relation 3793072 Edgemont - Nebraska Line - Crawford, Nebraska Needs TIGER Review 45 km (28 miles) total in South Dakota, then meets BNSF Black Hills Subdivision in Edgemont
Marshall Subdivision BNSF relation 7403179 Willmar, Minnesota - Granite Falls, Minnesota - Marshall, Minnesota - Pipestone, Minnesota - Minnesota Line - Garretson - Minnesota Line - Hills, Minnesota - Sioux Center, Iowa - Sioux City, Iowa Lightly TIGER Reviewed 20+ km (about 12 miles) total in South Dakota, then slips into Minnesota after serving Garretson both southerly and northerly

Branch

Here is an OT query to find usage=branch rail in South Dakota which may be helpful.

Subdivision Operator Relation Route TIGER Review Notes
Aberdeen Subdivision BNSF relation 2297177 Sioux City - Elk Point - Vermillion - Yankton - Napa Jct. - Mitchell - Wolsey - Redfield - Aberdeen Partially TIGER Reviewed 428 km long
Appleton Subdivision BNSF relation 2297178 Aberdeen - Summit - Milbank - Minnesota Line - Ortonville, Minnesota - Odessa, Minnesota - Appleton, Minnesota Moderately TIGER Reviewed
Canton Subdivision BNSF relation 2297179 Sioux Falls - Harrisburg - Canton Done The way the official state rail map colors this line, it appears BNSF is owner. The way the official state rail map labels this line, it appears the state is the owner and both BNSF and D&I have trackage rights / are operators. Perhaps this labelling implies the state is an operator? Please clarify if better data are known.
Corson Subdivision BNSF relation 2297181 Sioux Falls - Brandon - Garretson Barely TIGER Reviewed The south end continues 97.6 km SW to Yankton as an unnamed relation of abandoned rail.
Madison Subdivision BNSF relation 2297191 Sioux Falls - Crooks - Wentworth - Madison - Prairie Village / Lake Wentworth Needs TIGER Review The north end has a 1.2 km segment which did connect to Prairie Village, but appears to be accurately tagged as abandoned.
Mitchell Subdivision BNSF relation 2297193 Canton - Parker - Marion - Bridgewater - Emery - Alexandria - Mitchell Done The east end continues 27 km to "Kiwana's Trail," a 878 meter railtrail on the west side of Rock Valley, Iowa, then continues as abandoned (old_railway_operator=Milwaukee) ROW 37 km to Sheldon, Iowa (as an unnamed relation), where it connects to Worthington Subdivision northerly and CP line easterly.
Mobridge Subdivision BNSF relation 2297194 Aberdeen - Mobridge - McLaughlin - McIntosh - Lemmon - Hettinger, North Dakota Needs TIGER Review
Watertown Subdivision BNSF relation 2297199 Yale - Willow Lake - Watertown - South Shore - Minnesota Line - Bellingham, Minnesota - Appleton, Minnesota Mostly TIGER Reviewed RCPE has trackage rights between Huron and Yale (via owner State of South Dakota) and Yale and Watertown (via BNSF)

Industrial

Here is an OT query to find usage=industrial rail in South Dakota. It returns very limited results. There may be other rail (Short Line and/or Class III railways, spurs now without usage=* tags...) in the state which are best characterized with this tag. Place these in their proper railway company sections (including this one, BNSF's Industrial lines in South Dakota).

Canadian Pacific Railroad (CP)

CP is a historic Canadian Class I railroad which also operates in the USA. In South Dakota, CP partly operated through its subsidiaries Dakota, Minnesota and Eastern Railroad (DME) and Soo Line Railroad (SOO). In 2014, CP sold much of the western portion of its (Class II) subsidiary Dakota, Minnesota and Eastern Railroad (DME) to GNWR. These rail assets are now Rapid City Pierre and Eastern Railroad (RCPE), described in the next section. CP and RCPE interchange at Tracy, Minnesota.

Believed owned and operated by CP directly:

Subdivision Operator Relation Route TIGER Review Notes
Veblen Subdivision CP relation 2304646 Rosholt - north to Elbow Lake Subdivision west of Fairmount, North Dakota Needs TIGER Review The old_railway_operator=* was SOO. Only one member in the relation. The southern end connects to Sunflour Railroad at Rosholt.

Rapid City, Pierre & Eastern Railroad, Inc. (RCPE)

RCPE, a Class II railroad, is owned by Genesee & Wyoming (GNWR), a "railroad holding company." After purchasing the western end of its predecessor railroad, CP's Dakota, Minnesota and Eastern Railroad (DME) in 2014, RCPE owns or leases (through trackage rights) 577.56 miles (959.52 km) of rail in South Dakota, interchanging with BNSF in Wolsey and Crawford, Nebraska, with CP in Tracy, Minnesota and with UP in Mankato, Minnesota. It isn't clear if CP has trackage rights on portions of RCPE, or where, if any.

Main

Discussion has resulted in rail between Winona, Minnesota (a terminus of CP's DME) and Mankato, Minnesota (UP) upgrading from usage=branch to usage=main, though these four subdivisions are "borderline" mainline rail. As RCPE is Class II and these subdivisions are largely single-tracked and have weight restrictions, traffic amounts are "just enough" to consider them sufficiently mainline. A lack of any other significant east-west rail corridor in this (low population density) region was another factor which also helped promote these contiguous (over 500 miles) rails to mainline, especially as they nearly link other mainline rail.

Subdivision Operator Relation Route TIGER Review Notes
RCPE Black Hills Subdivision RCPE relation 3693887 Dakota Jct. near Chadron, Nebraska - Buffalo Gap - Rapid City - Blackhawk - Piedmont - Sturgis - Whitewood - Saint Onge - Belle Fourche - Wyoming Line - Colony, Wyoming Done At Rapid City, NW to northern terminus at Colony, Wyoming is largely usage=branch, becoming usage=industrial after a railway=switch at a small yard N of Belle Fourche's Wool Warehouse, as beyond that, serves only several large quarries. S from Rapid City to southern terminus Dakota Jct. (NW Nebraska) is tagged usage=main. Continuing SW on RCPE's Crawford Subdivision (20.5 miles / 33 km of usage=branch) connects to BNSF's mainline Butte Subdivision. An exception to "don't prefix Subdivision names with Operator," this has RCPE in front of its name to disambiguate from nearby and almost parallel BNSF Black Hills Subdivision. 282 km.
Huron Subdivision RCPE relation 8780810 Huron - Iriquois - De Smet - Lake Preston - Arlington - Brookings - Elkton - Minnesota Line - Verdi, Minnesota - Lake Benton, Minnesota - Tyler City, Minnesota - Tracy, Minnesota Barely TIGER Reviewed A significant east-west rail corridor across east-central South Dakota and southwestern Minnesota. Commodities include bentonite clay, cement, ethanol, fertilizer, grain. Interchange with CP in Tracy, Minnesota. RCPE enjoys trackage rights east from Tracy to Mankato, Minnesoto to interchange with UP. 222 km.
Pierre Subdivision RCPE relation 8780866 Huron - Wolsey - Blunt - Pierre Partially TIGER Reviewed A component of a significant east-west rail corridor in the region. Name and edge boundary data come from bts.gov data. 189 km.
PRC Subdivision RCPE relation 8780866 Pierre - Fort Pierre - Midland - Wall - Wasta - Rapid City Done An important component of an east-west corridor in the region. Assuming PRC stands for Pierre Rapid City. Name and edge boundary data come from bts.gov data. 269.5 km.

Branch

Subdivision Operator Relation Route TIGER Review Notes
Mansfield Subdivision RCPE relation 8778251 Mansfield west of Aberdeen Subdivision (which this closely parallels) southward about 45 km to Redfield Partially TIGER Reviewed Name and edge boundary data come from bts.gov data. RCPE owns this spur and also has trackage rights on BNSF's closely parallel tracks Aberdeen Subdivision. Abandoned rail continuing northwards from Mansfield connects to Northern State University campus in Aberdeen, not in this relation.
Onida Subdivision RCPE relation 8778051 Blunt - Onida Partially TIGER Reviewed Name and edge boundary data come from bts.gov data.
Yale Spur Subdivision RCPE relation 8780809 Huron (Yard) - Yale Only one element (the tight curve north of Huron Yard) needs TIGER Review Between Huron and Yale, owned by State of South Dakota, and RCPE is an operator. At Yale, meets Watertown Subdivision (BNSF, no interchange here, that's in Wolsey) where RCPE enjoys trackage rights to Watertown.

Short Lines

Often Class III (minor) USA railroads. These may be branch or industrial; this hasn't been fully sorted out yet. Here is an OT query to find usage=industrial rail in South Dakota. It returns very limited results. It is possible there is other rail in the state better characterized with this tag, rather than usage=branch. If there are "multiples," it may make structural sense to further place these into separate railway company tables and/or sections. (There don't seem that many of them here now). That could change these tables/sections substantially if many, usually short industrial spurs begin to be more accurately tagged in the map with usage=* and service=* and are added to/categorized in this wiki.

Branch

D&I Railroad (DAIR)

D&I operates three railroads in South Dakota (now tagged usage=branch). The name=* tags seem odd, but they are from the state official rail map. One (from Dell Rapids) is corporate-owned. To gain access to the other two railroads where it operates, D&I must use its trackage rights with BNSF on Canton Subdivision (and briefly, Mitchell Subdivision). The other two railroads are owned by the State of South Dakota, though D&I is an operator on them. (The state official rail map states a mileage total on these segments of "South Dakota Owned/D&I Operated" of 68.6 miles). D&I may also use segments of Aberdeen Subdivision south of Elk Point to gain access to Sioux City and the Missouri River. By the way, the name of the railroad does not stand for Dakota and Iowa Railroad (which might be considered a "nickname") rather the name is only "D&I Railroad."

Line Name Operator Relation Route TIGER Review Notes
P.O. D&I Railroad (DAIR) relation 8778092 Dell Rapids - Madison Subdivision (near Sioux Falls Regional Airport) Done D&I-owned segment. To gain access to other (southerly) segments where it operates, D&I uses BNSF trackage rights, chiefly on Canton Subdivision. North of Dell Rapids (to Trent and beyond at Sioux Junction) connects to various abandoned railways. The official state rail map says this segment is 16.8 miles, yet OSM totals these segments as 20.9 miles (33.7 km).
S.D. D&I Railroad (DAIR) relation 8778219 Canton - Fairview - Hudson - Hawarden, Iowa - Akron, Iowa - Westfield, Iowa - Elk Point Done Owned by State of South Dakota, D&I is an operator; duplicated below. The name given on South Dakota's official rail map is really "S. D."
S.D. D&I Railroad (DAIR) relation 8779539 Beresford - Alcester - Hawarden, Iowa Done Owned by State of South Dakota, D&I is an operator; duplicated above. The name given on South Dakota's official rail map is really "S. D."

Others (EE, SMRR, SNR)

Several other rail companies operate additional railways/railroads in South Dakota (now tagged usage=branch), unfortunately we don't have good name=* tags on some of them now.

Line Name Operator Relation Route TIGER Review Notes
BRRA (so tagged only on the relation, not is member elements) Ellis and Eastern Company (EE) relation 8777904 Sioux City - west to W. H. Lyons Fairgrounds / Fodness Pit Quarry - North La Mesa Drive Needs TIGER Review Owned by Sweetman Construction Company, hauls primarily aggregate products for Concrete Material Company in Corson. There are two gaps in the relation (one about 1.2 km, one < 50 meters) where EE uses BNSF's Corson Subdivision as a crossover to its own tracks. Eastern segments are believed under construction to better serve the former Minnesota Southern Railroad (MSWY) that EE acquired (and started operating?) in mid-2017. By rehabilitating this previously-MSWY line (abandoned by C&NW) to connect with Minnesota Southern at Manley, EE can use the route to interchange with UP at Worthington, Minnesota. The name "BRRA" comes from the state official rail map and its origin is unknown.
Sisseton Milbank Railroad Sisseton Milbank Railroad (SMRR) relation 8778485 Sisseton - Milbank Partially TIGER Reviewed A subsidiary of Twin Cities and Western Railroad, so tagging that value on owner=* is sensible. In a rare case of this being true, the railroad name appears to be the same as the operator, though these differ from the owner.
Sunflour Railroad (Is there a better name? This is the operator.) Sunflour Railroad (SNR) The single way is entered Rosholt - New Effington Needs TIGER Review About 10 miles. Eastern end at Rosholt connects to C&P Veblen Subdivision (SOO) north to Fairmount, North Dakota (Elbow Lake Subdivision). Westward from New Effington to Claire City (about 9 miles) is abandoned.

State of South Dakota Department of Transportation (DAIR, DSHI?, DSRC, DMVW, RCPE, SD?)

The state owns several rail segments, some are abandoned (as "railbanked," a legal definition that allows them to become railtrails), the rails in the table below are operated by rail companies. So, these are tagged owner=State of South Dakota. See also Canton Subdivision Notes in BNSF Branch section above.

Line Name Operator Relation Route TIGER Review Notes
Britton Spur Dakota Missouri Valley & Western (DMVW) relation 8794912 From DSRC branch south to Britton No TIGER tags Owned by State of South Dakota. Name is a guess.
Napa Junction to Platte Line DSHI? DSHL? relation 8779835 Napa Jct. - Platte No TIGER tags Owned by State of South Dakota. Official rail map says "DSHI" (DSHL?) is an operator from Napa Jct. to around Ravinia and/or Lake Andes, where a portion has become rail trail, but further west (to Platte) it is clearly abandoned. Also in Abandoned, Others sections, below and above. 54.5 miles (87.7 km) active rail (to Ravinia), 97.6 miles (157 km) inactive rail (Kadoka to Platte).
P.O. (How the state rail map names it!) Dakota Southern Railway (DSRC) relation 8778385 Mitchell - Chamberlain - Presho - Kadoka Largely TIGER Reviewed Tagged operator=DSRC. How far west is this "in use?" It had/has some segments tagged railway=disused west to Presho (with state of South Dakota's assertions, some were changed back to active rail, even as they might actually be disused). Better data on these segments / this disused boundary are appreciated. It most certainly is abandoned relation 8778383 from Kadoka further west to Rapid City. 190.9 miles (307.2 km).
S.D. (Is there a better name? This seems like an abbreviation for the owner.) Dakota Missouri Valley & Western (DMVW) relation 8778478 Aberdeen - Putney - Claremont - North Dakota line - Geneseo Jct. / Dakota Subdivision Largely TIGER Reviewed Tagged operator=DMVW. 76.71 miles (123.45 km).
S.D. (Is there a better name? This seems like an abbreviation for the owner.) D&I Railroad (DAIR) relation 8778219 Canton - Fairview - Hudson - Hawarden, Iowa - Akron, Iowa - Westfield, Iowa - Elk Point Done Tagged operator=D&I
S.D. (Is there a better name? This seems like an abbreviation for the owner.) D&I Railroad (DAIR) relation 8779539 Beresford - Alcester - Hawarden, Iowa Done Tagged operator=D&I. 68.6 miles (110.4 km), including the Canton to Elk Point segment with trackage rights on BNSF Canton Subdivision, of which this is a spur.
Yale Spur Subdivision RCPE relation 8780809 Huron (Yard) - Yale Only one element (the tight curve north of Huron Yard) needs TIGER Review Between Huron and Yale, owned by State of South Dakota, RCPE is an operator. 15.3 miles (24.6 km).

Industrial

The primary semantic of usage=industrial is to convey rail which serves mines, quarries and connecting similar heavy industry to other branch or mainline rail. However, in the USA, this tag is often (also) used on rail which "serves clusters of businesses engaged in light- or heavy-industry in urban industrial zones."

Passenger trains

Tracks and stations used for passenger train routes are correctly collected into route=train relations. A statewide OT query for passenger train routes currently (late 2018) returns empty results.

National (passenger=national) trains (none)

Unique in the continental 48 states, South Dakota has never had Amtrak® service.

Regional (passenger=regional) trains (none)

Presently, no "regional rail" (sometimes "intercity") exists in South Dakota, nor are there any known plans. These are middle-distance trains of 150 km to 1000 km; shorter than passenger=national rail but longer than passenger=suburban "commuter" trains, passenger=urban light-rail and passenger=local trams.

This is an interesting source with some maps and ideas for future passenger (regional?) rail in South Dakota from the perspective of service between Twin Cities/Minnesota and Milwaukee, Wisconsin and Denver, Colorado, with Sioux Falls being a hub of sorts.

Commuter (passenger=suburban), light rail (passenger=urban) trains, trams (passenger=local) (none)

South Dakota has no known rail systems serving suburban, urban and local passengers via full-sized "heavy rail" (commuter) trains, light rail and trams.

Heritage rail (BHCR)

South Dakota has two known heritage railroads: w:Black_Hills_Central_Railroad and w:Prairie_Village,_Herman_and_Milwaukee_Railroad. These are entered into OSM as ways tagged railway=preserved usage=tourism and relations tagged route=railway usage=tourism.

This first table contains route=railway relations.

Name Relation Route TIGER Review Status
Black Hills Central Railroad (BHCR) relation 8785256 Hill City - Keystone No TIGER tags A complete route=railway. Tracks are tagged usage=tourism, railway:preserved=yes and are standard gauge. About 15.4 km of track.
The Prairie Village, Herman & Milwaukee Railroad relation 8785255 Prairie Village, west of Madison No TIGER tags A complete route=railway. Tracks are tagged usage=tourism, railway:preserved=yes and are standard gauge. About 2.4 km of loop track, a simple spur and a turntable-fed yard near the museum.

This second table should contain route=train relations, yet none are known. Known destinations/stations and current online/printed schedules are useful sources as passenger rail routes and platform locations develop in OSM.

Route Trains Passenger Service Relation Status
Black Hills Central Railroad Needs "some" data about train routes here. No specific route=train relation(s) is/are known except State Train.svg trains are believed to operate between early May and early October. local Relation not defined yet Here, "local" means passenger=local is suggested on this 10 mile long route=train relation.
The Prairie Village, Herman & Milwaukee Railroad Please complete with Train #s, departure times, known schedules, seasonal closures, etc. State Train.svg Trains are believed to operate between May and September. Museum Loop Train Relation not defined yet No route=train relation; no schedules are known

In the USA, passenger=local is sometimes tagged on historic/heritage/museum/tourism/mining route=train relations. It is also is seen on, for example, airport-style railway=monorail or "People Mover" trains (often conductor-less / fully automated) linking airport terminals, rental car areas, long-term parking and correspondences with other transit networks.

Disused lines

Lines that don't have regular traffic but with all infrastructure in place. Tracks are tagged railway=disused.

The only military rail entered into OSM in South Dakota is "Ellsworth Spur" (name is speculative). Updates are welcome.

This is an early, stubby table only just getting started. It needs more population as there is a modest amount of disused rail in South Dakota. Very much under construction and only in its infancy here.

Here is an Overpass Turbo (OT) query which can be helpful.

Name Operator and/or old_railway_operator=* Relation Route TIGER Review Notes
Unknown May be BNSF, not sure The single way is entered Glenham off a siding off the Mobridge Subdivision TIGER Review required An initial stub entry into the Disused table
Ellsworth Spur US Government The single way is entered PRC Subdivision near Box Elder to Ellsworth AFB No TIGER tags Tagged railway=disused and usage=military.

Abandoned lines

Former railroad lines, whether still visible on the ground or not. A formal abandonment process with FRA has completed. Ways are tagged railway=abandoned or sometimes railway=razed if they have become completely built over in urban areas or are now, for example, farmland which has reverted to a more natural state with no evidence of tracks having been there. These should be historically determined or able to be so, but sometimes this is difficult because of lost history.

This is an early table only just getting started. It needs more population as there is quite a bit of rail history in South Dakota. Under construction.

Here is an Overpass Turbo (OT) query which can be helpful.

Name of Subdivision/Line and/or Operator (at abandonment) old_railway_operator=* Relation Route TIGER Review Notes
Abandoned Milwaukee Road Railway (needs better naming) Milwaukee Road Railway relation 8779834 SW of Scotland on Aberdeen Subdivision - Tyndal - Running Water No TIGER tags 48 km
C&NW (please rename here with the line, not the operator) C&NW The single way is entered Redfield - Faulkton - Gettysburg No TIGER tags 119.5 km
Kadoka to Rapid City Dakota Southern Railway relation 8778383 Rapid City - Kadoka No TIGER tags 156.6 km of ROW believed to be owned and maintained by SDDOT (State of South Dakota)
Name not known, connects to what is now Sunflour Railroad C&P; Soo Line The single way is entered West of Claire City - south to Minnewasta Lake No TIGER tags Traced from USGS topos. 80 km.
Napa Line Milwaukee Road Railway? relation 8779835 Napa Junction - Tabor - Tyndall - Ravinia - (it isn't clear how much is abandoned, how much is cycleway near here) near lake Andes - Geddes - Platte No TIGER tags Abandoned ROW owned by SDDOT, some apparently (Lake Andes) has become railtrail/highway=cycleway, though a tag on that way urges "check cycleway." 133.6 km. Some sources call this "Napa Junction to Platte Line."
Prairie Trail ROW? C&NW The single way is entered Aberdeen - Columbia - North Dakota line - south of Oakes, North Dakota where it joins the active Red River Valley and Western Railroad No TIGER tags ROW apparently makes up part of the Prairie Trail (railtrail) in Aberdeen. Needs to be turned into a relation as there is more to the railtrail than one single way.

Railtrails

A railtrail uses a former railroad right-of-way (ROW) for equestrian, bicycle or hiking paths, preserving the ROW for possible future re-use as a railway while providing a useful service in the meantime. These are often tagged highway=cycleway or highway=footway depending on whether they prefer or allow bicycle or pedestrian traffic. It is OK to tag both railway=abandoned and highway=cycleway if it is the case that an abandoned railway became a railtrail (for bicycle use, for example). Where a (multi-use) pathway is designated for pedestrians but also allows bicycles, tag highway=footway and bicycle=yes.

Clearly, this is an early Railtrails table. It needs more work and to be more fully statewide due to lack of local knowledge of South Dakota's railtrails. Work on/ entries from the Abandoned section above may allow discovery of a railtrail, so enter it here.

Name Relation Route TIGER Review Notes
George S. Mickelson Trail relation 2297255 Edgemont - Lead - Deadwood Mostly TIGER Reviewed A regional cycleway that also allows foot traffic. 112+ miles (>180 km) long.
Napa Junction to Platte Line The single way is entered Lake Andes No TIGER tags A tag urges "check cycleway" and this seems like more than the way should be included, please make a complete relation
Prairie Trail Only a single way is entered, but it appears longer, so please create a relation Aberdeen No TIGER tags Hard to tell from how it's mapped now: is this parallel to the abandoned tracks or actually on the old railroad bed?

Yards

It would be very kind for more OSM volunteers to build up this statewide "Yards" table (stub) with status on every single South Dakota rail yard. It is incomplete as there are a least a dozen rail yards in South Dakota. Here is an OT query to help get started.

Name Railroad(s) Area Subdivision(s) Served TIGER Review Status
Rapid City Rail Yard CP/RCPE, possibly others Rapid City RPC&E Black Hills Unknown Simply a stub entry
Yale Yard BNSF, RCPE (or interchange only in Wolsey?) Yale Yale Spur, Worthington Unknown Simply a stub entry

About (status) colors in TIGER Review, Route, Name columns

Green means that the route's (TIGER) data highly approach or are fully OSM-reviewed. This strongly implies other relation attributes are correct, but this isn't always strictly true; see Notes/Status column. Green does not conflict with active public_transport:version=* v1-v2 growth. Go!

Yellow means "only partially reviewed" ; additional volunteer work is needed to enter or correct additional route data (railway and/or train) into OSM. Yellow may also mean a route has a volunteer entering data, yet route ambiguities persist about what is actually correct. TIGER review is an early priority (do first or now), and tiger_reviewed=no tag should be deleted now when true or superseded by newer, better data.

Red means "something" (often very little) is known about the route (or yard), so it is useful to put a row in the table about it as a placeholder, but it is early in creating a route relation: route data attributes are unknown or significantly missing/incomplete and need work.