Monday, October 27, 2014

Have you traveled on ND Highway's first roundabout?

Every Monday we welcome our daughter Kirsti to blog from her home in Western North Dakota's oil patch. Take it away Kirsti.

Now you have.

Or at least, you've seen a video from the dash of a vehicle going through it.

Close enough? I hope so.

North Dakota's first traffic roundabout was installed at the intersection of Highways 22 and 200 in Killdeer in 2012. It assists in moving traffic through the busy intersecting truck routes and is great improvement to the four-way stop that was used formerly. The roundabout started out as a bit of an experiment, testing to see if it was a good fit for all the truck traffic that travels on the routes. It was quickly deemed a success and has continued to be thought of as such.

Now, I know these are a commonplace elsewhere in the world. But here? It's the first. Having the first of anything in our great state is pretty neat.

Things are getting fancy in the oil field!

(Or at least the traffic is flowing better.)

Have a great week!
-Kirsti

Pin It

3 comments:

  1. First roundabout on at the intersection of two highways.

    Plenty of roundabouts already in the state.

    ReplyDelete
    Replies
    1. Yes, indeed, there are nine roundabouts in Fargo and four in West Fargo. I don't know if that is plenty as there is one being planned in Grand Forks and Bismarck may have a roundabout or two. All in cities and not on highways.Reviews are mixed as to added safety, especially in icy conditions, which are common for about six months of the year. Thank you for reading the blog.

      Delete
  2. Modern roundabouts are the safest form of intersection in the world. Visit http://tinyurl.com/iihsRAB for modern roundabout FAQs and safety facts. Modern roundabouts, and the pedestrian refuge islands approaching them, are two of nine proven safety measures identified by the FHWA, http://tinyurl.com/7qvsaem
    The FHWA has a video about modern roundabouts that is mostly accurate (http://tinyurl.com/6v44a3x).

    ReplyDelete