Loading...
HomeMy WebLinkAboutSDP200400084 Review Comments Major Amendment, Final Site Plan 2021-03-2200UNTY OF ALBEMARLE Department of Community Development 401 McIntire Road, North Wing Charlottesville, Virginia 229024596 Phone (434) 296-5832 Fax (434) 972-4126 March 23, 2021 Keane Rucker, EIT Shimp Engineering, P.C. 912 E. High Street Charlottesville, VA 22902 (434) 227-5140 / keane@shimp-engineering.com RE: Comment Letter for SDP-2020-00018 (Brady Bushey Ford — Major Amendment); 4fh Submittal Dear Mr. Rucker: The Planner for the Planning Services Division of the Albemarle County Department of Community Development will recommend approval of the plan referred to above when the following items 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 to the Albemarle County Code.] The original comments from the first review and action letter for SDP2020-00018 are in gray font. Follow-up comments from the review of the second submittal are in bolded black font. Please address these follow-up comments as well. Each comment is preceded by the applicable reference to Chapter 18 of the Albemarle County Code (Zoning Ordinance), unless otherwise specified. (The following comments are those that have been identified at this time; additional comments may be added or eliminated based on further review.) Review comments from the other reviewing divisions and agencies are also attached. Please submit ten (10) copies of the revised plan to the Community Development Department when revisions have been made. Please contact me at your earliest convenience if you have questions or require additional information or assistance. Sincerely, Andy Reitelbach Senior Planner / areitelbach@albemarle.org / (434)-296-5832 x 3261 1 Albemarle County Planning Services (Planner) — Andy Reitelbach, areitelbachgalbemarle.org — Requested Changes: 1. 132.5.2(b); 32.5.2(n)] Revise the parking schedule on the cover sheet of the site plan and the labels on the plan sheets. a. Counting the number of spaces on sheet C4, there are more than 243 spaces provided, including the accessible spaces in front of the sales and service buildings on TMP 78-6, which do not appear to be included in the total of 243 when counting the full number of spaces. There are only 240 parking spaces labelled as being for customers/employees/service spaces, even though the cover sheet identifies there being 242 spaces. The discrepancy appears to be the small parking lot to the east of Building B. There are only 18 spaces depicted, even though the label says there are 20 employee/service spaces. Revise the cover sheet to state there are only 240 spaces, or add an additional 2 spaces in somewhere else. In addition, the row of "13" spaces north of Buildings B and C actually only has 12 spaces. 12 spaces would make sense with the overall label for that area identifying 34 spaces (12 + the 22 spaces directly south of the preserved steep slopes), so revise the " 13" to a "12." It appears that there continues to be miscalculations in the number of parking spaces provided. On the cover sheet, it states that there are 225 spaces provided. However, 181+46=227 spaces, based on the numbers provided. In addition, counting the number of spaces depicted on sheet C4 that are not display spaces, I can only find 224 spaces. Part of the issue may be in the existing parking lot behind Building A2, there's a label for 56 spaces, but the individual numbers only add up to 55 (unless the one van accessible space by itself on the northwest side of the building is counted as a part of that 56, then then that subtotal works). However, there are still only 224 spaces depicted. Comment addressed. 2. [32.7.2.31 Provide internal sidewalks or crosswalks on the site to connect the buildings and to connect the sidewalk along Route 250 with the enlarged sales building. Provide an accessible ramp for the sidewalk in front of the enlarged sales building. Accessible ramps need to be provided at all spots where the ends of sidewalks meet travelways, including between Buildings B and C, and in front of Building A. Also, the sidewalk referenced in the comment response letter connecting Route 250 to Building A does not appear to be depicted on the site plan. Show this connection. Accessible ramps need to be provided for the sidewalk leading from the front of Building B to the front of Building C. Comment addressed. 3. [4.17; 32.7.8] Include footcandle measurements for the existing lights to demonstrate that the combination of the existing non -conforming lights with the proposed new lights does not increase the footcandle measurements above the permitted range, where the light from the poles would overlap. It appears that the existing lights are labelled as "D" on the lighting plan. Include this identification in the key on sheet C8. None of the lights on the photometric plan have the labels that are identified in the lighting schedule. The footnote indicates that the existing lights are labelled as "A however. none of the existing lights appear to have an "A" labelling them. Revise the labelling regime Comment addressed. 4. Now that staff has a better understanding of where the proposed parking is and which parking spaces are proposed for each use, it has been determined that there is not enough parking on each of the two lots for them to be able to stand separately if the parcels were sold to different owners. A shared parking agreement will be required to be reviewed, approved, and recorded at the courthouse for these two properties before the site plan can be approved, ensuring that sufficient parking is provided for each use on each parcel. Comment has not been addressed. A shared parking agreement will be required prior to approval of the site plan. The shared parking agreement will need to be reviewed by County staff and recorded at the courthouse prior to approval. Please let me know if you would like an example of previously recorded shared parking agreements for reference. With the proposed closure of the entrance directly into TMP 78-6 from U.S. Route 250, a shared access easement will also need to be a part of this agreement to ensure continued access onto 78-6. It is recommended that these items be included with the easement plat required by Engineering for the stormwater management facilities and access easements; however, the various agreements and easements can be done with separate plats and deeds if so desired. Comment still needs to be addressed. Comments from Other Reviewing Departments and Agencies Albemarle County Architectural Review Board (ARB) Margaret Maliszewski, mmaliszewski@albemarle.org — Requested changes; see the comments below: Indicate the location of the Porsche DC charge box on the plan. (If the location was already added to the plan with revision date of 11/30/20, please describe the location or highlight it on the plan.) Ensure that it is screened from view from the EC street. 2. Provide documentation from ACSA that the proposed frontage landscaping is acceptable Albemarle County Engineering Services (Engineer) John Anderson, janderson2galbemarle.org — Requested changes; see the attached memo. Albemarle County Service Authority (ACSA) Richard Nelson, melson@serviceauthority.org —Requested changes; seethe comments below: Submit 3 hard copies and water/sewer data sheets for review and approval. Please clarify what fixtures are serving what building. Sheet C5: Adjust water main alignment, as shown on PDF Call out 8x8x8 tee and have a 6" reducer afterwards. Shift proposed FHA 2' away from edge of pavement. Labeling is congested behind Building B Move FHA closer to the end of island. Sheet C6: One of the proposed trees in a parking island is within the proposed easement. This may be corrected once the alignment is shifted. I will discuss the proposed trees within the ACSA easement along 250 with Pete and Jeremy. Virginia Department of Transportation (VDOT) Adam Moore, Adam.Mooregvdot.vir iginia.gov — No objections at this time; see the attached memo. 3 � AI �h �lRGIN�P COUNTY OF ALBEMARLE Department of Community Development 401 McIntire Road, Room 227 Charlottesville, Virginia 22902-4596 Phone (434) 296-5832 Fax (434) 972-4126 Site Plan Review Project title: Brady -Bushey Ford — Major Site Plan Amendment Project file number: SDP2020-00018 Plan prepares Shimp Engineering, 912 E. High St. Charlottesville, VA 22902 Justin Shimp, PE [ justin(i�shimp-engineering.com ] Owner or rep.: Flow 1300 Richmond LLC / 500 West 5' Street, Winston-Salem, NC 27101 [ bthomasAflowauto.com ] Plan received date: 4 Mar 2020 (Rev. 1) 26 Jun 2020 (Rev. 2) 5 Nov 2020 (Rev. 3) 8 Feb 2021 Date of comments: 7 Apr 2020 (Rev. 1) 31 Jul 2020 (Rev. 2) 6 Nov 2020 (Rev. 3) 2 Mar 2021 Plan Coordinator: Andy Reitelbach Reviewer: John Anderson SDP2020-00018 1. Recommend revise title to include ref, to project file number: SDP202000018. (Rev. 1) Addressed. 2. Provide deed bk.-pg, ref. to interparcel access easements (Final Site Plan checklist, Easements, 0 item). (Rev. 1) Comment persists. Applicant (6/15/20 letter): `No interparcel access easements exist.' This appears inconsistent with SDP201800089, Final Site Development Plan for Pantops Comer , [image removed with Rev. 2 review comments] which shows an interparcel 37' access easement. It seems there should be a corresponding easement on the Brady -Bushey parcel, unless easement operates in one direction only (it may), as easement that allows one-way travel from Brady -Bushey to Pantops Corner, but not travel in the reverse direction. In that instance (if this is an intentional, 1-way easement), comment will be withdrawn. (Rev. 2) Addressed. Applicant response (10/22/20 letter): `Yes, this access easement only operates in one direction —its function is to allow vehicle delivery trucks to enter the property. Those trucks (and customers/employees) will depart via Rte 250 entrance.' 3. Major site plan amendment approval requires an Approved VSMP /WPO plan. Please submit VMSP /WPO application at earliest convenience. (Rev. 1) May persist. Applicant: `Acknowledged. A VSMP plan has been submitted.' A quick county system (CV) search yields no match for Brady -Bushey Ford VSMP, but Engineering anticipates WPO plan submittal, per Applicant response. (Rev. 2) Addressed. WP0202000032 review is in process. (Rev. 3) Persists. Revised WPO Plan received 2/8/21, review pending, with comment due 3/8/21. 4. Include title sheet Note that preserved and managed steep slopes exist on parcels. (Rev. 1) Addressed. 5. VMSP /WPO plan approval requires permanent SWM facility easement plat recordation (for any on -site SWM facilities). (Rev. 1) May persist. Applicant: `Acknowledged. SWM easement is now shown on the plans and an easement plat will be recorded prior to approval.' As follow-up: Please direct reviewer to sheet showing SWM easement for proposed dry detention pond. It appears an identifying label was cutoff on C4. (Rev. 2) Addressed. 6. Provide brief narrative of Stormwater Management on C 1. Consider stormwater quantity and quality in context of increased impervious area /post -developed land cover, 100-year floodplain, stream buffer, etc. C4 91 91 [Id Engineering Review Comments Page 2 of 10 (Rev. 1) Addressed, but as follow-up (please address via VSMP plan), please note that discharge to mapped floodplain meets flood protection portion of 9AVAC25-870-66.C, but design must also address channel protection (9AVAC25-870-66.B). Looking forward: a. Relatively recent DEQ correspondence explains that energy balance applies at limits of analysis for discharge to natural conveyance. That is, simply discharging to a natural conveyance at limits of analysis is insufficient. Instead, at limits of analysis, discharge to natural conveyance requires demonstration that Qi_Y, post -development meets the Energy balance equation requirement. (Rev. 2) Addressed via WPO202000032. Applicant: `Noted ... This condition has been met and is addressed in the VSMP plan WPO202000032,' b. Please revise label, CS to read: `Conveyance will be designed to meet channel and flood protection requirements, see WO plan' since this is where design will meet requirements, and where Albemarle County will evaluate design for channel and flood protection compliance. (Rev. 2) Addressed. c. Do not locate proposed SWM facility on preserved steep slopes since SWM facilities are not listed as a by -right use (18-30.7.4.b.1.). Applicant may apply for a special use permit to allow siting a SWM facility on preserved steep slopes —see 18-30.7.4.b.2. (Rev. 2) Addressed. Applicant: `The proposed SWM facility is outside of the preserved slopes. Following our correspondence on September 2, 2020, a note has been added to ensure no disturbance of preserved steep slopes during construction and maintenance.' Evaluate drainage feature at north property boundary for perennial stream features. Include note on plans that perennial stream exists or does not exist on subject parcel. GIS stream buffer layer may be unreliable at this location. Provide date of field evaluation, and any field data. Ref. code 17-600.A. (Rev. 1) May persist. Applicant: `USGS maps categorize this stream as intermittent. This was field verified on May 21, 2020, by Justin Shimg P.E. No aquatic life was found in the stream. Stream bottom was rounded, rather than cut with deep grooves. Additionally, debris was blocking a portion of the stream which suggested that flows were not strong enough to clear out the debris. A note is now included on the plans near the stream location stating that it is intermittent and was field verified.' Note cannot be located. In this circumstance, a plan sheet reference would be very helpful. Please guide reviewer to sheet with note. (Rev. 2) Addressed. Applicant: `Note is located on C2, the note is located around property line L3-L4.' Show and label preserved and managed steep slopes on C3, C4, C5. (Rev. 1) Partially addressed. As follow-u : Please label preserved and managed steep slopes on C3, C4, C5. (Rev. 2) Addressed, Resolve WPO2018-00088, Amendment 1 as prerequisite to SDP202000018 approval (email, this date). (Rev. 1) Addressed. Applicant: `Revised plans have been submitted and approved.' Revise C3 consistent with actual existing conditions (image, below). Shimg Engineering should have access to designs for development on adjacent parcels to the west. Please rely on these, as well as satellite imagery (for examplee343,120 image, below image removed with Rev. 1 comments) Also, please ref. Final Site Plan checklist for plan reviewers, Existing conditions plan view information, l't item: `accurate current existing topography at the time of submittal, including all existing features, and any recent disturbances.' (Rev. 1) Addressed. Applicant: `The existing conditions page has been updated to show the stockpiles that exist on site currently. Please note that the original topography (without stockpiles) is shown on other grading pages, as stockpiles will be moved at the beginning of construction and it is easier to see how the grading will tie in once the stockpiles are removed.' 11. Show pipes as well as storm MH /inlet structures on C4 or turn storm utility MH /inlet layer off. (Rev. 1) Addressed, 12. Revise loading zone east of existing service building, TMP 78-7, Lot 8, since not adjacent to the structure it serves and since it impedes parking spaces to north, and circulation, generally. Ref. 18-4.12.13.a.b. (Rev. 1) Addressed, 13. Provide autotum figure for dumpster pad. Use single -unit (SU) truck design vehicle. Ref. Fig. 1, VDOT Road Design Manual, Appendix B(1), 20-ft wheelbase. Include entering site, reverse maneuver, and exiting site. (Rev.1) Partially addressed. As ollow-up: SU-30 does not align with dumpster. Operation Engineering Review Comments Page 3 of 10 requires forks on waste management vehicle to align closely with slots in dumpster; oblique alignment does not work. Ref autotum fig., C 13. Provide design sufficient to allow proper operation. Note that in rage be-lew, vehicle strikes dumpster, dumpster enclosure, and grazes a curb with no appreciable clearance. (Rev. 2) Addressed. `The curbing in the area has been slightly revised. The dumpster location has also been revised and can now adequately accommodate truck movement. See updated autotum diagram on C 13.' [ Image removed with Rev. 3 comments.] 14. Provide field survey data that supports note that `portion of preserved slopes disturbed is less than 25%.' Engineering Div. has received no information that would exclude a portion of the steep slopes overlay district (preserved steep slopes) from limits against disturbance or development found at 18-30.3. (Rev. 1) Addressed. Applicant: `LIDAR data showed that the slopes we had previously proposed to be disturbed were less than 25%, however we have no way of submitting a certified survey now because approximately 3,000 CY dirt have been placed directly blocking those slopes. The site plan has been revised showing 4 less parking spaces in that area to allow for the retaining wall to remain outside of the preserved slopes district.' [ Initial review image removed with Rev. 3 comments.] 15. Provide guardrail (VDOT GR-1 or GR-2) at top of 4', 13' and 6' proposed retaining walls along northern edge of parking on TM 78-6, Lot 7. (Ref. Retaining Wall Plan checklist for plan reviewers, Plans, 2nd item). (Rev. 1) Not addressed. Applicant: `Guardrail has been provided along the northern -most wall where a car would be traveling with potentially greater speed in the direction of the wall. The other walls are along parking spaces where cars would be either stopped or driving slowly, and we do not see the need for anything other than handrails in these locations.' As follow-up: Please revisit /consider review -comment exchange for Oak Hill Convenience Store, SDP201800082 (SE project): a. Extensive exchange (email /perhaps meetings) to discuss guardrail for parking spaces fronting retaining walls (Rev. 2) Addressed. Applicant: `Noted, we have provided guardrail along retaining walls near parking areas.' b. Exchange included Albemarle County Engineer who expressed not a preference but a requirement for this design circumstance. (Rev. 2) Addressed. Applicant: `Noted.' c. County Engineer affirmed rationale for guardrails for retaining walls next to parking (to prevent vehicles from (however unlikely) crossing a retaining wall, from which there is no immediate recovery) as structures that may help minimize risk of injury to persons, or damage to property. (Rev. 2) Addressed. Applicant: `Noted.' d. Final Site plan checklist for plan reviewers, p. 1 /last item: (Rev. 2) Addressed. Applicant: `... correct, retaining wall checklist dictates guardrails shall be installed with new retaining walls.' Retaining Wall Plans checklist. Any walls supporting roads or necessary infrastructure require engineered plans (not generic manufacturer's details) and computations. {Design Manual, section 81 This will also be required where walls are close to property lines and there is the danger of affecting neighboring property, either during construction, with later failures, or with pedestrian or vehicle safety. These concerns can be alleviate with layout spacing also. In any case, retaining walls will require building permits at construction. e. Retaining Wall checklist for plan reviewers, (Rev. 2) Addressed. Applicant: `...... correct, retaining wall checklist dictates guardrails shall be installed with new retaining walls.' Plans: safety railing shown for retaining walls over 4' high guardrail with VDOT designations or equivalent shown for retaining walls next to parking or travelways VDOT approval for any walls in right-of-way Accurate depiction of horizontal depth (batter) on site plans. All structural reinforcement, steal, or geogrids specified. All dimensions specified Constructability; there should be no vertical cuts on property lines during construction, such that abutting property does not become unstable. Adequate room for construction needs to be available. f. Given this, emphasizing that (county) Engineering position is unchanged (nor will it), please consider and respond to initial comment and provide guardrail at proposed 4' and 15' Max. height Engineering Review Comments Page 4 of 10 walls west of 18 parking spaces, and east of 13 parking spaces. These are not display spaces, but sections of a 54-parking space employee /service space parking lot. East of this parking lot are unrecoverable preserved steep slopes (beyond 15' Max. In. wall), west of this parking lot are proposed 2:1 slopes (falling) to a 7' retaining wall on Pantops Corner parcel (4' Max. ht. wall). Ref. SDP201800089 /SE, C5' orange highlight, image below. Engineering withdraws request for GR-2 at 6' Max. ht. wall for 22 parking spaces, location shown in lower right of rebel. [image removed with Rev. 2 review comments] (Rev. 2) Addressed. Applicant: `Walls have now been provided for 4' and 15' height walls where marked on image.' From SDP201800089, C5 [ image removed with Rev. 2 review comments ] g. New: Provide GR-2 at 18 display spaces, image, below. Existing slopes west of these 18 spaces are 0.5:1 (10' h, 20' v) with a series of tiered walls presenting —20' drop onto the adjacent parcel. 40' grade break over 25' horiz represents unacceptable risk (at present, without guardrail), and risk should Malloy convert display spaces to public use, or should parcel transfer or rezoning require transition from display to public use parking spaces. Engineering requests design revision, there may be an argument from a design or approval perspective, but only guardrail alleviates risk inherent at these now -unprotected display spaces, and at other locations shown with this major amendment. Please consider plan review checklists. Inadvertent risk presented by proposed design and recently -constructed offsite improvements are the basis of review comment request. (Rev. 2) Withdrawn. Applicant: `The existing slopes at west of that parking lot were shown based on a survey completed at time of offsite retaining wall construction. Those slopes showed the cut required to install the walls along with backfill and geogrid. Currently, there is only a 4' vertical drop from the curb to the off -site walls. The top offsite wall is located about 13' from the back of the curb —so the existing slope adjacent to the parking lot is about a 30% grade (slightly flatter than a 3:1 slope.) So the biggest issue was that the topo that was shown is not representative of the current site conditions, and has now been fixed. Based on the VDOT GRIT manual, Figure 1 page 1-5, a guardrail is not warranted for 30% slopes. Since there is an existing 13' wide 30% slope adjacent to the parking lot, this should satisfy VDOT requirements. For additional consideration, if Engineering were to interpret that the retaining walls offsite add an additional 20' drop, there is no ordinance that requires an applicant to improve existing conditions based on an existing offsite retaining wall. We do agree that if the applicant builds a wall that requires guardrail, they have to provide that guardrail. However, the retaining wall checklist covers new construction —construction completed as part of the site work. In this case, the wall is simply an existing condition, albeit a recent one. Technically, the wall applicant should have built a guard rail for the wall, if a guard rail were required. So to summarize, I think the recoverable 30% slope does not require a GR at this location (based on VDOT char[), and even if that wall were to require a GR, the ordinance should have required the wall applicant provide that during wall construction. So for these reasons, we cannot find requirements for our client to install a guardrail above the existing offsite retaining wall at the western boundary near TMP 78- 5A.' (Rev. 2 / Rev. 3 As follow-up: • Request for guardrail is withdrawn. • Request for GR was made, but is now withdrawn. • Engineering recommends guardrail. • If no GR, Engineering recommends a low -profile block wall that may prevent a car inadvertently mounting curb, crossing the 13' strip, and possibly experiencing a 20' vertical drop. • A specific, unambiguous requirement may not exist in ordinance that requires applicant (SE client Malloy Ford) to install a guardrail above the existing offsite retaining wall at the western boundary near TMP 78-5A. Malloy Ford may simply want to weigh the decision and minimize potential liability that attends design that forsakes protection beyond a modest concrete curb. • Engineering rejects the argument that a pre-existing off -site 20' high retaining wall forecloses site plan review request for GR on the Malloy Ford parcel. Engineering Review Comments Page 5 of 10 Consider this example (though not the case here): Site A constructs a 20' retaining wall to develop Site A. This wall provides 20' vertical break to adjacent Site B, at higher elevation. Site B is undeveloped at time Site A application is approved. There is no indication that parking will be proposed in close proximity to the top of this newly - constructed retaining wall. As consequence, Engineering requests handrail for the retaining wall, but not guardrail. Later, Site B is developed. Site B proposes parking 13' from the top of the retaining wall /20' drop. Engineering requires GR adjacent to parking as a barrier to minimize risk that a vehicle may mount the curb, and within space available, be unable to halt progress across a strip between curb and wall. Engineering requests GR to protect Site B personnel, public, etc. In this example, Site A, developed first, is allowed to construct a 20' high wall without GR, since no indication Site B will in the future need GR to accompany unforeseen design /parking proximity. This example highlights circumstance where GR is required later but not with initial wall. Rev. 2, 3) Request for GR reflects reviewer's PE-credentialed approach that recognizes public welfare as a consummate principle (minimize risk), request for GR provides assurance that recognizes and helps protect this Applicant's interests, now and in the future. Intent is not argumentative, intent is conservative approach to design that recognizes risk, that seeks the best outcome. Engineering does not impose requirements where none exist, however finely drawn. Engineering (with GR comment) had hoped to engage on topic of safe, conservative design in the public and Applicant's interest. We now recommend a barrier behind existing concrete curb, to mitigate effects of unforeseen circumstance. (Rev. 3) Engineering restates recommendation for a low -profile barrier, if not a guardrail. The case here: Engineering, during review of Pantops Corner ESP, raised issue/s relating to retaining walls with Shimp Engineering (SE), then representing Pantops Comer. In comment response, above, SE draws a distinction between requirements then vs. now, stating `Technically, the wall applicant should have built a guard rail for the wall, if a guard rail were required.' We appreciate and would like to examine this response in light of SE response when issue of retaining walls /offsite easement (with Malloy Ford) was raised with SE by J. Anderson during review of Pantops Comer (SUB201900059) plat. Engineering did not request GR for the Pantops Corner retaining walls. It is unclear we would have ever requested GR. In all likelihood, we would not have since GR would have to be installed on adjacent parcel (Malloy Ford). Retaining wall design for Pantops Comer ran to the property line and left no room to install GR on Pantops Comer parcel (since wall locations critical to site development —hotel, Wawa, etc.). We cannot be certain, since we did not request GR with Pantops Comer development. What we do know is SE response when Engineering attempted to engage on topic of retaining wall /off -site easement requirements when reviewing Pantops Comer development. Please consider whether it is perhaps disingenuous to now state that Engineering should have committed to require GR for these retaining walls, given resistance when Engineering raised topic of easements (in 2019) tied to retaining walls to be constructed on Pantops Comer parcel. It is one thing to say Engineering should ensure requirements are met contemporaneous with development. It is another to say this while at the same time forcefully resisting Engineering overtures to do that —to identify or ensure valid ordinance requirements are met. Quotes below, from SE response to review comments, Pantops Comer easement plat (SUB201900059). 0 Applicant [SE] response: `Regardless of whether this is a current issue, you have brought up a site plan review item. This is an easement plat, so while this comment may be appreciated on the site plan (if indeed the County Attorney deemed it an issue), this should not be applicable to this easement plat.' 0 Applicant response: `The temporary grading easement on TMP 76-6, as shown on previously submitted site/road plans for Pantops Corner, was already 16. 17 18 Engineering Review Comments Page 6 of 10 recorded in DB4553 PG 473-486. This is not a proposed easement, nor is it onsite so therefore it will not be shown on this plat.' o Applicant response: `Plats are required to show all known easements on the subject property. These are known easements, recorded in the Albemarle courthouse in DB5147 PG 221, 228 & 229, therefore they will be shown. We would like to remind County Engineering that their review is for engineering items on this easement plat only. Please leave legal questions, such as debating whether a recorded item is an easement, to the County Attorney, who is the qualified professional in this matter. The existing easement will remain on the plat as it is required to be shown.' Again, Engineering did not request GR for Pantops Corner proposed retaining walls, either when reviewing Pantops Comer Final Site Plan (SDP201800089) or easement plat (SUB201900059). There was, however, a clear attempt to engage on topic of retaining walls and off -site grading easement (on Malloy Ford parcel), but SE appeared disinclined to engage on any but technical grounds, and Engineering relented, on both points. Engineering encourages Malloy Ford (SE client) to consider consequence that may arise should a vehicle, however unlikely, cross curb and retaining wall with a 20' vertical drop. (Rev. 3) Engineering encourages consideration of consequence. SDP202000018, C5, Grading and Utilities (2/8/21) (10/22/20, left: 2/8/21, right) ITo ..�uw FFE BFE lam'. a Y 3rq_ l Itzaz + r-1\\ Provide handrail (safety railing) Inbe6 1'or retaining walls over 4' high (see Retaining Wall checklist). (Rev. 1) Partially addressed. As follow-W: Provide handrail label for retaining wall (Max. ht. =8') east of building B. (Rev. 1) Addressed. Engineering defers to VDOT on entrance requirements from Richmond Road, U.S. Rt. 250. (Rev. 1) Persists. Applicant: `Acknowledged. This is still being worked out with VDOT.' (Rev. 2) Addressed. Applicant: `Coordination with VDOT is ongoing. It is likely that VDOT will approve the current strategy (one full entrance with one right -in -only entrance).' (Rev. 3) Persists. Engineering defers to VDOT. Applicant submitted Functional Analysis of Existing Entrances, Albemarle County TMPs 78-6 & 78-7, d. 2/5/21 [revised, now 4' iteration] with most recent plan submittal. Engineering recommends provide distance from proposed revised entrance to adjacent entrances, east and west (entrance 2, entrance 4, sheet C8). (Rev. 1) Addressed. C5 Engineering Review Comments Page 7 of 10 19. Sidewalk at SE comer of new sales building (FEE 419.50) appears < 5' w. Ensure all sidewalks are 5' minimum width. (Rev. 1) Addressed. Applicant: `Sidewalk at the SE comer of the new sales building (now labeled Building A4) is 5 ft. the dimension is now shown. It does taper off to a smaller width, but it is used to facilitate vehicular circulation, not pedestrian circulation since there is no door in that location.' 20. Label all sidewalk widths. (Rev. 1) Addressed. 21. Label drive aisle width between curbing from entrance 2 to buildings that are interior to TM 78-6, Lot 7. (Rev. 2) Addressed. 22. Provide CG-12 pedestrian ramps at each entrance: 2, 3, 4. (Rev. 1) Partially addressed. Asfollow-up, depict ramps as shown in CG-12 detail (radially /curved), see detail, CC 12 or, modify as needed if CG-12 does not offer precise depiction required to align ramps with pedestrian direction of travel. A visually impaired pedestrian may `read' detectable ramp surfaces to align travel (similar to reading braille, by touch). Note orientation of schematic representation of CG-12 ramps on C4. Note detail on C 12, From C4: Examine orientation /graphic depiction of every CG-12 adjacent to U.S. Rt. 250, some within Rt. 250 RW. Virtually all require revision to show orientations that align detectable surfaces with receiving ramps such that a visually impaired person does not stray into Rt. 250 by mistake. CG-12 design assists visually impaired and ambulatory impaired, alike. Other VDOT standards /devices alert when it is safe to enter a crosswalk; pavement markings and traffic signs alert motorists to the presence of pedestrians. All of it may be needed to protect pedestrians, especially in highspeed or high traffic volume locations. U.S. Rt. 250 presents both. CG-12 at this location is a critical design element; please show ramps in plan view, as they are intended to be built to safely direct any pedestrian from one ramp to the next. (Rev. 2) Addressed_ [ An image removed with Rev. 3 comments. ] Ax / A \a I x.mll 6 r - I -- +— II --- L!l L I I of I I I I I I I -7'7 APPRONIMATE LOCAPC O ' wAMRLINE EASEMENT 23. Wherever curb (CG-2) concentrates runoff against curbing, specify CG-6. Engineering understands this is a dealership and that parking will be primarily for stored vehicles (automobile sales, services, and display). Nevertheless, storm conveyance is critical to pavement integrity, which may affect retaining wall stability. (Rev. 1) Addressed. 24. Include notes that this development: (Rev. 1) Addressed. a. May not impact preserved steep slopes, b. Is not authorized to impact preserved step slopes, c. Is subject to steep slopes overlay district requirements (18-30.3), and d. That preserved or managed steep slopes will be staked /flagged prior to land disturbance, and that flags /stakes will be maintained for the duration of the project, to final completion. 25. Proposed 4', 6' and 13' high retaining walls support parking (infrastructure). Please submit geotechnical retaining wall designs (PE -sealed) to Engineering as prerequisite to recommendation to approve major site plan amendment. Note: detailed geotechnical design is also required with building permit applications for retaining walls. (Rev. 1) Persists. Applicant: `Acknowledged. We have contacted a geotechnical engineer and retaining wall design will be provided prior to approval.' Engineering appreciates this. (Rev. 2) Persists. Applicant: `This is ongoing, geotech has not yet completed ret. wall plans.' (Rev. 3) Partially addressed. Circeo Geotech 12-sheet wall design d. 2/7/21 is inconsistent with SDP labels specifying max. wall In. (C4, SDP202000018), and requirements at 18-4.3.3. Further, these walls, A-E, each requires building inspection division review and approval. Each requires a building permit. Building inspections division will likely flag or reject height that exceeds standard listed at 18-4.3.3. It is unfortunate that now - proposed 24' wall height and SDP stated maximum height (15') exceed county code max. retaining wall In. (all planning /zoning districts, not just steep slopes overlay). Once Wall E design is revised consistent with code, Engineering recommends coordinate with building inspections via building permit application process at earliest convenience. Engineering Review Comments Page 8 of 10 For future reference, 18-4.3.3: Max. wall In. measured from grade =10% otherwise, stepped walls required. TAe louawir5 ueriµn rra naam, apph ro aM ....nand Yamnt[m Pym(rtY%appenmp+nw myna It—., rv6emem>re6ram MUllappuearidn pun, er M.A. A " A�en[Tnemavmum nawm aga lItt �e-1111nmu niwrm rpm naem nuc Aarb�raLY�rIVYrnateemn vmenoervaanreuinmIr, unedw wouq ue--1 wa man be bmunrad mumaazrgpeb w1 u. a.�rw. arrorawnr:a.wupod..mmrm.mro.�.bdrai d�eudraam�«rnr manudurdudedur..edummmarrr.m�b.aepped.an,nwm add wnoeu.dwpw.�m arredmr,b e,aadrmodredrobrt.rt- a. romararcn orwanmmae,yrro acvnag era gwas a.ce.ewwrnw mromensgrraawa.gmwmaybnmrepnamewrwrrµ neurm.gwansircbrµ.nwimbmedesrg. arabuiidi.gsran.arbesupenro negm imimwnsosrvbsmionlsXlr. Sec. 4.3.3 - Grading standards. The following design standards apply to any land disturbing activity requiring a Virginia Erosion and Sediment Control Prograr A. Retaining walls. Retaining walls shall meet or exceed the following minimum standards: 1. Height. The maximum height for a single retaining wall, measured from grade to grade, shall be ten feet, except as provi 2. Multiple stepped walB; separation. A minimum horizontal distance of three feet shall be maintained between each indivi 3. Incorporation of wall into design of building. Retaining walls maybe incorporated into the design of a building so that t Portions of Wall E attain 24'. This height is impermissible. Please compare SDP202000018, 10/22/20/Wall F and 2/8/21/Wall E (same wall with different labels), with Circeo reatining wall design d. 2n121 [ 1 day prior to 2/8/21 SE SDP]. SDP (Oct. /Feb.) states max. ht. =15' while Wall E design indicates max. ht. =24'. Engineering requests SE revise SDP labels /design• and requests revised retaining wall design consistent with 18-4.3.3/Grading Standards. Engineering anticipates three (3) stepped walls of 8' ht. each without impact to preserved steep slopes. Wall F. 10/22/20 SDP. sheet C4 etc s- C9 Engineering Review Comments Page 9 of 10 � 39B 3J . SGN�A806�1 6W h� y BOW ='3WW BOW=))lOD un.. -0O% �^ Drcinpip•to peylll ' BOW=—.67 (Le•P, F--n__—;--ti—. - 0 0 ® tl E WM � • 1 •`>.IOIM 26. Add SL-1 labels to profiles for MH In. >12'. MH Str. A3 and A3a, for example. (Rev. 1) Addressed. 27. At Str. A2 and any MH Str. with vertical drops > 4', include note /label for Y:" steel plate in floor of structure. Ref. VDOT Drainage Manual, 9.4.8.7. (p. 9-37, 9-38). (Rev. 1) Addressed. 28. Provide VDOT SL-1, IS-1, PB-1, GR-1, CG-6, CG-9a details on the plans (safety slab, inlet shaping, pipe bedding, guardrail, curb /gutter, commercial entrance). (Rev. 1) Addressed, 29. Provide and label dimensions of existing outlet protection at Str. Al. Design relies on existing riprap ditch. Provide dimensions of existing riprap ditch (typ). (Rev. 1) May persist. Applicant: `The existing outlet protection is now dimensioned on the plans (4 ft).' As ollow-W: Please direct reviewer to which plan sheet shows dimensions of existing outlet protection. (Rev. 2) Addressed. 30. Design relies on existing ditch downstream of Str. Al. Include notes on plans that existing riprap ditch meets design requirements for channel and flood protection for manmade conveyance, if that is the case. (Rev. 1) Addressed. Applicant: `This is now noted on the site plan. The VSMP includes more specific information about the existing conveyance channel adequacy.' Also, please seefollow- n at item 6. above. (Rev. 2, D Addressed. WP0202000032 is under review. 31. If existing riprap ditch does not provide adequate channel or flood protection, provide adequate design. (Rev. 1) May persist. VSMP Plan should present details concerning adequate channel and flood protection. (Rev. 2,3) Addressed. WP0202000032 is under review. 32. Revise storm Al -A6 design. Every pipe in this run has velocity that exceeds (VDOT Drainage Manual 9.4.8.7.) 10 fps standard. (Rev. 1) Withdrawn. Review error. Applicant: `The referenced section is for concrete pipes. HDPE pipes are significantly more resistant to abrasion. The design standards manual states design velocities should be between 3 and 20 fps with a maximum pipe slope of o16%. All pipes meet these standards.' Engineering Review Comments Page 10 of 10 9.4.8.7 Maximum Grades Slopes that incur uniform Flow velocities in excess of 10 fps should be avoided because of the potential for abrasion. Slopes in excess of 16% are not preferred because of the need for anchor blocks. When anchor blocks are used, they should be installed at Every other pipe joint, as a minimum. (See Special Design Drawing No. A-73 and MA- 73 for Anchor Details for Concrete Pipe) 33. Provide retaining wall safety railing detail. (Rev. 1) Addressed 34. Provide LD-204, inlet design. (Rev. 1) Addressed. Please feel free to call if any questions. Thank you I Anderson 434.296-5832 -x3069 SDP2020-00018 Brady -Bushey Ford FMJ 030221rev3 (Z) COMMONWEALTH of VIRGINIA DEPARTMENT OF TRANSPORTATION Stephen C. Brich, P.E. 1401 East Broad Street Commissioner Richmond, Virginia 23219 March 22, 2021 County of Albemarle Department of Community Development 401 McIntire Road Charlottesville, VA 22902 Attn: Andy Reitelbach (804) 786-2701 Fax: (804) 786,2940 Re: SDP-2020-00018- Brady Bushey Ford — Major Site Plan Amendment Review #4 Dear Mr. Reitelbach: The Department of Transportation, Charlottesville Residency Transportation and Land Use Section, has reviewed the above referenced plans as submitted by Shimp Engineering, dated February 8, 2021 and find it to be generally acceptable. If further information is desired, please contact Max Greene 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 land Use Section at (434) 422-9399 for information pertaining to this process. Sincerely, Adam J. Moore, P.E. Area Land Use Engineer Charlottesville Residency VirginiaDOT.org WE KEEP VIRGINIA MOVING