Reverted in changeset/174663931

This changeset should be reverted. The U.S. community reached a consensus to deprecate subarea members of boundary relations:

https://community.openstreetmap.org/t/proposed-removal-of-subarea-members-from-us-boundary-relations/122865

Thank you for your quick response. changeset/174456278 changes the name=* tag back to the Hanafi Rohingya name, preserving the Burmese name in name:my=*.

If it turns out that the Burmese name is more appropriate for this village and the original edit was inaccurate, please feel free to change it back. Thank you for your help and understanding.

Hello, this changeset modified node/5095558947 to have a name=* tag matching name:my=* instead of name:rhg-Rohg=*. Meanwhile the linked Wikidata item still says the native name is in the Hanifi Rohingya script. Do you know if that’s inaccurate, or was the edit intended to be consistent with how other nearby places are tagged?

This came to my attention because I’ve been working on improving MapLibre’s support for Unicode text. Burmese script has been a priority, but I’ve also been using this Hanifi Rohingya name as a test case, so I was surprised to see it change suddenly. Thank you for any insights you can provide.

Reverted in changeset/174229200: short_name is for conventional abbreviations (e.g., AP abbreviations). USPS/GPO state codes go in ref.

Reverted in changeset/174229200: short_name is for conventional abbreviations (e.g., AP abbreviations). USPS/GPO state codes go in ref.

Thank you. There was some prior discussion about using NBI in [1], but it focused on weight restrictions rather than start dates. Perhaps you could help with the idea to map weight restrictions based on this dataset, since it seems to have stalled.

NBI could also be useful for improving road coverage in OpenHistoricalMap. OHM has mappers doing more bespoke research on road openings, but bridge-based inferences could complement that work very nicely. I proposed something similar to your process in the OHM forum. [2] Feel free to chime in based on your experience doing this in OSM. (You can log into OHM using your OSM account, then log into the forum using your OSM account.)

[1] https://community.openstreetmap.org/t/adding-bridge-information-in-kentucky-and-other-states/113229
[2] https://forum.openhistoricalmap.org/t/national-bridge-inventory/578

What were your sources for these dates?

¡Gracias! changeset/172690338

Fixed in changeset changeset/172039442

Thanks for catching my mistake again. Similar to last time, I searched for “cưỡi ngựa” and this was all that showed up. The translation for leisure=pitch sport=equestrian got renamed, so it was back to English again. I just updated the translation, so it should be back in the next release.

I fixed the mistagging in changeset/172038103.

Thank you for fixing it. 🙂

This seem more like service=parking_aisle than service=driveway.

This crossing and others along the busway have *three* different kinds of signals. If you remove crossing=traffic_signals, at least add crossing:signals=yes.

https://community.openstreetmap.org/t/do-we-really-need-railway-tram-crossing-resp-tram-level-crossing/118987/25

Thanks for adding official_name at least. The artificial names are unfortunate. Even with official_name, it’s implying that *normal* people call it “Bus 806 (Eastbound) Eagle Mountain - Saratoga Springs - Lehi Station - UVU”. Now that iD can generate similar descriptions automatically, we could get the website and JOSM to do something similar so that the real-world name can be tagged as a real-world name.

I cleaned up relation/9671226 to be have valid multipolygon geometry (without any touching outer rings) and joined way/298116730 to its outer way.

Hi, just to be clear, OSMUS the organization doesn’t have anything to do with this. It’s just a few of us local mappers discussing what to do about the fact that some parts of these preserves are open to the public while others are off-limits. Each of these preserves used to be mapped as two separate boundary=protected_area relations with disambiguators in the name, but mappers from abroad criticized this approach for making up names. The boundary=forest_compartment areas are the closest alternative that preserves information while retaining just one overall park boundary.

Ideally, yes, the compartments should be connected to the overall park boundaries at each node instead of having these duplicate nodes everywhere. I’ve already cleaned it up for a couple of other preserves, but it’s very tedious.

New Brunswick is legally bilingual and this is a big deal to its residents. If anything the name=* tag on the relation should be bilingual to match, based on the documented community consensus. [1] If you plan to give English more prominence than French, I suggest taking the matter up with the Canadian community. [2] Incidentally, I’ve proposed to delete the Canadian place=state points to properly acknowledge the provinces as provinces. [3] If this would affect Lyft as a data consumer, please say so on the forum. Thank you.

[1] osm.wiki/Multilingual_names#New_Brunswick
[2] https://community.openstreetmap.org/c/communities/ca/95
[3] https://community.openstreetmap.org/t/acknowledging-provinces-in-website-search-results/127164

It’s a concession stand run by the Cincinnati Marlins inside Keating Natatorium. It was called the Bait Shop when I went to St. X back in the 2000s, but they might’ve renamed it since. A video of the natatorium’s recent remodeling shows a concession stand still there. [1] I restored the POI in changeset/170455842 but retagged it as a concession stand to avoid confusion.

[1] https://www.facebook.com/shp1901/videos/st-xavier-high-school-natatorium/1065818547585793/

I reverted this in changeset/170225644. I-280 continues all the way to the interchange with U.S. 101. The overhead sign you’re referring to is telling drivers to get into the right lane if they want to continue on to I-680. I’ve added a destination:ref tag to indicate that.