Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 150
 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]
Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 151
 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]
Warning (512): Unable to emit headers. Headers sent in file=/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php line=853 [CORE/src/Http/ResponseEmitter.php, line 48]
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 148]
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 181]
LATEST NEWS UPDATES | Uttarakhand report: Time to rethink our development models

Uttarakhand report: Time to rethink our development models

Share this article Share this article
published Published on May 1, 2014   modified Modified on May 1, 2014
-The Hindustan Times
 

The June 2013 disaster in Uttarakhand had taken many - including the state administration - by surprise. But it should not have been so because it was a tragedy waiting to happen. The immediate reason may have been a natural cause - the state was hit by its heaviest rainfall on record that month, causing lakes and rivers to burst their banks, inundating towns and villages downstream - but the collateral damage was excessively high because of the successive state governments' desire to build hydropower projects in a fragile ecosystem.

 

This view has now been corroborated by the findings of a Supreme Court-mandated panel. In a report released on Monday, the panel said that badly managed hydropower projects were partly to blame for the floods.
The building of hydroelectric plants, it added, had led to the build-up of huge volumes of sediment in rivers that was not managed properly. The sediment raised river beds during the floods and was then flushed downstream, aggravating the severity of the flooding.

 

The plan for building what is called bumper-to-bumper hydroelectric plants has been controversial from day one. However, it is not just the green lobby that was warning the state against such construction hara-kiri: In 2010, a Comptroller and Auditor General's (CAG's) report warned that large stretches of the Ganga will dry up if these hydroelectric power projects were built. According to the CAG, some projects, outrageous as it may sound, had gone to cycle manufacturers, paan masala firms and garment manufacturers with no experience in building hydropower projects, leave alone constructing them in seismic zones like the Himalayas.

The panel findings highlight the problem facing the country, one of the world's lowest per-capita energy consumers, as it rushes to expand power generation to meet rising demand. But as India progresses and formulates plans to meet its various demands - land, water, energy, etc - it has to clearly answer one question: Can we go for unsustainable myopic development plans that may have disastrous consequences for its citizens in the long run?


The Hindustan Times, 30 April, 2014, http://www.hindustantimes.com/comment/it-s-time-to-seriously-rethink-our-development-models/article1-1214151.aspx


Related Articles

 

Write Comments

Your email address will not be published. Required fields are marked *

*

Video Archives

Archives

share on Facebook
Twitter
RSS
Feedback
Read Later

Contact Form

Please enter security code
      Close