Hi there, is it really standardized to create nodes in the middle of crosswalks for kerbs as with node 8964643061? I've more often seen this information on the crossing node or the crosswalk way.

Hey there! I'm interested in completing this data to give more coverage in the area, do you still have the original building and address info handy?

Oh nice lol I think I probably talked to the same people as you. I actually called WW and then Pomeroy, and there's a Heritage/archaeologist guy at Pomeroy who said he'll check with someone who handles naming. At the very least we want accurate names for things as well, or perhaps if it's a dispersed camping opportunity, like we'd want to have the correct "Skyline Springs Campground" road name or whatever it is, etc.

Thanks for all your work with this!

Yeah I was trying to figure out which area of their website referenced this campground but couldn't make heads or tails of it, I figured since you created it you might have a slightly better clue than me https://www.fs.usda.gov/activity/umatilla/recreation/camping-cabins/?recid=56399&actid=29

Hi there! The campsite at node 5796588469 seems to be named after a spring whose name has changed. Do you know who's in charge of naming the campsite to see if it's changed as well?

Hey there thanks for this contribution however there was already a node for this feature when you added the line (10017047729), and it seems like a node (coordinates sourced from USGS) may be more appropriate than a line (topo maps suggest the basin is not linear, and doesn't really extend north-south in this area.)

Thanks for your fixes! I've made some further tweaks in changeset 126713932. I like using osmcha to view changes, it might be useful for you: https://osmcha.org/changesets/126713932/

I've left judgment calls like way 1098323697 and 828423084 as you mapped them just to not impose my viewpoint on everything, but I would personally map them as service roads as well. (Yes they're technically only accessed for parking in a lot, but it'd be real easy for them to be used just to get in and out of the business/lot.) As you can see I've modified ways 1098323700 and 1098323695: it's going to be hard to get in/out/around these businesses/lots without using those routes; many "parking aisles" serve a dual purpose of getting people in/out/around the lot and we call those service roads in OSM's funky syntax. Way 852641139 hardly has any parking spaces, it's very much used for getting to/from the business. Way 181513335 is only really a driveway for the parts that loop around the backside, but even then it's totally fine to leave it as a service road. Don't be afraid of just leaving every unnamed place where cars go as service roads, there's nothing wrong with that.

We don't really need to subdivide sections of asphalt down to the foot as to what's what: the main goal here is to allow maps to look good (renderers can choose which parts to show in order to balance visual clutter) and to route GPS apps appropriately (some basic apps may choose to ignore parking aisle routing entirely, or at least reduce their routing priority, to produce more sane routing more quickly.)

Here's the wiki page on parking aisles for your reference. Again don't worry, I redid parking lots about a dozen times before I figured out what the standard was. osm.wiki/Tag:service%3Dparking_aisle#Disambiguation

Hey there thanks for your contributions! FYI parking aisles are confusing tags. They should only be used for the minor gridlike rows of parking spots in a large lot and not for the main ways in/out/around the lot. Basically you should be able to get to the front door of where you need to go using only service roads.
---

Published using OSMCha: https://osmcha.org/changesets/126704153

The shortest answer to your question, as far as I know, is that you should probably query for natural=coastline and then join the coastlines together (maybe with a few extra fake lines added to your renderer afterwards just to make it work) to create oceanic polygons.

Separately, the waterway to the West is a relation of coastlines: osm.org/relation/2389633 if we really wanted to make areas for the East River, Bowery Bay, etc, we can do so by adding the coastlines to a new relation with a couple inserted lines here and there to separate them out and close them, but it's probably not necessary.

We have a rule, don't tag for the renderer: if the map objects represent reality then the renderer should generally figure out how to process/display that. (We can't reasonably create a relation of every single coastline to form an ocean, and there is some OSM consensus about where to distinguish the mouth of a river versus the bays and ocean it goes into.)

See here for more: osm.wiki/Coastline

Good morning to you, too, America!

As you can see in my changeset https://overpass-api.de/achavi/?changeset=126155487&relations=true I also connected the service road to the building and marked it as a parking garage entrance. Thanks again!
---

Published using OSMCha: https://osmcha.org/changesets/126152100

Hi there thank you for your submissions! FYI the parking aisle tag is only for those parts of a large parking lot where you only access them because you're trying to find a parking space. Major routes in/out/through a parking lot are simply plain service roads. I'll make this fix and thanks again!
---

Published using OSMCha: https://osmcha.org/changesets/126152100

Way (33162264) should probably not have its own tags as an inner member of a relation

Tkbonesdir, way #817955240 and its new connected way #1093503220 are marked as golf cart = no however I wonder if they should be?

Hey there thanks for contributing! Do you know what this feature is, is it a gas station? I updated the tagging because layer=-1 generally means underground and what we normally do for drive-thrus is make the building a roof and all roads a tunnel, maybe with the roof at layer 1. Having the roads split their nodes merged at the edge of the building also helps validators freak out a bit less. Cheers!
---

Published using OSMCha: https://osmcha.org/changesets/125769336

Hi there! Your fix of the building name looks good but your edit of node 8454667838 giving it the name of the building appears wrong because node 8454667838 is the address of a specific floor and door inside the building. I think the building's "house name" of being a courthouse should be good enough and we don't need additional tags about the fact that it's a courthouse with a name.
---

Published using OSMCha: https://osmcha.org/changesets/125764968

Looks good to me! You can probably consolidate the 5330 address tags onto just the building, and if there are unit numbers you can copy paste the address and add the unit to whatever's inside. If the name of the building doesn't actually include "Book Shoppe and Coffee" you can omit that as well since the book shop is well represented on its own. Finally if the building is a church or office or retail type amenity you can add that tag as well besides just having a generic building with a name.

Cheers!

Looks good to me! Thanks for contributing.

Looks good to me! You can add the warehouse to the north to make the building more L shaped if you want, but I see no problems here. You seem to know what you're doing, no need to request review of every change.

Hi Bridget, please do not undo changes without talking about it. The description and image tags you're using are spammy and won't help anything, and the "categoery=psychic" tag will do nothing for you: not only is it misspelled, it's also just not an openstreetmap tag. I want your business to show up for customers just as much as you do, and that's why I changed it the way I did. Please look at wiki.openstreetmap.org for guidelines on how to tag things and other rules that editors must adhere to.