Indiana State Road 269

State Road 269 (SR 269) is a part of the Indiana State Road that runs through rural Posey County in US state of Indiana. The 0.89 miles (1.43 km) of SR 269 that lie within Indiana serve as a mirror highway. None of the highway is listed on the National Highway System. The whole length is a rural two-lane highway. The highway passes through farmland and woodland properties.

State Road 269
SR 269 highlighted in red
Route information
Maintained by INDOT
Length0.890 mi[1] (1.432 km)
Major junctions
West endHarmonie State Park
East end SR 69
Location
CountiesPosey
Highway system
← SR 267SR 301 →

Route description

SR 269 begins at a rural intersection in Posey County at County Road 330 and Old Dam Road. The route heads southeast away from Harmonie State Park, as a two-lane highway, passing through farmland and woodland. The highway turns due east and heads towards SR 69. SR 269 ends at a 3-way intersection with SR 69.[2][3]

No segment of SR 269 is included as a part of the National Highway System (NHS).[4] The NHS is a network of highways that are identified as being most important for the economy, mobility and defense of the nation.[5] The highway is maintained by the Indiana Department of Transportation (INDOT) like all other state road in the state. The department tracks the traffic volumes along all state highways as a part of its maintenance responsibilities using a metric called average annual daily traffic (AADT). This measurement is a calculation of the traffic level along a segment of roadway for any average day of the year. In 2010, INDOT figured that 100 vehicles and 10 commercial vehicles AADT along the route.[6]

Major intersections

The entire route is in Lynn Township, Posey County.

mi[1]kmDestinationsNotes
0.0000.000 SR 69 – New Harmony, Mt. VernonEastern terminus of SR 269
0.8901.432Harmonie State ParkWestern terminus of SR 269
1.000 mi = 1.609 km; 1.000 km = 0.621 mi
gollark: I thought about that, but:- strings in a binary format will be about the same length- integers will have some space saving, but I don't think it's very significant- it would, in a custom one, be harder to represent complex objects and stuff, which some extensions may be use- you could get some savings by removing strings like "title" which XTMF repeats a lot, but at the cost of it no longer being self-describing, making extensions harder and making debugging more annoying- I am not convinced that metadata size is a significant issue
gollark: I mean, "XTMF with CBOR/msgpack and compression" was being considered as a hypothetical "XTMF2", but I'd definitely want something, well, self-describing.
gollark: Also also, why a binary format?
gollark: Also, XTMF can do runtime update, you just need to allocate, say, 4KB at the start of the tape, and write metadata to that. The offsets might be fiddly, though.
gollark: You should probably not do that.

References
  1. Indiana Department of Transportation (July 2015). Reference Post Book (PDF). Indianapolis: Indiana Department of Transportation. Retrieved October 4, 2016.
  2. Google (November 6, 2012). "Indiana State Road 269" (Map). Google Maps. Google. Retrieved November 6, 2012.
  3. Indiana Department of Transportation (2012). Indiana Transportation Map (PDF) (Map) (2011–2012 ed.). 1:550,000. Indianapolis: Indiana Department of Transportation. § O1–O2. OCLC 765461296.
  4. Federal Highway Administration (December 2003). National Highway System: Indiana (PDF) (Map). Scale not given. Washington, DC: Federal Highway Administration. Retrieved November 6, 2012.
  5. "National Highway System". Federal Highway Administration. August 26, 2010. Retrieved August 9, 2011.
  6. "INDOT Traffic Zones". Indiana Department of Transportation. 2010. Archived from the original on May 5, 2011. Retrieved July 9, 2012.

KML is from Wikidata
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.