The same can be said for almost every street in the US, spelling out street names is just one of OSM's conventions. This allows for data consumers such as renderers and routers to choose whether or not to abbreviate them.

Hi,
Thanks for adding these addresses. Please note however that we don't abbreviate street names in OSM, including directional prefixes (see osm.wiki/abbreviation)

amenity=hospital should only be used for hospital grounds, I would use building=hospital for the buildings

Hi and welcome to OpenStreetMap! Thanks for mapping these houses/addresses. Quick tip: you can square corners of a building by pressing 'q' when selecting it.

Hi and welcome to OpenStreetMap! Thanks for mapping these houses. Please note however that the name field isn't used to describe features in OSM (see osm.wiki/Names#Names_are_not_for_descriptions).

Just because it doesn't exist on USGS doesn't mean this isn't a real place name. West Hazel Dell is one of the neighborhood associations in Clark County, all of which were imported from CCGIS.

In OSM, we only map current features, not places from 1956. If you're interested in mapping historical places like these, I recommend taking a look at https://openhistoricalmap.org/

As noted on the OSM Wiki, `place=locality` is used in OSM for named places without a population, which Happy Valley definitely is not. (osm.wiki/Tag:place%3Dlocality)

Hi,

I noticed you changed Camas from a town to a suburb.

As noted on the OSM Wiki "OSM's usage of 'suburb' is different than that used by North American English, where a suburb is "an area, often residential, outside of a central city". Often these suburbs are distinct settlements and will be tagged as place=village, place=town, or place=city, depending on factors such as population."
(osm.wiki/Tag:place%3Dsuburb)

In other words, incorporated places like Camas should be classified as a city/town/village in OSM whilst suburb/quarter/neighborhood are used for neighborhoods within these incorporated places or unincorporated places such as CDPs.

Please note we cannot use Google or any other copyrighted sources as a source in OSM, see osm.wiki/FAQ#Why_don't_you_just_use_Google_Maps/whoever_for_your_data?

Hi,
What is your reasoning for moving the place node for Beaverton and changing it from city to town? As mentioned on the wiki (osm.wiki/Tag:place=city), city/town nodes should be placed at the 'center' of the city. I believe the previous location at the center of old town or city hall would be more appropriate than the middle of the 217 auxiliary lane.

In OSM, towns (osm.wiki/Tag:place=town) are considered to be larger than villages, but smaller than cities. While there isn't a set cutoff for what is considered a city or town, in the Portland metro area incorporated places with 50K or more people are typically tagged as cities while those less are tagged as towns and villages.

Hi,
Just curious what source you used for the airport terminals you added near the fire station (ie osm.org/way/1250050984). Based on Bing imagery, this seems to just be the place where modular pieces of the new terminal roof are constructed before being transported over to the main terminal.

Hi,
It looks like you're upgrading minor residential roads with centerlines to tertiary. While this was historically how these were tagged in the US, the community has recently started shifting away from using just physical characteristics and prioritizing connectivity when determining highway classifications (osm.wiki/United_States/Highway_classification).

Instead, I recommend using lane_markings=yes to show that these roads have centerlines (osm.wiki/Key:lane_markings)

For multipolygons such as this track (osm.org/relation/7724479), the tags should only be on the relation itself and not on the member ways.

Also I highly doubt that a public school in California would be religious

Please note that only buildings should be tagged with building=*. Since this are is encompassing the entire school grounds, just amenity=school is sufficient

Hi,
Thanks for realigning these roads! In the future, I recommend using the 'Oregon DOGAMI Lidar' background layer to align wooded roads/trails like these. Also, please note that we don't use the name field to describe attributes of a feature like access restrictions. Instead an access tag should be used:
osm.wiki/access

I believe Magnolia being secondary here makes more sense as it's important to distinguish Magnolia from other surrounding primary roads such as Beach and Brookhurst. Those streets get a lot more traffic, which is evident by how they have three or even four lanes in each direction as opposed to just two.

While functional classification maps are a good start to identify what highway classifications roads should be, I would avoid following them one hundred percent of the time. A lot of the times functional classifications are based on previously planned projects that were never completed. For example, Gilbert from La Palma to Orangethorpe was likely classified as a minor arterial because of a planned overpass over I-5.

Lately, the US community has been moving towards forming a coherent network for each classification, meaning that stubs, particularly secondary and above, should be avoided (see osm.wiki/United_States/Highway_classification)

Here's a useful diary entry from another fellow mapper on classifying roads in the LA area: osm.org/user/willkmis/diary/399345

Almost got it, for multipolygons you only need to have the tags you want on the relation. It looks like the outer way also had `natural=wood`. Since this way seemed to follow the park boundary, I've changed the outer way of this multipolygon to be the way used for the park in osm.org/changeset/145588701