Stickney, Kansas

Stickney is an unincorporated area in Wheatland Township, Barton County, Kansas, United States.[1][2] It is the site of a grain elevator, but there is no community or settlement at Stickney.[3]

Stickney, Kansas
KDOT map of Barton County (legend)
Stickney
Stickney
Coordinates: 38°38′17″N 98°49′46″W
CountryUnited States
StateKansas
CountyBarton
TownshipWheatland
Elevation
1,955 ft (596 m)
Time zoneUTC-6 (CST)
  Summer (DST)UTC-5 (CDT)
ZIP code
67544
Area code620
GNIS ID484733[1]

History

A post office opened at Stickney in 1898 and remained in operation until 1913.[4]

Geography

Stickney is located at 38°38′17″N 98°49′46″W (38.6380672, -98.8295292) at an elevation of 1,955 feet (596 m).[1] It is 1 mile (1.6 km) east of U.S. Route 281 and 19 miles (31 km) north of Great Bend, the county seat.[5]

Stickney lies roughly 1.5 miles (2.4 km) east of Sellens Creek, a tributary of the Smoky Hill River, in the Smoky Hills region of the Great Plains.[5][6]

Transportation

Stickney lies at the intersection of NW 190 Road, a paved east–west county road, and NW 30 Avenue, an unpaved north–south county road.[5]

The Atchison, Topeka and Santa Fe Railway formerly operated a freight rail line that ran east–west through Stickney, but the line has since been removed.[2][5]

gollark: It works on my phone's Firefox for Android, but *not* on another Firefox on Linux install which isn't signed into my account.
gollark: I assume they would be HTTP or HTTP/2 ones, and while I seem to be able to see the rest of those going to my server, there's just *nothing* for the websocket.
gollark: This is weird. I may be capturing wrong, or... Firefox just isn't actually sending any requests to make the websocket?
gollark: I tried looking at it in Firefox's network pane in the debug thing, the websocket connection just doesn't show. I also tried mitmproxy, which also doesn't show anything. Now I'm trying wireshark, but I don't know how to work that, though it seems to show discord opening websockets okay.
gollark: I know websockets don't work with HTTP2 because it doesn't support protocol upgrade, but as far as I know it should just use HTTP 1.1, and Chrome does this.

References

Further reading



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