By: James Bonanno
Traffic volume is one of the most important pieces of information that transportation professionals consider when building or updating road infrastructure. Volumes are systematically collected using automated technology at locations statewide to provide reliable average daily counts of vehicles along corridors and in intersections.
Traffic volumes are also important in the planning and design of pedestrian and bicyclist infrastructure; however, such data is not systematically collected the way that it is for vehicles. Pedestrian and bicycle traffic is usually counted on a case by case basis that gives a snapshot of what traffic could be like in an area. If the weather is bad on the days that the counting is planned to take place, counts may be significantly lower than on an average day with nice weather. Vehicle traffic data on the other hand, is collected frequently throughout the year and compounded into an average daily traffic volume. Recording this data over a longer period of time results in a better representation of the actual traffic volume the corridor may experience in an average day.
Vehicle counts are collected frequently thanks to the automated technologies used to collect the data. One method is laying a simple rubber tube across the road, attached to a counter. Every time a car drives over it, a count is registered. These counts give planners and engineers a good representation of how the corridor is being used and helps them in their decisions to improve the corridor. Pedestrian and bicycle traffic however, has traditionally been recorded manually. This process is time consuming, monotonous, expensive, and can yield unreliable results. In busy urban areas with high pedestrian and bicycle traffic, it can be very difficult for an employee to keep up with the amount of people and bicycles passing by. Video cameras can be used, but an employee must still go through the videos and manually count each pedestrian and bicyclist, as the automated video-counting technology is not always reliable.
The New Jersey Department of Transportation has acknowledged this shortcoming in pedestrian and bicycle traffic data and has begun researching new technologies to implement that will provide accurate pedestrian and bicycle traffic data. Infrared Beam Counters, Passive Infrared Counters, Piezoelectric Pads, Laser Scanners, and Computer Vision are all emerging technologies in pedestrian counting that NJDOT has considered. Each is a viable option for counting pedestrians and bicyclists but each also has its own drawbacks.
In addition, there are tools available to count bicyclists, such as the same rubber tube used to count cars, or induction loops installed in the pavement. These devices do a good job at counting bicyclists but cannot count pedestrians at all.
These are some of the current technologies being considered by the New Jersey Department of Transportation to improve the accuracy of pedestrian and bicycle counts. Which technology is installed will ultimately depend on multiple factors having to do with each devices count accuracy, cost, availability, and deployment method.
A good example of pedestrian counting can be taken from Melbourne, Australia. The city uses overhead sensors to count pedestrians and bicyclists and decipher which direction they are moving. Twenty-eight sensors are at work counting twenty-four hours a day, seven days a week and the information is all publicly available on the internet. They can do this because the sensors track movements instead of images resulting in anonymous travel data.
In New Jersey, the new Route 52 Bridge to Ocean City was built with technology to count pedestrians and bicyclists. The multi-use path on the side of the bridge uses a combination of infrared beam and induction loop to count and differentiate between pedestrians and bicyclists. You can read more about it here.
Having more systems such as this deployed in New Jersey could provide excellent pedestrian and bicycle travel information and help planners and engineers make future pedestrian and bicycle infrastructure decisions.