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: 629
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: 629
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: 629
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: 629
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: 629
Function: headerdata
File: /home/iweblogix/iweblogix/demo/hpforest/php/index.php
Line: 315
Function: require_once
Western Tragopan is among the rarest pheasants, endemic to a narrow range in the temperate region of the Greater Himalaya, between Northwest Frontier Province in Pakistan and western Uttarakhand in India (Birdlife International 2001). With only 2,000-3,000 sq. km area of potential habitat available, its world population size is precariously low, with much fewer than 5,000 individuals as per the estimate in early 1980s. This species is a habitat specialist, favouring conifer and oak communities with sufficient undergrowth of bamboo and other dense vegetation. The state of Himachal Pradesh is a stronghold for this species as it is distributed widely in sizable populations in all three major catchments (Beas, Satluj and Ravi) and also serves ‘flagship’ value on account of socio-cultural linkages with the traditional people. These attributes essentially guided the successful declaration of Western tragopan as 'the State Bird’ of Himachal Pradesh.
While concerted efforts are continuing for in-situ management within the limits of resource pool (both fiscal and trained man-power), conservation breeding of Western Tragopan has long been included in the conservation agenda of the State, attributed to (a) small population size of the species in the wild, (b) virtually no captive population anywhere in the world, and (c) no credible technical know-how for breeding the species in captivity. Presently, there are 24 captive birds in Sarahan Pheasantry which is the only place in the world to hold Western Tragopan in captivity.
Given the conservation significance attached to Western Tragopan, it is important to maintain a viable captive population (ex-situ conservation) and it has huge potential for supporting conservation in the wild by supplementing individuals to existing populations and reintroduction wherever required. Although it may not be a desperate necessity to reintroduce this species in wild at present, the species is likely to face such situation if the prevailing conditions in the field continue. It is, therefore, critical that adequate scientific skills and infrastructure for captive breeding are developed.
Central Zoo Authority (CZA) of India had approved a Project for Conservation Breeding of Western Tragopan at Sarahan Pheasantry during 2003-04 for Rs. 493.90 lac in 2003 having CZA share Rs.364.95 lac and State share Rs.128.95. Conservation breeding which is breeding for supporting conservation in wild or in-situ conservation is highly challenging, particularly of rare and elusive species for which no prior successful experiences exist. Recently from 2010-11 onwards, Wildlife Institute of India has also been associated in this programme for effective implementation of this conservation programme both at in-situ and ex-situ level.
During the year 2012, a total of seven females incubated the eggs naturally, which represents nearly 75% of the individuals of the captive population and is the highest number of females incubating the eggs naturally till now. Seven chicks have been mother reared. A state wide survey has also been planned during the year 2013 across the distribution range to assess the status of the natural populations and threats to this species.
?© 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.