Neighborhood Compatibility Sample Clauses

POPULAR SAMPLE Copied 1 times
Neighborhood Compatibility. The Project should be designed such that the buildings, site improvements, and landscaping build pride, reflect neighborhood character, and show commitment to the cultural and architectural heritage of the neighborhood. Designs and materials should be complementary to and compatible with the surrounding area building forms, incorporating high-quality, durable materials and colors. Designs and materials should include the use of brick along with simple, rectangular forms that have a vertical emphasis.
Neighborhood Compatibility. The design for site and building details, materials and colors are compatible with and complementary to the Project’s neighborhood; The design evidences methods to mitigate immediate neighbor impacts, including, but not limited to, the following topics: outdoor storage, garbage, noise, nighttime operations, deliveries, graffiti, outdoor maintenance, outdoor lighting, and odors; the design is consistent with implementation of the basic traffic management plan required by Section 5.4 below;
Neighborhood Compatibility i. Loading and unloading activities may not encroach on or interfere with the use of sidewalks, drive aisles, or parking areas, or public thoroughfares. ii. Maneuvering aisles and driveways may serve both required parking and loading bays if they meet the design needs of each activity. Loading facilities requiring vehicles to back in from a public thoroughfare are permitted. iii. Loading and unloading activities for lots Abutting the NR or UR districts are limited to the hours of the day between 7:00 a.m. and 10:00 p.m. All loading docks on these lots must be signed to indicate, “no idling”.
Neighborhood Compatibility. [The intent of this section is to encourage the applicant to design the proposal in consideration of the physical impact it will have on the immediate neighborhood (within five (500) feet if the property is in the Urban Growth Area Districts and within thousand (1000) feet if the property is in the Planned Development and/or Rural Districts).] (a) Is the proposal compatible with and sensitive to the character of the site and neighborhood relative to: [1] Land uses; [2] Architectural design; [3] Scale, bulk and building height; [4] Identity and historical character; [5] Disposition and orientation of buildings on the lot; and [6] Visual integrity? (b) Are the elements of the site plan (e.g., buildings, circulation, open space and landscaping) designed and arranged to maximize the opportunity for privacy by the residents of the immediate area? (c) Will the proposal maintain safe and healthful conditions within the neighborhood? This criterion shall not be limited to the standards affecting safety and health as outlined in this land use ordinance. Additional regulations may be found in the City of Augusta Code, as amended. (d) Will the proposal have a significant detrimental effect on the value of adjacent properties (which could be avoided by reasonable modifications of the plan)? In determining whether this criterion has been met, the Planning Board may require the applicant to submit an appraisal prepared by a State of Maine certified appraiser. (e) Will the proposal cause exterior queuing of vehicles or loitering of pedestrians which would have a negative impact on the surrounding neighborhood?

Related to Neighborhood Compatibility

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Drainage Systems (1) Clear culvert inlets, outlets, and sediment catching basins. (2) Maintain waterbars, drainage dips, and other water diversion measures. (3) During active use, patrol and maintain functional drainage. (4) Repair damaged culvert ends.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Troubleshooting USER AGENCY agrees that its employees will contact the USER AGENCY Information Technology (IT) Department or representatives before contacting SYSTEM PROVIDER regarding issues related to this Agreement. USER AGENCY agrees that if its IT Department determines there is a problem related to connectivity with SYSTEM PROVIDER, the USER AGENCY will contact SYSTEM PROVIDER's IT Help Desk at (▇▇▇) ▇▇▇-▇▇▇▇ and will send an email to ▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇.▇▇▇. After business hours, USER AGENCY may contact the SYSTEM PROVIDER Police Command and Control Center at (▇▇▇) ▇▇▇-▇▇▇▇ for assistance. SYSTEM PROVIDER agrees to make reasonable efforts to identify and remediate any problem as quickly as possible; however, SYSTEM PROVIDER does not guarantee any specific uptime, nor is SYSTEM PROVIDER liable for any damages associated with performance under this Agreement, including but in no way limited to any downtime.