This article is within the scope of the U.S. Roads WikiProject, an attempt to build a comprehensive and detailed guide to
state highways and other major
roads in the
United States. If you would like to participate, you can edit the article attached to this page, or visit the
project page, where you can join the project and/or contribute to the
discussion.U.S. RoadsWikipedia:WikiProject U.S. RoadsTemplate:WikiProject U.S. RoadsU.S. road transport articles
This article is within the scope of WikiProject United States, a collaborative effort to improve the coverage of topics relating to the
United States of America on Wikipedia. If you would like to participate, please visit the project page, where you can join the ongoing discussions.
Unnecessary when the the rest of the lead already states the direction, and the length is covered in the infobox.
Nova Crystallis(Talk) 16:52, 18 February 2022 (UTC)reply
Ok you are correct you can leave it this way. It would just sound better the other way because if someone that lived in Alabama or travelling west reading this would think it begins at the east end. -
420Traveler (
talk) 22:35, 18 February 2022 (UTC)reply
Add sources to the existed from date in the infobox.
"and the route travels eastward into rural, forested Lauderdale County" Change "into" to "through", as it sounds like it didn't start in Lauderdale County. -
420Traveler (
talk) 22:41, 18 February 2022 (UTC)reply
How do I use the traffic count reference? You need to add directions to the reference such as "Select Lauderdale County then zoom into route 496" or something similar. -
420Traveler (
talk) 14:46, 19 February 2022 (UTC)reply
Maybe you should click on the reference and read the instructions.
Nova Crystallis(Talk) 17:10, 19 February 2022 (UTC)reply
I did but to the average reader its not that clear. Here is an example: [1] -
420Traveler (
talk) 14:54, 20 February 2022 (UTC)reply
@
420Traveler: how is this reference any different from the Kansas PMIS reference? I don't recall seeing instructions for that in any article? –
Fredddie™ 04:13, 23 February 2022 (UTC)reply
My mistake, I didn't see that was already discussed. However, if I find that in a Kansas article I'm going to remove it especially if it's as poorly worded as it is. –
Fredddie™ 04:18, 23 February 2022 (UTC)reply
History
The history section is good. You dont have to, but I found an
article that you could add to lead up to the 1964 project. -
420Traveler (
talk) 15:43, 18 February 2022 (UTC)reply
Major intersections
I would add the exact length and the source that backs it up. I realize that Mississippi doesn't have route logs like new york or kansas has for example, so the mileage for MS 897 can rely on google.
There are no public sources that state the exact length for the intersections within the route.
Nova Crystallis(Talk) 16:44, 18 February 2022 (UTC)reply
I know, but there is for the east terminus so add that and leave the MS 897 length as a google reference. The total shouldn't be different in the major intersections than the infobox. -
420Traveler (
talk) 22:24, 18 February 2022 (UTC)reply
It's confusing to the reader that they are both different. -
420Traveler (
talk) 14:32, 19 February 2022 (UTC)reply
So you would rather lie instead? I'm not changing my mind on this.
Nova Crystallis(Talk) 16:47, 19 February 2022 (UTC)reply
How is that lying? Im saying to leave mileage for MS 897 at 12.4 miles with the google reference and change the eastern terminus to 13.198 with reference #1. Its done like this in many other road articles. -
420Traveler (
talk) 20:54, 19 February 2022 (UTC)reply
(Outside comment) The guidelines at
MOS:UNCERTAINTY permit rounding in cases where the level of precision has no bearing on how the content is read. The difference here is so minor that it's not worth spilling ink over. SounderBruce 21:11, 19 February 2022 (UTC)reply
@
Imzadi1979:, sorry to bother you, just need a second opinion on this. Is it ok to leave it the way it is or should bothe mileages be the same? Thanks for the help. -
420Traveler (
talk) 14:53, 20 February 2022 (UTC)reply
Ideally, the terminal intersection should have the length as its milepost, or be mathematically the length (say if the other terminus isn't set at 0.000, the difference between the two should equal the length of the highway).
The level of precision of the mileposts though is almost more important. I've run into situations where a single milepost, determined using an alternative source, was given with greater precision than technically warranted so that the decimal points stayed lined up down the column of the table. The reverse situation would apply here: rounding everything down to the same level of precision for consistency. That consistency aids readability of the numbers in the table. If other articles are mixing precision, they should be changed. We should round off lengths in prose, (please do so in the lead sentence), so if the infobox is the only location with the full precision, that's ok too. There are some other issues in the article, but I'll leave that to another conversation. Imzadi 1979→ 00:28, 21 February 2022 (UTC)reply
Final comments
Just a quick run-through, will add more later. -
420Traveler (
talk) 15:54, 18 February 2022 (UTC)reply
Passing now as you have fixed everything. -
420Traveler (
talk) 16:37, 25 February 2022 (UTC)reply
^Kansas Department of Transportation (2014).
"2014 Condition Survey Report". Topeka: Kansas Department of Transportation.
Archived from the original on March 19, 2012. Retrieved August 2, 2015. For Wilson County type '47' for route number, type '4' for district number, type '103' for county number; for Neosho County type '47' for route number, type '4' for district number, type '67' for county number; for Crawford County type '47' for route number, type '4' for district number, type '19' for county number; then add all three values for total mileage.