Thank you so much for your contributions to the schools in OSM! You requested a review and I noticed some tagging improvements that can be made:

- please avoid having areas and landuses like school grounds share nodes with buildings: the moment that someone wants to include a parking lot or additional building or sidewalk or fence in the school grounds, or adjust a building, or turn the school grounds/buildings into a relation, suddenly a bunch of unrelated stuff is glued together and it takes effort to messily unglue.

- somehow you seem to have parking_aisles and service roads partially overlapping, especially one case I can see north of the baseball field. parking_aisle isn't intended to be a way that overlaps anything else: to better achieve what you did would be to create two nodes inside of the service road, split the service road at each node, and then edit the service road in between those nodes to have the appropriate tags, instead of just drawing a new way on top of the existing one. however even that isn't right, because per the wiki parking_aisle is only intended for roads whose *only* purpose is to find a parking spot (like in big gridlike mall lots), not roads that people use to get in and out of an area that also have parking. the best way to represent a sort of alleyway with parking on one side is either a service_road split and tagged with "parking:lane:left=perpendicular" for the appropriate parts, or a service_road that enters into a "amenity=parking" area like you've done elsewhere. (people tend to overuse the driveway and parking_aisle tags: it's okay to have most entrances/exits to buildings just be plain service roads, nothing will break.) to fix the overlapping road piece, click on the parking_aisle nodes, choose Disconnect, move the parking_aisle out of the way and delete it, and then proceed to split/tag the service road as appropriate. (nodes and ways in OSM should generally not overlap or connect unless they are really two things that really overlap or connect. tons of validation errors happen when i.e. roads touch buildings or pass over water/barriers without an appropriate tags for the connection or bridge. the school grounds area sharing nodes with buildings would probably also show up as a warning.)

- go ahead and merge the Ridgway High School POI node with the School Grounds if you like. if there's one address for the entire school, go ahead and merge the address POI node with the grounds (or appropriate building, or building-relation) as well, though this is somewhat optional (it's just good to avoid duplication of i.e. objects named Ridgway High School, but since we did a local address POI import sometimes it's ok to just let those POIs hang out as long as, again, there's no duplication or omission.)

thanks again for your contributions! i highly suggest reviewing the wiki as much as possible, it's very informative.

On further review there are some other nitpicky bits to be aware of:

- opening_hours has a special format, instead of Monday – Friday (9:00 AM - 5:00 PM) you should enter Mo-Fr 09:00-17:00 in order for people's apps to be able to understand correctly. (Click on the (i) and View Documentation to see the wiki pages for tags you're unfamiliar with, the wiki is essential reading.)

- the format for phone is +17072368048 without hyphens or parenthesis

- description should only be a few words and not marketing-ese at all per the wiki. For example you can probably leave it blank, but if it's essential you could write something like "Digital marketing agency and coworking space." If people need any more info than that, that's what the website link is for.

It's important to fix all the issues I've mentioned or they'll be fixed for you: apps have a hard time with nonstandard tag formats, and long descriptions can really clutter up the view in some apps. (Just imagine if Google Maps had a full paragraph describing the menu, overlaid on top of every Taco Bell in the country. It'd be unusable.)

Thanks again!

Hi there thanks for your contribution! A few questions or tips:

- am I able to walk into your front door and pay you to use a computer or wifi for a few hours? If so, your website might want to reflect that, and if not then you're not an internet_cafe. Probably you're a office=advertising_agency .
- for addr:unit, you just want the identifier and not the name. So addr:unit=18, without the word "Suite."

Thanks again and as internet marketers please remember to keep all edits useful to map users and don't try to flood your edits with keywords for SEO. If Google Maps or Wikipedia would consider an edit to be spammy, OSM will too. Just the facts, no lengthy editorializing :) thanks again!

Hi there! Yes to my knowledge this hotel is now open for business (especially given that you have a phone number for it now) -- when I tagged it as construction many months ago it was barely built. Obviously it will require some local knowledge or viewing the company website to really make a good determination, but OpenStreetMap should always reflect the visible on-the-ground reality as much as possible.

You did nothing wrong besides removing the building tag from the building. I just additionally made some changes to this area so that it is as accurate as I can make it.

Thank you for your contributions!

Hi Riyana and thanks for the contribution, however it's important not to remove the building tag from buildings. Also, since the construction is completed, we can remove the construction landuse. Finally I did some cleanup to remove the duplicate POI and move the 210 5th St address POI outside of the hotel which has a new address. You can see my changes here: changeset/102947025

Hi there thanks for your contribution! Please consider mapping all buildings on a property OR mapping the boundary of the property for use in a future relation. Many apartments, hotels and motels consist of multiple buildings and so function more like a campus than a single point or structure.

Hi there, thank you for your contributions! FYI according to the wiki the parking_aisle tag should be reserved for service roads that are only used to park in (like the gridlike aisles in front of grocery stores) and not used for service roads that are the main way of getting into or out of a parking lot or business. In other words, a parking aisle should probably never intersect with a street or be present outside of a parking lot.

No biggie just thought I'd share. Thanks again!

No prob! I'll try to wrap this up within 30 days, please to feel free to reach out when you have energy again. I'm always happy to collaborate or help with other local mappers!

Let me know ~12hrs before you make significant changes, I'm in the middle of almost executing this import (you can review my .OSM files for an idea of what's about to be imported, namely the items in the clean folder) https://github.com/zyphlar/sonoma-import/tree/main/out -- my thinking is that either before or after the sonoma import, we do a pass to conflate your address points with building addresses... which should probably be done automatically somehow, but with great care to i.e. merge house addresses but keep the individual address points in strip malls that are valuable. I'm happy to coordinateor work together!

Oh and always happy to have another local mapper!

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.