Entry Features Sample Clauses

Entry Features. Entry Features and signs are to be regulated per the LDC. Entry features and signs may be constructed at the entrance/exit to the project in approximate locations as shown on the Master Plan. The Owner reserves the right to construct secured entry gates. Vehicular access shall be designed to accommodate emergency vehicle access at both access locations, pursuant to dimensional requirements defined by the LDC.
Sample 1Sample 2
AutoNDA by SimpleDocs
Entry Features. “Purchasers are advised that entry features may be located on the southwest corner of Xxxxxxxx Road and Chinguacousy Road and on the southeast corner of Brisdale Drive and Xxxxxxxx Road as per the City of Brampton Community Design Guidelines. For further information, please contact the City of Brampton, Development Engineering Division at (000) 000-0000 or by email to xxxxxxxx.xxxxxxxxxxx@xxxxxxxx.xx”
Sample 1Sample 2
Entry Features. The Development entrances and the boundary along Easthampton Blvd. shall be attractively landscaped in a manner that is acceptable to the City and may contain a wall/fence and permanent monument type project signage.
Sample 1
Entry Features. The Developer may install stamped or colored concrete or brick pavers in the private streets and sidewalks to create a distinctive entry feature into the Project. The Developer may install a freestanding entry monument sign (“Entry Sign”) for the Project at the intersection of the Southerly Access, described in Section 5.1, above, and the private road leading into the Project, such placement must be consistent with the Flagstaff Zoning Code. The Entry Sign shall be placed on property belonging to the Pinnacle Pines Homeowners Association and shall conform to all of the provisions of the Flagstaff Zoning Code, including those related to freestanding signs, location, size, material and illumination. Prior to construction, the Development shall receive a Sign Permit from the City to ensure compliance to the Zoning Code and the provisions of this Agreement.
Sample 1
Entry Features. The entrance to the Project shall be attractively landscaped with subdivision identification features meeting the LDC. The Project may be gated from within the Project road system at the Owner’s option; provided, however, that the roadways are designed so that there is no external stacking possible from the Project onto Xxxx Drive.
Sample 1
Entry Features. There should be a significant landmark feature marking the gateway or entrance. This feature could be part of the architecture of a signature building, a work of public art, or major environmental feature in addition to, or instead of, gateway posts or fence walls.
Sample 1
Entry Features. Development entry features may be up to 16 feet in 9 height as measured vertically from the finished grade at the base of the supporting 10 structure, however, any proposed entry features shall incorporate architectural variations 11 between 8 feet to 16 feet. The design for all entry features shall be substantially similar 12 to the elevations attached as Exhibit “C”.
Sample 1
AutoNDA by SimpleDocs
Entry Features. “Purchasers and Tenants are hereby advised that an entry features will be located on the southwest corner of Xxxxxxxx Road and Xxxxxxx Road as per the Parkside Heights Community Design Guidelines. For further information, please contact the City of Brampton, Development Engineering Division at (000) 000-0000 or by email to xxxxxxxx.xxxxxxxxxxx@xxxxxxxx.xx.” “Purchasers and Tenants are hereby advised that Block 223 (corner gateway feature) and the roundabout (special character area at the intersection of Arctic Turn Avenue and Housefinch Avenue) will be landscaped and function as entry features to the neighbourhood.”
Sample 1
Entry Features. Each use shall include an entry feature at the curb cut. This visual feature can be combined with signage in compliance with the applicable ordinance. The entry feature should be visually integrated with the landscaping features.
Sample 1

Related to Entry Features

  • Contract Database Metadata Elements Title: Xxxxxxx-Xxx Xxxxx Central School District and Xxxxxxx-Xxx Xxxxx Teachers Association (2007)

  • User Content You retain your rights in Your Content, subject to the rights granted below and our rights in Our Property (as defined below). You hereby grant and agree to grant us a worldwide, non-exclusive, perpetual, irrevocable, royalty-free, fully-paid, transferable license, with the right to sublicense through multiple tiers, to copy, edit, modify, adapt, publish, transmit, distribute, prepare derivative works, perform, display and to otherwise use in any manner, Your Content in connection with operation and promotion of the Service and any other purposes reasonably related to the Service or our business. To the extent reasonably necessary or appropriate to effect or support the license granted by you above, you hereby waive and agree to waive (or if not waivable, agree not to assert) any rights of privacy or publicity, or any moral rights or other similar rights, with respect to Your Content. You agree that we are not responsible for any use or disclosure of Your Content by other Users or any third party who gains access to it through the Service (which may include unintended activities by third parties, such as by hackers). You represent and warrant that you own all proprietary rights in Your Content or, with respect to any of Your Content you do not own, that you have the full authority and right to create, upload, store and/or transmit Your Content, and to grant the licenses and rights you have granted in this Agreement, and that your creation, uploading, storage and/or transmission of Your Content, and the exercise by us and other Users of the licenses and rights granted by you herein, shall not infringe any third party intellectual property or proprietary rights, nor violate any rights of privacy or publicity. We do not control User Content, and we are not responsible for its content, accuracy or reliability. We are under no obligation to edit or control User Content, although we reserve the right to review, and take certain actions with respect to, User Content in accordance with this Agreement, including the Privacy Policy (as defined below). In the event that we deem, in our sole discretion, any User Content to be inconsistent with the terms of this Agreement, the Privacy Policy, or any other rules or policies we may publish from time to time, we may remove such User Content from the Service, including incomplete posts, duplicate posts, or any other User Content we deem, in our sole discretion, to be misleading or otherwise inappropriate. On termination of your account, or this Agreement, we have no obligation to return any User Content to you, so you should retain copies of all of Your Content. In addition to and without limiting any other rights herein (including in the Privacy Policy), you also grant us the rights to (i) de-identify Your Content (i.e., to remove your name and other identifying characteristics, consistent with applicable laws and regulations), (ii) use or disclose de-identified data for any purpose, and (iii) share de- identified data with third parties.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.

  • User Data We will maintain certain data that you transmit to the Services for the purpose of managing the performance of the Services, as well as data relating to your use of the Services. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Services. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.

  • Use of Book-Entry System The Fund shall deliver to PFPC Trust certified resolutions of the Board approving, authorizing and instructing PFPC Trust on a continuous basis, to deposit in the Book-Entry System all securities belonging to the Portfolios eligible for deposit therein and to utilize the Book-Entry System to the extent possible in connection with settlements of purchases and sales of securities by the Portfolios, and deliveries and returns of securities loaned, subject to repurchase agreements or used as collateral in connection with borrowings. PFPC Trust shall continue to perform such duties until it receives Written Instructions or Oral Instructions authorizing contrary actions. PFPC Trust shall administer the Book-Entry System as follows: (i) With respect to securities of each Portfolio which are maintained in the Book-Entry System, the records of PFPC Trust shall identify by book-entry or otherwise those securities belonging to each Portfolio. PFPC Trust shall furnish to the Fund a detailed statement of the Property held for each Portfolio under this Agreement at least monthly and from time to time and upon written request. (ii) Securities and any cash of each Portfolio deposited in the Book-Entry System will at all times be segregated from any assets and cash controlled by PFPC Trust in other than a fiduciary or custodian capacity but may be commingled with other assets held in such capacities. PFPC Trust and its sub-custodian, if any, will pay out money only upon receipt of securities and will deliver securities only upon the receipt of money. (iii) All books and records maintained by PFPC Trust which relate to the Fund's participation in the Book-Entry System will be open to the inspection of Authorized Persons at all times during PFPC Trust's regular business hours, and PFPC Trust will furnish to the Fund all information in respect of the services rendered as it may require. PFPC Trust will also provide the Fund with such reports on its own system of internal control as the Fund may reasonably request from time to time.

  • Book-Entry System Provided (i) the Bank has received a certified copy of a resolution of the Board specifically approving deposits of Fund assets in the Book-Entry System, and (ii) for any subsequent changes to such arrangements following such approval, the Board has reviewed and approved the arrangement and has not delivered an Officer's Certificate to the Bank indicating that the Board has withdrawn its approval: (a) The Bank may keep Portfolio Securities in the Book-Entry System provided that such Portfolio Securities are represented in an account ("Account") of the Bank (or its agent) in such System which shall not include any assets of the Bank (or such agent) other than assets held as a fiduciary, custodian, or otherwise for customers; (b) The records of the Bank (and any such agent) with respect to the Fund's participation in the Book-Entry System through the Bank (or any such agent) will identify by book entry the Portfolio Securities which are included with other securities deposited in the Account and shall at all times during the regular business hours of the Bank (or such agent) be open for inspection by duly authorized officers, employees or agents of the Fund. Where securities are transferred to the Fund's account, the Bank shall also, by book entry or otherwise, identify as belonging to the Fund a quantity of securities in a fungible bulk of securities (i) registered in the name of the Bank or its nominee, or (ii) shown on the Bank's account on the books of the Federal Reserve Bank; (c) The Bank (or its agent) shall pay for securities purchased for the account of the Fund or shall pay cash collateral against the return of Portfolio Securities loaned by the Fund upon (i) receipt of advice from the Book-Entry System that such Securities have been transferred to the Account, and (ii) the making of an entry on the records of the Bank (or its agent) to reflect such payment and transfer for the account of the Fund. The Bank (or its agent) shall transfer securities sold or loaned for the account of the Fund upon (i) receipt of advice from the Book-Entry System that payment for securities sold or payment of the initial cash collateral against the delivery of securities loaned by the Fund has been transferred to the Account; and (ii) the making of an entry on the records of the Bank (or its agent) to reflect such transfer and payment for the account of the Fund. Copies of all advices from the Book-Entry System of transfers of securities for the account of the Fund shall identify the Fund, be maintained for the Fund by the Bank and shall be provided to the Fund at its request. The Bank shall send the Fund a confirmation, as defined by Rule 17f-4 of the 1940 Act, of any transfers to or from the account of the Fund; (d) The Bank will promptly provide the Fund with any report obtained by the Bank or its agent on the Book-Entry System's accounting system, internal accounting control and procedures for safeguarding securities deposited in the Book-Entry System;

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