Cũng được gọi là Cáp Ve, nhất là ngoài VN. Nên có alt_name:vi=* để người ta có thể tìm kiếm đến.

Cám ơn, anh chỉ đặt dấu để thống nhất với tên vịnh México theo yêu cầu của cộng đồng thế giới. (Người Mỹ vẫn hay gọi là vịnh Mễ Tây Cơ, miễn là không đổi tên theo thời tiết chính trị.)

Ủa, sao lại bỏ tên Uy Kiên, hình như tên này vẫn được sử dụng một cách không chính thức. Ngoài VN Uy Kiên chắc được nhắc đến nhiều hơn Ukraina (nhưng ít hơn Ukraine). alt_name:vi=* có thể có hơn một giá trị được phân cách bằng dấu ;

Arab chắc là một thay đổi mới gần đây phải không? Có ai còn gọi là Ả Rập Xê Út không? Nếu có thì có thể đưa vào alt_name:vi=* luôn.

Chắc nên giữ Ai-len trong alt_name:vi=* vì đôi khi vẫn được sử dụng trên thực tế. Có cả Ái Nhĩ Lan trên một bản đồ số (Apple).

Thực sự mọi ngôn ngữ cũng hay viết tắt tên này. Sau thay đổi này, chỉ có tiếng Việt có thẻ name là tên viết tắt. OSM có quy định tránh chữ viết tắt trong name=*, chỉ đặt chữ viết tắt trong short_name=*. osm.wiki/Abbreviations Vậy có nên tuân theo quy định không, hoặc có cần một ngoại lệ vì không ai biết đến tên đầy đủ chính thức?

Các lối biên giới này có thẻ maritime=yes nhưng không phải là biên giới trên biển. Một số bản đồ OSM đang ẩn các biên giới tỉnh vì thẻ không chính xác này.

OK, looks like it should’ve been highway=proposed proposed=motorway. Someone in Slack did some sleuthing and determined that ground hasn’t broken on this bypass (and is unlikely to in the near future).

Hello, what was your source for changing these roadways from highway=proposed to highway=construction (contrary to your changeset comment)?

I only added node/11306007733 node/11306007734 node/11306007735 around the railroad crossing, though it looks like there are only “Stop Here On Red” signs and stop bars. I’d be OK with deleting them. Normally I only map highway=stop when there’s an actual stop sign at the crossing, as opposed to a yield sign or traffic light.

In changeset/143555657 I tried to handle the requirement to go through the toll booth. It was difficult to model, but I think I had it right at the time. If things have broken since, I’d appreciate your help debugging and fixing the issue. Thanks!

That hasn’t been the general practice for many years. Maybe it was an isolated case that we had overlooked?

I suggest replacing “Business” with either 💼 or 🕴️to adhere to OSM Carto’s mandatory limit while avoiding abbreviations. (A rebus isn’t an abbreviation.)

In seriousness, please direct anyone who expects an accurate road layer to a map that can render route shields: osm.wiki/United_States/Road_signs#Implementations

Is the reservation really known as “Iowa (KS-NE) Reservation”? Or is that just a Census Bureau invention to avoid confusion with the Iowa the state? changeset/181159559 replaces it with the common and official names from the tribe’s website.

Also, Báxoje comes from changeset/116831339, where NFZANMNIM conflated the reservation with the people. changeset/181160635 replaces it with something that appears in land acknowledgements that seems to resemble a trustworthy dictionary entry [1] (other than apparent grammatical inflection). I’m still not 100% sure this is correct, but it’s better than what was there before.

[1] https://iowayotoelang.nativeweb.org/pdf/r_engtobax_sep_09.pdf#page=3

Please consider copying from Wikidata labels instead of Wikipedia article titles. Wikipedia article titles often contain disambiguators that don’t belong in a map label. Many data consumers already know how to fall back to Wikidata’s more cleaned-up labels when OSM lacks a name tag, but this edit forces them to show the messier names that you copied from Wikipedia.

As discussed in: https://community.openstreetmap.org/t/migrating-proposed-routes-to-a-lifecycle-prefix/141573

Yeah, I just mentioned memorial_name=* because it’s in use and matches federal terminology. I forgot that honorary_name=* is more common. But this would all need to be sorted out in a broader discussion, not here.

In case there’s any misunderstanding, if a highway=* is known by multiple names, the common name usable for wayfinding should go in name=*. [1] I never said name=* has to be usable for in-car navigation specifically. I am sympathetic to the argument about searchability, hence my habitual use of official_name=*, but many mappers recognize that this is far from ideal. After all, federal law emphatically states that these names are *not* official.

changeset/180078301 records another memorial name designation in Miami, Avenue of the Americas. In one Mapillary frame, you can see how this city distinguishes between a memorial name designation and a generic alt_name=*, Biscayne Boulevard Way. [2] Granted, New York City doesn’t make the distinction so apparent. Different state, different standards. They figure everyone should know that streets in Lower Manhattan are denominated by ABCs and 123s. Prompted by your comment, changeset/180075547 scales Sesame Street back to just the block on which it’s signposted.

As far as the on-the-ground rule goes, Trump Boulevard is nothing more than a single double-sided sign posted at one end of the street, which I’ve taken the liberty of adding in changeset/180080039. It takes a certain amount of wishful thinking to extrapolate this into name=*, so I hope we can leave it here at alt_name=*. However, this will be a prime candidate for memorial_name=* once a proposal gets underway.

[1] name=*#Values
[2] https://www.mapillary.com/app/?pKey=329012028614409

The name got reported on because of its namesake, not because of “ground truth” as you put it. It’s functionally obscure because, by law, it can’t be posted anywhere you’d be able to navigate based on it. It’s trivia because memorial name designations are so exceedingly commonplace. That is not to say anyone would be against geocoders exposing this information, appropriately downweighted to reflect relatively minor functional utility. Do I understand that you would be fine with memorial_name=* if only it were better supported by Nominatim?

Please put your pitchfork away and assume good faith. changeset/180033385 was clearly about more than this one obscure street name that you care way too much about. Perhaps the changeset comment could’ve called out this particular retagging. I think we can give NE2 the benefit of the doubt that it was an oversight. If he had wanted to cover his tracks, he wouldn’t have commented on this changeset, alerting you to his edit.

NE2’s edit was clearly more correct than incorrect. Before you toss around accusations of “close to vandalism”, remember that your initial edit was based on a forward-looking article from a local TV station that someone overseas may not have the local context to interpret correctly. Anyone in the U.S. would by now be familiar with such reports of “renamings” that turn out to be memorial name designations. NE2 is asserting that this is a memorial name designation and I see no evidence to refute that. The law is very clear that a memorial name designation is not intended for wayfinding, so it isn’t a candidate for name=*. [1]

Over the years, memorial_name=* has come up often in OSMUS Slack because mappers believe official_name=* is putting too fine a point on it and alt_name=* doesn’t distinguish them as memorial name designations. These mappers are fine with it falling out of search results, because it amounts to trivia. Some mappers don’t even bother to tag any name and map the sign instead. I personally use official_name=* because I haven’t encountered enough instances of a feature having both an official name and a memorial name designation, but I guarantee you that if we take this conversation to the forum, memorial_name=* will proliferate as a result.

[1] https://mutcd.fhwa.dot.gov/pdfs/11th_Editionr1/mutcd11theditionr1hl.pdf#page=571

alt_name=* is also fine. The main thing is to keep Southern Boulevard as the name=*.