Talk:New York State Route 36/GA1

GA Review
The edit link for this section can be used to add comments to the review.''

Reviewer:  Dough 48  72  04:01, 11 December 2010 (UTC)
 * GA review (see here for criteria)

 I am placing the article on hold for fixes to be made.  Dough 48  72  04:01, 11 December 2010 (UTC)
 * 1) It is reasonably well written.
 * a (prose): b (MoS):
 * The sentence "The highway runs in an approximate north–south direction for 95 miles (153 km) from the Pennsylvania state line at Troupsburg, Steuben County—where it continues as Pennsylvania Route 249 or PA 249—northward to Ogden, Monroe County, where it ends east of the village of Brockport at an intersection with NY 31." should be split. Can the use of "NY 36" in the route description be cut down? The sentence "5 miles (8 km) north of Arkport in the town of Dansville, NY 36 intersects the current southern terminus of NY 70 at an intersection due east of Canaseraga." should not begin with a numeral. "NY 36 heads northwestward across gradually less developed areas as it traverses the west side of a wide, flat valley known locally as the flats.", is "the flats" supposed to be all lowercase? "junction of Main and Buffalo (NY 33) Streets" looks awkward, can this be reordered? The sentence "It never reaches the hamlet, however, as NY 36 intersects the western terminus of NY 531 (Spencerport Expressway) and ends at a junction with NY 31 100 yards (91 m) later at intersections 0.5 miles (0.8 km) south of Adams Basin." sounds awkward.
 * a) Trimmed/split.
 * b) Some uses replaced.
 * c) I don't see a problem with this, but it's been reworded anyway.
 * d) Probably. There's no formal name for the gully; I've seen "Genesee River flats", "river flats", and just "flats" used interchangably.
 * e) Word order changed.
 * f) I have no idea what happened there. Totally reworded.
 * 1) It is factually accurate and verifiable.
 * a (references): b (citations to reliable sources):  c (OR):
 * Most of the route description is sourced from Yahoo Maps. Is it possible for another source to be added to supplement it?
 * As I commented on IRC, I don't see a need to do so. Much of the RD was derived from the cited map, and citing what was derived from it to something else would be a bit misleading. I added the 2009 DOT log for NY 36's termini, but I'm not seeing a need for additional refs for anything else.
 * 1) It is broad in its coverage.
 * a (major aspects): b (focused):
 * Can some more details about the physical surroundings of the route be added to the article? Does it pass through farmland or woodland in rural areas? Are there any historical events that have occurred to the road since the 1950s? Is it possible for street names to be added to the junction list?
 * a) I'm not seeing a need to get super-detailed here, considering the route's 96 miles long. I bet if you asked some editors from other states, they'd say that it's too long as it is. (I don't believe so, but I bet others do.)
 * b) Ditto. Expanding the RD to cover exactly what the route traverses puts far too much weight on areas that are otherwise unremarkable.
 * c) If you examine the RD, it mentions a 1970s realignment in Hornell. The reason it's in the RD and not the history is that it fits better there. In the history, it'd either be a one or two-sentence paragraph or a tack-on sentence somewhere.
 * d) I get this for a local route, but for a route that traverses so many locations and miles, I'm not seeing the point. It should also be noted that many of these routes don't have names when 36 meets them.
 * 1) It follows the neutral point of view policy.
 * Fair representation without bias:
 * 1) It is stable.
 * No edit wars, etc.:
 * 1) 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):
 * 1) Overall:
 * Pass/Fail:
 * 1) Overall:
 * Pass/Fail:
 * Pass/Fail:
 * Replied above. –  T M F 04:44, 11 December 2010 (UTC)
 * I will now pass the article.  Dough 48  72  04:51, 11 December 2010 (UTC)