User talk:Minh Nguyen

From OpenStreetMap Wiki
Jump to: navigation, search


I noticed you seem to have a preference for using the SR ## format for state routes, rather than US:OH ##. Is there a practical reason for this, to explain why you re-did all the ref tags on Columbus's West Innerbelt (US:OH 315)? I prefer the US:OH format, because it indicates what state. Maps should make that distinction, too — I've not drawn (even by hand) a map that uses a simple circle for a state route since I was about 10 years old. Then again, when the route relations are done, and the renderers use those, it will be a moot point. Vid the Kid 05:21, 18 April 2009 (UTC)

See User talk:Vid the Kid.
These entangled threads of discussion further continued at User talk:Vid the Kid.

Ref for Overlapped Routes

I also just noticed you set Harrisburg Pike to "ref=US 62" and "ref_1=SR 3". I'm pretty sure that's not the way to do it. Faq#What_shall_I_do_for_roads_that_have_multiple_values_for_a_tag? That entry only mentions using relations, and using a semicolon to separate multiple values in a single "ref" tag. The whole _1, _2, etcetera business seems to be a TIGER thing and I don't think applying it to native OSM tags like "ref" will accomplish anything.

It would certainly be nice if the renderers actually displayed overlapped routes nicely. As it is, they don't seem to do anything special with the relations or semicolon-delimited ref tags. Vid the Kid 05:35, 18 April 2009 (UTC)

See User talk:Vid the Kid.
These entangled threads of discussion further continued at User talk:Vid the Kid.

Route 4 != Dixie Highway

You have labeled the route relation for US:OH 4 as "Dixie Highway". I believe that to be incorrect. After a small amount of research, it seems that the Dixie Highway in Ohio followed Route 4 from Cincinnati to Middletown, then hopped over to Franklin on route 73, and from there followed US 25 to Toledo. Wikipedia:Dixie Highway, Wikipedia:File:Dixie Highway Map.gif, 1932 Ohio Map

I believe the Dixie Highway should have a route relation for its two main branches, but this should be separate from US:OH 4. However, United States Numbered Highway Relations doesn't have a section for all historic roads, just National Scenic Byways. The Dixie Highway is not in the NSB program. Similarly, the Lincoln Highway is in the NSB program, but only the Illinois segment. I think I'll suggest on that talk page to expand that section to include other (and full lengths of) significant historical roads. Vid the Kid 21:28, 30 June 2009 (UTC)

See User talk:Vid the Kid.

US 42 is apparently north/south in Ohio

I've just noticed that the "direction of survey" for US 42's straight line diagrams are all "north". Therefore, I've noted on the relevant Wiki pages that US 42 is north/south in Ohio. I've already changed the roles for the member ways in downtown Cincinnati as part of a larger route clarification and relations effort. (I can't recall what directions are used on actual signage in my area, but it wouldn't surprise me if it's inconsistent.) Vid the Kid 09:36, 24 September 2009 (UTC)

See User talk:Vid the Kid.

You may have a point about the SLDs not being entirely authoritative regarding directions. As another example, I-270's survey direction is "north" in the clockwise direction. But I'm not sure one can expect the SLD survey direction to match the signed direction on loop roads. Still, part of I-270's SLD makes reference to US 62 NB, while US 62's survey direction is "east". (I personally think US 62 should be north-south, but that's another issue altogether...)

I suppose I should try to do some field checking for US 42 before we go to too much trouble changing stuff. For the most part, ODOT uses the US 42 shield with no directional auxiliary signs, but I know of a couple of places where there should be some. Vid the Kid 18:02, 24 September 2009 (UTC)

Update: Field checking done from LaFayette to Delaware. When used, direction signage is consistently "north" and "south". Vid the Kid 21:37, 25 September 2009 (UTC)


Anh Minh giúp mình với, mình sửa bản đồ ở chế độ áp dụng ngay nhưng không thấy nút lưu, không biết cách nào để lưu cả, chỉ với--Magicknight94 00:24, 28 September 2009 (UTC)

Xem User talk:Magicknight94.

Re: Townships

See User talk: Vid the Kid. I like to keep both sides of a discussion in one place. (Reply count: 3) Vid the Kid 09:25, 27 October 2009 (UTC)

Leaflet in vi.wp?

Can you give me please an example link to your edit. I want to try and compare leaflet but if I look at I see only a link to WikiMiniAtlas. I want to upgrade the documention. --Kolossos 19:45, 27 September 2012 (BST)

See User talk:Kolossos.

CLDR is an unreliable, inconsistent source for Vietnamese names

Sorry that I don't speak Vietnamese. Could you describe me please more what's the problem was with my import. You change 10 of the 200 countries, would you say my import war in summary acceptable or more a disaster? I believe also manually translations would have some mistakes.

My next plan is to translate all capitals by using Wikipedia interwikilinks and Add-tags. Do you think that's a better source?

My second larger plan is to translate states in ISO 6133-2 by using a debian package. So it's the top-to-down way for zoomlevels 0-6, which we already have in Wikipedia in different languages. Later we need for Multilingual maps Wikipedia project more users for translations. --Kolossos 18:46, 15 October 2012 (BST)

See User talk:Kolossos.

USBR 25 in Southwest Ohio

See User talk:Stevea.

Thank you for your excellent edits everywhere, and nice to "meet" you (we've brushed up against each other in the talk-us pages regarding boundary=census and other topics).

I've added relation 3087492 as a SW Ohio USBR 25 candidate relation based upon your OKI data of where it goes. I agree with you that overloading the UGRR relation is incorrect, so thank you for deleting that relation from the USBR table. However, I believe 3087492 is either mostly or entirely correct.

—Preceding unsigned comment added by Stevea (talkcontribs) 19:48, 17 July 2013 (UTC)

Tag pages for Highway networks


your creating a lot of pages with highway tags for each county:

What is the intention of this pages. What will be it's content?

Wouldn't it be simpler to just add a page for all highway networks in Ohio?

--Werner2101 (talk) 12:16, 25 May 2014 (UTC)

(moved from talk:werner2101)
There is, but I've been creating separate wiki pages so that Taginfo can describe each value specifically. Descriptions are especially useful for network=US:* because many values include abbreviations that may not be familiar to every mapper. – Minh Nguyễn (talk, contribs) 12:20, 25 May 2014 (UTC)
This creates a lot of noise in the wiki. Not every tag needs a tag description. Consider what will happen if someone starts to add tag pages for each name tag. You can use Overpass API to get all Highways with a specific network tag. --Werner2101 (talk) 12:27, 25 May 2014 (UTC)

(moved from talk:werner2101) Names don't need descriptions. Separate pages make sense for network=* because its values are all abbreviated, not spelled out like cuisine=* or denomination=*. There would eventually be no more than 88 pages for Ohio county route networks, and each of them would tell you what the abbreviation means, an example route shield that a renderer is expected to use for each route in this network (also displayed in taginfo), and the standard format for the ref tag on member ways (CR 123, C-123, CH 123, etc.). Is the problem that I'm cluttering up Special:RecentChanges? If so, I'm pretty much done, because we've only added route relations in a few more counties. Taginfo already knows how to parse pages like Map Features; I'll file a bug requesting that it parse additional pages where we can aggregate all this information. Sorry for the inconvenience I've caused you today. – Minh Nguyễn (talk, contribs) 12:39, 25 May 2014 (UTC)

Im not worried about the cluttering of the Recent Changes list. The tag pages are cluttering all the categories of the tag descriptions. (e.g. Category:Tag descriptions) where all tags are listed.
The created tag description don't contain any description. It is just a simple forwarding to Ohio/Route relations. I think a single page about mapping US highways would be more helpfull than several hundred Tag:network=US:XX:YY pages. Ohio is not the only state in US. US is not the only country that uses road route references. --Werner2101 (talk) 19:08, 25 May 2014 (UTC)
The description is in the {{ValueDescription}} box on the right; that's what taginfo is using. But I can add more information to the body of each page, too. Ohio is one of two or three states that use separate network values for each county, because each county has a completely distinct route shield design; most states are using a single US:*:CR network instead. The pages I've created make up about 1% of Category:Tag descriptions and 0.5% of Category:Tag descriptions by value. Even if I were to create a page for each of the 444 values of network being used anywhere in the world – which no one is proposing to do – that would only total 23% and 11% of the respective categories. Still, to allay your concerns, I've modified {{DescriptionCategories}} to exclude these pages from Category:Tag descriptions as long as Category:Tag descriptions for key "network" exists. (See Tag:network=US:OH for example.) The changes will take effect once the wiki's job queue (currently at 1,485) finishes processing the affected pages. – Minh Nguyễn (talk, contribs) 22:22, 25 May 2014 (UTC)


If you really want to humour the fruity hipsters you can write {{languages|Category:macOS}} similarly to iD.--Andrew (talk) 09:04, 1 October 2016 (UTC)

:^D – Minh Nguyễn (talk, contribs) 18:53, 1 October 2016 (UTC)

GeoMapTool / geoBingAn

Just to let you know since you've contributed most to the page, I've added a big fat warning to the page. Versions of this software have caused a huge amount of damage and wasted a lot of time (especially of on-the-ground mappers, but also of the ours at the DWG) trying to clean up the mess. I've also removed the website and store links. Problems caused by this software have included creating dozens of versions of the same object (applying a change over and over again), creating dozens of duplicates of objects, and adding all new nodes at latitude -1. The OSM wiki really shouldn't be recommending this as an iOS editor (as it did at ). --SomeoneElse (talk) 08:39, 20 June 2017 (UTC)

See User talk:SomeoneElse.

Simple 3D buildings software list

Hi, I'm not entirely convinced of your decision to order the software list on Simple 3D Buildings alphabetically. It was closer to a chronological sort order before (although not entirely) – wouldn't it make more sense to keep that basic idea and maybe add a "release date" column to make the sort criteria visible? Disclaimer: This would place my own renderer higher up, so of course I'm biased. ;) --Tordanik 14:33, 2 September 2017 (UTC)

See User talk:Tordanik