I typed out a whole nice comment and my phone erased it so here's the short and sweet version:

- definitely import guidelines, it's easy to cause mass havoc
- this looks high quality minus the duplication between building addresses and new address POIs
- my import will probably need to just ignore anything in city limits, or anything with an existing address POI nearby, though if we want to be fancy we could conflate your address POIs and buildings automatically as a first step
- do you have written authorization that this is public domain data? I've been chatting with Mike and Matt at the city and just didn't get that far

Heya are you interested in working on local address/building imports? It looks like you beat me to the punch (and maybe did an import against OSM guidelines, not that I'm mad about it), I'm in the middle of a county-wide import myself: https://github.com/zyphlar/sonoma-import

Hi @mueschel @rivermont and @catjam I just noticed these issues and am probably one of the more active local mappers. As far as I know, California government data is in the public domain (and I'm in the process of verifying this and doing an authorized and proper import of county buildings/addresses) so I'm not too worried about licensing, but I do want the data to be clean, accurate, and easily updateable. What's the recommended thing to do in this case, simply remove all the foreign tags?

I'm happy to do this myself but want to check that we don't remove data that is useful i.e. for linking future updates, or for describing the nature of the boundary/feature. For example, LAYER=LAGUNA could be useful in that it describes a section of unincorporated land surrounded by city, and that land is referred to as Laguna De Santa Rosa land (a nature reserve not owned by the city.) Perhaps useful LAYER data like that could be moved to a description (or name if there's no duplicate-named way/node) and the rest of the GIS data like objectid/shape/create/edit removed? How are admin boundary imports typically handled/validated/conflated, just manually?

Thanks for noticing this, I dug and found this previous discussion and will comment on it to hopefully improve the local data changeset/76180011

Careful of removing all useful tags and leaving random untagged ways laying around. I know you're highly motivated to prevent people from using these footpaths but the appropriate tag for a traveling path that exists in the world but is illegal to use is highway=* access=no -- otherwise it's basically just bad data that could be rivers or buildings or park boundaries or anything. Also thank you for not deleting them: they exist, whether or not we agree with them. Finally remember that adventurous hikers will tend to go wherever a path appears, GPS or not. All we can do is discourage and inform. (Consider that state park staff may also use these trails for maintenance and may want this map to be complete for their own private authorized purposes including prevention of unauthorized trails.)

Finally it seems you're saving your changes after every single edit. You can make multiple changes per save if you want!

Thanks for your enthusiasm in mapping our city and keeping the environment safe.

TODO: remove conditional tag in October 2020

firstly the name is not in uppercase except in government data. you probably want Whipple not WHIPPLE.

also the excel data source says "W. of Rte. 101 at S.W. quad of Veterans Blvd./Whipple Ave." which is odd because that would be the other side of the street from here and the quadrants are N/W/S/E not NW/SE/SW/NE.

finally the government data says the P&R is at 37.4877962,-122.2430472 which is a few blocks away. very confusing, should be verified with street level imagery maybe.

why remove the "Santa Clara Valley Transportation Authority" tag? seems still accurate. if you're going to edit entire regions' park and rides at once please consider doing it all in one big changeset or stick to one area at a time. reviewing changesets with two edits and bounding boxes hundreds of miles across is tiring.

looks ok

"rohnert park and ride" is incorrect, the name of the city is rohnert park and the place is a park and ride. duplicated "rohnert park park and ride" is preferred.

making tiny edits to geometry across hundreds of miles is not recommended. i'm sure you can contribute in much more useful ways, for example adding building addresses or local business names.

looks ok! minor edits to make stuff match the satellite aren't super important but your contrbutions are appreciated. one tip is avoid making many edits over a wide area in one changeset if you can avoid it, since it will draw changeset boxes across entire cities and no one editor will have local knowledge of all those areas.

Hi Cordelia! Can you clarify this intermittent stream that starts near the athletic field, goes through a building and ends up in the front lawn? Does it really flow towards the lawn? Does it go anywhere? Is it underground where it goes through the building? Is it just for helping students get water Pokemon? I don't have a Magikarp in this fight, just trying to clean up things that don't make sense (like a stream flowing into a lawn)

(i should mention the opposite is also true: a parking lot without any roads going into it is flagged as weird. as you can see just south of your property, the most minimal parking situation is often a service road going into a parking lot area.)

looks great! the very last thing is that a parking aisle that isn't inside a parking lot is often flagged as weird, so consider drawing some boxes around the areas of your business where parking spaces can be found, and tagging them as parking lots. details such as customer/public/private access, fees, # of spaces/handicap, etc, can also be added as desired.
thanks for your contribution!

review:
hi there! looks pretty good. FYI parking aisles should *only* be the in-between aisles of a large lot that are only used to find a parking space, and driveways should generally be a stand-alone thing going right up to a building like at your house, or perhaps a loading dock.

to be most accurate, i believe the recommended way is to tag everything used for getting in and out of the parking lot as a service road. you can leave the back-and-forth in-between rows as parking_aisles.

review: looks okay, however please try to edit existing objects instead of deleting and recreating. history is lost when things are deleted.

review: looks fine!

Review: looks fine! I notice a plaque on this building, if it has a name or is unique in some way feel free to add that info using the name or description tags.

@Adamant1: thanks I've been learning more about the proper way to tag things and went through a spat where I thought lots of POIs was a good idea. In this case I probably knew there was a business here but not what the exact name was, so my goal was to use it as a placeholder that an app like streetcomplete could fill in the details of. But the reality seems to be somewhat different so I plan to change these as appropriate when I have time.