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 editContent deleted Content addedVisualWikitext
Revision as of 18:23, 5 September 2006 editLpangelrob (talk | contribs)Extended confirmed users, Rollbackers8,109 edits Legend: default line?← Previous edit Latest revision as of 01:32, 6 August 2024 edit undoCewbot (talk | contribs)Bots7,298,450 editsm Maintain {{WPBS}}: 1 WikiProject template. Create {{WPBS}}.Tag: Talk banner shell conversion 
(415 intermediate revisions by 54 users not shown)
Line 1: Line 1:
{{User:MiszaBot/config
==The altering of WikiProject templates==
|maxarchivesize = 100K
Someday I'd love to do that. But right now it's not possible due to the NC hysteria, the infobox backup, the browse mess, etc. Also we'd have to take it one state at a time. But at one point I'd like to do that. --'''] (] - ]) ''' 20:41, 29 August 2006 (UTC)
|counter = 2
|minthreadsleft = 1
|minthreadstoarchive = 1
|algo = old(60d)
|archive = Misplaced Pages talk:WikiProject U.S. Roads/Maps task force/Archive %(counter)d
}}
{{talkheader|WT:USRD/MTF}}
{{WikiProject banner shell|
{{WikiProject U.S. Roads|class=Project}}
}}
{{tmbox|image=]|text=The maps task force asks that '''all''' map requests be left on the ''']''' and not on this page. Your cooperation is appreciated.}}


== Overhaul of page tags == == Help! ==


I created KML data for this draft, ], in the References section, and converted it to GeoJSON, but upon loading, it just throws an error. How can I fix this? <span style="font-family:monospace; font-weight: bold"><span style="color:ForestGreen">]</span>: ] <span style="">$</span></span> 19:33, 1 June 2024 (UTC)
Here is an example of a page tag being used widely:


:Never mind, I figured it out. <span style="font-family:monospace; font-weight: bold"><span style="color:ForestGreen">]</span>: ] <span style="">$</span></span> 21:34, 1 June 2024 (UTC)
{{U.S. Interstate Highway WikiProject|class=NA}}
:Uploading GeoJSON to Misplaced Pages in raw form has been dying a slow death for years now- the preferred method these days is uploading to Commons under a Data:_____.map page and calling it using a ‘from’ parameter in the template <span style="background:#613314; padding:2px; font-family: 'Courier New'">''']]'''</span> 21:41, 1 June 2024 (UTC)

::The upside to putting the map data on Commons is that it's reusable on other editions of Misplaced Pages, or even the AARoads Wiki. ] and use the same map file on Commons, for instance. <span style="background:#006B54; padding:2px;">''']&nbsp;]'''</span> 21:55, 1 June 2024 (UTC)
It seems there are various methods of assessment being attached to these tags at the moment for some WikiProjects; from my limited amount of browsing, the most comprehensive of these is ], but they also reference ], so many more are possible. For examples, see ] and ].

There is an opportunity for bloat there, but the two uses that are a Very Good Idea and should be implemented are:
* '''Assessment''' - determining the state of an article and its room for improvement
* '''Map classification''' - using the template to identify which articles are in need for maps.

Here's where it gets interesting; while WikiProject Trains has precisely one level of complexity, U.S. Roads has about three; U.S. Roads, Interstates and U.S. Highways, and 50+ state projects. Theoretically, then, there will be 54 different tags to edit, versus WikiProject Trains' 1.

In other words, when these templates are edited, and the people that need to be notified are notified, we need to keep in mind that we don't want ]; we want ]. It's easy to fall into the trap of the former. Even ] should be avoided.

Anyways, this is all sort of related to the maps task force, but if we're going to be modifying many templates, we'll want to keep this in mind. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 20:45, 29 August 2006 (UTC)

: Further discussion on assessment-related issues will be located on the subproject site at ]. I would hate to dilute the discussion when the Maps Task Force has just started. :-) &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 20:56, 29 August 2006 (UTC)

== Maps in SVG format ==

This is just for everyone's information. I'd prefer to upload maps in SVG, but ArcMap's SVG export sucks and the output tends to crash Firefox and hang Internet Explorer. That's the sole reason all my maps are uploaded in PNG. ''']''' <sup>(] ])</sup> 21:34, 29 August 2006 (UTC)
* case in point, ], the image page loads fine but when you click to view full size it explodes and Firefox cries and IE usually hangs. ''']''' <sup>(] ])</sup> 21:37, 29 August 2006 (UTC)
** You could probably just run it through Inkscape and it would correct the code. —]] 06:36, 30 August 2006 (UTC)
*** Yeah, I haven't had any success with that as of yet. ''']''' <sup>(] ])</sup> 14:00, 30 August 2006 (UTC)
**** Tried saving as "plain SVG" instead of "Inkscape SVG" yet? —]] 14:28, 30 August 2006 (UTC)
***** yep ''']''' <sup>(] ])</sup> 14:42, 30 August 2006 (UTC)
******I may have some info for you on this. This link is to the Firefox bugzilla website. This error has been noted as a browser error, not an image error. If I'm reading the notes right, it is fixed with version 1.5.0.7 (due in Sept.). ] 01:50, 2 September 2006 (UTC)
*******Thanks, I was aware that it was a bug with Firefox and I'm glad to see they're finally going to address it. However, I still think ArcMap's SVG export is not optimal, even on the highest settings I don't really like it's output. But, since SVGs are preferred for maps and diagrams, when the bugs in Firefox and IE (?) are fixed, I'll do my best to redo my maps in SVG...but I might wait until there's some hard map attributes hammered out for the task force. ''']''' <sup>(] ])</sup> 03:13, 2 September 2006 (UTC)

== Legend ==

The first thing we need to do is define a legend. Here's some ideas that I gleaned from various maps:

]

The numbers in parenthesis are the stroke width, which is derived by multiplying the number given and the width of "other numbered highway". The only thing I don't like about this is the double red line, which is close to impossible to do in Inkscape, but would make sense to most people. Ideas? —]] 15:01, 30 August 2006 (UTC)
:Hmm. All right. I'm a Rand McNally guy myself, so keep that in mind, but here's what I think...
:# I'd use green (for money) for turnpikes/toll roads.
:# How would divided highways and expressways be different? I'd consider merging these two, and where a divided highway is an expressway, using interchange markers (squares, circles or otherwise) to show that.
:# We might want to differentiate between state routes and county routes, where that level of detail is required. Also, U.S. Routes and state routes.
:# I don't know how I feel about separating Interstate and Other Freeway. At the least, I think it should be a dark, thick color, since I like the idea of having darker, thicker roads being more important than lighter, thinner ones.
So those are some of my thoughts. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 15:40, 30 August 2006 (UTC)

Also, regarding simplicity. Here's a good example:

]

No legend, and no need for a legend. Here's I-90, and everything else relative to I-90. I don't know if it can be done, but the more maps without legends (or with small legends), the better. At a certain scale, I would even be willing to sacrifice the subclassing of highways in favor of simplicity. I also think all the borders (town line, state line, etc.), if used, would be nice and obvious (with proper labeling where necessary, of course - nothing more annoying than a town line with no town name!). &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 15:59, 30 August 2006 (UTC)

:I agree with Rob on this. The amount of detail that a map actually needs will vary by the scope of the map. For example, a map for ] would have ''much'' more detail than a map for say, the ] (or ]). With that said, I see the point for a legend - to standardize maps regardless of scale. So here's my $.02 on the legend:
**Interstate is fine.
**Merge turnpike, other freeway and expressway into one road type.
**Divided highway - I use Inkscape myself, so I'm well aware of how difficult it will be to draw double lines. But it's probably the best way to do it, unfortunately.
**Other numbered highway and below - looks fine to me.

:May I suggest adding another entry for the highlighting of the route itself? --] <sup>] - ]</sup> 16:05, 30 August 2006 (UTC)
: My input on this, is we need to be careful not to get too specific when it comes to maps. Misplaced Pages isn't meant to be a road atlas. That work is best left up to Rand McNally, Google Maps, Windows Live, Mapquest and Mapblast. ''']''' <sup>(] ])</sup> 16:26, 30 August 2006 (UTC)
:: as added notes, it's dependant on the GIS data available whether or not one can distinguish between a 3 lane and a 4 lane highway. Double lines, like for the divided highway, tend to look like crap especially when a particular road has tons of segments to it. For example, using the GIS data for the national road network, I-96 is a pretty short highway, but the line is made up of 202 segments. When you apply the double line to the selection it looks bad. For anything other than Interstate, U.S. Route, State Highway, applying the different types of colors/lines indicated by the proposed legend will be difficult to maintain across the country since the information available varies from state to state.
:: When I designed the maps for the Interstates, U.S. Routes, and Michigan Trunklines, I went through many iterations before I found a map that was both useful and aesthetically pleasing. You can only cram so much information in there before a map becomes useless. ''']''' <sup>(] ])</sup> 16:37, 30 August 2006 (UTC)

Locator maps don't necessarily need to follow this legend, as they're simple enough that the meaning is obvious no matter what convention is used (blue=system and red=highlighted acts perfectly anyway.)

The reason I have turnpikes in orange is because that's what OK uses on their state maps. (KS uses yellow, so I'm used to yellow/orange = turnpike). It's like saying "avoid this if you don't want to pay up". If we can agree on another color we'll use that, of course.

I originally had expressway and divided highway separate because there are divided highways that are too slow to be considered an "expressway". However, dropping expressway and merging it into divided could work. Do we want to use the purple for that, or double red, or something else?

The best thing about having a unified legend would be that we could just link to the legend SVG on the image description page - no need to actually put it in the image :)—]] 17:41, 30 August 2006 (UTC)

All right, more stuff:
#Does anyone object to merging expy and divided highway, and using the purple 2x line?
#Do we want a class for other multilane highways (e.g. 4 lane with turn lane, 4 lane undivided, etc.)?
#Interchanges...<br/>]<br/>Here's some ideas. Thoughts?
#We could use light grey and tan for gravel and dirt roads respectively.

Also, I thought I should add the reason I have Interstate and Other Freeway separated is because interstates are part of a national system (thus more important) and other freeways might be built to lower standards. —]] 18:09, 2 September 2006 (UTC)

:# No objections here.
:# Probably not. We don't want to make the maps too complicated to make.
:# Looks sharp! I like it, personally.
:# We should only do that if the map has a zoom level small enough that would show these roads.
:# Your point makes perfect sense regarding expressways. Also, I'll create a map for ] in the next hour or so for critiquing. --] <sup>] - ]</sup> 18:35, 2 September 2006 (UTC)

::OK, maybe it wasn't an hour, but here it is.
::]
::The black lines are county roads. Red lines are state-maintained roads. NY 441 is blue as it is an expressway in the viewpoint above. --] <sup>] - ]</sup> 01:26, 3 September 2006 (UTC)
:::Good, except expressway/divided highway is purple on my legend, not blue. ;) Maybe I should change that; purple and blue could be easily confused. Would yellow work? —]] 05:49, 3 September 2006 (UTC)

::::I dunno, I've never associated yellow with expressways personally. Orange could definitely work, if we give green to toll roads. --] <sup>] - ]</sup> 16:41, 4 September 2006 (UTC)
:::::What would we do for Other Freeway then?—]] 19:23, 4 September 2006 (UTC)
::::::I'd say abolish it. Maybe I'm misunderstanding something, but I don't see the difference between an expressway and an "other freeway". --] <sup>] - ]</sup> 20:51, 4 September 2006 (UTC)
:::::::Ah, I forgot about the ambiguity of the word "expressway". By freeway, I mean something resembling an Interstate, full access control, all that good stuff. By ], I'm thinking of a fast, divided, four-lane road with at-grade intersections. —]] 01:56, 5 September 2006 (UTC)
I like the thick blue line = Interstate, thin blue line = other freeway idea. For divided highway/expressways? I'll favor orange for both, with interchange circles where necessary. The detail on the New York Map above is more than I would have expected; it looks nice. Keep in mind we may not know the exact nature of every road in the country, so I'd also include thick and thin red for arterial and minor "undivided or I-don't-know" options. But I like the balance of blue (about 20% of all lines), red (65%), orange (10%) and green (5%) for the maps. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 18:23, 5 September 2006 (UTC)

== Integrating into project tags ==

I've posted some code on the main pages of both the Maps Task Force and Assessment on how to integrate article talk pages into the Maps Task Force and Assessment projects. See ] for a working example. Statistics should be on the Assessment page by tomorrow. &mdash;] <span style="font-size:x-small">(</span>]<span style="font-size:x-small">)</span> 15:56, 31 August 2006 (UTC)

Latest revision as of 01:32, 6 August 2024

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 
This project page does not require a rating on Misplaced Pages's content assessment scale.
It is of interest to the following WikiProjects:
WikiProject iconU.S. Roads
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
 
The maps task force asks that all map requests be left on the requests page and not on this page. Your cooperation is appreciated.

Help!

I created KML data for this draft, Draft:Capitol Highway, in the References section, and converted it to GeoJSON, but upon loading, it just throws an error. How can I fix this? thetechie@enwiki: ~/talk/ $ 19:33, 1 June 2024 (UTC)

Never mind, I figured it out. thetechie@enwiki: ~/talk/ $ 21:34, 1 June 2024 (UTC)
Uploading GeoJSON to Misplaced Pages in raw form has been dying a slow death for years now- the preferred method these days is uploading to Commons under a Data:_____.map page and calling it using a ‘from’ parameter in the template BMACS1002 21:41, 1 June 2024 (UTC)
The upside to putting the map data on Commons is that it's reusable on other editions of Misplaced Pages, or even the AARoads Wiki. M-6 (Michigan highway) and M-6 (Michigan) use the same map file on Commons, for instance. Imzadi 1979  21:55, 1 June 2024 (UTC)
Categories: