Jump to content

Talk:Washington State Route 503

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Good articleWashington State Route 503 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.
Article milestones
DateProcessResult
February 12, 2013Good article nomineeListed

Orphaned references in Washington State Route 503

[edit]

I check pages listed in Category:Pages with incorrect ref formatting to try to fix reference errors. One of the things I do is look for content for orphaned references in wikilinked articles. I have found content for some of Washington State Route 503's orphans, the problem is that I found more than one version. I can't determine which (if any) is correct for this article, so I am asking for a sentient editor to look it over and copy the correct ref content into this article.

Reference named "log":

  • From Washington State Route 529: Washington State Department of Transportation, State Highway Log, 2006
  • From Washington State Route 527: Washington State Department of Transportation. "State Highway Log, 2006" (pdf). Retrieved 2008-09-24.
  • From Washington State Route 599: Washington State Department of Transportation. "State Highway Log, 2006" (pdf). Retrieved 2008-09-28.
  • From Washington State Route 538: Washington State Department of Transportation. "State Highway Log, 2006" (PDF). Retrieved 2007-04-22.
  • From Washington State Route 543: "State Highway Log - Planning Report" (PDF). Washington State Department of Transportation. 2007. pp. pg 1562. Retrieved 2008-08-17. {{cite web}}: |pages= has extra text (help)

I apologize if any of the above are effectively identical; I am just a simple computer program, so I can't determine whether minor differences are significant or not. AnomieBOT 00:36, 12 November 2008 (UTC)[reply]

GA Review

[edit]
GA toolbox
Reviewing
This review is transcluded from Talk:Washington State Route 503/GA1. The edit link for this section can be used to add comments to the review.

Reviewer: Dough4872 (talk · contribs) 03:26, 11 February 2013 (UTC)[reply]

GA review (see here for criteria)

  1. It is reasonably well written.
    a (prose): b (MoS):
    • As with SR 17, there are a lot of instances of commas followed by -ing verbs. Most of these should be reworded.
    •  Done Reduced to 4 in the RD (not including the AADT)
    • The sentence "The highway crosses the East Fork of the Lewis River and leaves Battle Ground to pass Lewisville Park, listed on the National Register of Historic Places,[11] located in the community of the same name, heading northeast into a heavily forested region of the Cascades foothills." needs to be split.
    •  Done
  2. It is factually accurate and verifiable.
    a (references): b (citations to reliable sources): c (OR):
  3. It is broad in its coverage.
    a (major aspects): b (focused):
  4. It follows the neutral point of view policy.
    Fair representation without bias:
  5. It is stable.
    No edit wars, etc.:
  6. It is illustrated by images, where possible and appropriate.
    a (images are tagged and non-free images have fair use rationales): b (appropriate use with suitable captions):
  7. Overall:
    Pass/Fail:

I will place the article on hold for a couple fixes to be made. Dough4872 02:19, 12 February 2013 (UTC)[reply]

I will now pass the article. Dough4872 02:42, 12 February 2013 (UTC)[reply]

"six-phase plan to provide congestion relief to the 502/503 corridor..."

[edit]

Hey everyone,

Local news article about recent completions of a third part of a six-phase overhaul project involving the 502 & 503 routes, here - [1]. Looks like the 503 page is lacking any of this project so this is more a heads up if someone finds it worthy to add (and it's not my strong suit, so I leave it up to experienced transpo writers). I'll go ahead and post this on the 502 talk page as well.

Cheers! Shortiefourten (talk) 18:06, 25 September 2023 (UTC)[reply]