Hackberry Road Study Log Out | Topics | Search
Moderators | Register | Edit Profile

City of Frisco Question and Answer Board » Archive » Hackberry Road Study « Previous Next »

  Thread Last Poster Posts Pages Last Post
  Start New Thread        

Author Message
 

Mark Varvil
New member
Username: Mvarvil

Post Number: 4
Registered: 02-2004
Posted on Thursday, April 29, 2004 - 09:07 am:   

I recently saw the traffic counter cables stretched across Hackeberry @ 423. Can you share with us the results of the study?

There is a HUGE increase in traffic on Hackberry now. So many cars are taking Hackberry around the main street and 423 stoplight during the week. And on the weekends, there is a constant and steady stream of traffic traveling to Hidden Cove Park.

I have lived in Saratoga off of Hackberry for 9 years, and can attest to the traffic increase, but I was curious as to what the study actually showed.

Thanks,
Mark Varvil
 

Brian Moen, Traffic Engineer
Moderator
Username: Brian

Post Number: 173
Registered: 07-2001
Posted on Thursday, April 29, 2004 - 05:37 pm:   

Mark,

The counts are probably being conducted by TxDOT, Denton County, or a private developer. The latest traffic count we have is from June 2003. That count was 798 vehicles in a 24 hour period. To see the count information maintained by the City of Frisco, please use the following link.

http://maps.ci.frisco.tx.us/

The link will take you to the GIS maps section of our homepage. Once in the GIS maps area, click on the traffic flow map box and then click the update map button. You will see various color coded links. If you move the pointer over the colored link, a text box will appear that has the traffic count information for that area.

Thanks
Brian Moen
Transportation Manager
bmoen@friscotexas.gov

Add Your Message Here
Post:
Username: Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Password:
Options: Post as "Anonymous"
Enable HTML code in message
Automatically activate URLs in message
Action: