Thanks for contributing to OSM! As a nearby resident I'm curious about this park. I cannot find evidence of this park existing, and when I last visited this location it was just a traffic island with grass. Is this an actual park, or just a lawn?

Thank you for contributing to OSM! Private driveways, even those leading to single family homes are considered acceptable to map on OpenStreetMap by most of the community. Can you explain why you deleted them? If the data was low quality, consider trying to improve the accuracy rather than removing it; usually low-resolution data is more desired than none at all.

Thank you,
Reid Pelton

I've noticed a similarly named account- @ISTC_GIS. It seems like both are in use. Using multiple accounts does not violate the rules, but I want to verify if both accounts are real. Is there anyone I can contact to verify this account?

Also, this changeset seems odd to me. I drive through this intersection often, and though my memory is not very good, I don't remember any construction happening here. Are you sure your data is up to date? Please correct me if I'm wrong.

Thanks,
Reid Pelton

Thanks for adding more tags. I cleaned them up a little bit and added a new feature, let me know if you have any questions or concerns.

Thanks for mapping this! When mapping these, add amenity=toilets as well, and don't give them a name unless they actually have one which they seldom do.

Looks pretty good! When adding names to roads, make sure not to abbreviate the direction or the suffix (always spell them out). Also, features without tags won't appear on the map, consider adding tags to features like node/6507430380. If you're not sure which tags to use, take a look at the wiki: osm.wiki. I hope this helps!

The name tag is not for describing a feature. Please leave it blank for features that don't have names, such as the swimming pools in this changeset or carports you have mapped previously. Thank you!

Well, I suppose it did have to come up at some point. Most of the details are accurate, but I do actually run editing sessions in tandem sometimes. I also am familiar with using JOSM, but I prefer iD most of the time because it's easier to use. My changesets took significantly longer than what people were saying; 30-60 seconds was the time it took for the changes to be uploaded and the changeset closed (as iD does automatically)

@DaveF, this changeset wasn't that quick. I opened up JOSM while working on this changeset to revert something else that I knew the validator couldn't fix.

iD is very inefficient; I'm not an expert coder but since changesets can't be saved in files I think it's stored in memory; but since sites can't directly do that the end result is JOSM barely slows down after making tens of thousands of changes and iD locks up after around 1000 on even the most high-end consumer computers. Thus many changesets are necessary for what can be done in one on JOSM.

This reverts an addition with its source listed as Google.

I'll go through the list manually from now on and fix other kinds of tags but leave the crossings be. I'm not usually an on the ground mapper because my area is very suburban and there's nothing useful to map here so I haven't really familiarised myself with the tagging for features that can only be determined from being on the ground or looking at 360 photos. My usual area is very inactive so I almost never get feedback on my edits.

One more thing: I didn't notice the validator changing crossings besides zebra, and I didn't even know there were different crossing types named after different animals. The problem is that they don't make any sense for most people in the US, since we have different names. I personally don't have separate names for each type of crossing, and I don't know of anyone who does. I think it's a bit questionable that this was included in iD if it's nowhere near agreed upon.

For sure! The validator catches so many different issues that this changeset was made in like five minutes, so I'm already saving pretty often, but it made my high-end PC start to freeze up, and others have expressed that it's difficult to see what changes have been made.

Yes, this was all from the validator. The validator automatically suggests changing crossing=zebra to crossing=marked and can do this completely automatically. It's possible the changeset tags for what issues were fixed is broken. Anyway, I didn't know about this controversy regarding certain tag changes, so I will turn off issues regarding "outdated" tags. Also, I don't think the tag crossing=zebra means much to Americans; I've only heard it being referred to as a marked crosswalk. I don't really see the difference or what data is being lost, but I'm not sure why iD would suggest that change. I'll make sure the validator avoids doing that in the future. The changes are automatic, too; I didn't see how they were different so at the time the tag change seemed fair to me.

Google Maps is not an acceptable source. This changeset has been reverted.

Haha, whoops. Good catch.

These roads are definitely not tracks. They are residential, even though some are unpaved. I'm reverting this changeset.

Thank you for adding this data! If you plan to add more street names, it is preferred practice to spell out the direction (South instead of S, West instead of W, etc.)

Nice

I must be really bad at mapping, you keep having to fix my ways. I honestly can't tell that I'm doing anything wrong.