Development Guidelines Sample Clauses

Development Guidelines. 12.1 It is recorded that STADSIG ESTATE falls within the jurisdiction of the Drakenstein Local Authority. The Drakenstein Local Authority approved the rezoning and also the subdivision thereof into the Portion Xxxxx and Private Areas on the condition that all dwellings to be constructed on Portion Xxxxx must comply with prescribed development guidelines as contained in the Architectural Guidelines and Design Xxxxxx.
AutoNDA by SimpleDocs
Development Guidelines. Controls As per Municipal and any other Statuary Authorities.
Development Guidelines. In connection with any development, and upon the reasonable request from AXP, GT will provide a report to AXP's Project Coordinator with respect to 1) functional, platform, system and database changes performed, 2) any foreseeable delay in development and estimates of time required for completion and action taken to resolve such delay and 3) indication of progress against prior plans with respect to such development.
Development Guidelines. A. The Declarant shall adopt such Development Guidelines as it deems necessary to inform owners and interested parties of the standards which will be applied in approving or disapproving proposed construction.
Development Guidelines. Lessee has received from Lessor a copy of the Development Guidelines of the Development Park. Lessee agrees to adhere to the Development Guidelines now in force and effect or that may be hereafter in force and effect. Any requested waiver from the Development Guidelines must be approved in writing by Lessor.‌
Development Guidelines. Healthcare Company agrees that in connection with each Project it will:
Development Guidelines. In order to insure that both Parties have every incentive to invest in the success of the joint effort contemplated by this Agreement, the Parties agree as follows:
AutoNDA by SimpleDocs
Development Guidelines. 12.1 It is recorded that the DóDEKA development falls within the jurisdiction of the BERGRIVIER MUNICIPALITY. The DEPARTMENT OF ENVIRONMENT AFFAIRS AND DEVELOPMENT, WESTERN CAPE approved the rezoning and the subdivision thereof on appeal into the Portion Xxxxx and Private Areas. There are no formal Architectural Guidelines and Design Manual for the project but all buildings plans must be submitted and approved by P2 GROUP ARCHITECTS, Vredenburg, before submitted for building plan approval at the local municipality.
Development Guidelines. Although the different tool developers have their own development conventions, it is an added value for ACDC to provide a set of guidelines to achieve a minimum quality standard. We outline next a list of best practices and code conventions widely adopted.  Java programming: This Code Conventions for the Java Programming Language document1 contains the standard conventions that we at Sun follow and recommend that others follow. It covers filenames, file organization, indentation, comments, declarations, statements, white space, naming conventions, programming practices and includes a code example.  SOAP Web services: Focusing on improving interoperability among the different existing web services standards and specifications (e.g. SOAP, WSDL, WS-CDL, WS-BPEL, WS-AtomicTransactions, WS-RM, etc), even more mature specifications such as SOAP and WSDL have different variations (e.g. disagreements in the use of document/encoded). There are many recommendations and guidelines for the design interoperable web services issued by well-known organizations and initiatives, such as the Basic Profile from the Web Services Interoperability (WS-I) group2. The WS-I Basic Profile (BP) contains a small subset of WS features, which are expected to be interoperable among any (compliant) platform and WS middleware. On the other hand, there exist many frameworks for web service development, for instance Apache CXF or Apache Axis2, claiming to be WS-I compliant, making it easier towards achieving this level of interoperability. 1 xxxx://xxx.xxxxxx.xxx/technetwork/java/codeconv-138413.html 2 xxxx://xx-x.xxx/Profiles/BasicProfile-2.0-2010-11-09.html Recommendations for the development of SOAP Web Service APIs can be found in [23] .
Development Guidelines. The neighborhoods in RN3 designated areas will incorporate flexible lot sizes to accommodate diverse housing types with regard for architectural character, environmental and open space factors in design decisions. Generally, higher density residential will be encouraged along avenues, boulevards and mixed-use avenues and other streets with significant bicycle and potential transit routes and within master planned projects. Street, sidewalks, and trails will have full connectivity. New developments will require neighborhood and community parks nearby in relation to the City’s open space and park planning. Typically, developments should be within ½ mile of a park. Open Space and Parks A City neighborhood park currently exists approximately ¼ mile to the south of this property in the Sunset Ridge neighborhood. This meets the Land Use goal of the proposed neighborhood being within a ½ mile of a city park. Additionally, the Ames 2040 Comprehensive Plan does have a general conceptual plan for acquisition of park space for a larger community park immediately north of this property. With the existing park and planned park to the north, no additional public park land is planned with this development. The Future Land Use Map Open Space/Greenway designation at the east edge of the site continues to be shown on the amended Master Plan as open space. The Future Land Use Map also shows a green swath of open space adjacent to Xxxxxx Avenue. This was intended to convey the conceptual location of a future public park. The actual location of the park will be north of this development. The extension of Xxxxxx Avenue will continue extension of the shared use path. The shared use path will eventually provide connection to the future park. Complete Streets Typology The proposed street extensions into this area are classified in the Ames 2040 Plan Complete Streets typology as Neighborhood Streets which are designed to be low traffic with separated walkways and some on-street parking. The technical functional classification is ‘local street’. These types of streets are intended in new expansion areas with low density zoning such as this development. One of the connecting streets, Xxxxxx Avenue, is designated as a ‘residential collector street’. This street type is intended as a connector to local streets in low density residential areas. The street typology is not affected by the requested master plan amendment. Public Actions Plan 2040 includes actions to guide City plans for in...
Time is Money Join Law Insider Premium to draft better contracts faster.