Wikipedia:Featured list candidates/List of Maryland state highways/archive1
- The following is an archived discussion of a featured list nomination. Please do not modify it. Subsequent comments should be made on the article's talk page or in Wikipedia talk:Featured list candidates. No further edits should be made to this page.
The list was not promoted by User:The Rambling Man 08:07, 1 July 2008 [1].
A list of all the state highways in Maryland, with a sortable table of their lengths, endpoints and the counties they pass through. The table may need to be split, but it may help to see what people here think of it. Otherwise, I think it may meet the requirements for featured list. Of course, any concerns will be addressed. - Algorerhythms (talk) 02:00, 13 June 2008 (UTC)[reply]
Comments
- Remove bold formatting or the link from the bold text, per WP:LEAD.
- Add a section to the table, perhaps named "Maryland state highways"
- "External links" section goes after "References" section.
Gary King (talk) 05:16, 13 June 2008 (UTC)[reply]
- Done. - Algorerhythms (talk) 13:53, 13 June 2008 (UTC)[reply]
Some more comments:
- Format the references per WP:CITE/ES, preferably with {{cite web}}. Be sure to include accessdates as well.
Gary King (talk) 07:40, 1 July 2008 (UTC)[reply]
- Comments
- It looks good. One thing though, how can the western/eastern terminus be verified? Is there a main reference for that, if not, one should be provided to verify it.SRX--LatinoHeat 15:22, 13 June 2008 (UTC)[reply]
- For most of the termini, I simply took them from the Wikipedia article (these can be verified using the MDSHA Highway Location Reference), and for the ones that don't have Wikipedia articles, I simply used the HLR. - Algorerhythms (talk) 15:33, 13 June 2008 (UTC)[reply]
- I added the reference tag to the column header to make it clear that that's the reference for the termini. - Algorerhythms (talk) 15:35, 13 June 2008 (UTC)[reply]
- If you are using the same ref for all of the table, you should make a row just for the source at the bottom of the table, like it is in this table.--SRX--LatinoHeat 16:20, 13 June 2008 (UTC)[reply]
- Done. - Algorerhythms (talk) 16:28, 13 June 2008 (UTC)[reply]
- If you are using the same ref for all of the table, you should make a row just for the source at the bottom of the table, like it is in this table.--SRX--LatinoHeat 16:20, 13 June 2008 (UTC)[reply]
- What happened to the Interstates and U.S. Routes? These are state highways, since the state maintains them. The title should probably be "list of state highways in Maryland". The capitalization in the headers is a bit off. --NE2 17:53, 13 June 2008 (UTC)[reply]
- Interstate and U.S. highways already have their own page. "State highways" in this sense refers to highways that are part of the state-numbered system, so U.S./Interstate highways are not included in this list. There really isn't anything wrong with the title, several other lists are titled this way (List of Maryland state parks, List of Maryland state symbols, List of Maryland state prisons, and List of Maryland state forests to name a few), the title is just a matter of preference. As for the capitalization of the headers, do you mean that the column headers are supposed to be lower case like section headers? If that's the case I'll go ahead and fix that.-Jeff (talk) 01:55, 14 June 2008 (UTC)[reply]
- If you're not going to include Interstates or U.S. Routes, the title and text should be changed to make it clear that it's state-numbered highways. --NE2 04:07, 14 June 2008 (UTC)[reply]
- I initially added the Interstates to the list with the intent to also add the U.S. Routes, but removed the Interstates after seeing Jeff's post. I can add them back, but for now I'll wait to get more input. One possibility, though, could be to put the Interstate and U.S. Routes tables on the List of numbered highways in Maryland (which might be a better solution, considering the List of Maryland state highways is already very large.) - Algorerhythms (talk) 03:58, 14 June 2008 (UTC)[reply]
Why is only one former state highway listed?Never mind - why does only one have the date it was deleted, and how did you determine which were "notable"? Also, what did you do for routes like MD 765 that are (a) unsigned and (b) don't have only two termini? --NE2 04:04, 14 June 2008 (UTC)[reply]
- Currently, whether a highway is signed isn't marked in the table (tracking down that information would take some work, though it is possible). For routes that have many segments, the longest segment was used. - Algorerhythms (talk) 04:09, 14 June 2008 (UTC)[reply]
- So some of the lengths, such as for MD 18, are shorter than the actual signed length? --NE2 04:10, 14 June 2008 (UTC)[reply]
- I'll have to check them, but as far as I know, the lengths are correct except for MD 648, for which the length of the longest section is used. For the termini, though, I used the longest section for each of the segmented routes. - Algorerhythms (talk) 04:33, 14 June 2008 (UTC)[reply]
- MD 18 doesn't use the longest section, which appears to be 18B from Castle Marina Road to US 50. --NE2 04:48, 14 June 2008 (UTC)[reply]
- This has been changed. - Algorerhythms (talk) 00:20, 26 June 2008 (UTC)[reply]
- Shouldn't the length agree with the termini listed? --NE2 02:31, 27 June 2008 (UTC)[reply]
- Fixed. - Algorerhythms (talk) 02:56, 27 June 2008 (UTC)[reply]
- OK, now you might see where I was going; the route listed is shorter than what is actually signed. This does not seem to be useful to the reader. --NE2 03:34, 27 June 2008 (UTC)[reply]
- Ok, the signed multisegment highways (MD 7, MD 18, MD 144, and MD 648) now all have the total signed length in the length column, the western terminus of the westernmost segment in the west terminus column, and the eastern terminus of the easternmost segment in the east terminus column. - Algorerhythms (talk) 13:40, 27 June 2008 (UTC)[reply]
- OK, now you might see where I was going; the route listed is shorter than what is actually signed. This does not seem to be useful to the reader. --NE2 03:34, 27 June 2008 (UTC)[reply]
- Fixed. - Algorerhythms (talk) 02:56, 27 June 2008 (UTC)[reply]
- Shouldn't the length agree with the termini listed? --NE2 02:31, 27 June 2008 (UTC)[reply]
- This has been changed. - Algorerhythms (talk) 00:20, 26 June 2008 (UTC)[reply]
- MD 18 doesn't use the longest section, which appears to be 18B from Castle Marina Road to US 50. --NE2 04:48, 14 June 2008 (UTC)[reply]
- I'll have to check them, but as far as I know, the lengths are correct except for MD 648, for which the length of the longest section is used. For the termini, though, I used the longest section for each of the segmented routes. - Algorerhythms (talk) 04:33, 14 June 2008 (UTC)[reply]
- So some of the lengths, such as for MD 18, are shorter than the actual signed length? --NE2 04:10, 14 June 2008 (UTC)[reply]
- As for the dates that the former routes were deleted, Jeff has taken care of that - the dates are left out on all of them, making the former routes consistent. - Algorerhythms (talk) 04:29, 16 June 2008 (UTC)[reply]
- I'm unable to sort by any columns but the first because of the "source" row. --NE2 04:10, 14 June 2008 (UTC)[reply]
- I was unable to find a way to get sorting to work with that row (class=sortbottom and class=unsortable both didn't work), so I took the row out. - Algorerhythms (talk) 04:33, 14 June 2008 (UTC)[reply]
Three comments:
- IMHO, the end of the second paragraph seems to make some claims that probably need to be referenced, but that could just be me. I'm wavering back and forth as to whether it's common sense or not. If you're seeking featured status, it's probably better to be safe than sorry though.
- Also, the third paragraph doesn't seem to be applicable. Is it a holdover from an old format? For example, it says that the higher numbered unsigned highways are listed only if they're notable. What makes MD 963 – a 0.01-mile section of pavement that doesn't intersect any other highways – notable?
- Speaking of 0.01-mile highways, at the end of the list, you appear to have added an extra digit of precision to the kilometer conversion for the "baby" routes. Any particular reason why? I notice that the source listed gives the mileposts to 3 digits, although I suppose this is questionable since 99% of the time, the thousandths digit is 0.
-- Kéiryn (talk) 17:47, 14 June 2008 (UTC)[reply]
- The third paragraph is a holdover from an earlier format and can be removed. As for the extra digits in the kilometer figures, the convert template seems to be adding those for the numbers that are less than 0.10 km. I'm not sure how to fix that. In addition, I've added a couple references to the first paragraph. - Algorerhythms (talk) 18:06, 14 June 2008 (UTC)[reply]
- See Template:Convert/doc#Rounding. Basically you can force it to two decimal places by adding another unnamed parameter, i.e.
{{convert|0.03|mi|km|2}}
→ 0.03 miles (0.05 km). -- Kéiryn (talk) 18:52, 14 June 2008 (UTC)[reply]- Fixed. - Algorerhythms (talk) 18:57, 14 June 2008 (UTC)[reply]
- See Template:Convert/doc#Rounding. Basically you can force it to two decimal places by adding another unnamed parameter, i.e.
Resolved comments from Matthew
Comments
- Can a map of the state highways be made, as is in List of Interstate Highways in Texas, a Featured List passed not long ago?
- This can be done, though it might take a while since the State Highway Administration doesn't (as far as I know) provide GIS data for the state highways.
- Needs a more engaging opening sentence, rather than "Below is a list of Maryland state highways...", which is simply a copy of the article's title
- How does it look now? (I seem to remember copying the original wording from List of Interstate Highways in Texas.)
- There's no need to sort the counties, as where more than one county is listed, only the first county sorts
- Done.
- Inconsistencies with capitalisation: "Road end near Potomac River", "road end near Berlin". "End of state maintenance at Love Point", "end of state maintenance at Assateague State Park". "Dead End", "Dead end". "DC Border", "DC border"
- I've fixed some of the ones I've found; if there are any I missed I can fix those, too.
- "Baltimore County", and "Garrett", "Allegany", "Somerset"
- This was done to avoid confusion between Baltimore County, Maryland, and the city of Baltimore, Maryland, which is separate from the county. I suppose I could add "County" after "Garrett," etc. to make it consistent.
- Changed for consistency. - Algorerhythms (talk) 00:34, 26 June 2008 (UTC)[reply]
- Navbox templates should be at the very end of the article, after external links
- Done.
- Too many redlinks
- The redlinks to villages that don't have articles can be removed, though a lot of the redlinks are state highways that don't yet have articles.
- "Source:Maryland State Highway Administration, Highway Location Reference, 2005" should be listed in the references
- Done.
- Take a look at Texas Interstate Highways. It may not be suitable for a list of this size, but it has a description column instead of just a terminus
- I had considered this, but decided that doing this for several hundred highways seemed impractical. - Algorerhythms (talk) 03:37, 23 June 2008 (UTC)[reply]
Oppose
- In the Western/Southern terminus column: "Old Marlboro Pike", "Colebrooke Drive", "Hill Road", "Rousby Road", "Dead end", "Beginning of state maintenance in Grays Inn Creek"
- Eastern/Northern terminus column: "End of state maintenance", "Middlebrook Road", "Chase", "End of Road", "Granny Branch Road", "Dead end".
- None of these are helpful to the reader. None, expect for Chase say which town/city, and Chase doesn't give any cross-streets.
- I've fixed the ones that I've found. If I missed any, point them out.
- I suggest this is looked over by the folks at WP:WikiProject U.S. Roads, and taken to WP:PR.
- Well, two of the reviewers here are ediors at USRD, in any event. - Algorerhythms (talk) 01:11, 27 June 2008 (UTC)[reply]
Matthewedwards (talk • contribs • email) 03:56, 26 June 2008 (UTC)[reply]
- The above discussion is preserved as an archive. Please do not modify it. No further edits should be made to this page.