Follow Us
Sukhmeet Bhasin
Tribune News Service
Bathinda, July 18
Confusion prevails over new zebra crossing and yellow lines marked in the city by the Municipal Corporation Bathinda (MCB).
It has surfaced that before marking these lines, no suggestions from experts were taken. The MCB has spent Rs 31 lakh on this work this year.
Sanjeev Goyal, an RTI activist and a resident of Model Town, had sought information from the MCB regarding the rules, regulation, terms and conditions followed while marking these lines.
He also sought information on the space that is to be left for parking a vehicle.
The MCB, in its reply, has stated that they didn’t have any information regarding this and such data should be sought from the traffic police.
The MCB has also written a letter to the in-charge of the traffic police asking the person concerned to give this information directly to Sanjeev Goyal and also communicate it to the MCB.
The traffic police, in their reply have clarified that painting yellow lines, leaving the space and making footpath was the work of the MCB, which had conducted it through its contractor.
“The traffic police have no concern with the information as their function is to regulate the traffic. Having said that we are returning the copy of your letter,” traffic police officials said.
Sanjeev Kumar has alleged that the MCB was wasting the government money on marking zebra crossing, white and yellow lines without taking any suggestion from any department.
The MCB didn’t even set norms regarding the drawing of these road markings, he added.
Kumar said even the MCB had admitted it in the RTI information.
In 2013-14, the MCB spent Rs 13.87 lakh on drawing zebra crossing, white and yellow lines in the city.
In 2014-15, it spent Rs 18.43 lakh on the work. While from April 1, 2015, till February 6, 2016, it spent Rs 9.85 lakh on marking traffic lines.
Municipal Commissioner Sanyam Aggarwal said marking of yellow lines and zebra crossing was done with the help of the traffic police.
DSP (Traffic) Gurjit Singh Romana could not be contacted over the issue despite repeated attempts.
1
3
6