Talk:U.S. Route 730
Appearance
(Redirected from Talk:U.S. Route 730 in Oregon)
U.S. Route 730 has been listed as one of the Engineering and technology good articles under the good article criteria. If you can improve it further, please do so. If it no longer meets these criteria, you can reassess it. | ||||||||||
|
This article is rated GA-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
GA Review
[edit]GA toolbox |
---|
Reviewing |
- This review is transcluded from Talk:U.S. Route 730/GA1. The edit link for this section can be used to add comments to the review.
Reviewer: Viridiscalculus (talk · contribs) 23:15, 25 March 2013 (UTC)
I plan to review this article this week. VC 23:15, 25 March 2013 (UTC)
- General
- Do a wikilink check. There are a large number of excessive wikilinks. You should only have one link for each subject in the Lead and either no links or one link, at most, for each subject in the body prose of the article. In addition, there are two dablinks (Washington State Route 12 and Columbia River Highway) and two redirect links (U.S. Route 730 Spur and U.S. Route 730 Spur (Washington)).
- Removed most of the wikilinks and fixed the dablinks, but I'll keep the first mention in RD/History overall.
- The dablinks are gone. The redirect links are still there. You should link to the subsection of the article #Spur route instead of the redirect article because the redirect article is never going to be an independent article.
- There's only one redirect link left, in the RJL.
- There are still lots of repeated links. There remain two in the RD and many in the sections below that. There is a Highlight Duplicate Links gadget you should use that highlights links that appear more than once in the prose below the Lead. Per WP:OVERLINK, you should only have one wikilink for each topic below the Lead. VC 00:50, 29 March 2013 (UTC)
- Removed the two in RD, should I remove all links (e.g. I-84 and US 12) from the History and spur route sections? SounderBruce 17:10, 29 March 2013 (UTC)
- Yes, you should remove all wikilinks unless the subject has not previously been wikilinked in the body of the article. VC 17:30, 30 March 2013 (UTC)
- Removed all repeated wikilinks in the history and spur route sections.
- Columbia River Highway No. 2 and I-82 are still overlinked. Once you solve those, you are done. VC 02:00, 3 April 2013 (UTC)
- Got them. Done
- Columbia River Highway No. 2 and I-82 are still overlinked. Once you solve those, you are done. VC 02:00, 3 April 2013 (UTC)
- Removed all repeated wikilinks in the history and spur route sections.
- Yes, you should remove all wikilinks unless the subject has not previously been wikilinked in the body of the article. VC 17:30, 30 March 2013 (UTC)
- Removed the two in RD, should I remove all links (e.g. I-84 and US 12) from the History and spur route sections? SounderBruce 17:10, 29 March 2013 (UTC)
- The dablinks are gone. The redirect links are still there. You should link to the subsection of the article #Spur route instead of the redirect article because the redirect article is never going to be an independent article.
- Removed most of the wikilinks and fixed the dablinks, but I'll keep the first mention in RD/History overall.
- In full dates, if the date does not end the sentence, you need a comma after the year. When using a city and state, if the state does not end the sentence, you need a comma after the year. "The Japanese selected December 7, 1941, to attack Pearl Harbor, Hawaii, and drag the U.S. into the war." Also, once you mention the state a city is in anywhere in the article, you should not mention it again. There are multiple inclusions of "Wallula, Washington."
- Dates and states fixed
- There are still three instances of city, state in the History and a county, state in the Spur route section that are not necessary because the cities/county are already introduced as being in those states. The dates are fine. VC 00:50, 29 March 2013 (UTC)
- All three instances corrected
- I still see several instances. "Cold Spring Junction, Oregon" is still in the History. San Diego and Spokane do not need the states because they are well known cities, but you can leave the state if you want. But if you keep the state, you need to put a comma after the state. VC 17:30, 30 March 2013 (UTC)
- Removed the CSJ in History and added commas after Spokane, Washington and San Diego, California.
- Sorry, I keep finding more. Hopefully this one is the last: Umatilla, Oregon in the Lead does not need the state. VC 02:00, 3 April 2013 (UTC)
- Removed. Done
- Sorry, I keep finding more. Hopefully this one is the last: Umatilla, Oregon in the Lead does not need the state. VC 02:00, 3 April 2013 (UTC)
- Removed the CSJ in History and added commas after Spokane, Washington and San Diego, California.
- I still see several instances. "Cold Spring Junction, Oregon" is still in the History. San Diego and Spokane do not need the states because they are well known cities, but you can leave the state if you want. But if you keep the state, you need to put a comma after the state. VC 17:30, 30 March 2013 (UTC)
- All three instances corrected
- There are still three instances of city, state in the History and a county, state in the Spur route section that are not necessary because the cities/county are already introduced as being in those states. The dates are fine. VC 00:50, 29 March 2013 (UTC)
- Dates and states fixed
- Route description
- There are only three paragraphs, so it is not necessary to split the Route description into subsections.
- Just following a precedent for multi-state highways
- "between its western terminus at I-84 and US 30 east of Boardman to the end of its concurrency with US 395 in Umatilla." The "and" between I-84 and US 30 makes this sentence confusing. Either remove "and US 30" (I do not think its inclusion is essential.) or change "between" to "from"
- Removed US 30 Done
- There are a lot of repeated details from the Lead in the Route description, such as "continuation of Columbia River Highway No. 2" and "rural Morrow County in Eastern Oregon". The Lead is supposed to be a summary. You should determine which details should be in the Route description and which should be in the Lead. For instance, the first quote is a detail that should only be in the Route description or in the History, if the term is no longer used for the current highway. In the second quote, Eastern Oregon should be in the Lead as a general geographic identifier. Let me know whether you have questions because you should reread the sections and fix more than just the examples listed here.
- The term is still used for the highway internally by ODOT. As for regional details, I removed as many as I could from the RD and History.
- I think you could do better on avoiding repetition, but I am not going to press the issue unless you want me to point them out. VC 00:50, 29 March 2013 (UTC)
- The term is still used for the highway internally by ODOT. As for regional details, I removed as many as I could from the RD and History.
- "short, 0.79-mile-long (1.27 km) concurrency" Using "short" and the exact length is redundant. Use one or the other.
- Removed exact length Done
- "the northern terminus of OR 207" The abbreviation OR has not been previously defined, so you need to properly introduce it here.
- Added the abbreviation. Done
- "The highway turns northeastward along Lake Wallula and a Union Pacific rail line after the northern terminus of OR 37 at Cold Springs Junction, heading into Washington.[10][11]" You should mention the lake is a reservoir of the Columbia River. The RJL mentions Warehouse Beach Recreation Area but the RD does not. Also, the OR 37 junction includes a wye and an overpass of the road to the recreation area. You should go into more detail instead of treating it as a bump in the word on the way to the state line.
- Mentioned the recreation area as well as a nearby state park. Done
- I suggest you move the Washington legislative sentence to the first paragraph of the Route description.
- Moved up.
- No, I said the first paragraph of the Route description, not the top of the Washington section. VC 00:50, 29 March 2013 (UTC)
- I misread that. Moved up to the correct section. Done
- No, I said the first paragraph of the Route description, not the top of the Washington section. VC 00:50, 29 March 2013 (UTC)
- Moved up.
- "This is expressed in AADT" The acronym AADT needs to be introduced.
- Introduced Done
- "In 2012, WSDOT that the Washington section of US 730 served between 1,500 and 2,400 vehicles, mostly at the Oregon state line.[14]" Remove the last clause of the sentence because there is nothing between the state line and US 12 that diverts traffic. Add "per day" or some kind of time modifier after "vehicles." Why is there an AADT range instead of a single value? Are there AADT numbers for Oregon?
- ODOT doesn't release AADT numbers to the public. The WSDOT AADT log includes multiple points on the highway, which range from the two stated averages.
- The last sentence has "In 2012, WSDOT that" I think there is a word or words missing. VC 00:50, 29 March 2013 (UTC)
- Forgot to add "calculated" in between Done
- The last sentence has "In 2012, WSDOT that" I think there is a word or words missing. VC 00:50, 29 March 2013 (UTC)
- ODOT doesn't release AADT numbers to the public. The WSDOT AADT log includes multiple points on the highway, which range from the two stated averages.
- History
- "US 730 within Oregon" The U.S. Highway System was not put in place until 1926, so you should use a modifier like "the highway that became US 730" when referring to the pre-1926 roads.
- Replaced Done
- "US 730 was subsequently extended west to Boardman in Morrow County,[22] later moved further south to its present interchange with I-84,[23][24] signed as I-80N until 1980.[25]" This sentence is missing a lot of years.
- Added the decade
- Do you have more specific dates for each clause of the sentence? There are three references there that have years attached, so you should be able to be more specific about when these changes occurred, even if it is just "was extended west to Boardman by 1964." VC 00:50, 29 March 2013 (UTC)
- Found a newspaper ref that gives the extension in 1962, with the I-84 interchange being built between 1964 and 1967. Done
- Do you have more specific dates for each clause of the sentence? There are three references there that have years attached, so you should be able to be more specific about when these changes occurred, even if it is just "was extended west to Boardman by 1964." VC 00:50, 29 March 2013 (UTC)
- Added the decade
- Spur route
- The infobox is missing the highway's length.
- Added to infobox
- I still do not see a length in the infobox (the small one for US 730 Spur). VC 00:50, 29 March 2013 (UTC)
- Forgot to specify that the length is in miles. Done
- I still do not see a length in the infobox (the small one for US 730 Spur). VC 00:50, 29 March 2013 (UTC)
- Added to infobox
- Major intersections
- Is the spur signed at all? It does not seem like an unsigned spur route is notable to include on its own line in the RJL. Perhaps just mention it in the Notes of the US 12 line?
- It is signed, I believe. WSDOT usually signs all spur routes with the proper plate or as the parent highway. Done
- Photo
- The license looks fine. It is not necessary to wikilink Lake Wallula in the caption.
- Un-linked Done
- References
- Ref 5 is a dead link.
- Fixed, I accidently linked to an Oregon map under the Idaho directory Done
- Are the quotes of the legislative material necessary in refs 16 and 17?
- I do think they are necessary
- I disagree, especially because you provide page numbers. But I am not going to press the issue. VC 00:50, 29 March 2013 (UTC)
- Point taken. Removed quotes in favor of letting readers look through the session laws themselves. Done
- I disagree, especially because you provide page numbers. But I am not going to press the issue. VC 00:50, 29 March 2013 (UTC)
- I do think they are necessary
- Do you have an author for ref 25?
- There was no credit for the author of the article and the ref was removed. Done
I will put this article on hold. VC 19:59, 26 March 2013 (UTC)
- All concerns have been addressed, so I will pass the article. VC 01:17, 5 April 2013 (UTC)
Categories:
- Wikipedia good articles
- Engineering and technology good articles
- GA-Class U.S. Highway system articles
- Mid-importance U.S. Highway system articles
- GA-Class Road transport articles
- Mid-importance Road transport articles
- U.S. Highway system articles
- GA-Class Oregon road transport articles
- Mid-importance Oregon road transport articles
- Oregon road transport articles
- GA-Class Washington road transport articles
- Mid-importance Washington road transport articles
- Washington road transport articles
- GA-Class U.S. road transport articles
- Mid-importance U.S. road transport articles
- U.S. road transport articles
- GA-Class United States articles
- Low-importance United States articles
- GA-Class United States articles of Low-importance
- GA-Class Washington articles
- Low-importance Washington articles
- WikiProject Washington articles
- GA-Class Eastern Washington task force articles
- Low-importance Eastern Washington task force articles
- Eastern Washington task force articles
- WikiProject United States articles
- GA-Class Oregon articles
- Low-importance Oregon articles
- WikiProject Oregon pages