Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 132
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 292
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 166
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 235
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 315
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 356
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 282
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 294
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 304
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 375
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/iweblogix/iweblogix/demo/hpforest/php/system/core/Exceptions.php:271)
Filename: include/header.php
Line Number: 6
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/views/frontendpages/include/header.php
Line: 6
Function: header
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 859
Function: view
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 681
Function: headerdata
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/iweblogix/iweblogix/demo/hpforest/php/system/core/Exceptions.php:271)
Filename: include/header.php
Line Number: 7
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/views/frontendpages/include/header.php
Line: 7
Function: header
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 859
Function: view
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 681
Function: headerdata
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/iweblogix/iweblogix/demo/hpforest/php/system/core/Exceptions.php:271)
Filename: include/header.php
Line Number: 8
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/views/frontendpages/include/header.php
Line: 8
Function: header
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 859
Function: view
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 681
Function: headerdata
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/iweblogix/iweblogix/demo/hpforest/php/system/core/Exceptions.php:271)
Filename: include/header.php
Line Number: 9
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/views/frontendpages/include/header.php
Line: 9
Function: header
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 859
Function: view
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 681
Function: headerdata
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /home/iweblogix/iweblogix/demo/hpforest/php/system/core/Exceptions.php:271)
Filename: include/header.php
Line Number: 15
Backtrace:
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/views/frontendpages/include/header.php
Line: 15
Function: header_remove
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 859
Function: view
File: /home/iweblogix/iweblogix/demo/hpforest/php/application/controllers/Frontend.php
Line: 681
Function: headerdata
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Sr. No. | Name of Projects / Schemes | Year | Name of Village Institution | No. of Village Institutions | Registered under |
---|---|---|---|---|---|
1 | HP Forestry Project (HPFP) | 1994-2001 | Village Forest Development Committees (VFDCs) | 154 | JFM Notification dated 12.5.1993 |
2 | Indo-German Eco-Development Project | 1994-2005 | Village Development Committees (VDCs) | 294 | JFM Notification dated 12.5.1993 |
3 | IWD (Kandi) Project | 1993-2005 | Village Development Committees (VDCs) | 137 | Societies of Registration Act 1860 |
4 | Sanjhi Van Yojana (SVY) | 1998 Ongoing | Village Forest Development Societies (VFDS) | 360 | Societies of Registration Act 1860 |
5 | Great Himalayan National Park | 1993 Ongoing | Village Eco-Development Committee (VEDCs) | 18 | Director, GHNP |
6 | Mid Himalayan Watershed Dev Project | 2005 Ongoing | Gram Panchayats | 602 | --- |
7 | National Afforestation Project (NAP) | 2010 Ongoing | Joint Forest Management Committees (JFMC) | 963 JFMCs | Registered by CFs/DFOs as per the provision laid down in Revised Operational Guidelines, 2009 of NAEB. |
8 | Integrated Watershed Management Swan River Project | 2006 Ongoing | Project Development Committees | Not available | Societies of Registration Act 1860 |
In the year 2002-03, National Afforestation and Eco-Development Board (NAEB) of the Ministry of Forests and Environment (MOEF), Govt, of India (GOI) initiated the National Afforestation Programme (NAP) with a broad objective of regeneration and eco-development of degraded forests. At present there are 1562 registered JFMCs out of which 963 JFMCs are active in carrying out the NAEB works in H.P. which are involved in execution of National Afforestation Programme.
Till the year 2009-10, FDAs were funded directly by the NAEB. However, in November 2009 revised operational guidelines were issued by the NAEB whereby it was enjoined upon the States to constitute State Forest Development Agency (SFDA) which was required to be registered as a society under Societies Registration Act. The chairperson of the SFDA would be Principal Chief Conservator of Forests and Chief Conservator Forests (PFM) would function as its member secretary. The hands from NAEB would be directly transferred to SFDA which, in turn, would transfer the funds to FDAs as per the Work Programme which would be approved by the NAEB. During 2010, SFDA H.P. was constituted and got registered under IIP Society Registration Act, 2006. From the year 2010-11 onward the NAP is being implemented in the state of Himachal Pradesh through SFDA. At present FDAs have been constituted in 36 territorial forest divisions, WL division Chamba and GHNP.
Year | Physical Targets achieved(ha) | Expenditure incurred (Rs. in Lakhs) |
---|---|---|
2007-08 [only 11 FDAs] | 1719 | 644.31 |
2008-09 [only 9 FDA] | 2263 | 448.17 |
2009-10 [only 7 FDA] | 2263 | 675.37 |
2010-11 [only 36 FDA] | 2467.10 | 575.40 |
2011-12 [only 36 FDA] | 1337.78 | 325.41 |
2012-13 [only 36 FDAs] | 2126.32 | 240.50 |
2013-14 [only 36 FDAs] | 1312 | 247.99 |
2014-15 [only 36 FDAs] | 303 | 62.59 |
joint Forest Management is a national program through which communities have been involved in forest management since the 1990s1. There are over one hundred thousand Joint Forest Management Committees (JFMCs) that are protecting and managing over 22 million hectares of forest lands in the country. Although initially JFM was supported through projects and initiatives of individual officers and NGOs, it was subsequently institutionalized through the National Afforestation Programme (NAP), a flagship scheme of the National Afforestation and Eco-Development Board (NAEB), MoEF&CC, Government of India. Under NAP, a three-tier institutional structure has been developed with jFMCs (or Eco-development Committees (EDCs)) at the village level, Forest Development Agencies (FDAs), which are federations of the JFMCs, at the Territorial Forest/Wildlife Division level, and State Forest Development Agencies (SFDAs), which are federations of FDAs, at the state level.
JFM and institutions promoted through it are important from the climate change perspective as these are the core institutional structures suggested under the National Mission for a Green India, one of the eight missions formulated under the National Action Plan on Climate Change (NAPCC). The Mission proposes revamping of JFMCs by reconstituting these as sub-committees of Gram Sabha and by devolving adequate powers to them for protecting and managing forests and deriving benefits from them2.
Himachal Pradesh has around two decades of experience with the JFM approach . i he state government issued the first JFM Notification in 1993 for constitution of Village Forest Development Committees (VFDCs). In 2001, Himachal Pradesh Participator)' Forest Management Rules were issued for registration of Village Forest Development Societies (VFDSs) under the Societies Registration Act. Subsequently - 2002-03 onwards - JFMCs were constituted and federated into FDAs at the Forest Division level with support from NAP. The JFMCs are registered with HPFD as per the provisions of the NAP guidelines, whereas FDAs are registered as Societies. The SFDA was constituted in 2010 in accordance with the central guidelines.
?© 2022 Himachal Pradesh Forest Department, Government of Himachal Pradesh. All rights reserved.
Content on this website is published and managed by HP Forest Department. For any query regarding this website, please contact the "Web Information Manager" at hpfd.itlab@gmail.com.