Misplaced Pages

This is an old revision of this page, as edited by Lowercase sigmabot III (talk | contribs) at 01:04, 5 September 2014 (Archiving 1 discussion(s) to Misplaced Pages talk:WikiProject U.S. Roads/Maps task force/Archive 2) (bot). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

U.S. Roads Project‑class

This page is within the scope of the U.S. Roads WikiProject, an attempt to build a comprehensive and detailed guide to state highways and other major roads in the United States. If you would like to participate, you can edit the article attached to this page, or visit the project page, where you can join the project and/or contribute to the discussion.U.S. RoadsWikipedia:WikiProject U.S. RoadsTemplate:WikiProject U.S. RoadsU.S. road transport Project This page does not require a rating on the project's quality scale.

This is the talk page for discussing improvements to the WikiProject U.S. Roads/Maps task force page.

Put new text under old text. Click here to start a new topic. New to Misplaced Pages? Welcome! Learn to edit; get help. Assume good faith Be polite and avoid personal attacks Be welcoming to newcomers Seek dispute resolution if needed Shortcut WT:USRD/MTF

Archives: 1, 2Auto-archiving period: 2 months

The maps task force asks that all map requests be left on the requests page and not on this page. Your cooperation is appreciated.

One-way pairs in KML files

How do I represent a one-way pair? Would two paths with names 'eastbound' and 'westbound' work, like I did on U.S. Route 460 in Virginia? --NE2 22:01, 7 July 2014 (UTC)

That's along the lines of what I usually do. If there's more than one one-way pair, I usually specify and name it "Eastbound in (city name)". TCN7JM 22:24, 7 July 2014 (UTC)

You could do what TheWombatGuru (talk · contribs) does and make separate lines for EB and WB for the entire route, not just the one-way couplet. –Fredddie™ 03:04, 8 July 2014 (UTC)

KML for Interstate Highway System

I cleaned up the topology of the NHPN data a bit and uploaded a KML file for the entire IHS (view on the Goog). For several reasons I'm not linking to it in the article:

• I didn't do much geometry cleanup from the NHPN data, so some Interstates are horribly imprecise (e.g. I-72 west of Jacksonville, IL; I-795 in NC, I-10 at TX exit 294).
• There are no objective standards for which future Interstates (suffixed F) I included. I may have also gotten the status of a few recent additions wrong.
• Curves are a bit too simplified in areas (due to Misplaced Pages size constraints).
• There's also a problem with multipart lines, which doesn't affect display, but creates annoying effects when editing.

However, it is good enough for small-scale mapping (for which you'd probably want to filter out all future routes). --NE2 02:03, 15 July 2014 (UTC)

• Project-Class U.S. road transport pages
• NA-importance U.S. road transport pages
• U.S. road transport articles