Revision as of 01:04, 5 September 2014 editLowercase sigmabot III (talk | contribs)Bots, Template editors2,293,067 editsm Archiving 1 discussion(s) to Misplaced Pages talk:WikiProject U.S. Roads/Maps task force/Archive 2) (bot← Previous edit |
Revision as of 01:05, 7 September 2014 edit undoLowercase sigmabot III (talk | contribs)Bots, Template editors2,293,067 editsm Archiving 1 discussion(s) to Misplaced Pages talk:WikiProject U.S. Roads/Maps task force/Archive 2) (botNext edit → |
Line 13: |
Line 13: |
|
|The maps task force asks that '''all''' map requests be left on the ''']''' and not on this page. Your cooperation is appreciated. |
|
|The maps task force asks that '''all''' map requests be left on the ''']''' 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 ]? --] 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)". ]]] 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) |
|
|
|
|
|
|
== KML for ] == |
|
== KML for ] == |
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)