Known Sites Database Sample Clauses

Known Sites Database. ‌ The Known Sites Database (KSD) identifies infrastructure, and cultural and natural resource sites throughout Alaska that may be threatened by wildfire. The dataset provides locations, descriptions, and jurisdictions, as well as direction regarding site protection priorities. The data are made available to fire managers through a password protected website in order to support wildland fire planning and decision-making. There are two primary sources of site information included in the KSD: • Jurisdictional Agency inventory and assessments may be directly submitted to AFS GIS at XXX_XX_XXX_XXX@xxx.xxx for immediate incorporation into the KSD. • Data collected by IMTs will be submitted to the local dispatch office for the incident along with the final fire package. The dispatch office will then provide that information to AFS GIS and the appropriate Jurisdictional Agency(ies) through the known sites clearinghouse. Data in the clearinghouse are preliminary, and subject to approval by Jurisdictional Agency administrative units on which sites reside. o Preliminary datasets will not be incorporated into the KSD until they have been verified by the Jurisdictional Agency. o Preliminary datasets will be viewable on the ArcIMS known sites map. The KSD will be updated by April 1. Each time the dataset is updated, and upon request, AFS GIS will provide metadata, summarizing changes, to all entities (Protecting and Jurisdictional Agencies’ FMOs as well as pertinent Native partners). The metadata will contain a list of Global Unique Identifiers with the action taken on the site (i.e., added, deleted, changed geographically, and changed attributes). Usernames and passwords to access the KSD can be requested through AFS GIS at XXX_XX_XXX_XXX@xxx.xxx. In 2017 Known Sites data structure and update processes are undergoing a revision. AWFCG will be notified as changes are implemented.
Sample 1See All (4)
AutoNDA by SimpleDocs

Related to Known Sites Database

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Location Data Apple and its partners, licensees and third party developers may provide certain services through the Apple Software that rely upon location information. To provide and improve these services, where available, Apple and its partners, licensees and third party developers may transmit, collect, maintain, process and use your location data, including the real-time geographic location of your computer, and location search queries. The location data and queries collected by Apple are collected in a form that does not personally identify you and may be used by Apple and its partners, licensees and third party developers to provide and improve location-based products and services. By using any location-based services provided by or through the Apple Software, you agree and consent to Apple's and its partners', licensees' and third party developers’ transmission, collection, maintenance, processing and use of your location data and queries to provide and improve such products and services. You may withdraw this consent at any time by going to the Location Services setting in the Apple Software and either turning off the global Location Services setting or turning off the individual location setting of each location-aware application on your computer. The Location Services setting is found in the Security & Privacy pane within System Preferences. When using third party applications or services on your computer that use or provide location data, you are subject to and should review such third party's terms and privacy policy on use of location data by such third party applications or services.

  • Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.

  • Customer Data 5.1 The Customer shall own all right, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Access to Customer Data You agree that we may, for the purposes of providing Maintenance and Customer Support and/or for the purpose of otherwise protecting the integrity of the Software, access and/or download your Customer Data on a limited basis.

  • Geological and Archeological Specimens If, during the execution of the Work, the Contractor, any Subcontractor, or any servant, employee, or agent of either should uncover any valuable material or materials, such as, but not limited to, treasure trove, geological specimens, archival material, archeological specimens, or ore, the Contractor acknowledges that title to the foregoing is vested in the Owner. The Contractor shall notify the Owner upon the discovery of any of the foregoing, shall take reasonable steps to safeguard it, and seek further instruction from the Design Professional. Any additional cost incurred by the Contractor shall be addressed under the provision for changed conditions. The Contractor agrees that the Geological and Water Resources Division and the Historic Preservation Division of the Georgia Department of Natural Resources may inspect the Work at reasonable times.

  • PRIVACY INFORMATION Through Your Use of the Website and Services, You may provide Us with certain information. By using the Website or the Services, You authorize the Company to use Your information in the United States and any other country where We may operate.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

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