If a tag needs to have multiple values, they should be separated with semicolons rather than slashes. Since edifice_height is an undocumented tag, it would be helpful to create a page on the OSM wiki explaining what it means. While it would be incorrect to delete it, it would clear up confusion for other mappers.

Thanks,
Allison P

One feature, one OSM element applies here.

You can edit other people's tags and delete them (OSM is a collaborative project after all), but don't delete them just because you don't understand them.

If you are testing, do not upload your data to OpenStreetMap. I recommend using JOSM and discouraging uploads.

Also, the changeset's bounding box is quite large and shows up when viewing edits in Belize, Timor Leste, and many other countries that weren't modified in the changeset.

In addition, your data was assumed to be an import. Undiscussed imports are reverted even if the data is good. Unsourced imports are also reverted because the other database may have an incompatible licence.

If you're using abbreviations, translate them into existing tags or make new ones that follow the usage of similar ones. If you cannot work with the data in that format, I would suggest using some other software. If you have information to add that is not in the database, add it to the existing tags for the volcano or if the volcano does not exist, create one.

Allison P

Also, in the future make sure you are tagging the way rather than a node in the way.

Hello gemstateroofing,

Thanks for contributing to OpenStreetMap. Ensure you are using standardised tagging and don't use description=* for advertising messages. If you have any questions, let me know.

Allison Pelton

Not just that, they have the wrong elevation too.

In order for the boundaries to work properly, there needs to be a relation containing all the ways with the boundary tag, name, and type=boundary. The way it's currently tagged is incompatible with many renderers. In addition, some of these boundaries are redundant because they follow county lines, national forests, etc.

Thank you for your contributions to OpenStreetMap. Please save your work by uploading the changeset before moving to a new area to avoid creating large changeset boundary boxes. This changeset covers a third of the Lower 48. It shows when looking at changesets in Wyoming, South Dakota, Iowa, and many other states even though changes were made in only Virginia and Washington. It makes it difficult to determine where edits have been made. If you have any questions, feel free to ask.

Highlands Elementary School is being renovated and the entire plot has been torn up, including the parking lot. This road no longer exists, and when the renovation is done the road will be located somewhere else. In addition, Mapbox Satellite imagery is out-of-date in Boise compared to the National Agricultural Imagery Program. NAIP imagery shows that the road has been torn up. I have removed the service road. Always ensure you are using the most recent imagery available when armchair mapping. Thank you!

This upgrade only applies to reservoirs mapped as ways or relations. Reservoirs as nodes (from the GNIS import) still have the outdated tags. This will make finding reservoirs that need to be mapped easier!

RapiD often believes long driveways to be residential roads. To be honest I don't use RapiD roads because they often have inaccurate classification and have too many nodes.

Congratulations on making node/6969696969

Just curious, should the reserve name be in title case? Right now some of the words are lowercased.

Thanks for the info! I used isolated_dwelling for places with only one or two households (farmhouses mostly) even if they previously had a larger population. If this isn't correct, let me know and I'll go back and retag them as hamlets.

Er... no. I kind of blanked out and added it to the road rather than the school. Feel free to remove it, or if not I'll remove it when I get the chance.

The most recent imagery available (National Agricultural Imagery Program) shows no such driveway exists, so I have removed it.

This looks like a building, shouldn't it have a building=yes tag?

Not sure how those made it through, good catch! I removed them. I double check all buildings with an odd number of nodes because they are often incorrect in some way, but some of these had an even number of nodes so I overlooked them.

I'd like to apologise for these. Many of them in the area seem to have been created by me. This is due to an issue I've had with JOSM that I have since fixed.

Sorry, not the MapWithAI GeoJSON plugin, the MapWithAI JOSM plugin.

This changeset specifically contained some overlapping buildings which I validated. I think I got them all but I'm not sure.

Several months ago I downloaded the building footprint GeoJSON for Idaho and attempted an upload but it was broken. Recently, I learned that RapiD added building footprints and I noticed they looked familiar. I compared them to the Bing footprints and realised they were the same! I have had great success using the MapWithAI GeoJSON plugin, and I would suggest giving it a look.

I found a program awhile ago that splits geoJSON files into smaller ones that can be loaded into JOSM but unfortunately it did so randomly and thus they were all over the place and any additions would have a bounding box covering all of Idaho.