Required Street Widths Sample Clauses

Required Street Widths. Where curb and gutter is provided, required pavement widths are measured from face of curb to face of curb. Where curb and gutter are not provided, pavement widths are measured from edge of pavement to edge of pavement. Street Type # Lanes Street Width Lane Width On-Street Parking ROW Width Curb/Gutter Arterial 5 55 11 n/a 90 Optional Collector 3 33 11 n/a 70 Optional Collector 2 22 11 Per Atoka 60 Optional Mixed-Use Local 2 20 10’-11’ 7’8’ 60 Required Neighborhood Local 2 28 n/a Included 50 Required Commercial Alley 2 20 n/a n/a 24 No curb Residential Alley 2 16 n/a n/a 22 No curb When curb and gutter are not provided, a three-foot gravel shoulder shall be required on each side of the pavement. Curb and Gutter shall be required for any lot widths less than 100 feet. The minimum street and right-of-way widths for all roads shall be as follows:
AutoNDA by SimpleDocs

Related to Required Street Widths

  • Trustee Not Required to Make Investigation Prior to the occurrence of an Event of Default hereunder and after the curing of all Events of Default which may have occurred, the Trustee shall not be bound to make any investigation into the facts or matters stated in any resolution, certificate, statement, instrument, opinion, report, notice, request, consent, order, appraisal, bond, Mortgage, Mortgage Note or other paper or document (provided the same appears regular on its face), unless requested in writing to do so by holders of Certificates evidencing in the aggregate not less than 51% of the Voting Interest represented by all Certificates; provided, however, that if the payment within a reasonable time to the Trustee of the costs, expenses or liabilities likely to be incurred by it in the making of such investigation is, in the opinion of the Trustee, not reasonably assured to the Trustee by the security afforded to it by the terms of this Agreement, the Trustee may require reasonable indemnity against such expense or liability as a condition to so proceeding. The reasonable expense of every such investigation shall be paid by the Master Servicer or, if paid by the Trustee shall be repaid by the Master Servicer upon demand.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • Joint Funded Project with the Ohio Department of Transportation In the event that the Recipient does not have contracting authority over project engineering, construction, or right-of-way, the Recipient and the OPWC hereby assign certain responsibilities to the Ohio Department of Transportation, an authorized representative of the State of Ohio. Notwithstanding Sections 4, 6(a), 6(b), 6(c), and 7 of the Project Agreement, Recipient hereby acknowledges that upon notification by the Ohio Department of Transportation, all payments for eligible project costs will be disbursed by the Grantor directly to the Ohio Department of Transportation. A Memorandum of Funds issued by the Ohio Department of Transportation shall be used to certify the estimated project costs. Upon receipt of a Memorandum of Funds from the Ohio Department of Transportation, the OPWC shall transfer funds directly to the Ohio Department of Transportation via an Intra- State Transfer Voucher. The amount or amounts transferred shall be determined by applying the Participation Percentages defined in Appendix D to those eligible project costs within the Memorandum of Funds. In the event that the Project Scope is for right-of-way only, notwithstanding Appendix D, the OPWC shall pay for 100% of the right-of-way costs not to exceed the total financial assistance provided in Appendix C.

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements

  • Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria

  • Accounts Not Required to Be Reviewed, Identified, or Reported Unless the Reporting Finnish Financial Institution elects otherwise, either with respect to all Preexisting Individual Accounts or, separately, with respect to any clearly identified group of such accounts, where the implementing rules in Finland provide for such an election, the following Preexisting Individual Accounts are not required to be reviewed, identified, or reported as U.S.

  • Entity Accounts Not Required to Be Reviewed, Identified or Reported Unless the Reporting Singaporean Financial Institution elects otherwise, either with respect to all New Entity Accounts or, separately, with respect to any clearly identified group of such accounts, where the implementing rules in Singapore provide for such election, a credit card account or a revolving credit facility treated as a New Entity Account is not required to be reviewed, identified, or reported, provided that the Reporting Singaporean Financial Institution maintaining such account implements policies and procedures to prevent an account balance owed to the Account Holder that exceeds $50,000.

  • FACILITIES AVAILABLE WITH THE CARD 4.1 Use during validity period 4.2 Operating card account via TBS 4.3 Card transaction by mail / telephone / facsimile / electronic mail / internet 4.4 Cash advance within given limit 4.5 Cash advance subject to fees and charges

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