Misplaced Pages

talk:WikiProject U.S. Roads/Maps task force: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages talk:WikiProject U.S. Roads Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 03:04, 8 July 2014 editFredddie (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, File movers, Pending changes reviewers, Rollbackers, Template editors102,318 edits →One-way pairs in KML files: another option← Previous edit Revision as of 02:03, 15 July 2014 edit undoNE2 (talk | contribs)Autopatrolled, Extended confirmed users, Pending changes reviewers190,449 edits →KML for Interstate Highway System: new sectionNext edit →
Line 29: Line 29:
: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)". ]]] 22:24, 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)". ]]] 22:24, 7 July 2014 (UTC)
::You could do what {{user|TheWombatGuru}} does and make separate lines for EB and WB for the entire route, not just the one-way couplet. –]] 03:04, 8 July 2014 (UTC) ::You could do what {{user|TheWombatGuru}} does and make separate lines for EB and WB for the entire route, not just the one-way couplet. –]] 03:04, 8 July 2014 (UTC)

== KML for ] ==

I cleaned up the topology of the NHPN data a bit and uploaded ] (). 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 , 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). --] 02:03, 15 July 2014 (UTC)

Revision as of 02:03, 15 July 2014

WikiProject iconU.S. Roads Project‑class
WikiProject iconThis 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
ProjectThis 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.
Shortcut
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.

blank map - help

File:Great River Road map.svg opens fine in Inkscape, but renders blank. --NE2 10:02, 24 June 2014 (UTC)

 Done - I guess you forgot to hit "fit window to selection." I fixed it using the background white path as the window. —Mr. Matté (/Contrib) 11:03, 24 June 2014 (UTC)

Quality control

Is there any way to view or download a bunch of KML files at once for quality control/error checking purposes? --NE2 17:07, 6 July 2014 (UTC)

Presumably you could use any browser extension designed for mass downloading for this purpose, e.g. DownThemAll! —Scott5114↗ 18:39, 6 July 2014 (UTC)

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)

Categories: