We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Vehicular Circulation Sample Clauses

Vehicular Circulation. Vehicular circulation among the various parcels depicted on Exhibit A and to and from the adjoining public and privates streets and busways; 41346839.441346839.5 5 41354031.1 (b) Pedestrian Circulation. Pedestrian circulation among the various parcels depicted on Exhibit A and to and from the adjoining public and privates sidewalks and walkways, particularly between and through the Commuter Parking Structures, transit station and the planned mixed-use development;
Vehicular Circulation a. Although Urban Systems, Inc. concludes that the associated circulation of vehicles for the Project during normal use as a park (which does not include Special Events) will not adversely impact the adjacent neighborhoods (Exhibit I), at the written request of the Association, the NOBC will support a Residential Parking Program if the residents in the affected area so desire, in accordance with the provisions set forth in City Code of Ordinances Chapter 154, Article VIII, Division 10 Residential Permit Parking ProgramH). b. Moreover, the NOBC agrees to also implement reasonable plans for the orderly egress of vehicles associated with periodic Special Events, causing peak traffic to flow onto larger streets such as Xxxxx Xxxxxx Xxxxxx and Elysian Fields Avenue. c. For Special Events, sufficient personnel will be provided to direct traffic to and from the on-site parking provided for the Special Event.
Vehicular Circulation. Although Urban Systems, Inc. concludes that the associated circulation of vehicles 23 will not adversely impact the adjacent neighborhoods (Exhibit IH), at the written 24 request of the Association, the NOBC will support a Residential Parking Program if 25 the residents in the affected area so desire, in accordance with the provisions set forth 26 in City Code of Ordinances Chapter 154, Article VIII, Division 10 Residential Permit 27 Parking Program.
Vehicular Circulation a. Although Urban Systems, Inc. concludes that the associated circulation of vehicles will not adversely impact the adjacent neighborhoods (Exhibit H), at the written request of the Association, the NOBC will support a Residential Parking Program if the residents in the affected area so desire, in accordance with the provisions set forth in City Code of Ordinances Chapter 154, Article VIII, Division 10 Residential Permit Parking Program. Comments: It is hard conceptualize how the influx of 3000+ people into the neighborhood for a special event will not has an adverse affect on circulation. The normal traffic on weekends without a city wide event such as Mardi Gras already causes vehicular circulation issues. Adding an event that can hold 3000+ people will only add to this issue if not planned properly. b. Moreover, the NOBC agrees to also implement reasonable plans for the orderly egress of vehicles associated with periodic special events, causing peak traffic to flow onto larger streets such as Xxxxx Xxxxxx Xxxxxx and Elysian Fields Avenue.
Vehicular Circulation. Driveways - Entry drives, service drives, parking entrances and other access points shall be aligned wherever practical directly opposite existing driveways. For that portion of Gate Parkway north of X. X. Xxxxxx no additional median cuts will be allowed without the approval of the Seller. Two way drives shall have a minimum width of twenty-four feet (24’). One way driveways shall have a minimum width of sixteen feet (16’). All driveways with more than one lane in each direction shall have a landscaped median and shall not have more than twenty four feet (24’) of pavement in each direction. The landscaped median shall be a minimum of ten feet (10’) in width from back of curb to back of curb. Curbing - All Interior parking areas including drives and landscaped islands shall be curbed.

Related to Vehicular Circulation

  • Traffic The provisions in this Section apply regardless how the ISP-bound traffic is determined.

  • Dissemination 1. All public events, activities, curricular materials, press releases, requests for proposals, bid solicitations, and other documents produced with OSHE funds provided pursuant to this agreement must state clearly that the project partnership is administered by OSHE and that OSHE is a partner in the project partnership. The only official name to be used in describing the overall program is “Educational Opportunity Fund (EOF)” and no other institutional- specific branded name shall be used in official communication about the grants.

  • Grievability Denial of a petition for reinstatement is grievable. The grievance may not be based on information other than that shared with the Employer at the time of the petition for reinstatement.

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Visibility 1. Unless the Council of Europe requests or agrees otherwise, the Grantee shall take all necessary measures to publicise the fact that the Action has been funded within the framework of a Joint Project between the European Union and the Council of Europe. Information given to the press and to the beneficiaries of the Action, all related publicity material, official notices, reports and publications, shall acknowledge that the Action was carried out with a grant from a Joint Project between the European Union and the Council of Europe and shall display in an appropriate way the Joint Projects’ visual identity (for instructions on use of the Joint Projects’ visual identity, see Appendix IV). 2. In cases where equipment or major items have been purchased using funds provided by the European Union or the Council of Europe, the Grantee shall indicate this clearly on that equipment and those major items (including display of the European Union and Council of Europe’s logos), provided that such actions do not jeopardise the safety and security of the Grantee’s staff. 3. The acknowledgement and Joint Projects’ visual identity shall be clearly visible in a manner that will not create any confusion regarding the identification of the Acton as a project of the Grantee and the ownership of the equipment and items by the Grantee. 4. All publications by the Grantee pertaining to the Action that have received funding from a Joint Project between the European Union and the Council of Europe, in whatever form and whatever medium, including the Internet, shall carry the following or a similar disclaimer: “This document has been produced using funds of a Joint Project between the European Union and the Council of Europe. The views expressed herein can in no way be taken to reflect the official opinion of the European Union or the Council of Europe”. 5. If the equipment purchased with a grant from a Joint Project is not transferred to the local partners of the Grantee or to the final recipient of the Action at the end of the implementation period of this Agreement, the visibility requirements as regards this equipment shall continue to apply between the end of the implementation period of this Agreement and the end of the Joint Project, if the latter lasts longer. 6. All layouts of any communication items prepared by the Grantee are subject to approval with the Contact point within the Council of Europe. 7. The Grantee accepts that the European Union and the Council of Europe may publish in any form and medium, including on their websites, the name and address of the Grantee, the purpose and amount of the grant and, if relevant, the percentage of co-financing.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Statistical, Demographic or Market-Related Data All statistical, demographic or market-related data included in the Registration Statement, the Disclosure Package or the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate and all such data included in the Registration Statement, the Disclosure Package or the Prospectus accurately reflects the materials upon which it is based or from which it was derived.

  • Disturbance Analysis Data Exchange The Parties will cooperate with one another and the NYISO in the analysis of disturbances to either the Large Generating Facility or the New York State Transmission System by gathering and providing access to any information relating to any disturbance, including information from disturbance recording equipment, protective relay targets, breaker operations and sequence of events records, and any disturbance information required by Good Utility Practice.

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.

  • MATERIAL SAFETY DATA SHEETS As applicable, Contractor shall provide Purchaser with all appropriate Material Safety Data Sheets (“MSDS”) at the time of delivery of each shipment of Goods which requires such compliance and/or and for materials used by Contractor while performing Services and any updates of the same.