Block · one region of the page, as the scanner read it. It may hold a whole story, part of one, several, or an advertisement; stitching blocks into articles is the next step. Text is supplied OCR.

Page 5 · column 6 of 6 · from the scan, no model involved

The clipping this text was read from
The clipping this text was read from

causing the problems are further jtlp Route 630 beyond the project terminus;

This flooding/drainage problem is firmly rooted in an adjacent landowner’s mismanagement of an entrance/stream crossing which is inadequate in width for the stream flow rate as well as overflows. The result of this “private property” mismanagement is damage and deterioration to the public right of way and . adjacent property during normal heavy rainfalls which occur several times a year. This problem has progressively worsened over the last syi to seven years. Perhaps instead , of a $400,000 public improvement project this should be, atjeast partially, a private insurance settlement to address the damage to the public facilities.

VDOT’s location and design consideration says, “The existing facility is a rolling two-lane road, a combination of paved and gravel treated surface.” It would seem quite logical that the average running speed would be more appropriate than using the statutory 55 mph. This average running speed is considerably closer to 35 mph than 55 mph.

I do not believe that we can afford this proposal, either in tax dollar costs or in the loss of the original rural character of an existing rolling, shaded country lane with large overhanging tree branches In place of this VDOT wants to provide us with a widened, improved, faster gun barrel for bullets to proceed down.

If the existing running speed of 35 mph is considered and designed for, then the drainage problems can be addressed with spot easements as is customary, thereby saving most if not all of the existing trees as well as the existing roadway character.

94.3%