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.

OK, that’s a relief.

We’re discussing this changeset more generally in Slack: https://osmus.slack.com/archives/CCN1KJ76U/p1781742162221729

Yes, the Caltrans report I linked to explains that the state and local governments sometimes name overlapping road segments, such that a given segment may have multiple official names. I also hope you haven’t renamed city streets according to Wikipedia. Wikipedia has never done a good job of tracking city street names – that’s what OSM is for.

(The FIFA-induced changes started several weeks ago and probably won’t revert immediately after the last match. Even in OHM, I wouldn’t ascribe it to those particular dates.)

See the forum discussion. This was also discussed more privately within the South Bay community. As I’ve said, if anyone disagrees enough, they can go ahead and change it back.

I won’t be using the date namespace syntax. That’s a crutch that some mappers use to avoid contributing historical information to OHM.

What do you mean “attempted”? Did you run into any problems?

Also, if you’re going to model official highway names, I would strongly encourage you to go beyond a cursory reading of a Wikipedia article and consult more serious sources. In particular, for official_name=*, please consult the latest issue of the Caltrans publication “Named Freeways, Highways, Structures, and Other Appurtenances in California”. [1] Wikipedia sometimes cites Caltrans publications, but this is no longer guaranteed, as the community has been taking a harder line against citations to highway authorities regarding their own highways.

[1] https://dot.ca.gov/-/media/dot-media/programs/research-innovation-system-information/documents/ohsip/2024-named-freeways-final-draft-benson-05-08-26-revised-a11y.pdf

Alright, changeset/184153268 replaces it with disused:tourism=information and planned:tourism=information, which are both in use.

Oh, right! I was going to ask about that one. You can see a photo of the boarded-up wayfinding signs and site maps in https://community.openstreetmap.org/t/fifas-temporary-stadium-names/144185/38 Do you think disused: would be more appropriate?

The key is defined to have no globally consistent meaning, only referring to access restrictions in certain places, and is hardly used by anything yet. So I figured it would still be feasible to use it as iterative refinement per the original proposal.

There was an alternative proposal to redefine expressway=yes to include freeways, but I’m strongly against that idea. https://community.openstreetmap.org/t/extended-expressway-tagging/137200

Long-term, motorway=* might be more defensible based on the old proposal that was supposed to go along with expressway=*.

This changeset was based on an in-person survey in response to https://community.openstreetmap.org/t/fifas-temporary-stadium-names/144185 .

The local and national communities do occasionally retag buildings undergoing renovations and major bridge closures. The most important consideration is whether we can effectively keep track of all such changes and change them back when appropriate. I anticipate restoring Levi’s as soon as the tarps come down.

I don’t care particularly strongly, since OHM also records this change (and the impending change back).

Hi, this change unfortunately violates osm.wiki/Tagging_for_the_renderer . The font rendering bug you saw is a known issue in OSM Carto or its underlying Mapnik dependency. Removing the name disadvantages other map styles that are able to render the Osage name just fine, such as the Shortbread layer or OSM Americana. See also the discussion in changeset/183279767. changeset/183890744 restores the Osage name.

Hi, it looks like this changeset removed the Osage name from Hominy. Perhaps this was in response to a font rendering bug in Mapnik? See the discussion in changeset/183279767. changeset/183890744 restores the Osage name.