My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CORRESPONDENCE_1984-1989
Environmental Health - Public
>
EHD Program Facility Records by Street Name
>
A
>
AUSTIN
>
9999
>
4400 - Solid Waste Program
>
PR0440005
>
CORRESPONDENCE_1984-1989
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/17/2023 4:12:55 PM
Creation date
4/7/2023 1:44:17 PM
Metadata
Fields
Template:
EHD - Public
ProgramCode
4400 - Solid Waste Program
File Section
CORRESPONDENCE
FileName_PostFix
1984-1989
RECORD_ID
PR0440005
PE
4433
FACILITY_ID
FA0004516
FACILITY_NAME
FORWARD DISPOSAL SITE
STREET_NUMBER
9999
STREET_NAME
AUSTIN
STREET_TYPE
RD
City
MANTECA
Zip
95336
APN
20106001-3, 5
CURRENT_STATUS
01
SITE_LOCATION
9999 AUSTIN RD
P_LOCATION
99
P_DISTRICT
004
QC Status
Approved
Scanner
SJGOV\cfield
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.
/
728
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
Mr. Herb Iwahiro <br />July 14, 1989 <br />Page 2 <br />source recovery effort) and earthcover requirements ... ". <br />See also page 27, where under the heading "South Littlejohn <br />Creek" it is stated, "The estimated life of the disposal <br />site proposed for the site north of Littlejohn Creek is 30 <br />years based on the disposal rate of 500 tons per day". See <br />also page 29, item #9 in the summary to the report which <br />states, "Based on a refuse disposal site of 500 tons per <br />day, it is estimated that the site has a total capacity of <br />approximately 4.7 million tons of refuse, and a site life <br />on the order of 30 years". <br />On October 31, 1972, there was completed an environmen- <br />tal impact statement which was done, as indicated in the <br />transmittal letter "in accordance with the guidelines estab- <br />lished by the San Joaquin County Planning Department". <br />That EIS used the figure of 500 tons per day to calculate <br />the number of vehicle trips which would be generated (see <br />IV A5 where it is stated "Disposal rate anticipated at the <br />site is 500 tons per day"). In short, the environmental <br />impact statement used the Emcon Associates report informa- <br />tion in determining the environmental impact and determined <br />that with that 500 tons per day, the amount of traffic <br />could be accommodated on the existing road. <br />Your other concern, as I understand it, was a concern <br />that the EIS had never been circulated to the State Clear- <br />inghouse. As I indicated to you there was, to the best of <br />my knowledge, no requirement that it be so circulated. I <br />have researched this issue and have determined the follow- <br />ing: <br />First, the requirement to circulate to the State Clear- <br />inghouse is contained in Title 14, CCR 15206. Leaving <br />aside the discussion of effective dates below, you will see <br />that pursuant to that section, it would not be required <br />that the EIS be submitted to the State Clearinghouse. <br />Assuming, however, that it was so required, you must under- <br />stand that the EIS was done in October 1972. At that time, <br />the law which established the requirements to circulate <br />items to the State Clearinghouse was not in effect. Public <br />Resources Code 521083, which directs the OPR to prepare <br />guidelines, was not even effective until December 1972, and <br />our information from Mr. Robert King, Senior Analyst of the <br />Office of Planning and Research is that Section 15206 was <br />not even enacted until 1976, effective 1977. In other <br />words, there was no procedure or requirement existing to <br />circulate the EIS at the time and therefore it could not <br />have been circulated. The requirement to circulate items <br />
The URL can be used to link to this page
Your browser does not support the video tag.