changeset/186152590 restores the normal name and branded features per survey.

Hi, thanks for adding the missing bit of cycleway. Are the YMCA’s parking lots really named “Parking Lot” followed by the secondary intercardinal directions? way/1537841823 It’s OK to leave a parking lot unnamed if it doesn’t go by a common name in practice.

By the way, if this street is highway=service, some routers will avoid using it as a cut-through. For example, Valhalla is passing the exit and taking the next exit, then doing a U-turn back onto Highway 85 in order to get to Almaden Expressway. Routers often try to avoid cutting through service roads because they aren’t intended as part of the public road network.

During its lifetime, Almaden Plaza Way has been through seemingly every possible highway classification except highway=raceway, so anything is possible. 😉

In isolation, the eastbound lanes do look like a candidate for highway=motorway_link. But we would need to either make the westbound lanes a link way that leads nowhere, or else the two sides of the street would have wildly different classifications. Most mappers avoid classifying a street differently on either side. There are occasional exceptions, typically because both sides are considered different streets.

A similar thing happens routinely in Texas. Freeway exits there typically empty onto a frontage road. If the ultimate destination of that exit is highway=primary, a short portion of the frontage road gets upgraded to match. Here’s an example: way/599989943

This situation is so rare here that I can understand how highway=primary would seem like a mistake.

I’ve reverted this changeset because Almaden Plaza Way is a connector for an Interstate exit onto an arterial road. Even if not for the ramp for I-280, service=driveway is for residential driveways and the like, not parking lot access roads.

changeset/185985290

We do use superrelations for some things like routes, but not for boundaries. Anyways, here’s the forum discussion on whether we should even have MSA boundaries in OSM:

https://community.openstreetmap.org/t/chicago-metropolitan-area-relation/131055/9

The handful of classification changes appear to be incidental to the route updates in the changeset. More discussion in https://community.openstreetmap.org/t/wholesale-missouri-route-edits-by-ne2/145510

https://community.openstreetmap.org/t/chicago-metropolitan-area-relation/131055/9

The sign is mounted on a streetlamp pole, actually a rigid metal sign now that I look more closely.

This was reverted in changeset/185552871

That would be my preference as well, but this was a compromise because another mapper insisted on deleting anything I tagged as man_made=mast and man_made=antenna. Feel free to weigh in:

https://community.openstreetmap.org/t/colocated-broadcast-antenna-structures-nodes-inside-an-area/122626

Hi, I’ve reverted this changeset in changeset/185362478 because the characters are in fact valid. You’ve come across an unfortunate bug in one OSM-based renderer. Please see the following pages for more information:

https://community.openstreetmap.org/t/glitchy-town-labels-in-oklahoma/144491
osm.wiki/Mapping_for_the_renderer

Does this mean the North Pacific Ocean would be The North Briney? 🤔

border_type=* isn’t totally redundant. Not everything at level 2 is a country and not everything at level 4 is a state, even in Australia. As it is, the search function on this site is only able to label Victoria as a state because of place=state. However, the place=* classification scheme is very limited, without established values for things like territories and unable to express Melbourne as a city.

changeset/183849933 already temporarily renamed the stadium in line with the FIFA host committee’s branding. The stadium building is practically synonymous with the stadium grounds, so I see no reason to give them different names. Your changeset removed both the usual and temporary names from the building, which seems excessive and inconsistent.

The stadium routinely hosts both American and association football (and concerts). We don’t need to track which sport is being played here on any given Saturday. I think the sport tag can include both sports, but we should leave the pitch at NFL dimensions because that’s the norm (as seen in aerial imagery).

Undone in changeset/184373122. I invite you to participate in https://community.openstreetmap.org/t/fifas-temporary-stadium-names/144185 where others have opinions about this as well.

I’m afraid there’s a misunderstanding as to the purpose of these highway classifications. Please consult osm.wiki/United_States/2021_Highway_Classification_Guidance for the standard that we use in the U.S. As far as I can tell, there is no expectation that every small town have highway=primary. We also expect classifications to be contiguous without haphazard changes near intersections.

That would be changeset/183741105. I agree that highway=motorway would be more straightforward than any of the possible alternatives.

“Motorway island” refers to an isolated section of highway=motorway, not a special tag of any sort. I clarified the wording in osm.wiki/Special:Diff/3051093

Thanks, it seems reasonable to extend the directional beyond this one stretch.

Many jurisdictions use directionals to indicate the quadrant of the street grid, whether or not there’s a counterpart on the other side of town. So there could be a North Horizon Boulevard to the north of Mesquite without a “South Horizon Boulevard” to its south.

The origin of Mesquite’s street grid is at the intersection of Mesquite Boulevard (the east-west axis) and Yucca Street (the north-south axis). They seems to apply the direction to arterial and collector streets but not to minor residential streets.

At the West Pioneer Boulevard intersection, Bing Streetside shows a street name sign that seems to say “N. Horizon Blvd.” It’s hard to make out in that footage, but there’s definitely a directional prefix.