Wikipedia

Wikipedia:WikiProject Highways/Assessment/A-Class Review/2014

< Wikipedia:WikiProject Highways | Assessment | A-Class Review
Latest comment: 8 years ago by Rschen7754

Ontario Highway 71

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Toolbox

Ontario Highway 71 (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: Highway 71 is an important highway in northwestern Ontario that connects Highway 11 and Highway 17. The highway was a substantial undertaking in the 1930s and as such has a rich history. I feel the article details the highway in a well written, well sourced and comprehensive manner, making it an ideal candidate to promote to A-Class.
Nominated by: Floydian τ ¢ 20:30, 11 July 2013 (UTC)
First comment occurred:

Review by TCN7JM

Review by TCN7JM

I can probably review this article either tonight or tomorrow night. TCN7JM 02:55, 13 July 2013 (UTC)

Well...five days later, here we are. Anyway, I do have a few comments.

  1. For A-class, it would be really great if we could get a map.
  2. In the Route description, you should mention which highway is on the other side of the bridge at Fort Frances and, for more detail, which state it crosses into.
  3. The lead paragraph of the History section needs at least one source.
  4. "The old routes were decommissioned on February 8, and the new route designated on March 10, 1954." Seeing as you mention 1953 in the previous sentence, and that February 8 doesn't have a year after it, this might be confused to mean February 8, 1953, although I'm pretty sure from reading it's supposed to be 1954.
  5. When was the Sioux Narrows Bridge rebuilt as a steel structure? As it is part of the highway, this is important for the history.
  6. Those periods shouldn't exist in the RJL for US Routes. As far as I know, only Arkansas does that.

That's about it for me. I myself copyedited one thing and fix a couple of typos and punctuation mistakes. This will be left on hold. TCN7JM 19:08, 18 July 2013 (UTC)

  1. Working on this. Unfortunately I have to trace about 200 km of Highway 17 and 100 km of Highway 11 to make the map, so it may take some time. I'm hoping other reviewers will continue to review in the absence of this and I will have it ready by the time the third review is complete with any luck.
  2. Done
  3. This is just a summary of the section to follow. As with an essay, the next paragraphs cover the information in detail with sourcing
  4. I added "several weeks later" to clear that up
  5. Yeah it is the major event in the history of the highway too.
  6. Hopefully the current discussion will clear that up, as Ontario shares a land border with Minnesota, Michigan and New York; I like it without them, but most of all want consistency within road articles, rather than with state signage. I've used them because the article itself uses them in its title.
-- Floydian τ ¢ 05:42, 3 December 2013 (UTC)

Support TCN7JM 05:14, 3 January 2014 (UTC)

Review by Rschen7754

Review by Rschen7754

I can take the second review, though it may be a while. --Rschen7754 09:54, 3 December 2013 (UTC)

Preliminary notes
  • Ref 16 has an error.
  • Map? (I know it was noted above...)
Route description
  • Not sure that repeating the length again when it was just in the lead is good, especially since it uses a different level of precision.
  • ... suddenly?
  • the road continues south as U.S. Route 71 in Minnesota, to Chapple. - please use US 71 :P
  • travel concurrently north -> travel north concurrently?
History
  • What is a "premier"?
  • mid to late 1950s - check MOS to see if there are hyphens needed.

Should be a support once these issues are addressed. --Rschen7754 03:26, 13 December 2013 (UTC)

  • Ref 16 fixed, and map is sooncoming (lots to do, but I understand it will likely be the final thing to have this ACR pass.
  • Removed redundant length, fixed wording. As for the U.S. vs US issue, has anything come of the discussion on standardizing this (I notice no further comments have been posted for about three weeks)? I would like to use US 71, but thus far I've used the term used by the article itself.
  • Premier linked to Premier of Ontario, the equivalent (IIRC) to the governor of a state. Hyphen issue raised at WT:MOS
-- Floydian τ ¢ 07:35, 13 December 2013 (UTC)

Review by Dough4872

Review by Dough4872

I will do the third review. Dough4872 01:11, 4 December 2013 (UTC)

Comments:

  1. In the infobox, you should note the communities at the end of the ON 11 concurrency.
  2. In the infobox, lead, and Route description, you should mention that ON 71 also connects to US 53 at the US border (you do in the Major intersections).
  3. The second paragraph of the lead appears to be out of chronological order.
  4. The sentence "The highway begins at the international bridge in Fort Frances; within the United States, the road continues south as US 71 in Minnesota, to Chapple" sounds confusing. It seems to imply that US 71 heads south to Chapple. Yet Chapple is 58 kilometers from the border crossing on ON 71. I would remove "to Chapple" as it does not seen relevant here and I would mention Chapple in the right part of the route description where ON 71 serves it.
  5. "old Cloverleaf Trail", is old an adjective describing the trail or is it a part of the formal name? If the latter, it should be capitalized.
  6. When was the Sioux Narrows Bridge rebuilt as a steel structure?
  7. As discussed with ON 61, the entry for the southern terminus at the US border crossing should be fixed. The format used for ON 61 is a good idea. Dough4872 03:21, 14 December 2013 (UTC)

@Floydian and Dough4872: - Floydian, are you going to address these items? --AdmrBoltz 17:33, 30 December 2013 (UTC)

  1. Done
  2. Done
  3. It's supposed to be that way. I find that wording is the best way to cover the whacky history in a few sentences.
  4. Done
  5. Old is an adjective, as there is no recognition that the trail existed now, only in history books.
  6. Added some info on this
  7. Done... though I still feel what I had looks nicer.
-- Floydian τ ¢ 01:26, 2 January 2014 (UTC)

Image review by Rschen7754

  • Fortunately the URAA stuff appears resolved *knock on wood*. The '39 image wasn't renewed by it, but the '51 image was. TCH shield template fixed, obviously the licence of the uploader is invalid. - Floydian τ ¢ 07:03, 4 January 2014 (UTC)
  Done --Rschen7754 07:05, 4 January 2014 (UTC)

Spotcheck by Rschen7754

  • Source 7: "and improved by 1885 into a wagon trail" - not seeing this in the source, or the bit about ON 602, or "As a lumber merchant, Mathieu promoted improved road access in the region."
  • Source 8: Missing "The Heenan Highway would become the first Canadian link to the Rainy River area; prior to its opening in the mid-1930s, the only way to drive to the area was via the United States." and "Nestor Falls was the northernmost point accessible by road from the Rainy River area. Heenan would become the Minister of Lands and Forests in Mitch Hepburn's cabinet."
  • Source 10: Good, but why not include the part about the jigsaw puzzle nature of it?

Spotcheck done, awaiting responses. --Rschen7754 20:32, 4 January 2014 (UTC)

  • Added a ref to fix #7 and first part of #8 issue, was another article on the same site as #7
  • Added the 1923 map to ref the northernmost point. Added a link to another legislature sessional paper showing Heenan as the Minister of Lands and Forests (and Hepburn, presumably in a lapse, as the "Prime Minister of Ontario")
  • Added the bit from source 10
- Floydian τ ¢ 23:48, 5 January 2014 (UTC)
  Done --Rschen7754 23:54, 5 January 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Ridge Route

The article will remain a Featured Article. TCN7JM 04:12, 23 January 2014 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Toolbox

Ridge Route (edit | talk | history | links | watch | logs) review

Suggestion: Demote from A-Class
Nominator's comments: Actually, I don't think the article should probably be demoted, per se. There's some opportunities here to bring this article up to modern expectations of a FA for USRD. I anticipate that with a little collaboration, this article can be improved and retained in its current status.
Nominated by: Imzadi 1979 → 15:08, 17 June 2013 (UTC)
First comment occurred: 17:07, 17 June 2013 (UTC)

Comments by Dough4872

Comments by Dough4872
  1. We should add {{infobox road}} to the article to show the termini and major intersections of the route before it was bypassed.
    Done. --Rschen7754 08:24, 29 September 2013 (UTC)
  2. The lead should be expanded to provide a decent summary of a description and history of the route.
    Done. --Rschen7754 06:22, 15 December 2013 (UTC)
  3. The sentence "Near the north end of this area, the Ridge Route curves away from the newer bypass." needs a citation.
    Done. --Rschen7754 04:32, 15 December 2013 (UTC)
  4. Citation needed for the sentence "A number of establishments were located in the forest, including the National Forest Inn, Kelly's Half Way Inn, Tumble Inn, and Sandberg's Summit Hotel."
    This just sets up the next few paragraphs; don't think this is needed. --Rschen7754 03:04, 18 October 2013 (UTC)
  5. I don't see the reason for coordinates to be included in the prose. We do have a KML for the article.
    Done. --Rschen7754 06:23, 6 July 2013 (UTC)
  6. The sentence "2 miles (3 km) north of the National Forest Inn is Serpentine Drive (34.639°N 118.719°W), where the road curves around the sides of hills as it climbs out of a low point in the route (about 3200 feet/1000 m above sea level)" should be reworded so it does not begin with a numeral.
    Done. --Rschen7754 23:48, 29 June 2013 (UTC)
  7. Citation needed for "and CR N2 uses the old Ridge Route to reach State Route 138 near Quail Lake."
    Fixed. --Rschen7754 09:31, 16 September 2013 (UTC)
  8. The Construction section seems out of order. It talks about the road opening in 1915 then mentions the designation as US 99 in 1926 before jumping back to 1917 where it mentions the road being paved.
    I don't think such a brief deviation is an issue; histories do that all the time, even on recent FAs. --Rschen7754 21:18, 6 September 2013 (UTC)
  9. The third paragraph of the Bypasses and the fate of the bypassed road section needs citations.
    Done. --Rschen7754 04:22, 15 December 2013 (UTC)
  10. There seem to be too many pictures in the article, leading to clutter. Some of them may need to be removed.
    Done. --Rschen7754 03:03, 18 October 2013 (UTC)
  11. A junction list should be added to the article, listing major junctions and possibly points of interest along the route.
    I'm a bit skeptical about this - I'm personally not a huge fan of junction lists for roads that no longer exist. --Rschen7754 07:00, 18 June 2013 (UTC)
    I must disagree. If an accurate junction list can be made of major roads when it was open, then it should definitely be added. TCN7JM 07:02, 18 June 2013 (UTC)
    But where would the mileages come from? Or the locations, for that matter, since city boundaries change? --Rschen7754 07:03, 18 June 2013 (UTC)
    Mileages are unneeded if none can be found, as I'd say that's nearly impossible for a road of this type, but is it not possible to write a note at the top of the junction list that says that the location are from the time the route was open? (Or just before it closed?) TCN7JM 07:05, 18 June 2013 (UTC)
    Done for major junctions. --Rschen7754 08:24, 29 September 2013 (UTC)
  12. The article heavily relies on the book from Scott. Are there any other sources that can be used?
    I have some articles, as well as part of a Wikisource article; I hope to work on this soon. --Rschen7754 10:59, 16 November 2013 (UTC)
    I have now added some material. --Rschen7754 05:59, 15 December 2013 (UTC)
  13. There are page numbers that are needed for some of the newspaper articles. Dough4872 17:07, 17 June 2013 (UTC)
    Page numbers added. --Rschen7754 21:55, 6 September 2013 (UTC)
I agree with most of the above. It's all pretty minor stuff, even the addition of a junction list is a minor task. Just to note, after I opened this, I pinged the editor who nominated the article at FAC in 2007, and I received this reply. I would not expect any assistance from those quarters on this effort. Imzadi 1979 → 18:02, 17 June 2013 (UTC)

Note: I still plan to work on this, perhaps later this summer. --Rschen7754 04:25, 13 August 2013 (UTC)

Just a quick observation here... I was working on a personal project related to the lengths of roads with FAs... this article doesn't seem to give the length of the Ridge Route anywhere. Surely any article on a road should have some indication of its length. Imzadi 1979 → 18:38, 13 August 2013 (UTC)
Sure, but the modern-day length of what is left of the road is all that is available, to my knowledge... --Rschen7754 07:43, 17 September 2013 (UTC)
Found approximate figures. --Rschen7754 08:24, 29 September 2013 (UTC)
@Dough4872: Could you strike the ones that you think are good to go? Thanks. --Rschen7754 03:20, 30 September 2013 (UTC)
Struck resolved issues. Dough4872 04:05, 3 October 2013 (UTC)
@Dough4872: All done now. --Rschen7754 06:22, 15 December 2013 (UTC)

@Imzadi1979: Since you nominated this, were you planning to review it? --Rschen7754 22:56, 15 December 2013 (UTC)

Review by Admrboltz (including an image review)

Comments by Admrboltz
  1. There is a dead link.
    Fixed. --Rschen7754 09:12, 5 January 2014 (UTC)
  2. File:Map_of_USA_Ridge_Route.svg does not match our current map standards. This should be replaced with a current standard map. (GFDL/CC-BY-2.0/CC-BY-SA-1.0, 2.0, 3.0)
    Done. --Rschen7754 00:10, 6 January 2014 (UTC)
    The map you've replaced it with needs a locator inset, as if I didn't know where that was I'd be confused. --AdmrBoltz 00:17, 6 January 2014 (UTC)
    Now done. --Rschen7754 00:22, 6 January 2014 (UTC)
  3. File:Ridge route map LATimes.png (PD-US-1923)
  4. File:Ridge Route National Forest Inn steps.jpg (PD-User)
  5. File:Ridge Route Swede's Cut.jpg (PD-User)
  6. File:Beale's Cut 1872.jpg (PD-US-1923) -- I am not so sure on this one. It was snapped in 1872, but their comment says that only unpublished works before 1923 are eligable for the 120+ year after death clause. This image may need to be removed.
    [1] says the author passed away in 1977. Also according to that page, the majority of the images were unpublished, so unless we can find proof that it was published, it's probably not good. I'm pulling it from the article pending resolution. --Rschen7754 01:50, 6 January 2014 (UTC)
    According to Rschen's link, there were about 1000 images in a private collection and someone started publishing about 250 of them from 1981 to 1996. The images that that the Santa Clarita Valley Historical Society obtained in 1996 (of which this is one) were among the ~750 that were not published (note that the collection owner is not the author—the photo was taken before he was even born). It's possible that the photo was published before it became part of the collection. If that's true, then the pre-1923 rule is in effect. Otherwise, it wasn't published and the 120-year-after-creation rule applies. Thus, PD either way. —howcheng {chat} 05:38, 6 January 2014 (UTC)
    Okay, got it. I'm okay with restoring this photo to the article, but I'll wait for Admrboltz to comment. --Rschen7754 05:44, 6 January 2014 (UTC)
  7. File:Ridge Route ca 1920 4.jpg (PD-Old (depreciated)) -- Image is from the 20s, however the creator is not credited, so we do not know when the creator died. The book was written in 1920, so if the book writer holds the copyright its eligible for PD-US-1923.
    I looked at the PDF of the entire book, and see no credits anywhere. However, archive.org is hosting the entire book as not in copyright... --Rschen7754 09:38, 5 January 2014 (UTC)
  8. File:Ridge Route ca 1920 4.jpg (PD-User)
  9. File:Lebec 1943.jpg (Fair Use) -- Does this image really help the article?
    I personally think that should be Template:PD-CAGov as no copyright is asserted, including at [2] - does this sound okay? --Rschen7754 09:38, 5 January 2014 (UTC)
    I am good with that. Send it off to Commons and CSD it here. --AdmrBoltz 16:51, 5 January 2014 (UTC)
    Now done. --Rschen7754 18:37, 5 January 2014 (UTC)
  10. File:Dead-Man's Curve in Lebec, California, 2010.jpg (Self - GFDL/CC-BY-SA-3.0)
  11. MOS wise, there are images on both sides of the page squishing text, which is to be avoided per MOS:LAYOUT#Images.
    Removed the image that did that. --Rschen7754 22:18, 5 January 2014 (UTC)
  12. Do we need a citation in the lead? Can we move the citation into prose?
    Moved. --Rschen7754 09:19, 5 January 2014 (UTC)
  13. There are a lot of hard-coded conversions, these should use {{convert}} or {{convert/spell}}
    Fixed. --Rschen7754 03:42, 6 January 2014 (UTC)
  14. There are costs listed in the article, {{inflation}} values would be appropriate.
    Fixed. --Rschen7754 03:42, 6 January 2014 (UTC)
  15. Are all the external links needed? Maybe just the first one, but I don't really see the others as being needed.
    Removed one, but the others provide additional media. --Rschen7754 18:52, 4 January 2014 (UTC)
    All done; still waiting for clarification on the image, but with it removed in the interim, it's not that consequential. --Rschen7754 03:42, 6 January 2014 (UTC)

Comments by Floydian

Comments by Floydian

Overall, this is pretty up to par. However, I noticed a few issues:

  • "The road enters the Angeles National Forest about one mile (1.6 km) south of Templin Highway,[14] with the Forest Service road designation 8N04. A number of establishments were located in the forest, including the National Forest Inn, Kelly's Half Way Inn, Tumble Inn, and Sandberg's Summit Hotel."
    • The last part of this paragraph needs citations. In addition, it is very short, but it looks like it would merge seamlessly with the next paragraph.
      • Moved the cite, but the last sentence sets up the next few paragraphs and doesn't need a cite. Nevertheless, I've moved it to the next paragraph.
  • The paragraphs beginning "Kelly's Half Way Inn was roughly halfway..." and "The Tumble Inn..."
  • "This Ridge Route Alternate or Ridge Alternate Highway[50]..."
  • "It turned out that the county officially owned it but did not maintain it; Scott had since convinced the county and forest to exchange ownership with the Santa Anita Canyon Road, then a county road.[54]"
  • Major intersections vs. Infobox
    • Why is SR 126 listed as the southern terminus but US 99 as the southernmost "junction" in the table? The KML leaves some mystery to this, but I'm assuming this has to do with the route US 99 took back in those days, which I-5 generally follows but not in the case of, for example, Grapevine Road at the northern terminus.
-- Floydian τ ¢ 02:08, 23 January 2014 (UTC)
All done. --Rschen7754 03:49, 23 January 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Great Eastern Highway

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
This article was promoted to A-Class. TCN7JM 08:03, 26 January 2014 (UTC)
Toolbox

Great Eastern Highway (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: Great Eastern Highway is the first section of the major road link between Perth and Adelaide, and part of Australia's National Highway system. The article on the 590-kilometre-long (370 mi) highway is quite substantial, has recently passed its GA nomination, and is the next article I would like to take to FAC. It is also the first High-importance AURD article to be nominated for A-class.
Nominated by: Evad37 [talk] 07:36, 29 November 2013 (UTC)
First comment occurred: 04:09, 2 December 2013 (UTC)

Review by Dough4872

Review by Dough4872

Comments:

  1. In the lead, why is "Great Eastern Highway" italicized?
    Unitalicized. I don't remember exactly what I was thinking when I used italics, but after checking the MOS, there's no need for italics. - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  2. "with the whole highway sealed by 1953", what does it mean for the highway to be "sealed"?
    Linked sealed to chipseal - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  3. "in Perth's east" sounds awkward, I would suggest changing this to "the eastern part of Perth".
    Changed. Perhaps not the best wording, but I can't think of anything better at the moment. - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  4. In the lead and infobox you mention part of the Great Eastern Highway is Alternate National Route 94. You should mention it again in the second paragraph of the route description when you are discussing the allocation of the highway.
    Added - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  5. What is a "lopped ramp"? Is this supposed to be "looped ramp"?
    Fixed typo - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  6. In many places, you refer to it as "Great Eastern Highway". Shouldn't you refer to it as "the Great Eastern Highway"?
    I don't think it's actually required, as its not part of the road name. And I've been told in previous reviews to be consistent with using or not using the direct article (the) when mentioning highways. Leaving it out for all roads and highways is less awkward than putting it in all for all of them. - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  7. "three point five kilometres (2.2 mi) east" sounds awkward, it should be "3.5 kilometers (2.2 mi) east".
    Changed. Seems {{convert/spell}} doesn't spell 3+1/2|km as "three and a half kilometres". -Evad37 [talk] 09:06, 2 December 2013 (UTC)
  8. "lonely scrubland" does not sound right. I would get rid of the word lonely here.
    Removed - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  9. Is it just speculation that a convict road was built in the 1860s or is it a known fact?
    Ref #17 ("Gt Eastern Highway's secret" video) says it was built in 1867, but Ref #16 ("Convicts' early roadworks unearthed") says "Thought to have been built by convicts in 1867, the road gives an insight into WA's convict history and early infrastructure" and Ref #19 (State Heritage Office "Convict road unearthed") says it was 145 years old, ie 1867, but later on says "Initial indications showed that the road was likely to have been constructed by convict labour in 1867". - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  10. Again, seeing the use of italics in the history.
    Removed as per #1 - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  11. The sentence "In 1994, the federal government approved a $43.9 million project to upgrade substandard section between Northam and Southern Cross." has verb agreement issues.
    Adjusted - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  12. In the Bypasses section, I would remove the link to Australian dollar as it is of little value and is not used elsewhere in the article.
    Removed - Evad37 [talk] 09:06, 2 December 2013 (UTC)
  13. Why are the bridges over the Helena and Avon rivers included in the Major intersections? Generally only bridges with articles are included. Also the formatting for both bridge crossings is inconsistent. Dough4872 04:42, 2 December 2013 (UTC)
    MOS:RJL lists "major water bodies" as items to include, so they are included based on the notability and significance of the rivers. I change the second one to also use {{Jctbridge}}. - Evad37 [talk] 09:06, 2 December 2013 (UTC)

Review / Image review by Admrboltz

Review by Admrboltz

References

  • Ref 18 (Gt Eastern Highway's secret (info)) doesn't seem to work for me.
    Then it's probably region-locked to Australia, because it is working for me - Evad37 [talk] 17:32, 24 December 2013 (UTC)
  • Your map references should have scales indicated.
    Added the scale for Ref 58 (Plan for the Metropolitan Region). The others don't specify a scale in numbers, they just have scale bars - presumably because with computer files, the scale varies based on your zoom level, or the paper size you print it out on. Same with Google maps, they don't have a fixed scale. - Evad37 [talk] 03:36, 25 December 2013 (UTC)
    Its something Imzadi1979 (talk · contribs) and I have discussed on IRC lately. You can either do "Scale not given" for your maps that just have the bar or either measure your screen with the pdf at 100% resolution or print the legend at 100% resolution then work out the scale fraction from there. Google Maps does not need a scale defined. (@Imzadi1979: - Might be worth noting on the Google Maps/Bing Maps/Yahoo Maps template documentation that scale is not needed.) --AdmrBoltz 06:22, 25 December 2013 (UTC)
    Seeing I was mentioned here, I'll just briefly comment. Of the two citation styles (Chicago Manual of Style, MLA) I used in my college classes this past semester, neither gave specific citation formats for maps. However, when looking up formats, various university websites did give citation formats for maps in Chicago, APA and MLA, and in all cases I found, "Scale not given" or a scale was listed for fixed maps. For dynamic scaled maps, like Google, etc, nothing was indicated. (As for the Google/Bing/Yahoo templates, they can't be given a scale anyway.) Imzadi 1979 → 06:51, 25 December 2013 (UTC)
  • Overlinking in your references (only the first instance of a newspaper needs to be linked, etc)
    Fixed - Evad37 [talk] 00:50, 27 December 2013 (UTC)
  • You have CS1 errors - these are mostly the use of seperate Month and Year fields (should use a unified date field) or coauthors.
    Fixed - Evad37 [talk] 04:19, 25 December 2013 (UTC)

Prose

  • "a river crossing into Perth's CBD (central business district)" - typically abbreviations are spelt-out first then put into () after > Perth's Central Business District (CBD).
    Changed - Evad37 [talk] 14:16, 26 December 2013 (UTC)
  • Typically, but not always, speed limits are left out of USRD articles as its a bit trivial and borders on Wikipedia is not a Travel Guide.
    WP:NOTEVERYTHING says "Verifiable and sourced statements should be treated with appropriate weight". I think that including a brief mention, in general terms, of the main speed limit zones is useful encyclopaedic information, and approriately weighted to the size of the article. It allows readers to see which parts are low speed/medium speed/high speed – without listing every single sections speed limit and each change point. (Also, lots of stuff in road articles comes somewhat close to one or more of the WP:NOT examples – RJLs, traffic volumes, dual/single carriagway, etc – but are still included, with an appropriate level of detail) - Evad37 [talk] 14:16, 26 December 2013 (UTC)
    Fair enough. --AdmrBoltz 14:27, 26 December 2013 (UTC)
  • With units under 10 (e.g. 2.1 km, etc), you should be using {{convert/spell}} and not {{convert}}, which will spell out the units.
  • "where the highway encounters a steep[note 1]" - why is this a foot note and not just in the prose?
    Integrated into prose. I originally put it in as a footnote because it is more of a technical detail, and I thought the prose flowed better that way. - Evad37 [talk] 14:16, 26 December 2013 (UTC)

Images

Otherwise, looks good. --AdmrBoltz 16:46, 24 December 2013 (UTC)

Thanks for your review, I'll be replying over the next couple of days - Evad37 [talk] 17:32, 24 December 2013 (UTC)
Review by Rschen7754
Infobox
  • Opened 1860s - source?
    Added a ref from the Convict-era road section - Evad37 [talk] 01:32, 12 January 2014 (UTC)
  • The "Major settlements" wide label makes the second column too narrow on small screens. Is there anything that can be done about this?
    I had a look at the difference between "Major settlements" and just "Major", and there's really not much in it. On Windows 7, regardless of window size, Firefox showed no difference, and Chrome and IE only had a 12 pixel difference in width. Everything that is currently going onto two lines would still be on two lines. - Evad37 [talk] 01:32, 12 January 2014 (UTC)
RJL
  • The table seems unusually crowded and dense. For example, do we need "Traffic light controlled intersection"? Also, is it possible to use abbreviations for "State Route"?
    Removed "Traffic light controlled intersection" notes. There are no official or commonly used abbreviations, and Wikipedia shouldn't be inventing abbreviations, so we are stuck with the unabbreviated form. - Evad37 [talk] 01:32, 12 January 2014 (UTC)
  • Check capitalization in the notes section - subsequent clauses should not be capitalized
    Adjusted - Evad37 [talk] 01:32, 12 January 2014 (UTC)
  • Is "T Junction" a proper noun?
    Adjusted - Evad37 [talk] 01:32, 12 January 2014 (UTC)
  • Usually we don't cite Google Maps in the table unless we're using that for the mileages. Not a deal-breaker, but it might help make the table header less cluttered.
    Removed (but if verification of the column contents is requested later, I'll put it or another source back) - Evad37 [talk] 01:32, 12 January 2014 (UTC)
References

Apologies for the delay - my time for HWY is about to decrease significantly, but I'll try and get this done...

Lead
Route description
History
Future

Review now completed. --Rschen7754 06:34, 17 January 2014 (UTC)

Spotcheck by Rschen7754
  • Source 5: Good on V and CP.
  • Source 7: Good on V and CP.
  • Source 8: Good on V and CP.
  • Source 11: Good on V and CP.
  • Source 19: Good on V and CP.
  • Source 20: Good on V and CP.
  • Source 26: Good on V and CP.
  • Source 27: Good on V and CP.
  • Source 32: Good on V and CP.
  • Source 33: Good on V and CP.
  • Source 41: Good on V and CP.
  • Source 44: Good on V and CP.
  • Source 47: Good on V and CP.
  • Source 53: Good on V and CP.
  • Source 55: Good on V and CP.
  • Source 62: scheduled/was to begin, because the article was written before the scheduled beginning.
    Added a 2007 source that specifies January 2001 - Evad37 [talk] 06:17, 26 January 2014 (UTC)
  • Source 63: will AGF here as it's in the abstract.
  • Source 72: was to begin, because the article was written before the scheduled planning.
    Adjusted wording - Evad37 [talk] 06:17, 26 January 2014 (UTC)
  • Source 73: "recent cost analysis had been undertaken" a bit too close to the source. Same with "is a federal government responsibility."
    Adjusted wording - Evad37 [talk] 06:17, 26 January 2014 (UTC)

Spotcheck done. --Rschen7754 02:52, 26 January 2014 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

The article was promoted to A-Class - Floydian τ ¢ 04:40, 25 February 2014 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Legacy Parkway

Toolbox

Legacy Parkway (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: Having just passed its Good Article Nomination, I believe that Legacy Parkway is ready for the next step.
Nominated by: AdmrBoltz 01:12, 2 January 2014 (UTC)
First comment occurred: 01:19, 2 January 2014 (UTC)

Review by Dough4872

Review by Dough4872

Comments:

  1. Why is the title of the article "Legacy Parkway" and not "Utah State Route 67"? It is common USRD practice to use the route number over the road name. See Maryland Route 200 versus Intercounty Connector.
    Per WP:NAMINGCRITERIA the highway is most commonly referred to in media as Legacy Parkway and not as SR-67. The designation is signed, but it's really more of a tracking tool than the actual name of the highway. --AdmrBoltz 01:42, 2 January 2014 (UTC)
  2. In the lead, you have the route description and history mixed. You should try to do the route description first followed by a chronological history in the lead.
    Done. --AdmrBoltz 01:42, 2 January 2014 (UTC)
  3. "The parkway begins at an incomplete interchange with I-215 in extreme northern Salt Lake County, allowing northbound motorists from the Interstate to transfer onto Legacy Parkway and vice-versa." the description of the partial movements at this interchange seem vague. I would expand upon this.
    I don't see how that is vague at all. It perfectly explains the movement. --AdmrBoltz 01:42, 2 January 2014 (UTC)
    I would perhaps mention that southbound Legacy Parkway motorists can trasnfer to southbound I-215. The "vice versa" wording may confuse readers. Dough4872 01:52, 2 January 2014 (UTC)
    Tweaked. --AdmrBoltz 03:15, 2 January 2014 (UTC)
  4. You should write more about the physical surroundings in the route description.
    There really isn't much to say about whats around it. There is the 2,000 acre wetlands to the west and some train tracks for most of the eastern side. It was built in undeveloped land. --AdmrBoltz 01:42, 2 January 2014 (UTC)
  5. "Should the parkway be extended further north, connections will be complicated due to the opening of the Farmington FrontRunner station just north of the parkway", wouldn't this sentence be more appropriate for the history?
    Moved. --AdmrBoltz 01:42, 2 January 2014 (UTC)
  6. The sentence "Original plans for the highway had included a six-lane freeway, compared to the four-lane controlled-access parkway that was built" may also better fit in the history.
    Moved. --AdmrBoltz 01:42, 2 January 2014 (UTC)
  7. "Legacy Parkway is part of the larger Legacy Highway project first proposed by then governor Mike Leavitt", shouldn't governor be capitalized?
    Done. --AdmrBoltz 01:42, 2 January 2014 (UTC)
  8. The history seems to be skewed toward the lawsuit. Maybe you should add more details about the planning and construction of the route. Dough4872 01:30, 2 January 2014 (UTC)
    The lawsuits were what made the highway notable in Utah. Yeah, its saving a bit of commute time, but it's main claim to fame was its its controversy. I have broken up the paragraph about it in the history so there is just the one paragraph about it plus the sentence in the route description. --AdmrBoltz 01:48, 2 January 2014 (UTC)
    There aren't any planning details from between the 1960s and 2001 that you can add? Any additional details about the groundbreaking (if there was a ceremony)? Dough4872 01:52, 2 January 2014 (UTC)
    With the recent gutting of the Google News archives (killing all access to old Deseret News articles and the fact that The Salt Lake Tribune only syndicates certain stories into ProQuest, I have added what I can. --AdmrBoltz 03:15, 2 January 2014 (UTC)

Image review by Philroc

  •  Y File:Utah SR 67.svg PD-MUTCD-UT
  •  Y File:Legacy parkway.png Non-free with appropriate fair use rationale
  •  Y File:Legacy Parkway map.png PD-self
  •  Y File:LegacyParkway3.jpg CC-BY 2.0

All images check out. Philroc (talk) 21:21, 28 January 2014 (UTC)

Review by Fredddie

Review by Fredddie

I'll give it a look-see. –Fredddie™ 02:54, 1 February 2014 (UTC)

Infobox and lead
  1. Nothing sticks out to me in the infobox
  2. Might want to mention in the lead that the wetlands are at the edge of the Great Salt Lake.
  3. Adding onto that, I'm not sure if the railroad is the best descriptor of what lies east of the highway. It seems like the road is the westernmost thing in the area.
  4. I'd like to see in the lead why the Sierra Club was against the road. Excuse the paraphrase, but it kinda reads "There are no trucks or billboards because Sierra Club."
  5. See the KML note in the History subsection
Route description
  1. The Utah route log says the county line is at 0.239. So it should be 1⁄4 mile (400 m) instead of 3⁄10.
  2. "The parkway then turns northeasterly and back north again, intersecting with 500 South..." Can we change "intersecting" into a present tense verb? I get uneasy when I see a comma and the first word after it ends in -ing. (see the first Pennsylvania Turnpike ACR)
  3. Is there an article for those screwy street names the Utah street name convention. If so, it might be good to link it at 500 South.
    • There isn't unfortunately. They also make perfect sense once you've lived here for more than a week ;) If this was entirely in Salt Lake County I could refer to the Salt Lake meridian but most of the route is in Davis County, and the numbering resets at county lines. --AdmrBoltz 17:01, 1 February 2014 (UTC)
  4. "The parkway continues north before beginning a curve to the northeast in West Bountiful." I don't like this sentence because if you look at the route on a map, you could argue that the curve begins at the 500 South interchange. You could say "In West Bountiful, the parkway curves to the northeast as it follows the contour of the wetlands which lie on the western side of the road." or something like that.
  5. Which do you like better?
    • "Past the intersection, the parkway parallels I-15 with Union Pacific and Utah Transit Authority (FrontRunner) railroad tracks in between."
    • "Past the intersection, Union Pacific and Utah Transit Authority (FrontRunner) railroad tracks run between the parkway and I-15 to the east."
  6. I-15 is really close, you should measure how far away it is and mention it.
  7. "The parkway, entering Farmington, gains one lane..." → "Upon entering Farmington, the parkway gains one lane..."
  8. It'd be neat if there were an article for the Weave. Obviously, I'm not going to hold it against you. I'm just thinking out loud.
    • Well... it was officially named when the highway opened and quickly forgotten about my everyone locally. Nobody uses the name despite it being its official designation. --AdmrBoltz 17:01, 1 February 2014 (UTC)
  9. I'm not sure I would mention the lawsuit in the RD; that's better suited for the history section. You could start off with "The road was designed to include extensive..." Basically start at the first comma of that first sentence.
  10. "In addition to the Legacy Nature Preserve,..." That's the first time you've mentioned the preserve by name, so you really can't say "in addition to".
  11. Another pic for the article would be nice (maybe one that is not snowy), but you knew that already.
History
  1. The first paragraph has a few issues:
    • Highway projects cannot aspire to anything, they are inanimate.
    • I don't like ", with the parkway being only a portion in between." at all. Refer back the PATP ACR for the ", with" issue, but also you already mention that the road is a part of the whole Legacy Highway project.
  2. Going back to the KML for a moment, you could roughly draw proposed corridors on there. I'd use a wide stroke (10 or 15px) with 50% transparency, just so we can visualize where the highway was proposed.
  3. What aspects of the EIS were allegedly not complete?
  4. Who opened the highway/cut the ribbon?
  5. Shouldn't you mention that it was designated a scenic byway six years before it opened?
  6. Wait, you waited until the last paragraph to mention details from the original plans?
    • Moved. That whole last paragraph was cut and pasted from the RD into the history during Dough's review. --17:28, 1 February 2014 (UTC)
  7. In the last sentence of the section, I think the shopping center is a bigger impediment than the train station.
Exit list
Looks fine
Overall
Right now, I am leaning oppose, but I could be swayed. This isn't a bad article, but I think there are some nuances that need to be addressed.
  1. The RD is written matter-of-factly, which isn't wrong, I think it lacks some color. We rag on Dough for asking to add scenery at every ACR, but he's right.
  2. If the road was truly controversial, foreseeably, the history section could be doubled in length. I know we're required to write in summary style, but some details (the completeness of the EIS, for instance) are completely glossed over.
Hopefully, this wasn't too harsh, do I see the potential in this article and could see it going all the way. –Fredddie™ 05:55, 1 February 2014 (UTC)
@Fredddie: I have responded to most of your points, mind taking a look again. --AdmrBoltz 13:40, 5 February 2014 (UTC)
I will get to it sometime today. I have been busy in the meatspace the last few days which resulted in me crashing at 7pm last night. –Fredddie™ 17:10, 5 February 2014 (UTC)
  Support Talking about the EIS adds the depth I was looking for. I do have one more thing, but obviously it's not going to hold you up. Above, you mentioned that nobody calls it the Wasatch Weave. I'd like to see that mentioned in the article and backed up by a reference. → "This interchange is officially called the Wasatch Weave, but is almost never referred to as such." But if you can't, you can't, no big deal. –Fredddie™ 21:08, 5 February 2014 (UTC)
The problem is citing that. Since its not called that... its hard to cite that its not called that :P. Though I did want it to be named the Chuck Norris Highway... The only four hits in ProQuest for the Weave are from the day or the day after the intersection was named. --AdmrBoltz 21:24, 5 February 2014 (UTC)
Figured. NBD. –Fredddie™ 21:27, 5 February 2014 (UTC)

Spotcheck by TCN7JM

Spotcheck by TCN7JM

I reviewed this article at GAN, so I'll do the spotcheck. I will start it after Fredddie's concerns are addressed. TCN7JM 21:13, 2 February 2014 (UTC)

@TCN7JM: Fredddie's review is done now. --AdmrBoltz 17:43, 10 February 2014 (UTC)
Yeah, I said yesterday on IRC I would try to get it done today, but I don't think you were around. I'll go ahead and do it in a couple hours. TCN7JM 21:14, 10 February 2014 (UTC)

Alright. As usually I'll review a quarter of the references. I can't review 6.5 refs, so I'll round up to seven. They will be, as of this revision:

  1. Source 1 –   Fine There seems to have been a typo in the infobox (said the road opened on 9/18/2008 instead of 9/13/2008), but I fixed it and now everything's alright.
  2. Source 5 –   Fine
  3. Source 6 –   Fine
  4. Source 10 –   Fine
  5. Source 18 –   Maybe you should...use Source 1 instead of this source the first time it's used. This one mentions nothing about I-15; the other one does.
  6. Source 25 –   Fine
  7. Source 26 –   Fine

I'll start on this immediately. TCN7JM 00:09, 11 February 2014 (UTC)

Now done. TCN7JM 00:49, 11 February 2014 (UTC)
Review by Rschen7754

I will take the last review. --Rschen7754 02:53, 16 February 2014 (UTC)

Preliminary checks
  • No issues.
Lead
  • near by -> nearby
  • speed and trucks - comma after
Route description
  • No issues.
History
  • 5600 West, however that -> 5600 West; however, that
  • Same for the last sentence of that paragraph.
  • Comma after Legacy Nature Preserve
  • then-governor here, but then-Governor earlier... be consistent.
  • "complicated" seems too colloquial.

Should be a support once these issues are resolved. --Rschen7754 03:02, 16 February 2014 (UTC)

Sorry, didn't notice this earlier. Will do this tomorrow night. --AdmrBoltz 02:56, 24 February 2014 (UTC)
Done with all but complicated. Suggestions on alternate phrasing? --AdmrBoltz 00:40, 25 February 2014 (UTC)
I would go into more detail. --Rschen7754 00:44, 25 February 2014 (UTC)

Support issues resolved. --Rschen7754 01:28, 25 February 2014 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Ontario Highway 402

There is consensus to promote this article to A-Class. TCN7JM 21:48, 7 March 2014 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Toolbox

Ontario Highway 402 (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: In hopes of bridging the line of Featured articles between Michigan and New York, I present Highway 402 for review! It's been a couple years since this went through GAN, so it may need tweaking. If you spot a full paragraph that seems wonky, just point out which one and I'll do a rewrite of it. Overall, however, it is high quality, comprehensive, and well sourced.
Nominated by: Floydian τ ¢ 21:18, 2 January 2014 (UTC)
First comment occurred: 03:50, 3 January 2014 (UTC)

Review by Dough4872

Review by Dough4872

Comments:

  1. Why is I-94 listed before I-69 in the infobox and exit list? Typically with concurrent routes of the same type we list the lower number first.
  2. The phrase "Motorists crossing into Michigan at the western end have direct access to Detroit via I-94 and Chicago and Minneapolis-St. Paul via I-69" needs a citation. Also, if you keep this phrasing, you need to elaborate how one gets to Chicago and Minneapolis-St. Paul as I-69 does not make it to either of those cities. I would simply reword this to "Motorists crossing into Michigan at the western end have direct access to I-69 and I-94".
  3. "With the exception of the Front Street interchange in Sarnia, the freeway features Parclos throughout its length", what kind of interchange is Front Street?
  4. The sentence "After interchanging with Forest Line, the freeway is crossed over by London Line, momentarily diverging from its straight alignment while dipping south of Warwick (where London Line meets Egremont Road and continues east of Warwick north of the highway)." reads awkward. I would also ditch the parentheses and incorporate into the sentence.
  5. "When it was opened at some point between 1946 and 1949, it featured at-grade crossings with Front Street, Indian Road and Modeland Road (the Highway 40 Sarnia bypass).", do we have a more exact date for this?
  6. Same concerns with the formatting of the border crossing in the exit list, should look like it does in Ontario Highway 61 and Ontario Highway 71. Dough4872 04:33, 4 January 2014 (UTC)
  1. Fixed
  2. I've just changed it to say I-69/I-94 into Port Huron, Michigan. Do you still feel this needs a source since the RD sources the same info?
  3. Added. Diamond/Parclo B-2 hybrid
  4. switched it around a bit, how does it look now?
  5. I don't have an exact date, but I found another source that gives a better impression.
  6. Fixed
-- Floydian τ ¢ 08:59, 6 January 2014 (UTC)

Review by Fredddie

Review by Fredddie

Let's have a look. –Fredddie™ 04:13, 14 January 2014 (UTC)

Infobox and lead
  1. Handy reminder for inset map on File:Ontario 402 map.svg
  2. Is it necessary to say Point Edward, Ontario?
  3. What quantifies a "sizable community"?
RD
  1. "...providing a quicker route over the busier Ambassador Bridge crossing in Windsor, which also has 13 traffic lights leading to the bridge.[3]" "Also" makes it read like both 401 and 402 have traffic lights, except you said 402 is non-stop.
  2. I don't like using interchange as a verb. I read it as "trading places" not "cars exiting the highway".
  3. @Haljackey: could you crop your Highway 4 photo so the horizon is level?
History
  1. I'm not going to force it, but I think a mini-lead would look better than starting the section with a 3rd-level header.
  2. You use alignment/re-aligned three times in quick succession.
Overall
Only a few things to look over and I fixed some minor stuff myself. –Fredddie™ 05:04, 14 January 2014 (UTC)
Lead
  1. Added, although you may need to purge your cache to get it to appear.
  2. I suppose not, fixed.
  3. Changed it to "the only town", since all other places near the freeway are little villages / unincorporated communities.
RD
  1. Originally it said "suffers from 13...", which I felt was an appropriate way to describe the pros/cons of one route over the other... but I've tried another wording that should work.
  2. I've always agreed with that, to be quite honest. Fixed the few instances.
  3. Fixed it for him.
History
  1. Added a minilead. As it encompasses all the sourced facts contained within the subsequent sections, I've left it without refs as I normally have done in such situations.
  2. Changed it up a bit.
Cheers, Floydian τ ¢ 21:59, 15 January 2014 (UTC)
It's been my experience at FAC that they want refs in those mini leads. –Fredddie™ 02:38, 16 January 2014 (UTC)
Refs added. - Floydian τ ¢ 13:55, 17 January 2014 (UTC)

  Support –Fredddie™ 18:22, 17 January 2014 (UTC)

Review by Admrboltz

Image review by Admrboltz

--AdmrBoltz 18:31, 17 January 2014 (UTC)

Images all check out. --AdmrBoltz 04:17, 18 January 2014 (UTC)

Prose review by Admrboltz

So... I am going to be nitpicky... since I can't find all that much wrong with it...

  • Nexus → NEXUS
  • There is a {{-}} at the top of the exit list. In my screen resolution this doesn't seem needed, is it on yours?
  • Redirect the red links to the county road list like is done with Lambton County Road 8, etc.
  • Add a link to the Sarnia Chris Hadfield Airport in the RJL notes column for Airport Road.

--AdmrBoltz 18:00, 10 February 2014 (UTC)

    • Fixed
    • No, but I'm stuck at 1024x768 at the moment. I imagine a very wide monitor might get issues with the photo nudging the junction list to the right and the article not looking as tidy as it could.
    • Done
    • Added
Glad you found it difficult to find issues, that means the ACR process works well methinks :) Cheers, Floydian τ ¢ 19:08, 10 February 2014 (UTC)
Spotcheck by Rschen7754
  • Source 3: 13 isn't in the source.
  • Source 4: currently -> as of X. Also, "a new route known as the Windsor–Essex Parkway" now disagrees with source 4, where a new name is given.
  • Source 5: Good on V and CP.
  • Source 20: does not back up the entire paragraph for the second citation.
  • Source 21: dead link.
  • Source 34: Good on V and CP, but "that of a man who succumbed to hypothermia on a nearby county road" is not an independent clause.
  • Source 35: Good on V and CP.

The results of the spotcheck are a bit disappointing, in particular source 3 and 20. Please go through the entire article and make sure that all statements are backed up by sources, and post here when you have done so.

In addition, I am happening to notice stuff that should have been pointed out by other reviewers, and am uncomfortable with signing off on a spotcheck when there could be other issues. Thus, in order to uphold our high standards at ACR, I will be conducting a fourth review of the article, and will be procedurally Opposing this article until I have done this additional review, and when the above issues have been fixed, including the additional source checking. --Rschen7754 07:08, 28 February 2014 (UTC)

I will also note that I am not trying to discourage those who reviewed this article, but to advise all our regular ACR reviewers to take a bit more care with their reviews. --Rschen7754 07:19, 28 February 2014 (UTC)
Fixed the two big ones. I had used the wrong ref for one and copied the other from the Highway 401 article without checking. The dead link has been updated to the new links and other changes made. As I said, this article was promoted to GA a while ago and I expected some issues to arise. - Floydian τ ¢ 00:22, 1 March 2014 (UTC)
Do you believe that there are other instances of this, apart from the sources that I checked? --Rschen7754 06:05, 3 March 2014 (UTC)
Looking over it, there was one case of a fact not in an article and one case of a google maps link referencing a 1964 date. I've fixed these, and upon scanning the full article, I believe it is now properly referenced. - Floydian τ ¢ 18:42, 6 March 2014 (UTC)
Okay, I'll mark the spotcheck complete, and begin my review soon. --Rschen7754 18:43, 6 March 2014 (UTC)
Review by Rschen7754
Images
  • Captions should not have a period if they are not a complete sentence, and should if they are.
  • Map needs a caption.
RJL
  • No periods in the notes
References
  • No ALLCAPS in the references
Lead
  • Controlled access should be linked earlier than it is
  • The freeway originally did not exit Sarnia -> something is missing
RD
  • is under construction as of August 2011 -> three years ago...
History
  • It forced drivers off -> too vague

Should be good for a support after this. --Rschen7754 20:34, 6 March 2014 (UTC)

I'm guessing the ALLCAPS ref was the "PRESS RELEASE", which I've fixed. Captions should be good now, RJL notes fixed, CAH better linked. The sentence you pointed out is correct: the freeway was originally within the Sarnia city limits. I could make it "...did not exit the Sarnia city limits" if that would help? Construction on the 401 extension began in 2011 and will continue until 2020, but I made that sentence read better nonetheless. I hope I've managed to clarify the last point as well now. Cheers, Floydian τ ¢ 21:11, 6 March 2014 (UTC)
@Floydian: that would be fine. --Rschen7754 19:41, 7 March 2014 (UTC)
Done. - Floydian τ ¢ 21:25, 7 March 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

U.S. Route 31 in Michigan

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Consensus has been established by this review to promote this article to A-Class.  VC  02:47, 12 April 2014 (UTC)

Toolbox

U.S. Route 31 in Michigan (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: This is the third-longest highway in the state of Michigan (after I-75 and US 23), so it's part of my long-term goal to get all of the top 10 to FAC. Note, I do plan to add some additional photos, and weather permitting, I'll be in the Traverse City area later this week.
Nominated by: Imzadi 1979 → 21:07, 10 December 2013 (UTC)
First comment occurred: 01:14, 11 December 2013 (UTC)

Image review by Dough4872

Image review:

  1. File:US 31.svg - PD-author, should be relicensed as PD-MUTCD
  2. File:U.S. Route 31 in Michigan map.png - CC-BY-SA-3.0,2.5,2.0,1.0. Map needs source for GIS data. Also the map is missing Canada and seems to imply there is a large ocean to the northeast of Michigan.
    The sources have now been added at Commons. --Rschen7754 21:01, 29 January 2014 (UTC)
  3. File:1-196 BLACK RIVER BRIDGE SOUTH HAVEN.jpg - PD-user. I would indicate this is a concurrency between I-196 and US 31 in the caption.
  4. File:US 31, Manistee, Michigan.jpg - CC-BY-SA-2.0
  5. File:Grandview Parkway Traverse City.jpg - CC-BY-SA-3.0
  6. File:US31 Sign Looking North Bay View Michigan.jpg - CC-BY-SA-3.0
  7. File:Alanson Michigan Downtown 2 US31.jpg - CC-BY-SA-3.0
  8. File:Michigan's Indian trails.png - PD US not renewed, published in 1959
  9. File:Mitchell's Satyr butterfly.jpg - CC-BY-3.0, OTRS permission confirmed. I would add a little more context in the caption as to how this pertains to US 31. Dough4872 04:31, 2 January 2014 (UTC)
Tweaks applied to the captions, and of course the bot run still needs to be done for the US Highway shields, but that's been updated too. @Algorerhythms: the GIS sources needs to be added to the map. Imzadi 1979 → 05:46, 2 January 2014 (UTC)
I will support the images with one reservation. The map needs to be fixed before the article goes to FAC. Dough4872 03:16, 30 January 2014 (UTC)

Review by Admrboltz

Resolved issues from Admrboltz

A more complete review will come over the following days but below are some of the first issues that pop out.

--AdmrBoltz 23:53, 31 December 2013 (UTC)

Word and I did a grammatical and spelling check. I fixed one spacing issue, but other than that I don't see anything wrong on that end.

Review by Evad37

Review by Evad37

I will review this article - Evad37 [talk] 02:48, 25 January 2014 (UTC)

Lead

Route description

History

Future

RJL

The rest looks good - Evad37 [talk] 04:29, 25 January 2014 (UTC)

Review by Rschen7754

Review by Rschen7754

I will pick up the third review. --Rschen7754 03:18, 30 January 2014 (UTC)

Preliminary checks
  • Everything looks good.
Lead
Route description
  • They trade places again - could be a bit more clear
  • A-2 has a duplicate link 2 paragraphs away from the first one (also run the script...)
  • runs as four-lane expressway - as a four-lane expressway
  • linear state park? linear-shaped?
  • "The highway" starting two consecutive sections in the second paragraph of NW Michigan.
  • In this area, the highway passes through an area ...
  • southeast of Charlevoix - missing a period
  • "the highway" used a lot in the rest of the paragraph. --Rschen7754 01:54, 1 February 2014 (UTC)
Memorial
Future
  • it was listed an endangered species - as?
  • Until the freeway is complete, US 31 follows - I don't think the preposition and the verb go very well together.
  • Currently - as of (several times in the section) --Rschen7754 08:01, 1 February 2014 (UTC)
History
  • Do we know much about when the Mackinac Trail was built?
  • through down... town?
  • At that time... at this time... could be more clear

This concludes the review. --Rschen7754 09:14, 1 February 2014 (UTC)

@Imzadi1979: --Rschen7754 06:11, 28 February 2014 (UTC)

  • The Mackinac Trail was an Indian trail, and all of those Indian trails predated European settlement in the region, so I can't tell you when it was built/created/etc.
  • Other items copy edited. Imzadi 1979 → 20:16, 28 February 2014 (UTC)

Spotcheck by TCN7JM

As promised earlier, I will do this spotcheck. I will try to do it by the end of this weekend. TCN7JM 17:22, 1 March 2014 (UTC)

I will be checking:

  • Source 10 –   Good
  • Source 11 –   I got confused at first...with where Petoskey was. The information itself is correct, but Petoskey isn't marked on the map, and I, having only visited Michigan a few times, had no clue where it was located. Is this an issue?
  • Source 12 –   Good
  • Source 13 –   Good, but Apple screenshot hurts my brain. Please switch to Windows immediately.
  • Source 14 –   Good
  • Source 15 –   Good
  • Source 16 –   Good
  • Source 17 –   Good
  • Source 18 – Cannot find, will discuss on IRC when you arrive.
  • Source 19 – Is in same document as Source 18; cannot find.
  • Source 20 –   Good
  • Source 71 –   Good
  • Source 73 –   Slight error...the source mentions a 9.5-mile stretch, not 9.1-mile.
  • Source 74 –   Good
  • Source 76 –   Good
  • Source 77 –   Good
  • Source 80 –   Good
  • Source 82 –   Good
  • Source 83 –   Good
  • Source 86 –   Good

The source numbers are as of this revision. TCN7JM 18:19, 2 March 2014 (UTC)

Progress? --Rschen7754 00:08, 2 April 2014 (UTC)
@TCN7JM: you have mail for the first batch (footnotes 10–20). I will compile the others here in a little bit. Imzadi 1979 → 00:46, 2 April 2014 (UTC)
And second batch taken care of as well. Imzadi 1979 → 01:14, 2 April 2014 (UTC)
Alright. Unfortunately, I will be mainly unavailable until next Monday, so I'm afraid this will have to wait almost another week. I will get this done, though; I promised I would. TCN7JM 01:17, 2 April 2014 (UTC)
Regarding footnotes 18 and 19. On page 27, there is the photo of the opening of the last segment of I-96 which splits the paragraph in two.

In the spring of 1973, Gov. William G. Milliken issued an executive order reorganizing the state highway department giving it jurisdiction over all state transportation programs. He directed the highway commission and the department to develop and deliver a unified, coordinated program for total transportation for the people of Michigan.

Symbolic of this sweeping change, Milliken signed legislation Aug. 23, 1973, adding "and Transportation" to the department's traditional designation of highways only

As for footnote 19, that is split on pages 30 and 31. The bottom of 31 has the photo of M-28 along Lake Superior. Above that is another photo of airplanes which is below the start of the cited passage, the second paragraph of which is located on the lower corner of page 31:

The year-by-year need for extra dollars for roads and transportation was met in 1978 with a legislative act informally known as "Transpack."It was an abbreviated nametag for a collection of highway laws and a constitutional amendment that put the department solidly in the business of moving people as well as vehicles.

The gasoline tax was raised from nine to 11 cents a gallon, the diesel fuel levy from seven to nine cents. The weight tax went up by 30 percent, truck fees by 35 percent. The distribution formula of the newly named Michigan Transportation Fund was rewritten to give the Michigan Department of Transportation, also a new title, 46 percent of gas and weight tax revenues.

I hope that helps.

I fixed the typo related to fn 73, and I don't think it should be an issue regarding fn 11. Imzadi 1979 → 22:33, 11 April 2014 (UTC)

They both look fine to me. I support this article's promotion. TCN7JM 01:45, 12 April 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Queen Elizabeth Way

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Toolbox

Queen Elizabeth Way (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: April Fools! This one is the big bad boy of the ACRs for this year. However, as the most recent major rewrite under my belt and newest 400-series GA, it should be pretty well up to scratch. Anyways, this is up there with the Pennsylvania Turnpike in terms of historical significance and should be an enjoyable read. Cheers.
Nominated by: Floydian τ ¢ 00:56, 2 April 2014 (UTC)
First comment occurred: 00:57, 2 April 2014 (UTC)

Review by Dough4872

Review by Dough4872

Comments:

  1. Why do you use "Fort Erie end" and "Toronto end" as opposed to a direction in a infobox? If the QEW is signed with directional banners, you should use them.
  2. I do not get how QEW fits in the browse between Highway 427 and Highway 400.
  3. In the lead, where did the QEW originally end in Toronto?
  4. "interchanges provide access to and from the freeway at Central Avenue, Concession Road and Thompson Road, Gilmore Road and Bowen Road.", is Concession Road and Thompson Road supposed to be one interchange. If so, I would use a slash instead of and to indicate these two roads are one interchange.
  5. The sentences "Throughout Lincoln, the QEW travels along the Lake Ontario shoreline through the Niagara Fruit Belt. Numerous wineries line the south side of the freeway." should be combined.
  6. "Over the next two years, the numerous bridges and cloverleafs along the new highway were constructed" maybe use "cloverleaf interchanges" here.
  7. The sentence "Service roads were installed and 13 intersections eliminated, and the accident rate was reduced by 50%" reads awkward.
  8. "The collection of tolls continued until December 28, 1973.", was this when toll collection stopped on both bridges or on just one of them? You should be more clear here.
  9. The sentence "Construction was carried out over two years, and the twinned structure was opened on October 11, 1985,[23] and christened as the James N. Allan Skyway, in honour of James Allan, Minister of Highways during construction of the original skyway." should be split at the comma after 1985.
  10. Again, you should indicate where the original Toronto terminus of the QEW was before it was truncated to Highway 427.
  11. In the exit list, I again notice you use cities instead of directions. Dough4872 00:44, 9 April 2014 (UTC)
As a preliminary comment, the QEW is not signed as an east/west or north/south highway as other provincial routes are. Rather, it is unique in that heading towards Toronto from Buffalo, it is consistently signed as "QEW" with a "Toronto" banner below; from Toronto towards Buffalo, it is signed as "QEW Hamilton", "QEW Niagara" and "QEW Fort Erie". It is the only highway in Ontario that uses cities as opposed to cardinal directions. - Floydian τ ¢ 06:07, 9 April 2014 (UTC)
You should perhaps mention in the article that the QEW uses cities rather than directions to give orientation of the route. Dough4872 01:01, 10 April 2014 (UTC)
  1. Addressed above.
  2. The browse lists the 400-series highways in this case. QEW is basically the Ace, high and low. Highway 400 has it listed as the "previous" route.
  3. Added
  4. Fixed
  5. Done
  6. Done
  7. Fixed
  8. Clarified. Tolls were removed from both on the same day.
  9. Done
  10. Done
  11. See #1
I'm adding a bit now regarding the directions to the lede of the RD. Just need to look up a ref. Thank you for the review! This one is quite a handful. - Floydian τ ¢ 01:18, 10 April 2014 (UTC)
  • Note I am withdrawing this candidate to take it to FAC. ACR is in a bit of a lull at the moment and I figure this article is a little more top notch than its counterparts. - Floydian τ ¢ 23:43, 26 May 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

List of Interstate Highways in Michigan

This nomination has been stale for a while now. Since there is no opposition, and FLC does not require a source spotcheck, I will invoke WP:IAR on the normal ACR procedure and promote our first A-Class list, with a suggestion to revisit our source spotcheck requirement for lists. -happy5214 02:06, 4 June 2014 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Toolbox

List of Interstate Highways in Michigan (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: In discussions earlier about this year's project goals, I had offered to be a guinea pig for the FLC goal. In order to do that, I present to you the first list that I think is ready to be evaluated for AL-Class and promotion to FL. It is also a keystone to a future GT on Michigan's highway system.
Nominated by: Imzadi 1979 → 01:51, 11 April 2014 (UTC)
First comment occurred: –Fredddie™ 01:56, 11 April 2014 (UTC)

Followup comment: I will be adding a map to the infobox and polishing the citations in the coming days. Imzadi 1979 → 10:09, 11 April 2014 (UTC)

Review by Fredddie

Comments by Fredddie

Some preliminary questions and comments:

  1. First of all, I am reviewing this as if USRD's featured lists don't exist. Didn't we begin this push to create featured lists because the ones we have are not that good. Anyway, since MILHIST has A-Class lists, I will be taking cues from that project.
  2. Do you think the second and third paragraphs of the lead be better split out as a history section and then re-summarized for the lead? I'm leaning that way, but I'd like your opinion and that of anyone else who plans on chiming in.
  3. I think each section could use an introductory paragraph. Since we're talking about the system in Michigan as a whole, I think we have a good opportunity to explain why routes were built where they were with respect to the system.
More to come... –Fredddie™ 22:44, 11 April 2014 (UTC)
I started with List of Interstate Highways in Texas as a starting template. Granted, that list was promoted several years ago, and undoubtedly FLC expectations have heightened over the years just as FAC expectations have.
One thing that concerns me is too much redundancy between the history of the state's highway system in Michigan State Trunkline Highway System and the lead here. By my way of thinking, this list's tables would be in that other article if it weren't for space considerations; in other words, this is the subarticle. There's probably some room to expand on the content, but I would hope that doesn't result in writing a "History of the Interstate Highways in Michigan" that has tables below it. Imzadi 1979 → 02:00, 13 April 2014 (UTC)
Fair points. I think this list (and all FL-wannabes) should answer a few questions for the casual reader:
  1. What is an Interstate Highway?
  2. Where are the IHs in Michigan?
  3. Why were they built there?
  4. When were they built?
  5. How are Interstates funded? (construction and maintenance)
I'm not asking for verbatim copy/pastes from the SHS article or even detailed analysis of the construction of each highway, but I think some explanation without relying on going to the individual articles is needed. –Fredddie™ 02:33, 13 April 2014 (UTC)
All of which should be addressed now with the expanded prose sections. Imzadi 1979 → 03:38, 13 April 2014 (UTC)

Review by Dough4872

Review by Dough4872

Comments:

  1. You should probably mention the total mileage of the Interstate Highway System in Michigan in the lead.
  2. In the Description section, you should maybe add a sentence briefly describing the standards of the Interstate highway (Granted, you have a link to the standards article, but a brief mention here would help too.)
  3. Maybe you should clarify the Mackinac Bridge is the only part of the Interstate Highway System in Michigan not maintained by MDOT.
  4. In the description, maybe you should mention the numbering scheme and how it applies to the Interstates in Michigan, giving examples.
  5. Which section of I-75 was the first to get signage and when was it built?
  6. Maybe you should mention why MDOT cancelled studies on I-73.
  7. In the tables, I noticed inconsistency with mentioning the names of the Interstates. You appear to mention all the names of I-75 but leave out the current names of I-96. You should be consistent in either including all of the names or none of them. Also, is it really necessary to mention the names of the Interstates? I can see if one name applies to the entire length, but it gets unwieldy for highways such as I-75.
  8. Why aren't the names of I-94 cited?
  9. Why do I-496 and I-696 have completion dates in the table but none of the other 3di or the 2di don't? I would again be consistent here in including or all or none or would mention the significance of including the completion dates for these two Interstates.
  10. I noticed the proposed interstates don't have highways at the termini listed. Is this because the exact termini were unknown? But if they were known to terminate at a route I would include the route they were proposed to terminate at.
  11. There are some uncited statements in the notes of the business routes table.
  12. I noticed for some of the business routes you mention the city of town it serves in the table. Shouldn't you do this for all of them for consistency? I would do it based on the fact business loops or spurs are typically identified with a specific community. Dough4872 02:13, 14 April 2014 (UTC)

Replies

  1. Added.
  2. Added, but I reserve the right to remove it later; I want to sleep on it to see if I like the way it flows there.
  3. Added.
  4. No, that's what Interstate Highway System is for. Since there are currently only four mainlines, at two of each north–south and east–west, it would be hard to give examples without duplicating the table. As for the 3dIs, it could take too much to explain why I-196 has an odd first digit even though it is not a true spur.
  5. Added.
  6. Added.
  7. Added. The trouble is that the 2dIs have been carved up into separate named segments, some of which (like the Fisher vs. the Chrysler on I-75) have distinct physical boundaries.
  8. Already done, per Evad's comments below before I read yours.
  9. Let me think over how to deal with this... At one time, before the templates were developed, I think there was a "completion" column, but it should be easy enough to add the others' years where they differ from the "formed". (I-296 was first designated when it was completed, so it's formation and completion dates are the same.)
  10. Given their proposed nature, I didn't think we needed to be so specific, especially since the locations are already rounded off because exact corridors were never really established.
  11. Those were all taken care of already before I saw that you saved your comments.
  12. I indicated them in the notes only when the termini are outside of the specific cities. The BL I-69 for Lansing, for instance, starts in Delta Township in Eaton County, run through Lansing and East Lansing in Ingham County before terminating in Bath Township in Clinton County.

Imzadi 1979 → 09:15, 14 April 2014 (UTC)

For now, pending any addition of a completion column, I've added all of the completion dates to the notes where they aren't the same as the formation date. (Some 3dIs were built and opened in one segment.) Imzadi 1979 → 00:57, 15 April 2014 (UTC)
  • Support - I feel that this list is thorough, well-formatted, and sets a good example for what future USRD lists should look like. Hopefully, consideration can be made for adding a completion column listing the completion dates of the Interstates. Dough4872 01:00, 15 April 2014 (UTC)

Review by Evad37

Comment by Evad37 – resolved

Not a full review, just a point that I think needs some discussion: Should all the notes in the note columns have at least 1 reference at the end of the note? Isn't a note without any references as much of a verifiability issue as a sentence or two at the end of a paragraph without any references? For example, where's the source(s) for I-94 having "one section named the Detroit Industrial Freeway, another named Edsel Ford Freeway"? Or that BL I-75 "Follows Woodward Avenue through downtown Pontiac", or that BS I-375 is "Unsigned along Jefferson Avenue"? - Evad37 [talk] 03:25, 12 April 2014 (UTC)

Well, there are two ways to look at this. All of the various locations, street names and most of the freeway names are all listed in MDOT's Physical Reference Finder Application, which is the citation for all of the lengths. We typically do not require redundant citations for notes on highway junction/exit lists if the information can be found in the source for the mileposts, so I'm not sure why the same principle wouldn't hold true here. (As for the BS I-375 notes, see note c below the article where that information is cited.) Imzadi 1979 → 03:46, 12 April 2014 (UTC)
@Evad37: I'm not opposed to making changes. In many ways, this ACR is a test case, and whatever we do here will be validated or not when this goes to FLC after this review closes. There hasn't been a FLC out of the various highway projects in several years, and we're testing new templates and the standards for lists USRD set up. I know that the AL-Class assessment will be provisional for a while, but the biggest test will probably be this first list. Also, in the past, FL-related comments have indicated to me that they prefer to have a references column on the far right that hold all of the footnotes for everything in a row., something the templates don't do yet, which would simplify when a single footnote handles information from multiple cells. Imzadi 1979 → 02:20, 14 April 2014 (UTC)
I get what you were saying earlier earlier about the top footnote in the length column referencing the info that's not specifically cited, but I don't think it looks good for some notes to have a ref at the end and others not having one, or only having one in the middle of the note - it just makes it look like its unfinished. I think that's the main difference between these lists and RJLs, which would typically only have a ref at the top of the table – but I can't really think of a good way around having "redundant citations". I'm not sure if this would actually be a problem at FLC or not, but the previous reference discussions [3][4] may have to be revisited. - Evad37 [talk] 02:57, 14 April 2014 (UTC)
(BTW, anyone else reading this is welcome to comment in this subsection... I don't know if I'm the only one with these concerns...? - Evad37 [talk] 02:57, 14 April 2014 (UTC))

I see that all the notes now have refs, so I am marking this as resolved - Evad37 [talk] 01:13, 15 April 2014 (UTC)

Review by Evad37

More comments and questions to turn this into a full review:

Lead

  • Feels like there should be a comma before "while the highways in Michigan..."

Description

  • link "control of access" to Control of access#Control_of_access, not necessarily an obvious term for the average reader
  • "50 to 70 miles per hour (80 to 113 km/h) (depending on type of terrain)" – suggest rephrasing or altering punctuation two avoid a double set of brackets
  • abbreviations of organisations is not consistent – all four have full name and abbreviation in the lead, but in this paragraph there's MDOT, FHWA abbreviated, and American Association of State Highway and Transportation Officials, Mackinac Bridge Authority in full
  • "(A fourth, the privately owned Ambassador Bridge connects I-75 and I-96 in Detroit to Canada.)" – are the brackets needed? Would seem to read just as well without.

History

  • "Seizing the opportunity brought by a 1957 state law" – which law? (if specified by source)

Tables

  • There doesn't seem much point in the Removed column being sortable in the Primary Interstates table
  • There should be a &nbsp; in "Highway 402"
  • Should there be a color key for the dark grey background color at the end of the tables (like {{Jctbtm}} does for RJLs)?

Images

  • Have you considered using <gallery mode=packed>, which centres the gallery and wastes less space around each image (more info/options at Help:Gallery tag) - Evad37 [talk] 05:27, 11 May 2014 (UTC)
    • @Evad37: all of the above are done that I can do by myself. I just double checked, but the 1957 state law has no title listed in the source. A quick check of the relevant statute that codifies the modern state trunkline highway system (McNitt Act, Public Act 51 of 1951) does show that it was amended in 1957 by PA 262, but that's getting into minor details. {{Routelist bottom}} is being updated to insert the key, which is something I've nagged about on IRC in the past. Since {{routelist top}} would have to be modified to switch sorting on and off for that one column, I'm not sure that is something that needs to be done, unless it comes up as an issue in the FLC. As for the gallery, I'm not sure I like that option, so I'm leaving it for now and will revisit during the FLC if necessary. Imzadi 1979 → 06:06, 11 May 2014 (UTC)
And I only got one ping, probably because the system didn't detect a new signature with the first edit - Evad37 [talk] 13:17, 11 May 2014 (UTC)

Image review

  1. File:I-69 (MI 1957).svg - PD-MUTCD, maybe link to historical MUTCD?
  2. File:Business Loop 75 (1957).svg - PD-MUTCD, maybe link to historical MUTCD?
  3. File:I-94.svg - PD-MUTCD
  4. File:Business Spur 96.svg - PD-MUTCD
  5. File:CapitolLoop.svg - PD-author, has OTRS confirmation
  6. File:Michigan Interstates.svg - CC-BY-SA-3.0, has GIS data
  7. File:Interstate Highway plan June 27, 1958 (MI).jpg - PD US no notice, published in 1958
  8. File:I-69 exit 70 MI.jpg - CC-BY-SA-2.0
  9. File:I-75 Chrysler Freeway looking south.jpg - CC-BY-SA-2.0
  10. File:Mackinac Bridge from the air4.jpg - CC-BY-2.0, maybe should mention I-75 crosses bridge.
  11. File:Non Interchange Signage with Mileage Signage.jpg - PD-user
  12. File:Interstate 96 E-L at M-39.jpg - CC-BY-SA-2.0
  13. File:Interstate 194 Michigan.jpg - CC-BY-SA-2.0
  14. File:I-196 entering Grand Rapids, MI.jpg - PD-user
  15. File:I-275S at M14 1 Northville.jpg - CC-BY-SA-3.0, has OTRS confirmation
  16. File:I-496 at MLK Boulevard.jpg - CC-BY-SA-3.0
  17. File:Interstate 696 pedestrian plazas Oak Park.jpg - PD-author, has OTRS confirmation
  18. File:Mixing Bowl Interchange (Novi, Michigan).png - PD-self, wouldn't this be PD-USGov as a work of the USGS? Dough4872 00:56, 15 May 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Not promoted as stale over 6 months. --Rschen7754 19:13, 18 June 2014 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Interstate 470 (Kansas)

Toolbox

Interstate 470 (Kansas) (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: Seems to meet the criteria.
Nominated by: Ks0stm (T•C•G•E) 20:46, 2 September 2013 (UTC)
First comment occurred: 22:20, 2 September 2013 (UTC)
Review by Scott5114

This would be an excellent companion piece for the Kansas Turnpike article, should you want to take it to FA. I have some photos of the I-470 portion of the turnpike I've been meaning to upload, so I can contribute those this evening.

As to the review:

  • Lead needs some expansion/restructuring. A good rule of thumb is one paragraph for each major section. You might want to leave the AADT information out of the lead as it is more of a technical detail.
  • It might be interesting, if you can find the sources for it, to include a Design section comparing and contrasting the design of the free section of I-470 with that of the turnpike portion. For the latter you could probably crib sources from the turnpike article.
  • After an abbreviation is introduced, don't use the spelled-out version; in the lead, "U.S. Route 75" appears after the "US 75" abbreviation was noted. (This also happens with "I-470" versus "Interstate 470".) Likewise, both "US 75" and "US-75" are used; select one and stick with it (probably "US-75" since that is used by {{jct}}). ["US 75" still appears in the History section.]
  • From there, the highway heads generally northeast through southeastern Topeka until I-470 reaches its eastern terminus with I-70. It's easy to get lost in this sentence because of all of the directions. Try breaking it into two sentences.
  • It may be worthwhile to emphasize that the half-diamond interchanges are missing movements, since "half-diamond interchange" could be interpreted as an interchange type by a non-technical reader.
  • ...making I-470 into a toll road. Well, it makes the eastern half into a toll road. Consider rephrasing.
  • The maintenance information in the final paragraph of the route description needs some work. We have lots of background on who KDOT is and what it does, but KTA is not mentioned at all. As it's worded here, the article is actually incorrect, since the Kansas Turnpike is a freeway. Remove the background information on KDOT and what AADT is (that information can be gleaned from the relevant articles if the reader needs it) and add information about KTA.
  • Two sentences in this paragraph begin with As part of.... It would read better to restructure one of them to avoid repetition.
  • Since completion of the freeway, the route has not been changed. It retains its original routing. These sentences are redundant. They say the same thing.
  • Consider using RJL colors for consistency with other Kansas road articles.

All in all not a bad little article. Shouldn't be hard to spruce up. —Scott5114↗ [EXACT CHANGE ONLY] 00:37, 3 September 2013 (UTC)

Alright, I've taken care of several of these; if you could go back through and mark which ones are done to your satisfaction that would help me know what else I need to do. Ks0stm (T•C•G•E) 16:44, 26 September 2013 (UTC)
Struck through the issues that have been addressed. —Scott5114↗ [EXACT CHANGE ONLY] 00:34, 28 September 2013 (UTC)
Alright, I've fixed the three things other than creating a design section. I don't know that there are plentiful enough sources for a design section, as sources for the non-turnpike portion of I-470 are quite scarce. I could maybe add a sentence or two to the route description, but a section would be unwarranted given the amount of sources available. Ks0stm (T•C•G•E) 06:57, 28 September 2013 (UTC)
Right, I'm not going to require a Design section; it would just be a nice-to-have if you are headed to FA. (Try contemporary Topeka newspaper articles?) I'm satisfied with the article as it is now, however. Support. —Scott5114↗ [EXACT CHANGE ONLY] 18:07, 28 September 2013 (UTC)

Review by TCN7JM

I'd like to review this article, but I didn't want to do it first. I'll review it after Scott's concerns are fixed, and if needed I can probably do either the image check or the spotcheck later on. TCN7JM 12:32, 4 September 2013 (UTC)

Okay, I guess it's my turn.

  1. Abbreviating all three Interstates in the lead after writing them out in full seems a bit redundant. After abbreviating (I-470), usually the rest of the Interstates can be used in either one form or the other, having both is unnecessary.
  2. There's got to be a better way to word the sentence in the lead about I-470 becoming a part of the Kansas Turnpike so as to remove the redundancy in using "I-470" twice without using ambiguous pronouns, but it may require rewriting the whole sentence.
  3. "...fall under the purview of the Kansas Turnpike Authority, who is responsible..." – This is incorrect, but I'm not sure which way it needs to be fixed. If KTA is being referred to as multiple people, "who are" should be used. However, if it's being referred to as one authority, "which is" should be used instead.

These are all of the concerns I have, and I am still open to doing the image review later. TCN7JM 18:45, 28 September 2013 (UTC)

My concerns seem to have been addressed. I will support this article's promotion to A-Class. Nice work. TCN7JM 20:57, 30 September 2013 (UTC)

Spotcheck by Rschen7754

I can review this article afterwards. --Rschen7754 20:52, 4 September 2013 (UTC)

Switching to spotcheck per comments below. --Rschen7754 17:07, 5 September 2013 (UTC)

Review by Viridiscalculus

I will lay a claim to review number four (if we still do four reviews).  VC  06:13, 5 September 2013 (UTC)

We only do three now... I can switch to a spotcheck if you want, since I will probably be running a database check for this one and that lines up fairly well. --Rschen7754 06:20, 5 September 2013 (UTC)
That would be good. I have some comments written down already, but I will wait until Scott5114 and TCN7JM are done before I post them.  VC  14:48, 5 September 2013 (UTC)

I have substantial concerns that need to be addressed before I will support this article being promoted.

Infobox
Route description
  • The names of the roads at each of the non-numbered-highway interchanges are not mentioned.
  • To be consistent, I suggest you remove mention of exit numbers from the first paragraph. You need to use exit numbers consistently, either at every interchange or no interchange.
  • There are no mentions of number of lanes anywhere in the article.
  • Mention the configuration of every interchange. For most, it will just be "this is a diamond interchange" or "this is a trumpet interchange."
  • Elaborate on the complex interchanges. For instance, instead of just saying "US-75 splits away from I-470 at a complex interchange with Burlingame Road", explain how the interchange is complex. Mention the flyover ramps.
History
  • The History is broad but not comprehensive. It begs a lot of questions that need to be answered before this will be viable at FAC.
  • Several of the interchanges have changed since the highway opened. There needs to be more details on the western I-70 interchange, the eastern I-70 interchange, the US 75 flyover ramps, and possibly the Kansas Turnpike/Topeka Boulevard interchange.
  • When was US 75 placed on I-470 west of the Turnpike?
  • There is no mention of the former service area within the eastern I-70 interchange.
  • Was I-335 planned as a Topeka Interstate in the 1950s? According to the Kansas Turnpike article, I-335 was assigned merely to allow a higher speed limit along what had been an unnumbered segment of the Turnpike.
  • The quotes around the memorial highway designation are not necessary. This applies to the Lead, too.
Exit list
  • "Exit 182 is a part of the Kansas Turnpike and uses its mileposts, as do all other Interstates signed on the turnpike." Instead of refering to Exit 182, say that the exit numbers on the Kansas Turnpike portion of I-470 follow the Turnpike's mileposts.
Done. Philroc (talk) 13:31, 19 October 2013 (UTC)
  • I suggest including the I-70 exit number of the western terminus in the notes for that row. Also, expand KC or rewrite the statement about exit 1A. You may wish to split the interchange into two rows.
  • For the interchanges that are pairs of half-diamonds, you should indicate a mileage for each half of the diamond. You can place both in the mile column.
  • For Exit 6, the mileage should be to two decimal places.
  • For the last exit, "182 & 183" looks strange. I suggest only including 182 because there is no exit 183 from I-470. You should indicate in the notes that it is Kansas Turnpike Exit 183 coming from the east.
  • In fact, you might want to split the eastern terminus entry because there is almost a mile between Exit 182 and where I-470 merges into I-70.
  • The Notes field for the last exit is not WP:MOS compliant. Splitting the eastern terminus entry would solve the problem that you use a jct template that produces shields that pop up within prose and abbreviations that should be expanded.
  • The West end of toll road row in the table is not necessary. That should be mentioned in the notes for the I-335 interchange.
Done. Philroc (talk) 13:40, 19 October 2013 (UTC)
References
  • Instead of linking to the KDOT historical maps page, link to the individual maps.
  • Do you have authors for the newspaper articles?
  • This may not be necessary, but you may wish to update the mileage source or any other references that are not using the most up-to-date editions.
General
  • Use the link checker tool to avoid overlinking in the prose. Just from scanning the article, I see there are two links to I-70 in the Route description.
  • Would it be possible to get some photos of I-470? Scott5114 mentioned he took some a while back. No more than one or two are necessary because this is a short article.

I typically do a second run-through after most or all of the issues have been addressed, so I may have more comments later.  VC  23:48, 3 October 2013 (UTC)

@Philroc: Please let the reviewer strike items out, and please let the nominator decide whether to fix an issue. It may be that the reviewer decides that something was not fixed to his satisfaction, or that the nominator decides that making that fix would be counterproductive. Either way, that's not something for you to decide. --Rschen7754 19:47, 19 October 2013 (UTC)

Due to inactivity, this review has been suspended. The nominator has 5 6 months from this posting to reactivate the nomination and address the issues before this review is automatically failed. --Rschen7754 04:23, 1 December 2013 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Ontario Highway 405

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Toolbox

Ontario Highway 405 (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: Out of all the freeways in Ontario, Highway 405 likely has the simplest history, and as such is the shortest of the 400-series articles. Coincidentally, it was also my first road GA. A perfect candidate for the shortened month of February!
Nominated by: Floydian τ ¢ 07:55, 31 January 2014 (UTC)
First comment occurred: 01:35, 5 February 2014 (UTC)

Review by Dough4872

Review by Dough4872

I will review this article. Dough4872 01:35, 5 February 2014 (UTC)

Comments:

  1. In the lead, maybe you should mention that I-190 continues into New York.
  2. Is it really important to mention the speed limit in the lead?
  3. "The additional lane provided along this section is for the queueing of trucks", should specify this is the eastbound lane.
  4. "It then passes over the Niagara Parkway and begins to cross the Lewiston–Queenston Bridge" sounds awkward. I would change "begins to cross" to "heads onto".
  5. Again, should mention I-190 continues into New York in the Route description.
  6. Also, you should mention the body of water at the U.S. border in the lead and Route description.
  7. You have inconsistent date formatting in the History.
  8. Does the former interchange need to be included in the exit list? Usually, I wouldn't bother to include them.
  9. As with several other Ontario articles (such as ON 61, ON 71 and ON 402) that connect to highways at the U.S. border, I have a concern with the alignment of the I-190 shield in the exit list. This should be fixed the same way it was in those articles. Dough4872 05:28, 5 February 2014 (UTC)
  1. Added
  2. That's usually the only spot it tends to get a mention, I've removed it though.
  3. Done
  4. Done
  5. Yuck! DMY formatting. All fixed :D
  6. I include former interchanges from 50 years ago if I can, it's a good place to mention those details in longer articles (ie 401) especially. If the info's there why not after all?
  7. Yeah I tried to get some commentary on that at MOS:ICONS but got no response. You're killing me, but fixed.
Thanks for the review! - Floydian τ ¢ 02:47, 11 February 2014 (UTC)

Image Review by the Admiral

Extended content
  • Added sources and image location to the two images. I personally like them stacked, but I've fixed Attached KML so that it is the same width as the commons box, which looks much better. - Floydian τ ¢
Review by Rschen7754
Preliminary checks
  • The formatting for ref 11 seems off - shouldn't NYT be what is in italics?
Lead
  • In the US, we generally say Interstate 190 (I-190) the first time, and then I-190 everywhere else.
  • Why italics?
  • Last sentence not cited, and the information is not found elsewhere.
Route description
  • The primary purpose... notable.... seems a bit like editorializing.

This completes the review. --Rschen7754 00:33, 2 April 2014 (UTC)

First issue fixed... had NYT as the publisher instead of work. Fixed the I-190 issue. Changed italics to boldface as it should be. Added OPP info to RD with a citation. Finally, I've reworded those two sentences to make it less essay-like. Cheers, Floydian τ ¢ 01:14, 2 April 2014 (UTC)

Review by Evad37

Review by Evad37
  • (pronounced "four-oh-five") – reference?
  • It then crosses the Niagara River, where it crosses – avoid using crosses twice in the same sentence
  • ... is not subject to alternative, federal, administration, ... – sentence would flow better as "... is not subject to federal administration, ..."
  • named the General Brock Parkway – why the italics?
  • Toll rates – external should not normally be placed in the body of an article per WP:EL
  • Please be consistent with using either a dash (-) or endash (–) for Lewiston–Queenston Bridge
  • Infobox – caption for image?
  • All fixed, except the first issue. I'm not sure where I can find a text-based source for this... it's completely standard everyday practice to pronounce the 400-series highways with the "oh" instead of as a three digit number, but only in speech. Any thoughts? - Floydian τ ¢ 00:57, 9 June 2014 (UTC)
  • Maybe tv or radio news reports or stories? Not sure what the CBC or other Canadian broadcasters are like with putting stuff online, but you might find something. Otherwise, is the pronunciation actually necessary? It's not mentioned in the FA article Ontario Highway 402. - Evad37 [talk] 02:37, 9 June 2014 (UTC)
  • Meh... it'd be too difficult to find. There is one I found for the "four-oh-one", but that's all it mentioned :/ Oh well. I just removed it until such time as one can be found. - Floydian τ ¢ 03:21, 10 June 2014 (UTC)

Support - Evad37 [talk] 04:10, 10 June 2014 (UTC)

Spotcheck by Rschen7754

I will take the spotcheck. --Rschen7754 02:11, 20 June 2014 (UTC)

  • Source 9: Good on V and CP.
  • Source 11: Good on V and CP... but is this a reliable source?
  • Source 16: Good on V and CP.
  • Source 17: Dead link.
  • Source 18: Good on V and CP.
Glad this one is finally right on the money without mistakes. Cheers, Floydian τ ¢ 23:33, 20 June 2014 (UTC)
Okay, sounds good, and the spotcheck is now complete. --Rschen7754 23:34, 20 June 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Interstate 69 in Michigan

The article was promoted. –Fredddie™ 23:42, 13 July 2014 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Toolbox

Interstate 69 in Michigan (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: Might as well nominate this since Ontario Highway 402 is here at ACR, and if both are promoted, Michigan's network of FA-/A-Class articles will be connected to Ontario's. This would also be the third of four 2dIs for Michigan to be promoted.
Nominated by: Imzadi 1979 → 03:52, 3 January 2014 (UTC)
First comment occurred: 03:54, 3 January 2014 (UTC)

Review by Dough4872

Review by Dough4872

Comments:

  1. "Interstate 69 (I-69) is a part of the Interstate Highway System that runs from Indianapolis, Indiana, to the US–Canadian border at Port Huron, Michigan." this is not entirely true as I-69 has several disjoint segments between Texas and Indiana.
  2. Maybe you should mention I-69 is concurrent with I-94 at its eastern terminus in the lead.
  3. I do not think it is really important to mention that the distribution center is a Walmart distribution center. Typically, we do not mention specific business names in a route description.
  4. "and through an interchange with M-96 west of downtown Marshall." sounds awkward.
  5. Is the sentence about the Indian trails and the map really necessary given the fact I-69 follows none of them?
  6. "The first span of the Blue Water Bridges", I know the Blue Water Bridge is a twin-span bridge but is it officially called Blue Water Bridges? If not, "Bridges" should be singular here.
  7. "In 1980, a Flint-area politician wanted to dedicate a highway after the United Auto Workers (UAW).", what was the name of this politician? Dough4872 03:32, 5 January 2014 (UTC)
Image Review by Admrboltz

--AdmrBoltz 04:32, 5 January 2014 (UTC)

Review by Floydian

Review by Floydian
Lede
  • I've never been a fan of "running" as a verb for describing highways. I'd suggest "travelling concurrently" in this case. YMMV in each of the cases that I mention it below.
  • Again in the second case, and remove the link to concurrency.
Route description
  • Nitpicky, but "crosses into Calhoun County and over the St. Joseph River." - if the county line is the river, then you should swap the order of these.
  • Intersecting M-60?
  • "North of I-94, I-69 has one more interchange before crossing into Eaton County" - You mention the road at other interchanges, but not this one.
  • "Near Olivet, I-69 begins to turn in a northeasterly direction. As it continues in that direction, it runs to the north side of Olivet." - Reads somewhat awkward, and again with the run bit.
  • " I-69 follows the path of a line of the Canadian National Railway" - I'm assuming you mean parallels it?
  • "I-69, the railroad and the Swartz Creek all run together" - sounds like a marathon :) There's another "run" shortly after this too.
  • "It jogs to the north around Lake Nepessing on the southwest of Lapeer." Reads weird/grammatically incorrect.
  • "follow part of the Black River in the area." - "in the area" seems redundant here.
History
  • I believe left aligned photos are supposed to be placed above level 3 headers to align better.
  • "The first major overland transportation corridors in the future state of Michigan were the Indian trails.[9] None of these followed the path of the modern I-69 however." - Just curious why you put this here, it seems irrelevant to I-69 in this case.
  • "By 1936, the highway was extended all the way into Flint to end at M-21." - M-78 or M-104?
  • The second paragraph of the Predecessor highways section gets confusing when you introduce M-78 into the picture. It may be prudent to mention as you go along which segments of these would line up with I-69, since Pittsburg, for example, isn't mentioned in the RD.
  • In the last paragraph of Interstate Highway era, you mention that BUS I-69 was designated in 1984, congress extended the designation for a final time in 1987 to Port Huron, but the final segment of the route wasn't completed until October 1992. This is rather confusing.
  • "...the Michigan Legislature designated that I-69... would be named..." - declared would be more appropriate than designated in this case.
  • "The following October" - is that October 2001 (that October) or October 2002 (the following), as I would come to read it?
  • Why would it ever be a mistake to head to Canada? ;)
Exit list
  • Looks good
Business loops
  • May want to use a better source than Gmaps for validating that the loops followed those predecessors, as I can only see evidence of the ones in Coldwater and Charlotte being US 27
Refs
  • Ref 2: Scale / "Scale not given" needed
  • Do you think it may be better organized to group your refs so that maps can be given their own section? I've thought of doing this on a few articles with over 40-50 refs.

I'll add my history review in the next day or two. - Floydian τ ¢ 04:08, 11 February 2014 (UTC)

Or seven. Since you haven't replied yet, I've just inserted the history review above. - Floydian τ ¢ 21:36, 17 February 2014 (UTC)

Review by Evad37

Review by Evad37

Lead

  • A north–south freeway from the Indiana–Michigan border to Lansing, it changes direction to east–west and continues to Port Huron before terminating in the middle of the twin-span Blue Water Bridge while running concurrently with I-94 at the border – long sentence, suggest splitting into two

Route description

  • on average is an WP:Easter egg link to Annual average daily traffic
  • I-69 carries the Lake Huron Circle Tour in the Port Huron area and the I-69 Recreational Heritage Route – why is only the second mentioned in the infobox?
  • the business loop ends at the cloverleaf interchange that marks the first of I-69's two junctions with I-94 in the state northwest of Marshall – would something like "the business loop ends at a cloverleaf interchange northwest of Marshall, the first of I-69's two junctions with I-94 in the state" read better? I would assume that "northwest of Marshall" is more relevant to the specific interchange than to the two I-94 junction.
  • before crossing into Eaton County[6][7] – missing a full stop
  • Southwest of Capac, there is a temporary welcome center at the rest area along the westbound lanes. Do you have a ref for it being temporary? And what are the plans for the future?
  • On the eastern bank, I-69/I-94 – photo caption says "I-94/I-69", and later in the history section there is also "I-94/I-69". Can you make them consistent?

History

RJL

Business loops

Infobox

Looking good otherwise - Evad37 [talk] 04:36, 6 June 2014 (UTC)

@Evad37: as noted above, the appropriate fixes have been implemented. Imzadi 1979 → 01:43, 12 June 2014 (UTC)
Spotcheck by Rschen7754
  • Source 20: Good on V and CP.
  • Source 29: Do you mean 1947? Also, the print is too small on both the original (which was found through archive.org as the FHWA site is down) and what is on Commons.
  • Source 30: Good on V and CP.
  • Source 34: Good on V and CP.
  • Source 39: Good on V and CP.
  • Source 47: Good on V and CP.
  • Source 66: Good on V and CP.
  • Source 68: Good on V and CP.
  • Source 76: will AGF on the lanes part as the free part of the article cuts off. But what about the completed in 2012 part? That can't be in a 2011 article...
  • Source 78: Good on V and CP. --Rschen7754 23:02, 13 July 2014 (UTC)
    • For whatever reason (which could have been a blonde moment on my part), the wrong map citation was pasted into the article for fn 29. As for fn 76, there's a new FN 77 present to resolve that glitch. Imzadi 1979 → 23:30, 13 July 2014 (UTC)
  Done --Rschen7754 23:39, 13 July 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


California State Route 76

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Toolbox

California State Route 76 (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: This is a highway in the North County of San Diego, as part of my goal to get all San Diego County road articles as high as possible. Note: I have not done my usual pre-ACR tweaks (inflation, nbsp, map, OCLC) yet, but will do so over the weekend.
Nominated by: Rschen7754 20:03, 2 January 2014 (UTC)
First comment occurred: 03:50, 3 January 2014 (UTC)

Review by Dough4872

Review by Dough4872

Comments:

  1. Why is the length in the infobox and the lead different?
    Fixed, seems someone got confused by the postmiles. --Rschen7754 20:44, 4 January 2014 (UTC)
  2. You seem to overuse parentheses in the route description, particularly in the second paragraph. I would suggest rewording these sentences to not use parentheses.
    Done. --Rschen7754 02:22, 5 January 2014 (UTC)
  3. A lot of the sentences in the third paragraph of the route description read as [SR 76, the route, it, etc.] does [blah] before [blahing] [blah]. I would vary the wording here.
    Done. --Rschen7754 02:22, 5 January 2014 (UTC)
  4. The sentence "City of Oceanside plans for a road east through the San Luis Rey Valley to Fallbrook date from June 1889, and would include a bridge over the San Luis Rey River." begins awkward, I would reword.
    Done. --Rschen7754 02:22, 5 January 2014 (UTC)
  5. "legislative Route 195" shouldn't legislative be capitalized?
    No, because that is not part of the proper noun, or the then-official name. --Rschen7754 20:37, 4 January 2014 (UTC)
  6. " The legal definition was updated to reflect the new designation of I-5", maybe indicate I-5 replaced US 101.
    Done. --Rschen7754 02:22, 5 January 2014 (UTC)
  7. "state senator John Stull" shouldn't state senator be capitalized?
    Done. --Rschen7754 02:22, 5 January 2014 (UTC)
  8. "two point five miles (4.0 km)" I would change this to "2.5 miles (4.0 km)".
    Done. --Rschen7754 20:44, 4 January 2014 (UTC)
  9. " then-governor George Deukmejian", shoudln't governor be capitalized?
    Adjusted. --Rschen7754 21:32, 4 January 2014 (UTC)
  10. "Later that year, the California State Assembly renamed the first four miles (6.4 km) after Tony Zeppetella, an Oceanside police officer killed in the line of duty.", why is this included in the East of Oceanside section of the history when it is actually in Oceanside? Dough4872 04:41, 3 January 2014 (UTC)
    Adjusted. --Rschen7754 21:32, 4 January 2014 (UTC)
    All done. --Rschen7754 02:22, 5 January 2014 (UTC)

Image review by the Admiral

Images check out. Will not review prose as I was the GA reviewer. --AdmrBoltz 18:04, 22 January 2014 (UTC)

Review by Floydian

Review by Floydian

Since it's the only one here I can review, I will be reviewing this article. Cheers, Floydian τ ¢ 00:50, 8 March 2014 (UTC)

Lede
  1. "...through Pala and before..." - Extra "and" or missing town here
    Fixed. --Rschen7754 21:46, 9 March 2014 (UTC)
  2. The last sentence reads odd with the "Plans are to..." part.
    Fixed. --Rschen7754 21:46, 9 March 2014 (UTC)
RD
  1. "The roadway containing SR 76" might be better as "The roadway carrying the SR 76 designation", YMMV.
    Done. --Rschen7754 21:46, 9 March 2014 (UTC)
  2. If the legal definition and the maintaining body don't recognize the segment west of I-5, you should explain why the article includes mention of it.
    Well, the distance is about a quarter of a mile... --Rschen7754 21:46, 9 March 2014 (UTC)
    But do any official sources actual indicate that little chunk of road is part of CA 76? - Floydian τ ¢ 22:41, 9 March 2014 (UTC)
    No (see the GA review), but some maps do. --Rschen7754 23:52, 9 March 2014 (UTC)
  3. "SR 76 then meets the northern segment of CR S13, known as South Mission Road, heading north into Fallbrook;" maybe insert a while before "heading north"?
    Done. --Rschen7754
  4. "SR 76 intersects with the southern leg of CR S6" - the with is unnecessary
    Done. --Rschen7754 21:46, 9 March 2014 (UTC)
  5. "East of the..., the highway then encounters the northern leg of CR S6" - you could switch out "the highway then" with "it" for conciseness and flow.
    Done. --Rschen7754 21:46, 9 March 2014 (UTC)
  6. I don't believe a comma is necessary in "... while on duty, performing a traffic stop."
    Removed. --Rschen7754 21:46, 9 March 2014 (UTC)
History
  1. Delays and Postponement - "entered the bidding phase" - link bidding to construction bidding
    Done. --Rschen7754 21:46, 9 March 2014 (UTC)
  2. "Caltrans engineer Jacob Dekema announced in April 1969 that the construction on SR 76 and SR 78 to the south on the portions between I-5 and US 395 would be delayed until the construction on I-5 and US 395 was underway, or at least until 1976." - I'm assuming this should be "to the south of the portions...", but either way it reads rather oddly.
    Reworded. --Rschen7754 22:09, 9 March 2014 (UTC)
  3. "but SR 76 is not included in the system." - the jump to the present here is strange; may be better worded as "but SR 76 has not become part of the system.", or similar.
    Reworded. --Rschen7754 22:09, 9 March 2014 (UTC)
  4. "Following this..." - Shouldn't begin a paragraph referencing the previous one like this. Each paragraph should stand alone as a complete thought/concept explained. The first two sentences of this paragraph should possibly be merged into the previous paragraph.
    Done. --Rschen7754 22:09, 9 March 2014 (UTC)
  5. Widening and realignment - "Caltrans tentatively approved the first 2.5 miles (4.0 km) of the SR 76 widening project in May" - which portion was this 2.5 mile section between?
    Fixed. --Rschen7754 22:09, 9 March 2014 (UTC)
  6. "But the next year, the City Council voted..." - would read better as "However, the following year, the City Council voted..."
    Done. --Rschen7754 22:09, 9 March 2014 (UTC)
  7. "The rerouting of SR 76 away from Mission Avenue resulted in a decrease in business for establishments located on Mission Avenue." - Find a way to remove one instance of "Mission Avenue" here
    Done. --Rschen7754 22:09, 9 March 2014 (UTC)
  8. And actually, that last point holds true later down the paragraph, where the name is used six times!
    Fixed. --Rschen7754 22:09, 9 March 2014 (UTC)
  9. East of Oceanside - There are a few instances of the tense shifting mid-sentence in this section:
    1. "The city of Oceanside proposed plans for grade-separated interchanges with College Boulevard and Melrose Drive in 2004, should the expressway through Oceanside need to be converted to a freeway."
      Done. --Rschen7754 22:09, 9 March 2014 (UTC)
    2. "The purpose of this improvement was to reduce accidents on a stretch of road that now carries over 12,000 motorists per day, many headed for either the Pala Indian casino or a new gravel quarry that had recently opened." - was, now, headed, had.
      Done. --Rschen7754 22:09, 9 March 2014 (UTC)
    3. The westbound lanes between Melrose Drive and Mission Road opened to traffic in October, with the eastbound lanes scheduled to be open by November. - in this particular case it is almost outdated information. When did they end up opening?
      Updated, and added slightly newer information. --Rschen7754 22:37, 9 March 2014 (UTC)
  10. "in March 2009, two lanes of a new 1.3 miles (2.1 km) realigned segment of SR 76" - The convert her should be using |adj=mid|-long. Also, realigned seems redundant here.
    Reworded. --Rschen7754 22:09, 9 March 2014 (UTC)
  11. "Even after this, in 2009 the corner..." - There should be a comma after "2009"
    Done. --Rschen7754 22:09, 9 March 2014 (UTC)


Junction list
Looks good.
Refs/others
  1. Refs 7 and 11 need format=pdf added
    Done. --Rschen7754 22:17, 9 March 2014 (UTC)
  2. Ref 22: "p. Building" ?
    There was no page number, but it was in the Building section, so that is what I put. --Rschen7754 22:09, 9 March 2014 (UTC)
    There's supposed to be a section parameter in the citation templates, but I'm pretty sure it doesn't work right... oh well :/ - Floydian τ ¢ 22:41, 9 March 2014 (UTC)
  3. Refs 72 and 78 need the location added as with other instances of the Evening Tribune
    Done. --Rschen7754 22:17, 9 March 2014 (UTC)

-- Floydian τ ¢ 20:33, 9 March 2014 (UTC)

One response added above regarding that small quarter-mile segment. - Floydian τ ¢ 22:41, 9 March 2014 (UTC)

Since the nominator is not currently active on Wikipedia and it's been over 30 days since the last edit, I am suspending this nomination. If the nomination is not resumed by November 1, 2014, it may be failed in accordance with ACR rules. –Fredddie™ 19:02, 30 April 2014 (UTC)

Resuming. --Rschen7754 09:39, 18 June 2014 (UTC)

Review by Fredddie

Comments by Fredddie

I'll have a look. –Fredddie™ 22:54, 13 July 2014 (UTC)

Lead
  1. "It is a frequently used east–west route in the North County region of San Diego County that begins in Oceanside near Interstate 5 (I-5) and continues east. The highway serves as a major route through North County, connecting Oceanside with Bonsall while providing access to Fallbrook."
    Could this be reworded so North County and Oceanside aren't both repeated.
    Done. --Rschen7754 08:14, 14 July 2014 (UTC)
  2. Isn't it supposed to be 20th century and not spelled out?
    Done. --Rschen7754 08:14, 14 July 2014 (UTC)
RD
  1. As it begins to enter rural Oceanside, ... → As it leaves Oceanside, ...?
    No, should be rural Oceanside... a stretch of a few miles. --Rschen7754 08:11, 14 July 2014 (UTC)
  2. I don't like the comma-separated lists of intersected roads. I had to read the second half of "As it begins to enter rural Oceanside, SR 76 intersects with CR S14, Guajome Lake Road near Guajome County Park, and Melrose Drive.[4]" a couple times and cross reference the junction list to realize that CR S14 was not Guajome Lake Road.
    Fixed. --Rschen7754 08:11, 14 July 2014 (UTC)
  3. "It then has two overpasses over Mission Avenue and El Camino Real..." I don't like two here because it reads like two overpasses for each crossroad, which was really confusing when it crosses Mission Avenue again.
    Reworded. --Rschen7754 08:11, 14 July 2014 (UTC)
  4. When you say "this portion of CR S13's routing is not signed on maps." are you saying that there's an implied overlap that's not signed or one of the halves are not signed? I don't think the implied overlap is worth mentioning.
    Dropped it, because it's bordering on OR. --Rschen7754 08:11, 14 July 2014 (UTC)
  5. I think the sentence about Mr. Zeppetella would be better in the first paragraph.
    It's considered standard in California road articles to have all the designations at the end of the RD. --Rschen7754 08:11, 14 July 2014 (UTC)
History
  1. A history section that long should have a mini-lead.
    Done. --Rschen7754 08:30, 14 July 2014 (UTC)
  2. "Flooding in January 1916 resulted in the road that existed between Bonsall and Pala being closed; ... → closing between Bonsall and Pala; ..."
    Fixed. --Rschen7754 08:30, 14 July 2014 (UTC)
  3. "...though a bridge for the winter months was not in place." Was a bridge not necessary during other parts of the year?
    Rephrased, looking at the source again. --Rschen7754 08:30, 14 July 2014 (UTC)
  4. Was the road designated Legislative Route 195 but signed SR 76?
    Yes, there were two numbers for most CA roads before 1963. --Rschen7754 06:20, 14 July 2014 (UTC)
  5. The designations paragraph should be revisited as a whole. I think it's kind of hard to follow.
    Reworded. --Rschen7754 08:22, 14 July 2014 (UTC)
  6. The delays section is fine.
  7. The sentence for Mr. Zeppetella is redundant to the one earlier.
    Removed. --Rschen7754 08:22, 14 July 2014 (UTC)
  8. What is TransNet?
    Tried to clarify. --Rschen7754 08:22, 14 July 2014 (UTC)
  9. Where you mentioned the expiration of TransNet doesn't seem like the right spot.
    There was a typo in the year in a nearby sentence, which is now fixed. --Rschen7754 08:22, 14 July 2014 (UTC)
  10. Pala Indian band? Is that the right word?
    Yes, it shows up in Google - it's not quite right to call it a tribe, that's too big. --Rschen7754 08:30, 14 July 2014 (UTC)
Major intersections
  1. The postmile refs are out of order.
    Fixed. --Rschen7754 06:17, 14 July 2014 (UTC)
  2. Does Old Highway 395 require a historical shield à la US 66?
    With both of them it's mostly for decoration... not signed on maps or anything. --Rschen7754 06:17, 14 July 2014 (UTC)
  3. Should the CRs be linked to their lists?
    Done. --Rschen7754 06:17, 14 July 2014 (UTC)

Overall, this is a fine work. I do recommend going over the prose again, or have the GoCE do it, before taking this to FAC just to catch anything we may have missed. –Fredddie™ 01:44, 14 July 2014 (UTC)

All done, and I always go over the prose before FAC. --Rschen7754 08:30, 14 July 2014 (UTC)

Spotcheck by Floydian

Not many online sources here that aren't simple highway inventories or legal acts. However, I've checked all the sources I can.

- 32 / 33 - checks out.
- 94 - Checks out
- 101 - All checks out
- 109 - Not seeing anything about the project finishing by the end of 2012. The second use of this ref is good though.

-- Floydian τ ¢ 18:56, 20 August 2014 (UTC)

I can email you more sources, if you want... I will take a look at 109 later tonight. --Rschen7754 01:07, 21 August 2014 (UTC)
Fixed - unfortunately I don't have the source, so I adjusted the wording and used a different source. --Rschen7754 02:43, 21 August 2014 (UTC)
Sure, I suppose it would make this more thorough, though I don't expect to find many offsets. Could you send me refs 38, 66 and 84? - Floydian τ ¢ 02:38, 22 August 2014 (UTC)
Done. --Rschen7754 02:45, 22 August 2014 (UTC)
Ref 66 checks out perfect. All the info you provide in the article is also in refs 38 and 84. However, both of those appear to mention other projects that you don't mention, ie the plan to convert the section from Mission Road to U.S. 395 to expressway. I'm assuming these were just conjectures at the time and never came to fruition under those plans, or that you mention it elsewhere in the history. Either way, I'm satisfied on verifiability. - Floydian τ ¢ 20:34, 22 August 2014 (UTC)
Sadly, that project isn't even complete yet. :/ But yes, all significant projects are mentioned in the article. --Rschen7754 01:06, 23 August 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

The article was promoted. SounderBruce 00:26, 30 August 2014 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Ontario Highway 403

Toolbox

Ontario Highway 403 (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: It's March Madness! I know I said I didn't want three reviews here at the same time again... but, there are still 10 noms to go! This is at least a better example of recent writing than 402. The highway has a more varied history and plenty of controversy to go with it! Cheers, Floydian τ ¢ 19:10, 6 March 2014 (UTC)
Nominated by: Floydian τ ¢ 19:10, 6 March 2014 (UTC)
First comment occurred: 04:08, 10 March 2014 (UTC)

Review by Dough4872

Review by Dough4872

I will review this article. Dough4872 04:08, 10 March 2014 (UTC)

Comments:

  1. The sentences "It exits the small city to the east. Shortly after exiting Brantford, the highway curves northeast." should be combined.
  2. Instead of "former Highway 2" or " former Highway 8", maybe you should mention the current name/number so today's readers can understand what the road is. A notation can be left to indicate this is the former highway at the first instance it is mentioned.
  3. "Scenic views of Hamilton, its harbour, and a waterfall are located along this steep descent.", maybe you can add the name of the waterfall as the linked article has a list of all the waterfalls in Hamilton.
  4. "This section features a reduced speed limit." maybe mention what the speed limit is reduced from to.
  5. The sentence "Access to Highway 410, continues northward to Brampton." is awkward and incomplete.
  6. "The plan showed the expressway's eastern terminus as the Highway 401 and Highway 427 interchange.", I would change "as" to "at".
  7. I would combine the sentences "The final section to be opened took the longest to complete, involving construction of two bridges over the Credit River valley. It opened on December 2, 1982. "
  8. "On March 24, 1987, Chris Ward, MPP for Wentworth North officially announced that construction of the missing link between Brantford and Ancaster would begin in 1989.[48] Construction did not actually begin until the summer of 1990.", was there a reason the construction began a year late? Dough4872 00:51, 12 March 2014 (UTC)
  1. Done
  2. Even today, 16 to 17 years after the mass downloads, the majority of county roads that were major highways back then are still referred to by the old name. In many cases they're named "Highway X" on signs and numbered/maintained under the county/local road networks! Botched to say the least. The problem comes that Highway 2 tracks through several counties alongside Highway 403, going by different names or numbers (if any number). It's much easier to understand by referencing the old highway number in prose in this case. For Highway 8, it's just local named streets now inside Hamilton. The junction list provides both designations.
  3. Done
  4. Can do, but not sure how to source it other than G.Maps SV
  5. Fixed... not sure when/how that happened but it was fine at one point :P
  6. Done, also swapped "showed" with "featured"
  7. Done with a semicolon
  8. Government... Actually I'm not sure. I think the budget in the spring of '89 fell in non-confidence and triggered an election that fall, delaying the funding or scheduling or something. The latter source doesn't mention anything about delays, just that it was tendered last summer.
Cheers, Floydian τ ¢ 01:05, 17 March 2014 (UTC)

Review by Fredddie

Comments by Fredddie

I'll take a look at this now. –Fredddie™ 04:31, 18 June 2014 (UTC)

Infobox and lead
  1. For the 1997 date, do you think the it would be better to say "Opened December 1, 1963<br>Completed August 15, 1997?
  2. Cleaned up some duplicate links
  3. The majority of Highway 403 is surrounded by suburban land use, except west of Brantford and between Brantford and Hamilton, ... Could you reword that so Brantford isn't repeated?
  4. In the last sentence, you might want to mention 401 again.
Route description
  1. I think with the subheaders, it would be better to say "X to Y".
  2. Clarification needed: "a now-channelized river from which the freeway may take its name.[7]" (my emphasis) Are you not sure that the freeway gets its name from the river?
  3. Thank you for using the verb form of interchange correctly.
The history section is excellent. The only thing I'd like to see is an adequate summary in the lead.
Junction list looks good.

Overall, this is very good work. I was really impressed by the history section. –Fredddie™ 04:59, 18 June 2014 (UTC)

Thank you for the review, I'm glad you enjoyed the read :) I've fixed up most of the points, although I still need to write a History summary. Regarding the Chedoke Creek, it's unclear (even to historians) where the name Chedoke came from. It's presumed to be from "seven oaks" that stood on the escarpment over the creek ravine. The creek got its name from that location, but it's unclear if the highway was named after the area, or the creek. - Floydian τ ¢ 16:51, 18 June 2014 (UTC)
@Fredddie: progress? --Rschen7754 18:54, 27 June 2014 (UTC)
I've been waiting for a notice that the history summary has been written. –Fredddie™ 23:39, 27 June 2014 (UTC)
Sorry for the delay (had to psych myself up to the task); a summary has been added, partially by relocating the summary that was the first paragraph of the "Bridging the gaps" subsection. - Floydian τ ¢ 21:35, 1 July 2014 (UTC)
Review by Rschen7754
Preliminary stuff
  1. Map needs a caption.
  2. Perhaps a color should be used for the concurrency in the RJL?
  3. Image captions: if it is a complete sentence, it should have a period. If not, it should not.
Route description
  1. "It travels along the back lot lines of the second concession" - not following this.
  2. "some distance" - a bit too vague.
  3. collector lanes - should be linked earlier than the history section...
History
  1. The first sentence seems like it has some words missing.
  2. other freeways for over 20 years - period missing.
  3. has always been important to Ontario -> always been considered important?
  4. I'm not sure about the use of italics - is this allowed?
  5. As Toronto's anti-expressway movement gained momentum, plans ... whose plans?
  6. alongside the hydro corridor from Burlington to Etobicoke Creek was protected ... what do you mean by this?
  7. late-1985 - should not be a hyphen
  8. three discontinuous sections; - should be a colon
  9. driveway-lined - too ambiguous
  10. was site - seems like something is missing from this
  11. Should be a comma after "In particular"
  12. First paragraph of Recent construction - using However twice very close to each other
  13. High-occupancy vehicle - should not be capitalized
  14. links will be completed - trying to predict the future here. --Rschen7754 00:28, 18 July 2014 (UTC)
  • I've numbered your points for ease of reply, I hope you don't mind.
Preliminary stuff
  1. Done
  2. I personally don't like using the concurrency termini colour (:P). I find it imparts nothing useful, since the existence of a concurrency is a minor detail compared to the route that it is concurrent with. In short, I feel a note accomplishes it better, and using the colours here would be inconsistent with other Ontario highways.
  3. I think they're all correct now.
RD
  1. Concessions were rectangles of properties dished out by the government in ye olde days. A concession had roads built on the north and south sides, and property lots faced those roads, divided down the centre of the concession. The back of those lots, down the centre of the concession, is where the highway was built, to avoid splitting farms. Not sure how to reword as such.
  2. Made it slightly (but not really) less vague
  3. Done
History
  1. Not sure where exactly... looks fine to me.
  2. Fixed
  3. Fixed
  4. I tend to use them to highlight terms or names, but I've removed them
  5. Fixed
  6. A right-of-way parallel to a hydro (power-transmission line) corridor was protected from being blobbed into cookie-cutter subdivisions.
  7. Fixed
  8. Fixed
  9. Fixed
  10. Reworded
  11. Added
  12. Changed the second instance
  13. Fixed
  14. Well... the planning docs have both the widening and the ramps in the same project... but reworded nonetheless to be not as absolute
Thank you for the review. Cheers, Floydian τ ¢ 05:53, 19 July 2014 (UTC)

Image review by Rschen7754

  • Regarding the aerial 1987 photo (I'm hoping you meant the uploader GoldDragon and not the nominator myself hehe), it looks like it was taken on approach or takeoff from Pearson Airport, so it's not too far fetched that he took it himself and scanned the photo (which would explain the small res and sunburnt colours). I have never seen this photo elsewhere on the internet, so I'm not sure. Added sources to the map (will also reupload it shortly with fixed colours and an inset of Canada) and fixed the licence / linked the escarpment pic. Cheers, Floydian τ ¢ 17:26, 25 July 2014 (UTC)

Spotcheck by Rschen7754

  • Source 8: good on CP and V.
  • Source 28: good on CP and V.
  • Source 55: good on V, but the wording is too close ("due to a sudden increase in volume", for one). Seems to have been inserted by the same editor mentioned above... you may wish to check all his edits to the page to be safe.
  • I think I added this info originally, then he put the source in and changed the wording to be, AGF, verifiable. It's actually coincidental, but I've removed that sudden increase in volume bit and reworded it the best I can... hopefully it's better now. - Floydian τ ¢ 00:32, 29 August 2014 (UTC)
  • Source 57: was scheduled to be added? since the article was written before the installation...
  • Source 58: good on CP and V.
  • Source 59: not seeing the dates in the article, though I would assume that it is included in the one just below it on the page.
  • Source 60: not seeing it.
All good and ready for close. --Rschen7754 13:28, 29 August 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Interstate 275 (Michigan)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Withdrawn. --Rschen7754 01:03, 4 August 2016 (UTC)

Toolbox

Interstate 275 (Michigan) (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: I think this is a high-quality account of a once controversial freeway in the Detroit area worthy of promotion up the scale.
Nominated by: Imzadi 1979 → 04:00, 21 June 2014 (UTC)
First comment occurred: 04:19, 21 June 2014 (UTC)

Review by Dough4872

Review by Dough4872

I will review this article. Dough4872 04:19, 21 June 2014 (UTC)

Comments:

  1. In the first paragraph of the route description, you use "freeway" in consecutive sentences. One of these should be changed.
  2. In the second paragraph of the route description, you mention Eureka Road and I-94 both provide access to the airport then backtrack to describe the section between those two interchanges then continue on skipping mention of where you pass I-94. I would reword this portion of the route description to keep it in chronological geographical south-to-north order or at least mention where it passes I-94 after mentioning the part of the route between the two interchanges.
  3. In the route description, you mention I-275 "crosses" a number of highways it interchanges with. You should use better wording to indicate that they are interchanges as crosses does not necessarily imply an interchange.
    • The verb "interchanges" would be wrong, since that implies a swap of locations/routings. The current wording is fine, and by being a freeway we already imply that all junctions are interchanges and that all other crossings are grade-separated unless specifically noted. Imzadi 1979 → 02:01, 22 June 2014 (UTC)
  4. Is the history of Michigan Avenue and Ford Road really relevant to the route description of I-275?
  5. Citation needed for "It also crosses over the same CSX line a third time."
  6. How is the I-275 bike path 44 miles while the highway is 35 miles?
  7. The history seems to be missing information on planning, you skip from the Yellow Book in the 1950s to when the freeway started being built in the 1970s.
  8. The history also seems to be missing information about groundbreaking or beginning dates of construction of the segments of the highway.
  9. Why are the inflation costs as of 2012? Shouldn't they be as of the current year?
    • As noted someone in a previous ACR, these adjusted numbers rely on government statistics that are released about 15–18 months after the year ends. Since we're almost halfway through 2014, that means 2012 is the most recent year. If you want 2014 numbers, wait until 2016. Imzadi 1979 → 02:01, 22 June 2014 (UTC)
  10. The sentence "The original plans for I-96 in the Yellow Book routed that highway along a different routing into downtown Detroit, along a path adjacent to Grand River Avenue." uses "along" twice.
  11. "M-275 would have cut through a state park in Oakland County if completed.", what is the name of the state park? Dough4872 00:34, 22 June 2014 (UTC)

Review by Fredddie

I will review this article shortly. –Fredddie™ 22:58, 24 August 2014 (UTC)

  1. I will work on a new map that shows Canada.
  2. Do you think it's worth it to replace all the hyphens with &8209;, the non-breaking hyphen? It could be how I have the page set up for reviewing, but I'm getting a lot of I-<br>275.
  3. What do you think of adding the bike trail to the KML?
  4. Something I can't figure out is why there is a length discrepancy between MDOT and FHWA.

This is a pretty good representation of why I typically don't review articles from Michigan. After you write a couple-twenty FAs, you have all the kinks worked out.   –Fredddie™ 16:36, 28 August 2014 (UTC)

@Imzadi1979: --Rschen7754 03:29, 7 October 2014 (UTC)
  1. Thanks.
  2. I dunno. I'm not opposed, but the last time such a thing was done on an article, someone else reverted it just before the FAC closed. *shrugs*
  3. Also, not opposed there. What should it be colored? Sadly, the WMA doesn't respect the color coding though, so the two lines will show as overlapping blue from the pop-up map.
  4. Simply, FHWA doesn't consider I-275 to overlap I-96, yet MDOT does, and the various cartographers follow MDOT. Imzadi 1979 → 06:10, 9 October 2014 (UTC)
    <voice style=toddler>But why?</voice> Surely there's an article from some time period where MDOT stated that signing I-275 over I-96 was a better navigational aid than not signing it. The only reason I push this is because it's a more interesting answer than looking at maps and saying what you see, which is how the article is now. –Fredddie™ 05:27, 19 October 2014 (UTC)
    Well, there is also the fact that I-275 was supposed to run further north, and I-96 ran along what is now M-5 until it was rerouted to follow I-275 and the modern routing of the Jeffries. After digging through Newspaperarchive.com and Newspapers.com, all I can find is that I-96/I-275 opens to traffic before I-275 north of the overlap was canceled, even though some planning studies had already started to call that extension M-275. Within months after that first cancelation, the highway was given some new life before being fully reinstated within the next two years. It wasn't until the mid-1980s that it was finally cancelled for good. It seems like MDOT keeps the number in place due to inertia. Imzadi 1979 → 08:32, 19 October 2014 (UTC)
@Fredddie: --Rschen7754 17:21, 11 October 2014 (UTC)

Image review by Rschen7754

Please consider reviewing other articles too; we have a significant backlog. --Rschen7754 03:28, 28 October 2014 (UTC)

Review by Evad37

Review by Evad37

Lead

  • I-275 crosses several area rivers and rail lines. – what's an "area river"?
  • segment is used in three consecutive sentences, maybe try a synonym for one of them.
  • Right of way has different meanings in other parts of the world, so it should be linked
  • Infobox junctions should use {{Plainlist}} format rather than <br>

Route description

  • Norfolk Southern Railway and Plymouth Township have duplicate links in close proximity
  • Lower Branch ... Middle Branch – are these meant to be proper names? River Rouge (Michigan) uses the common noun forms 'lower branch' and 'middle branch', but I don't know which way is correct.
  • The interchange with the Jeffries Freeway on the border between Plymouth Township and Livonia is where the FHWA considers I-275 to end. – This gave me a bit of a "huh?" moment when I first read it (as the lead states that The FHWA considers I-275 to end at the junction with I-96 and M-14). I think it might read better, especially to someone not familiar to the area, if this (as the first sentence of the paragraph) was consistent with the lead, ie leave mentioning Jeffries Freeway to the next sentence.
  • At the time the freeway ... remained on state transportation priority lists through the mid-1980s. – is it necessary to have this much history in the route description section?

Bike trail

  • About half the section is whitespace on my screen, any chance of playing around with the formatting and/or infobox content?

History

  • Detroit City Council - link?
  • stated the project – should this be 'stated that the project ?
  • more at-grade intersections than a full freeway doesn't sound right, as it implies that a full freeway may have some at-grade intersections

Exit list – no issues that I can see

Otherwise looking good - Evad37 [talk] 01:44, 18 November 2014 (UTC)

@Imzadi1979: --Rschen7754 04:43, 26 November 2014 (UTC)
Finally getting some time to work on this. The changes for the lead and history have been applied, although it might be an American-ism to use "area" as an adjective to mean "X in the area", as in "area schoolchildren attend Foobar Elementary School". As for the RD comments, I would say that the River Rouge article is wrong as my maps label it as a proper name.
As for the bit of history in the RD, it ties directly into the "useless concurrency" and part of the why I-275 overlaps I-96. You'll note that a reviewer above has asked for an answer "why" on the overlap, and this is the spot in the article where it fits best to touch on that. I've trimmed it a bit, and once I receive a few MDOT memos, I can actually write a short piece in the History section citing two memos where the department considered, and then rejected, removing the duplicate designation during the 1980s, but it is still RD material to note the intergovernmental conflict over where I-275 ends. Imzadi 1979 → 11:16, 3 December 2014 (UTC)

Support, looks good - Evad37 [talk] 02:08, 14 December 2014 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Michigan Heritage Route

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Withdrawn. --Rschen7754 01:04, 4 August 2016 (UTC)


Toolbox

Michigan Heritage Route (edit | talk | history | links | watch | logs) review

Suggestion: Promote to A-Class
Nominator's comments: This list has recently been updated with some generous assistance from MDOT. They are still looking for the source materials necessary to expand the last few entries into full dates, but I don't think that should hold us up from reviewing the list at this time.
Nominated by: Imzadi 1979 → 23:49, 13 July 2014 (UTC)
First comment occurred: 00:35, 14 July 2014 (UTC)

Review by Dough4872

Review by Dough4872

Comments:

  1. Do you think we can get a map of the heritage routes for the infobox, possibly color-coding them by type?
  2. Do you think you can add a section to the list discussing the history of the heritage routes program?
  3. In the description section of the list, I would add some details as to what makes each heritage route either "historic", "recreational", or "scenic". For example, what makes the Chief Noonday Trail Recreational Heritage Route "recreational"?
  4. For the three proposed heritage routes, do you know what type they will be?

Overall, the basic structure of the list is fine as it lists all the basic facts and statistics that would be associated with any road. The preceding four points are just suggestions on how this list can be further improved to provide a model for lists of scenic byways. Dough4872 00:35, 14 July 2014 (UTC) Replies:

  1. The KML is up, and I've e-mailed a copy to my trusty cartographically enabled friend for a map. Hopefully one will be available soon.
  2. I will look into this point a little later and follow up afterwards.
  3. I'll see what I can do without breaching original research restrictions, but I think the various management plans MDOT sent me may have some details.
  4. No, I don't. MDOT only shows two on their map without indicating what type they might be assigned. The third is based on news article, and those articles also fail to mention which type it might be assigned if approved. Imzadi 1979 → 04:47, 14 July 2014 (UTC)
    @Dough4872: the map was added and I've added a history section as well as some notes on on features that pertain to the historic, recreational or scenic qualities of the routes. Imzadi 1979 → 11:22, 14 October 2014 (UTC)
Review by Rschen7754
Preliminary stuff
  • Images: (not an image review) the captions need a bit of work, there are some with complete sentences with no period, and some missing words on a few.
  • See also: "that run along county roads that are not eligible to be Michigan Heritage Routes" - awkward
  • Some dead links.
Program
  • thereby, providing economic benefits by stimulating tourism - fragment after a semicolon.
  • this report details the any new additions in the previous year - extra "the"
  • First - need comma after
Content
  • Northern Monroe city limists

Otherwise should be a support. --Rschen7754 20:09, 26 October 2014 (UTC)

@Rschen7754: all done, although to resurrect the dead link, I had to use a screen capture generated by a third-party archiving site to which we can't directly link at this time. The screen capture is sitting on Commons. Imzadi 1979 → 05:43, 27 October 2014 (UTC)
Support issues resolved. --Rschen7754 13:24, 27 October 2014 (UTC)
Image review by Rschen7754

Rschen7754 19:19, 8 November 2014 (UTC)

The three individual heritage route markers are not PD under federal law. They are creations of a department of the State of Michigan, so there is no automatic dedication into the public domain like with works of the federal government. Rather, we have an OTRS ticket that says all of Michigan's highway signs are public domain, so that's the license we have to use: the one that says they released the signs into the PD by MDOT. Imzadi 1979 → 00:23, 9 November 2014 (UTC)
Also, the barn photo has a license, {{attribution}}, which is located in the permission section of the information box. Imzadi 1979 → 00:53, 9 November 2014 (UTC)
Doing a bit of research, it is technically a valid enough license for Commons not to delete the file, though it could be at risk of being deprecated in the future. But the check is   Done. --Rschen7754 17:31, 9 November 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:WikiProject_Highways/Assessment/A-Class_Review/2014&oldid=640152875"