Loading...
HomeMy WebLinkAboutSDP201800006 Action Letter 2018-04-200 COUNTY OF ALBEMARLE Department of Community Development 401 McIntire Road, North Wing Charlottesville, Virginia 22902-4596 Phone (434) 296-5832 Fax (434) 972-4126 April 20, 2018 Justin Shimp Shimp Engineering 201 E. Main Street Charlottesville, VA 22902 SDP2018-6 Royal Fern Townhomes - Initial Site Plan Mr. Shimp, The Agent for the Board of Supervisors hereby grants administrative conditional approval to the above referenced site plan. This approval shall be valid for a period of five (5) years from the date of this letter, provided that the developer submits a final site plan for all or a portion of the site within one (1) year after the date of this letter as provided in section 32.4.3.1 of Chapter 18 of the Code of the County of Albemarle, and thereafter diligently pursues approval of the final site plan. In accordance with Chapter 18 Section 32.4.2.8 Early or Mass Grading may be permitted after the following approvals are received: 1. Engineering approval of a VSMP plan meeting the requirements of Chapter 17 of the Code of the County of Albemarle. 2. Approval of all easements for facilities for stormwater management and drainage control. The final site plan will not be considered to have been officially submitted until the following items are received: 1. A final site plan that satisfies all of the requirements of section 32.6 of Chapter 18 of the Code. 2. A fee of $1,613. Please submit 13 copies of the final plans to the Community Development Department. The assigned Lead Reviewer will then distribute the plans to all reviewing agencies. Once you receive the first set of comments on the final site plan, please work with each reviewer individually to satisfy their requirements. The Department of Community Development shall not accept submittal of the final site plan for signature until tentative approvals for the attached conditions from the following agencies/reviewers have been obtained: SRC Members: Albemarle County Planning Services (Planner) - 2 copies [Paty Saternye ext. 3250] Albemarle County Planning Services (Zoning) — 1 copy [Francis MacCall ext. 3418] Albemarle County Engineering Services (Engineer) - 1 copy [Matt Wentland ext. 3458] Albemarle County Architectural Review Board (ARB) — 1 copy [Heather McMahon ext. 3278] Albemarle County Planning Services (Planner) - 1 copies [Kevin McDermott ext. 3414] Albemarle County Information Services (E911) - 1 copy [Elise Kiewra ext. 30301 Albemarle County Department of Fire Rescue - 1 copy [Shawn Maddox 434-326-2623] Virginia Department of Transportation - 1 copy [Adam Moore 434-422-9894] Albemarle County Building inspections — 1 copy [Michael Dellinger ext. 3228] Albemarle County Service Authority (ACSA) - 3 copy [Alex Morrison 434-977-4511 ext 116] If you have any questions about these conditions or the submittal requirements please feel free to contact me at Extension 3250, psaternye@albemarle.org. Sincerely, G Seni r Planne Phone 434-296-5832 County of Albemarle Department of Community Development 401 McIntire Road, Charlottesville, VA, 22902 Memorandum To: Justin Shimp Qustin(c shimp-engineering.com) From: Paty Saternye, Senior Planner Division: Planning Date: April 4, 2018 UPDATE: April 20, 2018 Subject: SDP 201800006 Royal Fern Townhomes — Initial Site Plan Fax 434-972-4126 The County of Albemarle Planning Division will recommend approval of the plan referenced above once the following comments have been satisfactorily addressed (The following comments are those that have been identified at this time. Additional comments or conditions may be added or eliminated based on further review.): [Each comment is preceded by the applicable reference, which is to the Subdivision/Zoning Ordinances unless otherwise specified.] Comments to be addressed prior to the Initial Site Plan approval: 1. Pay the required notices fee of $215. UPDATE: Comment addressed. Fee paid. Comments to be addressed with the Final Site Plan submission: 2. A site plan meeting all the requirements of section 32.6 of Chapter 18 of the Code. [14-401, 14-419, 14-203.1 & 32.7.9.7] Double frontage lots for single family detached and attached residential uses are prohibited. Revise the plan to no longer have double frontage lots along 5t" street or request a special exception. The final site plan will not be able to be approved until either there are no longer double frontage lots or a special exception has been granted to allow the double frontage lots. Two possible layout changes to avoid the double frontage lots are to: • Change the section of the private road directly behind the double frontage lots to an "alley". • Provide a minimum of 20' of common area/open space between 5tn street and the lots. This common area/open space must be screened as provided in sections 14-419 and 32.7.9.7. 4. [32.7.2.3(a)] Provide in the site plan a sidewalk parallel to 5t' street for the full length of the parcel. Work with VDOT, engineering and planning to determine the section that will be required for the intersection with the road. The existing asphalt trail is not of sufficient width and is not properly maintained. Page 1 of 7 [32.5.1(c) & 32.5.2(a)] Address the following: • Provide the ZMA number in the zoning area of the data on the coversheet. • Show the adjoining portion of that parcel with the stormwater pond that will serve this development in the project area. • Include information (TMP, Owner, Developer, Zoning, etc.) for the adjoining parcel in the data on the coversheet since part of that parcel is being utilized to meet stormwater requirements. • Show the adjoining portion of that parcel with the stormwater pond that will serve this development in the project area. • Provide the bearing and distances for the existing boundaries. • Ensure that the scale for the Existing Conditions and Demolition Plan is correct and that all measurements can be scaled. 50 scale does not appear to be correct. The distances provided for the private road easement do not appear to be at 50 scale. • Revise the setback lines in the site plan to be correct. Address the following: o Provide garage minimum setback on the coversheet. o Show the Front Minimum garage setback for the units which front the internal "private street". The units along the private street do not currently appear to meet the Front Minimum Garage Setback. IMPORTANT: Note that the front setback is measured either from the edge of the private street easement (not the property line in the middle of the private street) or any sidewalk if it is outside of the private road easement. o Revise the location of the units which front on the internal "private street" so that their garages meet the minimum Front Setback for garages. o [NEW COMMENTI UPDATE: April 20, 2018: Front setbacks should be shown for the sides of the two buildings that adjoin the proposed private street(s). o [NEW COMMENTI UPDATE: April 20, 2018: Ensure that the front setback, on the two building along Wahoo Way that have their sides facing the proposed private street, is measured from whichever is the closer of the ROW of the private street and the back of the sidewalk along the private street. o Provide the Non-Infill Minimum Building Separation requirements on the coversheet. Since the adjoining lot is R-2 the separation requirement for buildings that exceed 35' in height applies. o Show the Front Minimum and Front Maximum setbacks along 5th street. Ensure that the buildings meet these requirements. (NOTE: The units along 5t" street are currently shown as double frontage lots, which are not allowed. See above in the comments on how to address the double frontage issue.) o Revise the setbacks for the building with three units located along Wahoo Way, and adjacent to the R-2 lot, so that the property line adjoining the R-2 parcel is shown as a side setback and not a rear setback. (NOTE: the proposed property lines for the end unit of the three unit building do not appear to be complete. The property line down the middle of the alley dead ends at the gutter and does not connect to any other property line. The lot is not complete and it is uncertain if all of the property adjacent to that unit, on that end, is meant to be part of that lot or if some of it is meant to be open space.) o Show the rear setback lines for all of the units that have their garages along the alleys. o It appears that the units that have garages facing the rear of the lot, along the private alleys, are not meeting the 20' minimum rear setback requirement. Revise the lot layout so that the units meet the requirement. IMPORTANT: Note that the front setback is measured from the edge private alley easement and not the property line in the middle of the private alley. • Show present use for the abutting parcel in the parcel information on the existing conditions sheet. • Provide the required datum reference for the elevation. 6. [32.5.2(b) & 17.3] Revise the "Proposed Use" portion of the coversheet data to specify that the site plan is a "Cluster Development", or a "Cluster Development" with "Bonus Levels" or increase the lot sized in order to meet the minimum lot size of a the R-10 "Conventional Development". The lot sizes shown do not meet the minimum lot size for "Conventional Development". Page 2 of 7 7. [32.5.2(b) & 32.5.2(n)] The number of required guest spaces are shown to be met within the lot. However, "Visitor Parking Along Wahoo Way" is listed in the parking calculations. If this continues to be specified on the site plan address the following: • Depict the parking in the site plan. • Dimension the parking in the site plan. • Ensure that the proposed road section meets all road, parking & pedestrian access requirements. There does not appear to be enough width in either the existing or the proposed private street section to include parking even on one side. • Engineering, Fire & Rescue and planning will have to approve the designs and sections. • Include a calculation, or both unit and guest parking, in the "Parking" portion of the coversheet data. 8. [32.5.2(b) & 32.5.2(n)] Provide the required recreational facilities/tot lot and address the following: • Show and include the details of the recreational equipment. • Show and provide details for the required fencing. • Show pedestrian connections to the tot lot that includes handicapped ramps and warning strips. • Ensure that the interior or the fenced area meets the minimum of 200 square feet per residential unit (30 units x 200 square feet = 6,000 square feet required). 9. [32.5.2(e), 32.5.2(p) & 32.7.9] Provide a full landscape plan that provides all required landscaping, calculations and meets the buffer & landscaping requirements for 32.7.9, the entrance corridor guidelines and to avoid any double frontage lots. Ensure all calculations and graphics correctly represent the existing and proposed plantings and planting areas. 10. [32.5.2(e), 32.5.2(p) & 32.7.9.5] Provide street trees on both sides of all private or public streets at the required spacing for the entrance corridor. UPDATE: April 20, 2018: Provide street trees on both sides of all private and public streets at the required spacing for the entrance corridor or request, and be granted, a waiver (32.3.5(b)) for that requirement from 32.7 for the portions of the private streets that you do not propose to include street trees. See GREEN highlight in attached markup. Staff may be able to support a waiver for the portions of the markup not highlighted in GREEN if the additional street trees are provided along all of the GREEN highlighted areas. 11. [32.5.2(b), 32.5.2(e), 32.5.2(p) & 32.7.9] Provide the value of the maximum amount of paved parking and other vehicular circulation areas on the coversheet and on the Landscape Plan and utilize it in the landscaping calculation. 12. [32.5.2(i) & (n)] Address the following: • Dimension the width, and centerline radii, and corner radii of all roads and alleys and ensure that the roads meet or exceed minimum road requirements. • Revise the width of "Road A Private", or the alley converted from "Road A Private", to be 20' in width. • Provide all road and alley names on the site plan. • Show on the site plan all of the existing and proposed private street, alley and access easements. UPDATE: April 20, 2018: Show and dimension on the site plan all of the existing and proposed private street, alley and access easements. Address the following: o Ensure that the proposed private street easement width encompasses all required street improvements (curb & putter, planting strip, street trees, and sidewalk) and is at least 30' in width, which is the minimum for a private street easement. o Show the existing private street easement for Wahoo Way as well as the easement for its proposed extension. o Show the proposed private alley easements. o Show the access easements for sidewalks that are proposed on adioinina Droperties. • Show where the road easement ends and the alley easements begin Page 3 of 7 Accurately represent existing right-of-way lines and the existing path/sidewalk network. In the site plan the existing asphalt trail appears to be within the pavement of the road. UPDATE: April 20, 2018: Accurately represent existing right-of-way lines and the existing path/sidewalk network. In the site plan the existing asphalt trail appears to be within the pavement of the road along 5t" Street. Also, the connection between the existing trial/sidewalks and proposed sidewalk does not appear to be accurate. Ensure they are accurately shown and connect appropriately. Show the existing guardrail along 5th street. Show the location of any outdoor lighting. Any free standing or building mounted lighting, including front porch lights, must be shown in a photometric plan and meet all requirements. Show all proposed signage on the site plan. 13. [32.5.2(j)] Revise the plan to show the existing storm, sanitary sewer and drain pipes and easements. Show the existing storm pipes and ditches within the site. • It appears there is an existing waterline from across Wahoo Way that is shown to connect to the proposed waterline. • There appears to be stormwater from off site, coming under 5th street into the site that is not currently shown on the Existing Conditions sheet. 14. [32.5.2(k)] Revise the plan to show the proposed sanitary sewer, water and drainage facilities and easements. Include the direction of flow on all pipes channels and watercourses with arrows. Address the following: • Show the connection of the proposed waterlines to the existing waterline. • Show the connection of the proposed sanitary sewer lines to the existing sewer lines. Please note that the sewer lines in this submission and the one for the single family detached subdivision do to appear to show the same proposed lines connections. • Ensure all waterlines use the correct linetype. 15. [32.5.2(1)] Provide the location of any existing or proposed utilities and utility easements including telephone, cable, electric and gas. Indicate the deed book and page reference for all exiting utility easements located on the property. 16. [32.5.2(m)] Show the distance to the centerline of the nearest existing street intersection from the proposed ingress to and egress from the property. 17. [32.5.2(n)] Provide the following • Additional walkways and crosswalks UPDATE: April 20, 2018: Additional walkways and crosswalks (see attached markup showing possible pedestrian connection layout for development.) o Provide a sidewalk and planting strip along 5th street for the full length of the property. UPDATE: April 20, 2018: Provide a sidewalk, street trees and planting strip along 5t" street for the full length of the property. See GREEN highlight in attached markup. Work with VDOT, engineering and planning to design the appropriate street section. o Provide a pedestrian connection from the sidewalk at the first entrance from Wahoo Way to the internal walkways. UPDATE: April 20, 2018: Provide a pedestrian connection from the sidewalk at the first entrance from Wahoo Way to the internal walkways. See ORANGE highlight in attached markup. o Provide a sidewalk along all sides of the tot lot that are private streets, on the far side of the planting strip from the road, that include handicapped ramps and warning strips. UPDATE: April 20, 2018: Provide a sidewalk along all sides of the tot lot that area private streets, on the far side of the planting strip from the road, that include handicapped ramps and warning strips. Moving the quest parking, in the center open space, to the private alley that is parallel to Wahoo Way would allow these requirements to be met along the private street. Page 4 of 7 o It is suggested that there be a sidewalk along at least two sides of the tot lot in order to connect, by way of crosswalks, the tot lot to the rest of the site. UPDATE: April 20, 2018: It is suggested that there be a sidewalk alonq at least two sides of the tot lot in order to connect, by way of crosswalks, the tot lot to the rest of the site. See the ORANGE Highlights and BLUE crosswalks showing these additional pedestrian linkages. o Provide three additional crosswalks connecting the tot lot and the internal walkways to each other and the external pedestrian network. UPDATE: April 20, 2018: Provide four additional crosswalks connecting the tot lot and the internal walkways to each other and the external pedestrian network. See the RED and BLUE crosswalks showing these pedestrian linkages. o Pedestrian access to the tot lot's fenced in area including a handicapped ramp and warning strip. o A sidewalk warning strip at the beginning of the sidewalk coming off the private alley near the four guest parking spaces on the west side of the property. o Ensure that the sidewalk coming off the private alley near the four guest parking spaces on the west side of the property extends far enough to connect to the crosswalk to the tot lot. o Provide a crosswalks across both entrance onto Wahoo Way from the development. UPDATE: April 20, 2018: Provide a crosswalks across both entrance onto Wahoo Way from the development. See RED Crosswalk in attached markup. o Provide a crosswalk across Wahoo Way and connecting the proposed pedestrian network to the existing sidewalk on the far side of the Wahoo Way. UPDATE: April 20, 2018: Provide two crosswalks across Wahoo Way and connecting the proposed pedestrian network to the existing and proposed sidewalks on the far side of the Wahoo Way. See RED Crosswalk in attached markup. o NEW COMMENT -UPDATE: April 20, 2018: Provide planting strips along all sides of the private streets or request, and be granted, a waiver (32.3.5(b)) for that requirement from 32.7 for the portions of the private streets that you do not propose to include planting strips. See GREEN highlight in attached markup. Staff may be able to support a waiver for the portions of the markup not highlighted in GREEN if all planting strips are provided within the site that are GREEN highlighted. o NEW COMMENT -UPDATE: April 20, 2018: Provide sidewalks along all sides of the private streets or request, and be granted, a waiver (32.3.5(b)) for that requirement from 32.7 for the portions of the private streets that you do not propose to include sidewalks. See GREEN highlight in attached markup. Staff may be able to support a waiver for the portions of the markup not highlighted in GREEN if all additional pedestrian connections are provided within the site in order to provide a full pedestrian network. o NEW COMMENT -UPDATE: April 20, 2018: Provide curb and putter along all sides of the private streets or request, and be granted, a waiver (32.3.5(b)) for that requirement from 32.7 for the portions of the private streets that you do not propose to include curb and putter. See GREEN highlight in attached markup. Staff may be able to support a waiver for the portions of the markup not highlighted in GREEN if it is supported by engineering. Fencing Walls (if any) Open space areas (ensure parking areas are not park of open space calculations) 18. [32.5.2(p) & 32.7.9.4(b)] Preserve all existing trees that are to remain. There are existing street trees along Wahoo Way. If they are to remain include the following: • Areas and other features shown on landscape plan. The landscape plan shall show the trees to be preserved, the limits of clearing, the location and type of protective fencing, grade changes requiring tree wells or walls, and trenching or tunneling proposed beyond the limits of clearing. • Conservation checklist. The applicant shall sign a conservation checklist approved by the agent to ensure that the specified trees will be protected during construction. Except as otherwise expressly approved by the agent in a particular case, the checklist shall conform to the specifications in the Virginia Erosion and Sediment Control Handbook, pages III-393 through 111-413, and as hereafter amended. Page 5 of 7 19. [32.7.2.2, 14-411 & 14-412(B)l Ensure that each private street and travel way within the development is designed and constructed to the standards of Virginia Department of Transportation. 20. [Comment] Address the following: • Provide reference benchmarks for the survey. • Indicate the available sight distance for the new entrance onto Wahoo Way. • Indicate the deed book and page references for all existing utility easements located on the property. • Provide a copy of all off -site easements, or letters of intent to grant them from off -site property owners. 21. [Comment] Show any off site easements that will be required, including those for the construction of the sidewalk shown on the far side of Wahoo Way and stormwater management. UPDATE: April 20, 2018: Show any off site easements that will be required, including those for the construction of the road, sidewalk & landscaping shown within the proposed extension of Wahoo Way and any associated stormwater management area. 22. [Comment] Show the Dam Break Inundation Zone line on the site plan. The site plan was submitted to Virginia Department of Conservation and Recreation (DCR) for review of its impact on the Dam Break Inundation Zone (DBIZ). 23. [Comment] See the attached comments from the other SRC reviewers. 24. [NEW COMENTI UPDATE: April 20, 2018: Show any off site easements that will be required for sidewalk and storm water ponds on the adjoining property. Page 6 of 7 Comments to be addressed for the Special Exception request for a rear setback reduction for seven units adjacent to SWP: Planning staff is unable to support this special exception request. Address the following comments and then resubmit the request for review: 1. The request is for a reduction in the rear setback for the seven lots (lots 21-27). The three unit building along Wahoo Way (lots 28-30) also seems to show the building that does not meeting the rear setback requirement although it is not specified in the special exception request. However, it appears that instead this is a side yard that is shown as a rear yard in error. Revise the setbacks for this one building (lots 28-30) appropriately. 2. Revise the property lines for the end unit of the building mentioned above. The property lines for the end unit, closest to the R-2 adjoining parcel do not appear to be complete. There is a property line down the middle of the alley that dead ends at the gutter and does not connect to any other property line. 3. For clarity of the exhibit it is suggested that the following setback errors are also addressed prior to resubmission of the special exception request: • Show the rear setback lines for all of the units that have their garages along the private alleys. • It appears that the units that have garages facing the rear of the lot, along the private alleys, are not meeting the 20' minimum rear setback requirement. Revise the lot layout so that the units meet the requirement. IMPORTANT: Note that the front setback is measured from the edge private alley easement and not the property line in the middle of the private alley. • Show the Front Minimum garage setback for the units which front the internal "private streets". The units along the private streets do not currently appear to meet the Front Minimum Garage Setback. IMPORTANT: Note that the front setback is measured either from the edge of the private street easement (not the property line in the middle of the private street) or any sidewalk if it is outside of the private road easement. • Revise the location of the units which front on the internal "private street" so that their garages meet the minimum Front Setback for garages. 4. Revise all labels as needed for the setbacks changes specified above. 5. Provide a justification for the special exception request. Please contact Paty Saternye in the Planning Division by using psaternye(a)-albemarle.org or 434-296-5832 ext. 3250 for further information. Page 7 of 7 Review Comments for SDP201800006 11nitial Site Plan Project Name: ROYAL FERN TOWNHOME - INITIAL Date Completed: Thursday, March 29, 2018 DepartmentlDivisionlAgency: Review Sys: Reviewer: LMafthew Wentland CDD Engineering El I Requested Changes 1 _ A VMP plan will need to be approved prier to final site plan approval- 2- Road plans will need to be approved prior to final site plan approval_ 3_ Private streets should follow VDOT and AA HTO regulations, such as a minimum angle of intersection of 60 degrees The smaller curb radii shown will need to be verified to be adequate by showing vehicle turning movements and will also need to be approved by Fire Rescue- 4- Any work or facilities located off -site will require easementslagreements_ Also please keep in mind the DEQ recommended building and property line setbacks for the stormwater facilities_ Page: County of Albemarle Printed On: 10410412 018 Review Comments for SDP201800006 11nitial Site Plan Project Name: ROYAL FERN TOWNHOME - INITIAL Date Completed: Sunday, March 18, 2018 DepartmentlaivisionlAgency: Review sus: Reviewe r:Ihawn Maddox - Fire Rescue Requested Changes El 1_ Based on building heights provided on the plans the structures must be able to be served by aerial fire apparatus_ See below } for related code sections to assist with ensuring appropriate access- 2- Minimum turning radius should be 25'_ 3_ All private alleys and Road A shall be marked no parking due to current proposed widths- 4- Fire flow test results shall be provided prior to final acceptance_ D105.1 Where required. Where the vertical distance between the grade plane and the highest roof surface exceeds 30 feet (9144 mm), approved aerial fire apparatus access roads shall be provided. 8106-2 Width_ Aerial fire apparatus access roads shall have a minimum unobstructed width of 26 feet (7926 mm), exclusive of shoulders, in the immediate vicinity of the building or portion thereof_ D105.3 Proximity to building_ At least one of the required access routes meeting this condition shall be located within a minimum of 15 feet (4572 mm) and a maximum of 30 feet (9144 mm) from the building, and shall be positioned parallel to one entire side of the building_ The side of the building on which the aerial fire apparatus access road is positioned shall be approved by the fire code official_ D105.4 Obstructions_ Overhead utility and power lines shall not be located over the aerial fire apparatrs access road or between the aerial fire apparatus road and the brilding Other obstructions shall be permitted to be placed }r5,ith the approval of the fire code official_ Page: County of Albemarle Printed On: 10410412 018 Review Comments for SDP201800006 11nitial Site Plan Project Name: ROYAL FERN TOWNHOME - INITIAL Date Completed: Tuesday, April 03, 2018 Departmentlaivision/Agency: Review sus: Reviewer: Heather McMahon CBBARB See Recommendations Motion: Mr_ Hancock moved to approve the consent agenda and forward the recommendations outlined in the staff reports for the Initial Site Plans to the Agent for the Site Review Committee, as follows_ ARB-2018-32: Royal Fern Townhouses Initial Site Plan - Initial Site Development Plan (TWParcel 07600000006400) Proposal: To construct 30 single-family attached units on 3.43 acres_ Location: North of 5th Street (Route 63110Id Lynchburg Road), east of Old Lynchburg Road, and west of Wahoo Way • Regarding requirements to satisfy the design guidelines as per § 18-30.6.4c(2), (3) and (5) and recommended conditions of initial plan approval: o Prior to Initial Plan approval the following items shall be resolved to the satisfaction of the ARB: None_ • Regarding recommendations on the plan as it relates to the guidelines: 1_ Consider providing large shade trees around the two guest parking areas in the center and in the southwest corner of the site- 2- Consider dedicating more frontage along the southern property line to sidewalk improvements_ Regarding conditions to be satisfied prior to issuance of a grading permit: None_ • Regarding the final site plan submittal: 1_ Submit architectural plans, elevations, and material samples for review with the final site plan- 2- Provide a landscape plan that addresses all EC landscape guidelines, complete with plant schedule, for review with the final site plan- 3- Provide all proposed utilities and associated easements on the utility plans- 4- Show mechanical equipment on the site plans and/or architectural plans if the mechanical equipment will be roof- mounted- 5- Provide the standard mechanical equipment note on the Cover Sheet (Cl) of the site plan set and on the architectural drawings: Visibility of all mechanical equipment from the Entrance Corridor shall be eliminated- 6- If any outdoor lighting is proposed, submit a lighting plan for final review that includes photometric values of all freestanding and wall -mounted lights as well as a luminaire schedule and manufacturer's specifications- 7- Reduce the on -center distances of the three trees proposed on the east side of Wahoo Way to meet the 40' spacing requirement- 8- Clarify the tie-in of the sidewalk at Wahoo Way's throat with proposed sidewalk expansion and/or existing asphalt path throughout the site plan set Mr_ Stoner seconded the motion_ The motion carried by a vote of 3:0_ (Binsted, Van der Wert absent) Page: County of Albemarle Printed On: 10410412 018 APPLICATION# TMP: County of Albemarle Department of Community Development 401 McIntire Road, North Wing Charlottesville, Virginia 22902 PLAN REVIEW COMMENTS - E911 SDP201800006 07600-00-00-05400 DATE: 3/13/2018 FROM: Elise Kiewra ekiewra@albemarle.org Geographic Data Services (GDS) www.albemarle.org/ads (434) 296-5832 ext. 3030 The following road will need a name: ROAD A This site will require a one (1) new private road name. Per Sec. 7-200-B of the County's Road Naming and Property Numbering Ordinance (Page 2 of PDF). "It is intended by this article that all roads within the county which serve or are designed to serve three (3) or more dwelling units or business structures shall be named." Please review the procedures in the Road Naming and Property Numbering Manual to decide upon a road name for the road accessing Old Lynchburg Road. We recommend providing three (3) candidate names for each road to our office for review, in case your first choices are not acceptable. A PDF version of the Ordinance and Manual can be found here: httns://www.albemarle.ora/unload/imaaes/Forms Center/Departments/Geoaraphic Data Service s/Forms/Road Namina and Prooertv Numberina Ordinance and Manual.odf Please consult the County's Road Name Index to check your road names prior to submittal. The Index can be found here: http://www.albemarle.org/albemarle/upload/images/webapps/roads/ Parcel and mapping information can be found here: http://gisweb.albemarle.org/ If you should have any questions, please do not hesitate to contact our office. Review Comments for SDP201800006 11nitial Site Plan Project Name: ROYAL FERN TOWNHOME - INITIAL Date Completed: Tuesday, April 03, 2018 DepartmentlDivisionlAgency: Review sus: Reviewer: Kevin McDermott ODD Planning Requested Changes Page: County of Albemarle Printed On: 10410412 018 Review Comments for SDP201800006 11nitial Site Plan Project Name: ROYAL FERN TOWNHOMES - INITIAL Date Completed: Tuesday, March 20, 2018 DepartmentlaivisionlAgency: Review Sys: Reviewer: Richard Nelson LJ AOSA Requested Changes Page: County of Albemarle Printed On: 10410412 018 COMMONWEALTH of VIRGINIA DEPARTMENT OF TRANSPORTATION 1601 Orange Road Culpeper, Virginia 22701 Stephen C. Brich, P.E. Commissioner April 3, 2018 County of Albemarle Department of Community Development 401 McIntire Road Charlottesville, VA 22902 Attn: Paty Saternye Re: Royal Fern — Initial Site Plan SDP-2019-00006 Review #1 Dear Ms. Saternye: The Department of Transportation, Charlottesville Residency Transportation and Land Use Section, has reviewed the above referenced plan as submitted by Shimp Engineering, dated 20 February 2018, and finds it to be generally acceptable as it appears only sidewalk and landscaping work are being proposed within the public right-of-way. If further information is desired, please contact Justin Deel at 434-422-9894. A VDOT Land Use Permit will be required prior to any work within the right-of-way. The owner/developer must contact the Charlottesville Residency Transportation and Land Use Section at (434) 422-9399 for information pertaining to this process. Sincerely, )Z&44� . 11{x Adam J. Moore, P.E. Area Land Use Engineer Charlottesville Residency Virginial)OT.org WE KEEP VIRGINIA MOVING Review Comments for SDP201800006 11nitial Site Plan Project Name: ROYAL FERN TOWNHOME - INITIAL Date Completed: Monday, March 19, 2018 DepartmentlDivisionlAgency: Review sus: Reviewer: Michael Dellinger CDD Inspections No Objection Page: County of Albemarle Printed On: 10410412 018