I don't plan on adding it back, but it's clearly visible in imagery (including the access ramp from the main road), so someone will add it back eventually, and that person might not add "access=no", making it even more dangerous than if you hadn't deleted it.

But you deleted a service road, which does exist.

Just because a crossing is illegal doesn't mean it shouldn't be in OSM. access=no is enough. Removing it entirely means that the map is now inaccurate, and someone is going to add it back anyway.

The tasking manager project with instructions is here: https://tasks.openstreetmap.us/project/175 We organize OSM editing in the South bay as part of the Code for San Jose meetup at https://www.meetup.com/code-for-san-jose . The next meeting isn't until January, but we also have a Slack workspace at https://bit.ly/3f78NML where I and others would be happy to answer any questions.

Hi, thanks for your contribution! I'm working on an import of all San Jose buildings. It may be faster than tracing them yourself, so let me know if you'd like to help with that!

Did you mean to rename the road?

I guess I don't live there so I can't confirm, but I changed the tags the way I did because a park with "Planned" in the name seems like it shouldn't be open (and a park still under construction shouldn't have leisure=park); and it doesn't appear from imagery that the entire tower site is itself a building (nothing but actual building footprints should have building=yes; perhaps building=no would be better). Additionally, having *both* tags that something is proposed *and* active is just confusing.

Welcome to OSM, and thanks for your contribution! It looks like you've added a name and description to a part of a road. Normally schools are saved as areas around the school grounds. There should be a button in the editor labeled "area" that lets you draw the boundary, and it should ask you what type of area it is (a school). Or if you don't know the boundary, you can use the "point" button to give the school a general location. I'll give you the chance to fix it yourself, or I can fix it for you if you want. Finally, there's a button under "help" on the right to start an automatic tutorial, if you want to get more familiar with these concepts. Thanks again, and let me know if you have other questions!

Sorry for the big bounding box. This undoes suspicious changes from a MR challenge that I created. I consulted with the user who made the changes before doing this revert. This revert, as with the original changes, should only affect tags, not placement. The reverted changeset numbers are: 87877632, 87877634, 87877639, 87877647, 87877648, 87877650, 87877652, 87877653, 87877654, 87877655, 87877659, 87877661, 87877664, 87877667, 87877687, 87877693, 87877694, 87877698, 87877703, 87877707, 87877708, 87877711, 87877715, 87877719, 87877722, 87877730, 87877731, 87877733, 87877736, 87877738, 87877745, 87877752, 87877755, 87877757, 87877760, 87877763, 87877764, 87877765, 87877767, 87877768, 87877773, 87877774, 87877776, 87877780, 87877782, 87877789, 87877792, 87877795, 87877797, 87877798, 87877799, 87877803, 87877807, 87877812, 87877814, 87877815, 87877822, 87877834, 87877836, 87877842, 87877843, 87877844, 87877846, 87877850, 87877853, 87877854, 87877861, 87877864, 87877865, 87877866, 87877867, 87877872, 87877878, 87877883, 87877886, 87877888, 87877891, 87877892, 87877897, 87877899, 87877906, 87877910, 87877913, 87877921, 87877924, 87877929, 87877934, 87877939, 87877941, 87877944, 87877953, 87877954, 87877955, 87876296, 87876336, 87876347, 87876355, 87876380, 87876395, 87876396, 87876398, 87876401, 87876403, 87876406, 87876424, 87876429, 87876431, 87876434, 87876453, 87876458, 87876461, 87876470, 87876472, 87876476, 87876482, 87876486, 87876488, 87876489, 87876493, 87876494, 87876499, 87876503, 87876510, 87876515, 87876541, 87876544, 87876548, 87876549, 87876561, 87876563, 87876565, 87876569, 87876570, 87876572, 87876574, 87876577, 87876579, 87876581, 87876582, 87876593, 87876596, 87876597, 87876604, 87876607, 87876611, 87876621, 87876626, 87876628, 87876631, 87876636, 87876646, 87876653, 87876655, 87876658, 87876659, 87876661, 87876663, 87876665, 87876673, 87876683, 87876684, 87876699, 87876704, 87876705, 87876706, 87876707, 87876711, 87876714, 87876715, 87876716, 87876718, 87876720, 87876721, 87876725, 87876726, 87876727, 87876729, 87876731, 87876736, 87876737, 87876738, 87876739, 87876744, 87876751, 87876753, 87876755, 87876757, 87876759, 87876762, 87876768, 87876770, 87876774, 87876776, 87876803, 87876808, 87876811, 87876813, 87876819, 87876821, 87876823, 87876832, 87876835, 87876845, 87876847, 87876848, 87876857, 87876859, 87876860, 87876863, 87876867, 87876871, 87876872, 87876873, 87876874, 87876876, 87876880, 87876881, 87876887, 87876889, 87876892, 87876893, 87876901, 87876903, 87876910, 87876912, 87876922, 87876924, 87876928, 87876932, 87876934, 87876939, 87876943, 87876944, 87876945, 87876948, 87876949, 87876951, 87876954, 87876955, 87876960, 87876963, 87876968, 87876986, 87876988, 87876990, 87876995, 87876999, 87877004, 87877006, 87877007, 87877008, 87877011, 87877017, 87877020, 87877024, 87877031, 87877036, 87877043, 87877049, 87877056, 87877060, 87877068, 87877073, 87877075, 87877081, 87877089, 87877090, 87877094, 87877097, 87877100, 87877103, 87877104, 87877106, 87877111, 87877113, 87877114, 87877115, 87877116, 87877120, 87877122, 87877124, 87877128, 87877129, 87877136, 87877137, 87877140, 87877147, 87877148, 87877153, 87877157, 87877168, 87877170, 87877177, 87877180, 87877183, 87877188, 87877198, 87877202, 87877205, 87877212, 87877237, 87877245, 87877247, 87877253, 87877258, 87877263, 87877265, 87877268, 87877270, 87877278, 87877284, 87877285, 87877286, 87877291, 87877292, 87877293, 87877299, 87877301, 87877310, 87877313, 87877315, 87877316, 87877317, 87877319, 87877322, 87877329, 87877330, 87877334, 87877335, 87877339, 87877342, 87877352, 87877353, 87877354, 87877357, 87877361, 87877364, 87877371, 87877374, 87877380, 87877383, 87877387, 87877389, 87877390, 87877392, 87877393, 87877403, 87877415, 87877424, 87877425, 87877430, 87877435, 87877436, 87877438, 87877446, 87877456, 87877459, 87877460, 87877463, 87877468, 87877472, 87877478, 87877479, 87877481, 87877484, 87877491, 87877493, 87877499, 87877517, 87877525, 87877526, 87877534, 87877535, 87877537, 87877544, 87877552, 87877553, 87877557, 87877558, 87877563, 87877566, 87877569, 87877575, 87877587, 87877592, 87877598, 87877602, 87877603, 87877604, 87877605, 87877607, 87877624, and 87877631.

The John Lynch linked in Wikidata doesn't have a middle name with F, and was from Virginia, not Kansas.

The John Jones linked in Wikidata doesn't have a middle name listed. Since this is next to John Adams Court, it seems more likely to be named after the Revolutionary War commander.

This Jim Williams is more likely one of the sports athletes than the militia leader.

John Nicholas Brown is not John Brown the abolitionist.

This would seem more likely to have been named after John E. Rankin, US Representative from Mississippi, than the abolitionist from Ohio.

This is clearly incorrect. The Wikidata link is for a John Cook, but this hospital is for a John Stroger.

This doesn't seem right. The John Brown in Wikidata does not have a W middle initial.

The MapRoulette challenge you appear to be using (https://maproulette.org/challenge/3199) is specifically for mapping crossings as ways. If it is not your policy to map crossings as ways, please do not mark tasks in this challenge. Thanks.

Thanks for your contribution! Adding a crossing node is helpful, but this MapRoulette task is really to add ways that connect the opposite sidewalks. Can you do that as well please?

There's already a (misplaced) crossing way across Dana/Burell by West Hedding. It would be helpful if you moved misplaced items instead of just adding new ones. Thanks!

Other countries have a convention to offset address nodes that are on different floors. Just because Nomanatim can't find addresses with unit numbers doesn't mean it isn't valuable information; another search engine could fix that. I still think worrying about how the information is displayed in Carto is wrong: a better renderer could be smarter about placement or visibility. But if you know that the locations are actually incorrect, then that's okay.