FOREST FIRE DATA BASES Sample Clauses

FOREST FIRE DATA BASES. In 1992 a forest fire research project was within the Swiss National Research Program 31 (NRP 31) arid Disasters by the. branch station south of of the Swiss Federal Institute €or Forest, Snow and Landscape Research Sottostazione Sud Alpi). The NRP 31 enabled to reconstruct data date, time, duration, cause of ignition, area burnt, fire type, forest habitat, and other variables from more than 5500 fire events since 1900 (Conedera et al. 1993). This has been in a relational database. A similar data base is now in progress for the canton of Wallis (Bochatay and Moulin 1998). The spatial and temporal analysis of Occurrence has been studied for the canton of Grison through a case study et al. 1998).
AutoNDA by SimpleDocs

Related to FOREST FIRE DATA BASES

  • -1 Data Base The Contractor providing a health or human services within Vermont, or near the border that is readily accessible to residents of Vermont, will provide relevant descriptive information regarding its agency, programs and/or contact and will adhere to the "Inclusion/Exclusion" policy of Vermont's United Way/Vermont 211. If included, the Contractor will provide accurate and up to date information to their data base as needed. The “Inclusion/Exclusion” policy can be found at xxx.xxxxxxx000.xxx

  • Data Backup The Services do not replace the need for Customer to maintain regular data backups or redundant data archives. PROVIDER HAS NO OBLIGATION OR LIABILITY FOR ANY LOSS, ALTERATION, DESTRUCTION, DAMAGE, CORRUPTION OR RECOVERY OF CUSTOMER DATA.

  • Data Backup Plan Contractor must have established documented procedures to backup DHCS PHI to maintain retrievable exact copies of DHCS PHI or PI. The plan must include a regular schedule for making backups, storing backups offsite, an inventory of backup media, and an estimate of the amount of time needed to restore DHCS PHI or PI should it be lost. At a minimum, the schedule must be a weekly full backup and monthly offsite storage of DHCS data.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Information about Contractor Employees 23.1. The Authority may by notice require the Contractor to disclose such information as the Authority may require relating to those of the Contractor’s employees carrying out activities under or connected with the Framework Agreement.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Data shared with Subcontractors If DSHS Data provided under this Contract is to be shared with a subcontractor, the Contract with the subcontractor must include all of the data security provisions within this Contract and within any amendments, attachments, or exhibits within this Contract. If the Contractor cannot protect the Data as articulated within this Contract, then the contract with the sub- Contractor must be submitted to the DSHS Contact specified for this contract for review and approval.

Time is Money Join Law Insider Premium to draft better contracts faster.