Oops, that was an accident. I’ve restored it. Thanks for the catch.

Thanks for the head up. I admit, I found the wiki was a little confusing (or inconsistent) around these points.

I'm super busy for a few days, so I probably won't be able to get to it before the weekend at the earliest.

If you want to jump in before then, please feel free.

Congratulations! ✊

Whoops. I can see how a multipolygon with holes might let something slip through the workflow, but in this case I think the JOSM validator caught it, and I missed the warning. I'll clean it up and double check for other any other duplicates.

It is an import. The process is documented here: osm.wiki/Portland,_OR_Bldg_import and here: https://github.com/pdxosgeo/pdxbldgimport

Sometimes there are imperfections in the source data, and there's also the possibility that we screwed something up in processing it for OSM.

Do you have a few specific examples? We can trace it back to the source data and make sure we don't have systemic problem, or that if we do, we can fix it.

Feel free to send me a note via the OSM mail, or even better, before just fixing something, if you have a github account, you can open an issue and we can get more eyeballs on it to verify.

Either way, if you let us know about issues, we have a whole group of people who are dedicated to making this go well.

HI Timothy,

I noticed you made a few comments on fixing garages, or "fixing bad building imports"

We've done a lot of work to try to assure the import goes correctly.

could you share with me what's you're seeing, we may be able to fix it.