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.

Some of the buildings are overlapping existing ones, think you could double check those? Also, MapWithAI building outlines are the same as Bing, and it automatically removes buildings that are already mapped as well as adds a source tag to the buildings. Just thought this might be informative if you decide to continue mapping buildings. In addition, imports should be discussed with the community beforehand. If you manually review the data before uploading, no prior approval is required.

Allison P

I did not create the feature, but blind validation (when iD did the fixes for you instead of requiring user review) caused me to update the tags without realising. I've removed it. Good eye. I also try to specify when I'm using the iD validator nowadays. Let me know if you have further questions.

After doing some background research, a lot of buildings on the base were demolished, especially houses. I've removed those houses and streets.

Hi mapman44,

As you can see Bing imagery was used to check the buildings. I only discovered after submitting the changeset that there was higher resolution and newer imagery available. I will use this better imagery to review the building footprint accuracy within the next few days and make refinements. Thanks for the info.

Hi Alhamdulillah,

I would not classify this as an import. I am downloading building footprint data from MapWithAI, manually reviewing it, and fixing it to the best of my ability if inaccurate, then uploading the data.

Allison P

Perhaps name=The Church In Boise and official_name=The church in Boise? Or vice versa? I'm not sure. Capitalised looks better on the renderer but I don't want to tag for the renderer.

No worries! It's a very common error because iD seems to try to connect roads to boundaries before other roads. I made that mistake a few times while learning to edit. It can frequently be useful to open the map data menu and scroll down and disable boundaries so that you can't interact with them.

This seems to have fixed the rendering error.