Imagery Grid and Capture Types Sample Clauses

Imagery Grid and Capture Types. Exhibit A.1 – Statement of Work – Oblique Images
Sample 1
AutoNDA by SimpleDocs

Related to Imagery Grid and Capture Types

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • Bilateral Safeguard Measures 1. Where, as a result of the reduction or elimination of a customs duty under this Agreement, any product originating in a Party is being imported into the territory of another Party in such increased quantities, in absolute terms or relative to domestic production, and under such conditions as to constitute a substantial cause of serious injury or threat thereof to the domestic industry of like or directly competitive products in the territory of the importing Party, the importing Party may take bilateral safeguard measures to the minimum extent necessary to remedy or prevent the injury, subject to the provisions of paragraphs 2 to 10. 2. Bilateral safeguard measures shall only be taken upon clear evidence that increased imports have caused or are threatening to cause serious injury pursuant to an investigation in accordance with the procedures laid down in the WTO Agreement on Safeguards. 3. The Party intending to take a bilateral safeguard measure under this Article shall immediately, and in any case before taking a measure, make notification to the other Parties and the Joint Committee. The notification shall contain all pertinent information, which shall include evidence of serious injury or threat thereof caused by increased imports, a precise description of the product involved and the proposed measure, as well as the proposed date of introduction, expected duration and timetable for the progressive removal of the measure. A Party that may be affected by the measure shall be offered compensation in the form of substantially equivalent trade liberalisation in relation to the imports from any such Party. 4. If the conditions set out in paragraph 1 are met, the importing Party may take measures consisting in increasing the rate of customs duty for the product to a level not to exceed the lesser of: (a) the MFN rate of duty applied at the time the action is taken; or (b) the MFN rate of duty applied on the day immediately preceding the date of the entry into force of this Agreement. 5. Bilateral safeguard measures shall be taken for a period not exceeding one year. In very exceptional circumstances, after review by the Joint Committee, measures may be taken up to a total maximum period of three years. No measure shall be applied to the import of a product which has previously been subject to such a measure. 6. The Joint Committee shall within 30 days from the date of notification examine the information provided under paragraph 3 in order to facilitate a mutually acceptable resolution of the matter. In the absence of such resolution, the importing Party may adopt a measure pursuant to paragraph 4 to remedy the problem, and, in the absence of mutually agreed compensation, the Party against whose product the measure is taken may take compensatory action. The bilateral safeguard measure and the compensatory action shall be immediately notified to the other Parties and the Joint Committee. In the selection of the bilateral safeguard measure and the compensatory action, priority must be given to the measure which least disturbs the functioning of this Agreement. The compensatory action shall normally consist of suspension of concessions having substantially equivalent trade effects or concessions substantially equivalent to the value of the additional duties expected to result from the bilateral safeguard measure. The Party taking compensatory action shall apply the action only for the minimum period necessary to achieve the substantially equivalent trade effects and in any event, only while the measure under paragraph 4 is being applied. 7. Upon the termination of the measure, the rate of customs duty shall be the rate which would have been in effect but for the measure. 8. In critical circumstances, where delay would cause damage which would be difficult to repair, a Party may take a provisional emergency measure pursuant to a preliminary determination that there is clear evidence that increased imports constitute a substantial cause of serious injury, or threat thereof, to the domestic industry. The Party intending to take such a measure shall immediately notify the other Parties and the Joint Committee thereof. Within 30 days of the date of the notification, the procedures set out in paragraphs 2 to 6, including for compensatory action, shall be initiated. Any compensation shall be based on the total period of application of the provisional emergency measure and of the emergency measure. 9. Any provisional measure shall be terminated within 200 days at the latest. The period of application of any such provisional measure shall be counted as part of the duration of the measure set out in paragraph 5 and any extension thereof. Any tariff increases shall be promptly refunded if the investigation described in paragraph 2 does not result in a finding that the conditions of paragraph 1 are met. 10. Five years after the date of entry into force of this Agreement, the Parties shall review in the Joint Committee whether there is need to maintain the possibility to take safeguard measures between them. If the Parties decide, after the first review, to maintain such possibility, they shall thereafter conduct biennial reviews of this matter in the Joint Committee.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Contract Database Metadata Elements Title: Great Neck Union Free School District and Great Neck Paraprofessionals Association (2011) Employer Name: Great Neck Union Free School District Union: Great Neck Paraprofessionals Association Local: Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 5132 Unit Size: Number of Pages: 28 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/ ARTICLE# TITLE PAGE# Preamble 2 Article 1 Association Rights 2 Article 2 Board-Administration-Association Relationship and Procedures 4 Article 3 Exchange of Proposals 6 Article 4 Professionals Duties and Responsibilities of Paraprofessionals 7 Article 5 Work Assignments 8 Article 6 Annual Appointment 10 Article 7 Selection and Promotion 10 Article 8 Evaluations and Standards 11 Article 9 Procedures for Termination of Employment 11 Article 10 Conferences 12 Article 11 Human Resource File 12 Article 12 Professional Growth 13 Article 13 Sick Leave 14 Article 14 Personal Leave 16 Article 15 Other Leaves 17 Article 16 Grievance Procedures 18 Article 17 Legal Assistance 19 Article 18 Conformity to Law 19 Article 19 Health Insurance 20 Article 20 Retirement Plan 20 Article 21 Salary Schedule 21 Article 22 Seniority Policy 23 Article 23 Compensation for Financial Loss 24 Article 24 Duration of Agreement 25 Appendix A Determination of Negotiating Unit 25 Appendix B Payroll Deduction Authorization 26 Appendix C Bus Aides 26 Appendix D Salary Schedules 27

  • Technical Safeguards 1. USAC and DSS will process the data matched and any data created by the match under the immediate supervision and control of authorized personnel to protect the confidentiality of the data, so unauthorized persons cannot retrieve any data by computer, remote terminal, or other means. 2. USAC and DSS will strictly limit authorization to these electronic data areas necessary for the authorized user to perform their official duties. All data in transit will be encrypted using algorithms that meet the requirements of the Federal Information Processing Standard (FIPS) Publication 140-2 or 140-3 (when applicable). 3. Authorized system users will be identified by User ID and password, and individually tracked to safeguard against the unauthorized access and use of the system. System logs of all user actions will be saved, tracked and monitored periodically. 4. USAC will transmit data to DSS via encrypted secure file delivery system. For each request, a response will be sent back to USAC to indicate success or failure of transmission.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!