Thanks for these updates! By the way, it isn’t quite up-to-date enough to show the new elementary school coming in, but the KyFromAbove 2020 imagery is now available in the sidebar and is a little bit newer than the Bing imagery you were looking at. It might be handy for other updates you make in the area.

These destinations are inaccurate. Not every green sign should be recorded in the destination key; some of them should’ve been tagged as destination:symbol=train_station.

Destinations on freeways in most of San José have already been reviewed many times for accuracy. Minor mistakes or outdated information is always possible, but before making drastic changes, consider reaching out to the local community to double-check anything that looks amiss, in case there’s any context that isn’t apparent from the imagery you’re working with. Thank you.

I belatedly realized the flagpole in Washington is on private property. changeset/109721756 adds the flagpole in front of the embassy (still presumably flying the U.S.-recognized flag, designed in 2013).

Please follow the links to https://www.wikidata.org/wiki/Q108111555 and https://www.wikidata.org/wiki/Q30747910 . This change merely clarifies that, whatever happened in Afghanistan today, the flags in Washington and New York represent the internationally recognized government.

FYI, this changeset somehow removed much of the U.S. 278 route relation, and changeset/63079505 subsequently created a redundant relation for U.S. 278 that also had large gaps. I think I fixed the issue in changesets 109072963, 109075864, and 109077198, but if you had intended to make any changes to this route relation in this changeset, I may’ve inadvertently blown them away.

FYI, this changeset somehow created a redundant relation for U.S. 278 that had large gaps, possibly based on a relation that was broken in changeset/62564979. I think I fixed the issue in changesets 109072963, 109075864, and 109077198, but if you had intended to make any changes to this route relation in this changeset, I may’ve inadvertently blown them away.

changeset/109071854 restores the full U.S. 31 relation.

(Embarrassingly, I miscounted the number of boundaries above, but you get the idea.)

Take a look at the syntax that the Overpass turbo query wizard generates for the “in” operator <osm.wiki/Overpass_turbo/Wizard#Location_Filters> or, more directly for JOSM, the area filter in the raw query language <osm.wiki/Overpass_API/Overpass_QL#By_area_.28area.29>.

The contiguous U.S. has 51 state-level administrative boundaries to query within. If you prefer, you could batch up a few of the more compact states. This is quite a reasonable alternative to either extreme of a single changeset or thousands of them.

If the ramps are to remain highway=motorway_link, then that classification shouldn’t arbitrarily end at the foot of the flyover bridges. If the railroad weren’t there to require a bridge in the eastbound direction, I’m guessing you wouldn’t’ve ended the ramp at exactly that spot.

In lieu of a better answer, changeset/108716632 moves the start of both ramps to where the 0 mile marker for SR-201 is visible going in the westbound direction, opposite to the crash barrier in the median. There isn’t a corresponding mile marker in the eastbound direction, just a reassurance marker a little further to the east, but I’m assuming UDOT would consider the main road to start at around the same spot going in either direction.

Some state DOTs publish straight-line diagrams that take the guesswork out of this exercise, but at least we’re lucky to have street-level imagery here.

Hi, is the temporary turn restriction still in effect, or can relation/10279464 be deleted now?

Hi Yulia, no worries, I recognize that it’s a confusing situation for mappers. This particular situation was harmless, but I wanted to make sure your team was aware of the distinction in case there are situations where similar arrows elsewhere would produce misleading guidance for users.

Hi, these are wrong-way arrows, not straight turn lane indications. See turn=*#Identifying_a_turn_indication . The example on the page shows a different style of arrow, but Caltrans sometimes uses this style of arrow for wrong-way arrows too.

Thanks for this update! Do you happen to know if there’s still a tornado siren on the roof? node/6719056946 I suppose it’s possible it got replaced by a modern, pole-mounted siren nearby.

Any idea which Golden Gate Transit bus route got conflated with U.S. 101? I’m afraid I’m not familiar enough with that system to know what the stops should correspond to.

This changeset somehow replaced the route relations for northbound and southbound U.S. Route 101 between Los Angeles and Hopland (71162 and 108619) with the members of a bus route relation, presumably for Golden Gate Transit. The relations were then deleted as tagging mistakes in changeset/98079317. The relations have been restored in changeset/108175328 and unrepurposed in changeset/108175438.

These relations were somehow broken in changeset/93689318, but the correct fix would’ve been to revert that changeset rather than delete the relations, which represented U.S. Route 101. The relations have been restored in changeset/108175328 and were unrepurposed in changeset/108175438.

Documentation and consensus is the standard for bulk additions of data into OSM, not for backing out undiscussed bulk edits. Large-scale edits have been summarily reverted countless times in the past, not necessarily by anyone in a position of authority. What sets Coke County apart is only that it took a couple years for anyone to get around to it.

This does not need to be an adversarial situation. It could be an opportunity to make improvements to the data processing and redo the import while engaging with the broader mapper community according to the import guidelines. It’s quite rare to have the opportunity to cleanly refine and update an import years after the initial import.

Granted, it’s more work than you may have bargained for, but as someone who recently voluntarily followed the import guidelines for something that wasn’t even technically an import, I’d say it does lead to better results long-term.

Additionally, the surface street that runs parallel to the freeway has a speed limit of 30 mph, not 65 mph, even it also happens to be named Guadalupe Parkway.

Changesets 106625261 and 106625786 correct the speed limits along these two roads.

changeset/106625514 changes the speed limits back to mph, for consistency with the signs posted along the tracks. I’m unaware of any light rail system in the U.S. that posts speed limits in km/h.