heavens no I'm not that pedantic haha

note to the rest of OSM, I am not questioning the placement of the stoplight in the map only why it was done in the real world

Why Custer? Why not Sheridan? Oh WyDOT, you never cease to amuse me.

FYI I can get the rest of the "can't complete" ones in SD. Ran against most of them back in the day...

Also that open green field on the west side is the purple horse practice football field/discus area/only place to tie a tent to when it's windy, I added it back in

So this user is back at it again, and is making some rather odd edits (3-mile-long bridges, rural county roads as highway=track). I've commented on the changesets but have not received a response. There's additionally a jaxman005 account that was created to avoid the earlier block I think.

Hello! Out of curiosity, what justification is there for tagging 406th and 185th as highway=track? That tag has generally been reserved for two-track roads (like that section of 184th just south).

Hello! Thank you for your contributions! I've noticed that some of your edits are a bit unorthodox, e.g. personal identifying information shouldn't be mapped. Micromapping is all well and good, just don't put your neighbor's name on it. If you have any questions on how any of this works, I've been mapping in South Dakota since 2011 so feel free to reach out.

The wiki (osm.wiki/Main_Page) is also useful if you have questions about tags.

Miles

There's some other stuff I saw in the area while doing township stuff, think I can salvage it. My family homesteaded in Spink County so I kind of know the area.

probably should have added the French name of the James River in a different changeset, oh well

Update, iD didn't like me just using source either

"Line must have descriptive tags"

so I added a descriptive tag and then deleted it and it was okay with that

I've tried to document the SD oddities in the US boundary (or admin level, can't remember which one) page on the wiki

If you could add the "X is missing from OSM but is listed on the Census Bureau list of CDPs" ones that would be great... there's a couple out there that have name conflicts/SD-specific issues (Dakota Dunes is a CDP with an administrative boundary!).

Feel free to message me if things come up (it'll be easier to see than a changeset comment), there's a number of relations on the list that I either created or was the last editor on (some a long time ago when I didn't know what I was doing)

The issue was creating a boundary relation with untagged ways

I've had that pulled up as I've been going through the state, need to add some of the relations I've added to Wikidata

Basically the issue was I was seeing iD not let me save anything unless my ways in the boundary relation had a tag, I've been using boundary=administrative for that but moving forward I'll use the source tag

Once I have some free time (ha ha ha) I'll go back to the counties I've done boundary cleanup in and make that the standard way for tagging ways in boundary relations (at least in SD)

I think it was just warning about completely untagged ways that weren't part of a multipolygon relation, I went back and added the source tag to the way and that solved the problem

Should I not add "boundary=administrative, admin_level=whatever" to boundary ways when I'm updating them? The iD validator gets upset with me if the way isn't tagged

That's public access? I was always too nervous to check it out.

here's my first attempt, using the Chamberlain section as a guinea pig: osm.org/changeset/156538408

Makes sense, looks like it was added to the relations 4 years ago by someone in KC.

I'll do some digging and see if there's a good way to denote part-time fishing access rather than just yes or no.