Hi, fyi you broke the member order on a few bus route relations here when you split the way. (it's been fixed)

source also includes Mapillary

Are you sure? Both these stops still show up on the AC Transit schedule.

This sidewalk was already mapped here: way/969998938

Hi, the building with it's address is already mapped here: way/1047709621

The building:part area you edited is just for osm.wiki/Simple_3D_Buildings

Hi, something went wrong here and in some of your (and @atticquilt 's, who it looks like you're working with?) other edits to San Pablo Ave. There were a bunch of random-looking segments of streets that were deleted here, and multiple overlapping crossing ways and sidewalks created over several changesets.
I reverted the most problematic changesets, but it seems like there's a problem in your mapping process somewhere.

Hi, a couple of things I noticed/fixed in this edit to watch out for in the future: 1-The crosswalk nodes were already mapped here, but you added some new ones directly adjacent instead of connecting the crossing way to the existing nodes. 2-This is a signal-controlled intersection, but you tagged the crossings as uncontrolled (or "traffic_signals;uncontrolled", which doesn't make any sense) instead of crossing=traffic_signals.

Hi, Please don't change the crossing=traffic_signals and similar tags to the less-specific crossing=marked tag. Thank you.

The traffic restrictions are already covered by the motor_vehicle:conditional tag. "Designated" is used more in the sense of "this is a designated ____ route".

Hi, welcome to openstreetmap, but please don't make test edits like this directly to the database. Thank you.

Hi, has way/17369701/history been repaired? When I was there earlier this year I remember there being a sign saying something like "tracks out of service", and the northern end near E Washington Street was in pretty bad condition.

Don't you need a permit to use EBMUD trails?

This isn't correct. The Alameda/MLK changes names when it crosses Codornices Creek; there's a street sign at the exact spot with both names. It was fine before.

You should really be discussing major classification changes first, especially when you only have 17 edits. The idea is generally to maintain a coherent interconnected network, and you've essentially introduced a "gap" in the secondary network with this Marin/Masonic/Solano/The Alameda/Hopkins/Gilman loop you made.

Hi. What is this "BWA map" you're basing these classification changes on? Why did you introduce this jog in the highway classification at Masonic Ave?
It looks strange, doesn't reflect actual traffic patterns, and is very similar to some undiscussed classification changes made by a now-banned user with multiple accounts from about a year ago.

Thank you for your response.

Each terminal currently has a single exit path from the airside area (inside security) to landside (outside security). For example, in Terminal 2 someone leaving the airport passes a sign stating "Beyond this point you must be rescreened" with a security officer stationed to stop people from re-entering, then passes through a series of automatic doors that only allow one-way travel towards the landside exit.

Similarly, there is only one path of travel from landside to airside in each terminal, which is through the security screening area. These are separate from the exits.

It's possible that your software is set up to block routing through the barrier=checkpoint nodes that represent the security screening areas by default.

Similarly, if you are using a quality-assurance tool it's possible that the path through customs and immigration will be incorrectly flagged as a dead-end one-way, since the international flight it originates from isn't mapped in osm.

Were all the "Private Property No Trespassing", "Private Street Not For Public Use", and "Private Property No Trespassing No Soliciting" signs taken down around these three complexes?

If so, these streets would still be access=permissive at best since they're privately owned.

Hi,
The oneway/oneway:foot tags that were removed here are important; you can't enter the secured areas through the exit (you can't even turn around half-way since the doors close automatically behind you), nor can you go backwards through customs/immigration. The escalators only go one direction as well.

Hi,
Please note that highway=corridor is an entirely appropriate tag to use on indoor corridors inside buildings. Please don't change it to highway=footway. Also, you moved one of the terminal 2 entrances to line-up with the covered walkway, which would make sense, but that's not how it's actually built. Some surface/covered tags were lost as well around the entrances.

Hi, just a heads up: it looks like some bus route relations got broken here near the Martinez Amtrak station.

Hi,
Thank you for your interest in adding bicycle infrastructure to the map. Unfortunately, this is not the way that on-street bike lanes are mapped in osm. They are generally mapped by adding the tag cycleway=lane (for bike lanes), or cycleway:right=lane / cycleway:left=lane / cycleway:both=lane to specify which side(s) of the street have lanes. Please take a look at cycleway=* and/or osm.wiki/Bicycle for more info. They're only drawn as a separate cycleway when there's some kind of significant physical separation from the roadway (like a bike lane going behind a bus boarding island for a common SF example), or in rare complicated situations where things can't be represented accurately otherwise.

The bike lanes on Folsom Street were already mapped, tagged as cycleway=lane.