My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
SU0006254
EnvironmentalHealth
>
EHD Program Facility Records by Street Name
>
G
>
GRANT LINE
>
20058
>
2600 - Land Use Program
>
PA-0600364
>
SU0006254
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/16/2020 3:43:59 PM
Creation date
9/5/2019 10:46:51 AM
Metadata
Fields
Template:
EHD - Public
ProgramCode
2600 - Land Use Program
RECORD_ID
SU0006254
PE
2691
FACILITY_NAME
PA-0600364
STREET_NUMBER
20058
Direction
W
STREET_NAME
GRANT LINE
STREET_TYPE
RD
City
MOUNTAIN HOUSE
APN
20907026
ENTERED_DATE
9/15/2006 12:00:00 AM
SITE_LOCATION
20058 W GRANT LINE RD
RECEIVED_DATE
9/12/2006 12:00:00 AM
P_LOCATION
99
P_DISTRICT
005
QC Status
Approved
Scanner
SJGOV\wng
Supplemental fields
FilePath
\MIGRATIONS\G\GRANT LINE\20058\PA-0600364\SU0006254\CDD OK.PDF
Tags
EHD - Public
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
1070
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
would occur within the Mountain House Creek Restoration Plan; if not feasible, replacement — <br /> wetland would occur elsewhere in San Joaquin County. (See CDD COA#37) CDD has also <br /> included a condition (COA#38) requiring the applicant to prepare a Riparian Habitat Mitigation Plan <br /> (Habitat Plan)for the elimination of the riparian habitat on the site of the proposed project.The <br /> Habitat Plan would indicate sites that are to be developed or preserved to serve as offset for loss of <br /> riparian habitat as a result of the proposed project. To the extent practical, replacement sites would <br /> be located in San Joaquin County and would assist in the maintenance of riparian corridors. Finally, it <br /> should be noted that specified findings have been included in the Bases for Master Plan Amendment <br /> and in the Findings for Major Subdivision Application concerning the elimination of wetlands and <br /> riparian habitat on the project site. (Under Volume 1, Policy VI, G,6 of the General Plan, the Review <br /> Authority must find,when a development project would result in the elimination of wetlands, that:a) <br /> no suitable alternative site exists for the land use, and the use is considered necessary to the — <br /> public; b)there is no degradation of the habitat or numbers of any rare, threatened, or endangered <br /> plant, or animal species as a result of the project; and c) habitat of superior quantity and superior <br /> or comparable quality will be created or restored to compensate for the loss.) <br /> With respect to possible State regulation, since the drainage swale is a wetland feature that could <br /> be considered a water of the State of California (as defined by California Water Code Section <br /> 13260(a)(1)), the California Department of Fish and Game ("CDFG") may require a Streambed — <br /> Alteration Permit. If CDFG determines that the drainage Swale is a State Wetland, the applicant <br /> would also be required to meet State Regional Water Quality Control Board discharge <br /> requirements. As a result, CDD has included the following CDD Tentative Map COAs: <br /> COA#39:The appiicant shall submit a Notification Packet to the Streams and Lakes Division <br /> of the California Department of Fish and Game. If the Division of Streams and Lakes <br /> determines that a Streambed Alteration Permit is required, the permit shall be obtained prior <br /> to approval of the Final Map and prior to the approval of the subdivision Improvement Plans. <br /> COA#40: If the California Department of Fish and Game determines that the wetland on the — <br /> project site is a State Wetland, then the applicant shall contact the Regional Water Quality <br /> Control Board to obtain discharge requirements prior to approval of the Final Map and prior to <br /> approval of the subdivision Improvement Plans. <br /> Master Plan and Specific Plan III Amendments <br /> As noted previously, prior to approval of the Tentative Map, both the Master Plan and the Specific <br /> Plan III document would need to be revised to eliminate the riparian habitat/wetland feature and <br /> associated acreage shown on various tables and map figures of those plans. For the Master <br /> Plan, the following tables and map figures are proposed for amendment:Table 3.1: Land Use — <br /> Summary; Table 3.2: Land Use by Neighborhood; Table 7.1: Recreation and Open Space Areas; <br /> Figure 3.5—Master Plan Designations; Figure 3.8—Master Plan Designations—South Area; and <br /> Figure 7.1—Recreation and Open Space Plan. For Specific Plan III, the following tables and map <br /> figures are proposed for amendment:Table 3-1: Land Use Summary by Neighborhood; Table 3-2- <br /> Master Plan Land Use Designations in Specific Plan III; Table 3-3: Neighborhood Minimum, <br /> Maximum and Expected Residential Units; Figure 1-3: Master Plan Designations; Figure 3-2: <br /> Land Use Map and Residential Buildout; Figure 3-4: Implementing Zones for Master Plan Land — <br /> Use Designations; Figure 7-1: Recreation and Open Space Plan. <br /> In addition to the above amendments, the Neighborhood Entry at the intersection of"F Street and <br /> the Delta College Campus parcel is proposed to be deleted. The Neighborhood Entry at this <br /> location is shown on Master Plan Figure 4.18: Community Entries Location Plan and on Specific <br /> Plan III Figure 4-2: Landscape Framework Diagram. Neighborhood Entries are intended to mark <br /> the primary entry points into a residential neighborhood and are located at the intersection of _ <br /> Arterial and Collector streets. Since there is no street intersection at the subject location, and <br /> since the County cannot dictate the design of the Delta College campus at this location, retention <br /> 18 <br />
The URL can be used to link to this page
Your browser does not support the video tag.