Bike Path Sample Clauses

Bike Path. The Parties agree that the bike path through this parcel may be relocated to a mutually agreed upon location, to accommodate site design.
AutoNDA by SimpleDocs
Bike Path. Xxxxxxx agrees to pay for 4/10 of the bike bath in Xxxxx 00xx Xxxxxx.
Bike Path. The Developer shall construct an eight (8) foot wide bike path along Xxxx Road in accordance with Plans and Specifications and the Conditions of Approval.
Bike Path. Owner of each lot shall install the 10’ wide bike path (2” bituminous surface course over 6” aggregate base course) as set forth on the Plat, consistent with the plans and specifications of the City at such time as a building permit is issued for a building permit on each Lot of the Plat, or within three (3) years of execution of this Agreement, whichever occurs first.
Bike Path. The Bike Path shall remain unobstructed and open to the public as a means of recreation and transportation for bicyclists and pedestrians at all times. If closure is required during the fair, adequate detours shall be marked and signed so as to accommodate access via sidewalks around the Fair and the Property typically serviced by the Bike Path and existing sidewalks.
Bike Path. To the extent that the City retains possessory rights in portions of parcel 12-223-31-177- 014 and parcel 12-223-31-177-001 along the waters of Lake Michigan, the City will grant an easement to the County for the establishment of a bicycle path for the public use of the community. For the avoidance of doubt, the rights granted herein are subordinate to any interest in this land granted prior to entry into this Agreement. Moreover, the City does not warrant that the County’s purposes to establish a continuous bicycle path can be accomplished through entry into this easement. The portions of parcel 12-223-31-177-014 subject to this easement are more particularly described in Exhibit 4 attached hereto. The easement is subject to the following: (1) the County will work jointly with “Route of the Badger” consultants/staff to design and construct a safe bicycle path within the easement; prior to construction of the safe bicycle path, the design, which must include plans and specifications, must first have the approval of the City Engineer. The design submitted for approval must: (1) be compliant with the Wisconsin Department of Transportation Bicycle Facilities Design Handbook; (2) be compliant with all federal and state laws; and (3) bear the stamp of a licensed, professional engineer. The County will take no action to cause or allow any environmental damage. The County or its agents has the right to enter and use of the City's land with full right of ingress and egress over and across the easement area and adjacent lands of City for construction of the path. The City retains all other rights and responsibilities. In consideration of the foregoing grant, it is understood that during the time that the County maintains the easement pursuant to this grant, the County will indemnify, save, and hold harmless the City, its successors and assigns, from any and all claims, liabilities, losses, costs, damages or expenses for injury or death of any person and any damages to property arising out of the County’s exercise of any of its rights under this easement; excepting, however, (1) any claims, liabilities, losses, costs, damages or expenses arising out of negligence or willful acts on the part of the City, its successors and assigns, employees, agents and invitees; (2) any special, consequential or indirect damages, including but not limited to, loss of profit or revenue, and diminution in value; and (3) any environmental claims, liabilities, losses, costs, damages or ...

Related to Bike Path

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • License; Use Upon delivery to an Authorized Person or a person reasonably believed by Custodian to be an Authorized Person of the Fund of software enabling the Fund to obtain access to the System (the “Software”), Custodian grants to the Fund a personal, nontransferable and nonexclusive license to use the Software solely for the purpose of transmitting Written Instructions, receiving reports, making inquiries or otherwise communicating with Custodian in connection with the Account(s). The Fund shall use the Software solely for its own internal and proper business purposes and not in the operation of a service bureau. Except as set forth herein, no license or right of any kind is granted to the Fund with respect to the Software. The Fund acknowledges that Custodian and its suppliers retain and have title and exclusive proprietary rights to the Software, including any trade secrets or other ideas, concepts, know-how, methodologies, or information incorporated therein and the exclusive rights to any copyrights, trademarks and patents (including registrations and applications for registration of either), or other statutory or legal protections available in respect thereof. The Fund further acknowledges that all or a part of the Software may be copyrighted or trademarked (or a registration or claim made therefor) by Custodian or its suppliers. The Fund shall not take any action with respect tot the Software inconsistent with the foregoing acknowledgement, nor shall the Fund attempt to decompile, reverse engineer or modify the Software. The Fund may not xxx, sell, lease or provide, directly or indirectly, any of the Software of any portion thereof to any other person or entity without Custodian’s prior written consent. The Fund may not remove any statutory copyright notice or other notice included in the Software or on any media containing the Software. The Fund shall reproduce any such notice on any reproduction of the Software and shall add any statutory copyright notice or other notice to the Software or media upon Custodian’s request.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI 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 ECI 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 ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI 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 ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

  • Synchronization Rights The Licensor hereby grants limited synchronization rights for One (1) music video streamed online (Youtube, Vimeo, etc..) for up to 500000 non-monetized video streams on all total sites. A separate synchronization license will need to be purchased for distribution of video to Television, Film or Video game.

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • 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. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements.

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