[Federal Register Volume 88, Number 104 (Wednesday, May 31, 2023)]
[Notices]
[Pages 34850-34851]
[FR Doc No: 2023-11503]

-----------------------------------------------------------------------

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

Combined Notice of Filings #1

    Take notice that the Commission received the following electric
corporate filings:

    Docket Numbers: EC23-74-000.
    Applicants: Energy Harbor Corp.
    Description: Energy Harbor Corp., et. al. submits Supplemental
Submission and Request Not To Adjust Comment Period.
    Filed Date: 5/15/23.
    Accession Number: 20230515-5180.
    Comment Date: 5 p.m. ET 6/16/23.

    Take notice that the Commission received the following electric
rate filings:

    Docket Numbers: ER23-1942-000.
    Applicants: Idaho Power Company.
    Description: Sec.  205(d) Rate Filing: RS 172--IPC/PAC Kinport
Construction Agreement to be effective 4/14/2023.
    Filed Date: 5/23/23.
    Accession Number: 20230523-5198.
    Comment Date: 5 p.m. ET 6/13/23.

    Docket Numbers: ER23-1943-000.
    Applicants: Idaho Power Company.
    Description: Sec.  205(d) Rate Filing: RS 173--IPC/PAC Midpoint
Construction Agreement to be effective 4/14/2023.
    Filed Date: 5/23/23.
    Accession Number: 20230523-5202.
    Comment Date: 5 p.m. ET 6/13/23.

    Docket Numbers: ER23-1944-000.
    Applicants: Skylar Energy Resources LLC.
    Description: Tariff Amendment: Cancellation entire tariff to be
effective 5/24/2023.
    Filed Date: 5/23/23.
    Accession Number: 20230523-5216.
    Comment Date: 5 p.m. ET 6/13/23.

    Docket Numbers: ER23-1945-000.
    Applicants: Skylar Power Marketing, LLC.
    Description: Tariff Amendment: Cancellation entire tariff to be
effective 5/24/2023.
    Filed Date: 5/23/23.
    Accession Number: 20230523-5217.
    Comment Date: 5 p.m. ET 6/13/23.

    Docket Numbers: ER23-1946-000.
    Applicants: PacifiCorp.
    Description: Sec.  205(d) Rate Filing: Certificate of Concurrence
to Kinport Construction Agreement to be effective 4/14/2023.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5000.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1947-000.
    Applicants: PacifiCorp.
    Description: Sec.  205(d) Rate Filing: Certificate of Concurrence
to Midpoint Construction Agreement to be effective 4/14/2023.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5001.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1948-000.
    Applicants: Southwest Power Pool, Inc.
    Description: Sec.  205(d) Rate Filing: 1518R26 Arkansas Electric
Cooperative Corp NITSA NOA to be effective 8/1/2023.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5009.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1949-000.
    Applicants: Midcontinent Independent System Operator, Inc.
    Description: Sec.  205(d) Rate Filing: 2023-05-24_Cancellation of
Schedule 43J Teche Unit No. 3 SSR Cost Allocation to be effective 7/24/
2023.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5018.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1950-000.
    Applicants: Midcontinent Independent System Operator, Inc.
    Description: Sec.  205(d) Rate Filing: 2023-05-24_SA 4066 NIPSCO-
Sedge Meadow Solar Park GIA (J1407) to be effective 5/25/2023.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5034.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1951-000.
    Applicants: PJM Interconnection, L.L.C.
    Description: Sec.  205(d) Rate Filing: Amendment to ISA, SA No.
5869; Queue No. AE2-126 (amend) to be effective 7/24/2023.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5058.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1952-000.
    Applicants: Alabama Power Company, Georgia Power Company,
Mississippi Power Company.
    Description: Sec.  205(d) Rate Filing: Alabama Power Company
submits tariff filing per 35.13(a)(2)(iii: Chilatchee 115B LGIA Filing
to be effective 5/12/2023.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5091.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1953-000.
    Applicants: Midcontinent Independent System Operator, Inc.
    Description: Sec.  205(d) Rate Filing: 2023-05-24_SA 3373 Entergy
Arkansas-Newport Solar 2nd Rev GIA (J919 J1402) to be effective 5/16/
2023.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5100.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1954-000.
    Applicants: EIP Investment, LLC.
    Description: Initial rate filing: Exhibit C adding to be effective
5/24/2023.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5136.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1955-000.
    Applicants: Earthrise Lincoln Interconnection, LLC.
    Description: Baseline eTariff Filing: Filing of SFA and Request for
Associated Waivers and Blanket Authorization to be effective 12/31/
9998.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5167.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1956-000.
    Applicants: Earthrise Tilton Interconnection, LLC.
    Description: Baseline eTariff Filing: Filing of SFA and Request for
Associated Waivers and Blanket Authorization to be effective 12/31/
9998.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5174.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1957-000.
    Applicants: Earthrise Gibson City Interconnection, LLC.
    Description: Baseline eTariff Filing: Filing of SFA and Request for
Associated Waivers and Blanket Authorization to be effective 12/31/
9998.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5177.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1958-000.
    Applicants: Earthrise Shelby County Interconnection, LLC.
    Description: Baseline eTariff Filing: Filing of SFA and Request for
Associated Waivers and Blanket Authorization to be effective 12/31/
9998.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5178.
    Comment Date: 5 p.m. ET 6/14/23.

    Docket Numbers: ER23-1959-000.
    Applicants: Earthrise Crete Interconnection, LLC.
    Description: Baseline eTariff Filing: Filing of SFA and Request for
Associated Waivers and Blanket Authorization to be effective 12/31/
9998.
    Filed Date: 5/24/23.
    Accession Number: 20230524-5179.
    Comment Date: 5 p.m. ET 6/14/23.

    The filings are accessible in the Commission's eLibrary system
(https://elibrary.ferc.gov/idmws/search/fercgensearch.asp) by querying
the docket number.

    Any person desiring to intervene or protest in any of the above
proceedings must file in accordance with Rules 211 and 214 of the
Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5:00
p.m. Eastern time on the specified comment date. Protests may be
considered, but intervention is necessary to become a party to the
proceeding.
    eFiling is encouraged. More detailed information relating to filing
requirements, interventions, protests, service, and qualifying
facilities filings can be found at: http://www.ferc.gov/docs-filing/efiling/filing-req.pdf. For other information, call<PHONE_NUMBER>
(toll free). For TTY, call<PHONE_NUMBER>.

    Dated: May 24, 2023.
Debbie-Anne A. Reese,
Deputy Secretary.
[FR Doc. 2023-11503 Filed 5-30-23; 8:45 am]
BILLING CODE 6717-01-P


[Federal Register: January 30, 2008 (Volume 73, Number 20)]
[Notices]
[Page 5552-5554]
[DOCID:fr30ja08-72]

-----------------------------------------------------------------------

DEPARTMENT OF ENERGY

Federal Energy Regulatory Commission

[Docket No. CP08-46-000]

Tarpon Whitetail Gas Storage, LLC; Notice of Intent To Prepare an
Environmental Assessment for the Proposed Whitetail Natural Gas Storage
Project and Request for Comments on Environmental Issues

January 23, 2008.
    The staff of the Federal Energy Regulatory Commission (FERC or
Commission) will prepare an environmental assessment (EA) that will
discuss the environmental impacts of the proposed Whitetail Natural Gas
Storage Project involving construction and operation of natural gas
facilities by Tarpon Whitetail Gas Storage, LLC (Whitetail) in Monroe
County, Mississippi. The EA will be used by the Commission in its
decision-making process to determine whether the project is in the
public convenience and necessity.
    This notice announces the opening of the scoping process the
Commission will use to gather input from the public and interested
agencies on the project. Your input will help determine which issues
need to be evaluated in the EA. Please note that the scoping period
will close on February 25, 2008. Details on how to submit comments are
provided in the Public Participation section of this notice.
    If you are a landowner receiving this notice, you may be contacted
by a pipeline company representative about the acquisition of an
easement to construct, operate, and maintain the

proposed facilities. Whitetail would seek to negotiate a mutually
acceptable agreement. However, if the project is approved by the
Commission, that approval conveys with it the right of eminent domain.
Therefore, if easement negotiations fail to produce an agreement,
Whitetail could initiate condemnation proceedings in accordance with
Mississippi state law.
    This notice is being sent to affected landowners; federal, state,
and local government representatives and agencies; elected officials;
Native American tribes; other interested parties; and local libraries
and newspapers. State and local government representatives are asked to
notify their constituents of this proposed project and to encourage
them to comment on their areas of concern.
    A fact sheet prepared by the FERC entitled ``An Interstate Natural
Gas Facility On My Land? What Do I Need To Know?'' addresses a number
of typically asked questions, including the use of eminent domain and
how to participate in the Commission's proceedings. It is available for
viewing on the FERC Internet Web site (http://www.ferc.gov).

Summary of the Proposed Project

    Whitetail proposes to construct, own, operate, and maintain a high-
deliverability, multi-cycle depleted reservoir natural gas storage
facility, known as the Aberdeen Gas Storage Field, in Monroe County.
The Whitetail Natural Gas Storage Project would accommodate the
injection, storage, and subsequent withdrawal of natural gas for
redelivery in interstate commerce. Upon completion of the project, the
reservoir would have a total working gas storage capacity of 8.6
billion standard cubic feet.
    The primary facilities associated with the proposed project are as
follows:
     Up to 20 injection/withdrawal wells and 2 saltwater
disposal wells in two general locations (the ``West Well Pad Site'' and
the ``East Well Pad Site'');
     An interconnection (the ``TETCO Interconnect'') with Texas
Eastern's existing interstate natural gas pipeline that includes a
meter station, pig launcher/receiver, interconnect piping, and
associated facilities;
     About 4.9 miles of 24-inch-diameter pipeline (the ``West
Header Right-of-way pipeline'') and 1.0 mile of 16-inch-diameter
pipeline (the ``Field Line Corridor pipeline''); and
     14,200 horsepower (hp) of compression (four 3,550 hp
natural gas-driven compressors and ancillary facilities) at a new
compressor station (the ``Whitetail Compressor Station'').
    The general location of the proposed storage field project is shown
in Appendix 1.\1\
---------------------------------------------------------------------------

    \1\ The appendices referenced in this notice are not being
printed in the Federal Register. Copies are available on the
Commission's Internet Web site (http://www.ferc.gov) at the

``eLibrary'' link or from the Commission's Public Reference Room at
(202) 502-8371. For instructions on connecting to eLibrary, refer to
the ``Additional Information'' section at the end of this notice.
Copies of the appendices were sent to all those receiving this
notice in the mail. Requests for detailed maps of the proposed
facilities should be made directly to Whitetail.
---------------------------------------------------------------------------

Land Requirements for Construction

    The construction and development of the Aberdeen Gas Storage Field
itself would encompass about 2,850 acres. An additional buffer zone,
defined by the Mississippi Oil and Gas Board as necessary to ensure
reservoir integrity, would bring the total storage area to 4,840 acres.
    The West Header Right-of-way and the Field Line Corridor pipelines
would together require about 79 acres of temporary disturbance for the
construction rights-of-way, including extra work spaces. Of this total,
about 36 acres would be retained for Whitetail's permanent rights-of-
way.
    The proposed TETCO Interconnect site is a 1-acre tract at the
northwest terminus of the proposed West Header Right-of-way pipeline.
This site would be fenced and permanently converted to natural gas
operation.
    Most of the remaining facilities associated with the proposed
project would be constructed within the ``Plant Site,'' a 24.3-acre
tract owned by Whitetail. Within this site, the Whitetail Compressor
Station would encompass about 11.1 acres and the West Well Pad Site
(for construction of injection/withdrawal and saltwater disposal wells
and ancillary facilities) would encompass about 6.1 acres. About 4.3
acres would be used as temporary work space, pipe storage, construction
offices, and similar use. The remaining 2.8 acres of the Plant Site
consists of an existing facilities area which would not be disturbed by
Whitetail's proposed construction, though it could be used for
operational purposes. Once the project is completed, Whitetail would
construct a permanent security fence around the Plant Site.
    The proposed East Well Pad Site is about 1 mile southeast of the
Plant Site and at the eastern terminus of the proposed Field Line
Corridor pipeline. This site would encompass about 5 acres for
construction of injection/withdrawal and saltwater disposal wells, a
pig launcher/receiver, and ancillary facilities related to the wells
and pipeline.

The EA Process

    We \2\ are preparing this EA to comply with the National
Environmental Policy Act (NEPA) which requires the Commission to take
into account the environmental impact that could result if it
authorizes Whitetail's proposal. By this notice, we are also asking
Federal, state, and local agencies with jurisdiction and/or special
expertise with respect to environmental issues to formally cooperate
with us in the preparation of the EA. Agencies that would like to
request cooperating status should follow the instructions for filing
comments provided below.
---------------------------------------------------------------------------

    \2\ ``We,'' ``us,'' and ``our'' refer to the environmental staff
of the FERC's Office of Energy Projects.
---------------------------------------------------------------------------

    NEPA also requires the FERC to discover and address concerns the
public may have about proposals. This process is referred to as
``scoping.'' The main goal of the scoping process is to focus the
analysis in the EA on the important environmental issues. By this
Notice of Intent, we are requesting public comments on the scope of the
issues to address in the EA. All comments received will be considered
during the preparation of the EA.
    The EA will discuss impacts that could occur as a result of the
construction and operation of the proposed project under these general
headings:
     Geology and soils.
     Water resources and wetlands.
     Land use.
     Socioeconomics.
     Cultural resources.
     Vegetation and wildlife (including sensitive species).
     Air quality and noise.
    Our independent analysis of the issues will be in the EA. Depending
on the comments received during the scoping process, the EA may be
published and mailed to federal, state, and local agencies, public
interest groups, interested individuals, affected landowners,
newspapers, libraries, and the Commission's official service list for
this proceeding. A comment period will be allotted for review if the EA
is published. We will consider all comments on the EA before we make
our recommendations to the Commission.
    To ensure your comments are considered, please carefully follow the
instructions in the public participation section below.

Public Participation

    You can make a difference by providing us with your specific
comments or concerns about the project. By becoming a commentor, your
concerns will be addressed in the EA and considered by the Commission.
You should focus on the potential environmental effects of the
proposal, alternatives to the proposal, and measures to avoid or lessen
environmental impact. The more specific your comments, the more useful
they will be. Please carefully follow these instructions to ensure that
your comments are received in time and properly recorded:
     Send an original and two copies of your letter to:
Kimberley D. Bose, Secretary, Federal Energy Regulatory Commission, 888
First St., NE; Room 1A, Washington, DC 20426.
     Label one copy of the comments for the attention of Gas
Branch 1.
     Reference Docket No. CP08-46-000.
     Mail your comments so that they will be received in
Washington, DC on or before February 25, 2008.
    The Commission encourages electronic filing of comments. See 18
Code of Federal Regulations 385.2001(a)(1)(iii) and the instructions on
the Commission's Internet Web site at http://www.ferc.gov under the

``eFiling'' link and the link to the User's Guide. Prepare your
submission in the same manner as you would if filing on paper and save
it to a file on your hard drive. Before you can file comments you will
need to create an account by clicking on ``Login to File'' and then
``New User Account.'' You will be asked to select the type of filing
you are making. This filing is considered a ``Comment on Filing.''
    We may mail the EA for comment. If you are interested in receiving
it, please return the Information Request (Appendix 3). If you do not
return the Information Request, you will be taken off the mailing list.

Becoming an Intervenor

    In addition to involvement in the EA scoping process, you may want
to become an official party to the proceeding known as an
``intervenor.'' Intervenors play a more formal role in the process.
Among other things, intervenors have the right to receive copies of
case-related Commission documents and filings by other intervenors.
Likewise, each intervenor must send one electronic copy (using the
Commission's eFiling system) or 14 paper copies of its filings to the
Secretary of the Commission and must send a copy of its filings to all
other parties on the Commission's service list for this proceeding. If
you want to become an intervenor you must file a motion to intervene
according to Rule 214 of the Commission's Rules of Practice and
Procedure (18 CFR 385.214) (see Appendix 2).\3\ Only intervenors have
the right to seek rehearing of the Commission's decision.
---------------------------------------------------------------------------

    \3\ Interventions may also be filed electronically via the
Internet in lieu of paper. See the previous discussion on filing
comments electronically.
---------------------------------------------------------------------------

    Affected landowners and parties with environmental concerns may be
granted intervenor status upon showing good cause by stating that they
have a clear and direct interest in this proceeding which would not be
adequately represented by any other parties. You do not need intervenor
status to have your environmental comments considered.

Additional Information

    Additional information about the project is available from the
Commission's Office of External Affairs, at 1-866-208-FERC or on the
FERC Internet Web site (http://www.ferc.gov) using the ``eLibrary''

link. Click on the eLibrary link, click on ``General Search'' and enter
the docket number excluding the last three digits in the Docket Number
field. Be sure you have selected an appropriate date range. For
assistance, please contact FERC Online Support at
<EMAIL_ADDRESS>or toll free at 1-866-208-3676, or for TTY,

contact<PHONE_NUMBER>. The eLibrary link also provides access to the
texts of formal documents issued by the Commission, such as orders,
notices, and rulemakings.
    In addition, the Commission now offers a free service called
eSubscription which allows you to keep track of all formal issuances
and submittals in specific dockets. This can reduce the amount of time
you spend researching proceedings by automatically providing you with
notification of these filings, document summaries and direct links to
the documents. Go to http://www.ferc.gov/esubscribenow.htm.

    Finally, public meetings or site visits will be posted on the
Commission's calendar located at http://www.ferc.gov/EventCalendar/EventsList.aspx
 along with other related information. You can also

request additional information by calling Whitetail at<PHONE_NUMBER>.

Kimberley D. Bose,
Secretary.
 [FR Doc. E8-1590 Filed 1-29-08; 8:45 am]

BILLING CODE 6717-01-P


 MEMORANDUM

DATE:09/10/2014 FROM: 		Laura Farris/EPA Region 8 TO:CLEAN Power Plan for Existing Power Plants; Docket Id: OAR - 2013-0602 SUBJECT:	National Park Service Call on 111d on 09/10/2014

SUMMARY:         EPA participated in a conference call with representatives from the National Park Service, the Fish and Wildlife Service, and the National Forest Service on 09/10/2014 to discuss their questions about the Clean Power Plan for Existing Power Plants, which was proposed on June 2, 2014.

ATTENDEES:

EPA Headquarters Jan Cortelyou David Solomon Tom Powers Brian Fisher Gabrielle Stevens

EPA Region 8 Laura Farris

External Stakeholders Pat Brewer and Don Shepard, National Park Service  Meredith Bond, Fish and Wildlife Service Chuck Sams, National Forest Service

National Park Service 111d Discussion Questions    *    Concerns about 111d triggering PSD if the states re-dispatch to NGCC units    *    Concerns that carbon offsets were not allowed in the proposed rule    *    Concerns about NSR and criteria air pollutants


NMIM and MOVES Runs for RFS2 Air Quality Modeling: Memorandum

Harvey Michaels, OTAQ

January 12, 2010

The models and scripts used to run and process NMIM and MOVES for the
RFS2 FRM air quality modeling have been docketed on a DVD entitled
“NMIM and MOVES Runs for RFS2 Air Quality Modeling: DVD.”  This memo
describes the contents of the DVD and provides an overview of how these
models were used to generate the onroad and nonroad downstream
inventories.

Memorandum (this document)

Title: “NMIM and MOVES Runs for RFS2 Air Quality Modeling:
Memorandum”

Filename: RFS2_NMIM_MOVES_AQM.pdf

DVD

Title: “NMIM and MOVES Runs for RFS2 Air Quality Modeling: DVD”,
written on the physical DVD.

Volume Label:  RFS2 NMIM MOVES AQM

This memo is not on the DVD.

Contents of the DVD

MOVES folder

Batch Files_20090206 folder contains the batch files that execute the
MOVES runs.  Batch files are key to understanding the MOVES runs,
because they control the runs and specify the location and use of all
files.

HCSpeciation_new_Code folder contains MySQL scripts that are part of the
MOVES code.  The batch files copy these scripts into the MOVES code as a
way of making last minute corrections to the code.

MOVESGHGSource20080909 folder is the MOVES code.

The batch files modify the code by copying some MySQL scripts into it.
This modification does not require recompilation.

RunSpecs folder contains the RunSpecs referenced in the batch files that
control the MOVES runs.

MOVESDB20080828.zip contains the MOVES default database.

Input folder contains the user-supplied databases that are referenced in
the RunSpecs and modify the MOVES default database

Perl Scripts folder contains a few scripts used to process MOVES output.

NMIM

BatchFilesAndRunSpecs folder contains NMIM batch files and RunSpecs.
Batch files are key to understanding the NMIM runs, because they control
the runs and specify the location and use of all files.

NMIM20071009 folder is the NMIM code.

NCD20080727.zip is the zipped NMIM County Database

M6203CHC contains compiled MOBILE6 executable (M6203ChcOxFixNMIM.exe)
and external datafiles that NMIM used to run MOBILE6.

NR05d-Bond-Final.zip is the version of the NONROAD Model used to
generate these inventories.

Scripts folder contains Perl and MySQL scripts that prepare,
post-process, and generate diagnostics for the NMIM runs.

ProcessingScripts folder contains the scripts that post-processed NMIM
and MOVES output into the RFS2 FRM AQM Inventories.  An annotated list
of scripts is in rp.bat.

Description of the inventory production process

The MOVES runs produced emission factors at the state-month level for
all onroad gasoline vehicles except motorcycles.  Onroad gasoline
inventories were generated by multiplying MOVES emission factors by VMT
developed for the Office of Air Quality Planning and Standards's 2002
Version 3 Modeling Platform and used in the recently published
Locomotive-Marine Rule.

MOVES was used for onroad gasoline emission factors because of
significant improvements compared with MOBILE6.  Because of difficulty
with MOVES VMT allocation, MOVES was used as a emission factor model and
NMIM VMT was applied at the state-month-SCC level. Because of
performance limitations of MOVES, there was only time to run it at the
state-month level.  State inventories were allocated to the county-month
level based on NMIM’s MOBILE6 runs.  Despite the limitations of these
methods, it was EPA’s judgment that they provided superior inventories
to MOBILE6.

Both MOBILE6 and NONROAD were run using NMIM (version NMIM20071009) with
NMIM County Database NCD20080724.  NMIM supplied emissions from the
NONROAD Model and from onroad sources not produced from MOVES. The
MOBILE6 Model was M6203ChcOxFixNMIM, a special version that  includes
cold-start VOC and the cold-start controls of the Mobile Source Air
Toxics Rule that go into effect in 2011. The NONROAD Model version was
NR05d-Bond-Final, which is the same as the publically released version
NONROAD2008.

Onroad emissions generated at the state-month level from MOVES were
distributed to the county-month level using the results from MOBILE6 as
run by NMIM.

For both NMIM and MOVES, temperatures and humidity were those of the air
quality modeling base year 2005, and fuels for each case were those
developed for this rule.

For the EISA case, E10 and E85 inventories were weighted together at the
state level based on the energy consumed by these two fuels.

Onroad gasoline PM was run by MOVES at 72F and adjusted by OAQPS at the
grid-hour level based on temperature curves supplied by OTAQ..

For some fuel-process combinations, there were MOVES bugs in calculating
VOC from THC.  For these cases, VOC was generated by post-processing
from THC using fuel-specific algorithms developed by Rich Cook.  For
these cases, Rich also supplied fuel-specific algorithms to calculate
the HAPs that MOVES calculates from VOC.

  FILENAME \p  C:\Documents and Settings\hmichael\Application
Data\Microsoft\Templates\Normal.dot 	  PAGE  1

 See http://www.epa.gov/ttn/chief/emch/index.html.

 Final Rule: Control of Emissions of Air Pollution from Locomotives and
Marine Compression-Ignition Engines Less Than 30 Liters per Cylinder
(published May 6, 2008 and republished June 30, 2008).  For details, see
http://www.epa.gov/otaq/locomotives.htm#2008final


[Federal Register: November 9, 2009 (Volume 74, Number 215)]
[Notices]
[Page 57730-57732]
[DOCID:fr09no09-99]

-----------------------------------------------------------------------

SECURITIES AND EXCHANGE COMMISSION

[Release No. 34-60911; File No. SR-NYSE-2009-109]

Self-Regulatory Organizations; Notice of Filing and Immediate
Effectiveness of Proposed Rule Change by New York Stock Exchange LLC To
Extend the Pilot Program in Relation to Certain of Its Continued
Listing Standards

November 2, 2009.

    Pursuant to Section 19(b)(1) \1\ of the Securities Exchange Act of
1934 (the ``Exchange Act''),\2\ and Rule 19b-4 thereunder,\3\ notice is
hereby given that, on October 30, 2009, New York Stock Exchange LLC
(``NYSE'' or the ``Exchange'') filed with the Securities and Exchange
Commission (``Commission'') the proposed rule

change as described in Items I and II below, which items have been
prepared by the Exchange. The Exchange has designated this proposal
eligible for immediate effectiveness pursuant to Rule 19b-4(f)(6) \4\
under the Exchange Act. The Commission is publishing this notice to
solicit comments on the proposed rule change from interested persons.
---------------------------------------------------------------------------

    \1\ 15 U.S.C. 78s(b)(1).
    \2\ 15 U.S.C. 78a.
    \3\ 17 CFR 240.19b-4.
    \4\ 17 CFR 240.19b-4(f)(6).
---------------------------------------------------------------------------

I. Self-Regulatory Organization's Statement of the Terms of Substance
of the Proposed Rule Change

    The Exchange proposes to extend until February 28, 2010, the
operation of an amendment to the continued listing requirements in
Section 802.01B of the Exchange's Listed Company Manual (the
``Manual'') that is currently in effect on a pilot program basis (the
``Pilot Program''). The Exchange also proposes to remove from Section
102.01C of the Manual references to the ``Initial Listing Standard for
Companies Transferring from NYSE Arca,'' as it has ceased to be
operative.
    The text of the proposed rule change is available on the Exchange's
Web site (http://www.nyse.com), at the Exchange's Office of the
Secretary and at the Commission's Public Reference room.

II. Self-Regulatory Organization's Statement of the Purpose of, and
Statutory Basis for, the Proposed Rule Change

    In its filing with the Commission, the self-regulatory organization
included statements concerning the purpose of and basis for the
proposed rule change and discussed any comments it received on the
proposed rule change. The text of these statements may be examined at
the places specified in Item IV below. The NYSE has prepared summaries,
set forth in Sections A, B and C below, of the most significant aspects
of such statements.

A. Self-Regulatory Organization's Statement of the Purpose of, and
Statutory Basis for, the Proposed Rule Change

1. Purpose
    Prior to the adoption of the Pilot Program,\5\ Section 802.01B(I)
of the Manual provided that any company that qualified to list under
the Earnings Test set out in Section 102.01C(I) or in Section
103.01B(I) (in the case of foreign private issuers) or pursuant to the
requirements set forth under the Assets and Equity Test set forth in
Section 102.01C(IV) or the ``Initial Listing Standard for Companies
Transferring from NYSE Arca'' (the ``NYSE Arca Transfer Standard'') set
forth in Section 102.01(C)(V) was considered to be below compliance
standards if such company's average global market capitalization over a
consecutive 30 trading-day period was less than $75 million and, at the
same time, total stockholders' equity was less than $75 million. Under
the Pilot Program, companies that listed under the initial listing
standards set forth in the immediately preceding sentence are
considered to be below compliance standards if average global market
capitalization over a consecutive 30 trading-day period is less than
$50 million and, at the same time, total stockholders' equity is less
than $50 million. The Pilot Program expires by its terms on October 31,
2009, and the Exchange now proposes to extend its application for an
additional five months, until February 28, 2010.
---------------------------------------------------------------------------

    \5\ See Securities Exchange Act Release No. 59996 (May 28,
2009), 74 FR 26912 (June 4, 2009) (SR-NYSE-2009-48) (the ``Pilot
Program Notice'').
---------------------------------------------------------------------------

    For companies listed under the Earnings Test, the Pilot Program
returned continued listing requirements to those in place prior to the
adoption of the current requirements on June 9, 2005.\6\ Consequently,
prior to implementation of the Pilot Program, the Exchange had
considerable historical experience with the continued listing of
companies that had continued to trade on the Exchange with global
market capitalization and stockholders' equity each below $75 million
but greater than $50 million. In addition, the Exchange's experience
under the Pilot Program has been very positive, as none of the
companies that were [sic] deemed back in compliance as a result of the
adoption of the Pilot Program have [sic] subsequently fallen below the
standard as amended by the Pilot program as of the date of this filing.
Based on this experience, the Exchange believes that companies that
exceed the continued listing standards as amended by the Pilot Program
are suitable for continued listing on the Exchange.
---------------------------------------------------------------------------

    \6\ See Securities Exchange Act Release No. 51813 (June 9,
2005), 70 FR 35484 (June 20, 2005) (SR-NYSE-2004-20). The Assets and
Equity Test set forth in Section 102.01C(IV) and the NYSE Arca
Transfer Standard set forth in Section 102.01C(V) were adopted
subsequent to this amendment.
---------------------------------------------------------------------------

    The Exchange notes that the continued listing standards as amended
by the Pilot Program are still higher than those of any other national
securities exchange. Consequently, the Exchange believes that the Pilot
Program is consistent with the protection of investors and the public
interest and does not raise any novel regulatory issues. In addition,
the Exchange notes that the Commission stated in the Pilot Program
Notice \7\ that it believed that the continued listing standards
adopted under the Pilot Program met the requirements established in
Exchange Act Rule 3a51-1(a)(2)(ii) \8\ in that [sic] were reasonably
related to the initial listing standards set forth in paragraph
(a)(20)(i) of Exchange Act Rule 3a51-1 (the ``Penny Stock Rule'').\9\
---------------------------------------------------------------------------

    \7\ See the Pilot Program Notice at Note 5.
    \8\ 17 CFR 240.a51-1(a)(2)(ii).
    \9\ 17 CFR 240.a51-1.
---------------------------------------------------------------------------

    The NYSE Arca Transfer Standard explicitly provided for the
transfer of companies from NYSE Arca to the Exchange on or before
August 31, 2009. As that date has passed, the Exchange is deleting the
standard from Section 102.01(C) of the Manual. The reference to the
NYSE Arca Transfer Standard in Section 802.01B is retained, as it
continues to be relevant because it indicates which continued listing
standard will be applied to companies that originally listed under the
NYSE Arca Transfer Standard. A parenthetical has been added to Section
802.01B to indicate that the NYSE Arca Transfer Standard is no longer
operative.
2. Statutory Basis
    The Exchange believes that the proposed rule change is consistent
with Section 6(b) \10\ of the Exchange Act, in general, and furthers
the objectives of Section 6(b)(5) \11\ of the Exchange Act in
particular in that it is designed to promote just and equitable
principles of trade, to foster cooperation and coordination with
persons engaged in regulating, clearing, settling, processing
information with respect to, and facilitating transactions in
securities, to remove impediments to and perfect the mechanism of a
free and open market and a national market system, and, in general, to
protect investors and the public interest. The Exchange believes that
the proposed extension to the Pilot Program is consistent with the
investor protection objectives of the Exchange Act in that the
continued listing standards under the Pilot Program are set at a high
enough level that only companies that are suitable for continued
listing on the Exchange will exceed the standards. The deletion of the
NYSE Arca Transfer Standard is not a substantive change, as that
standard was not operative after August 31, 2009.
---------------------------------------------------------------------------

    \10\ 15 U.S.C. 78f(b).
    \11\ 15 U.S.C. 78f(b)(5).

---------------------------------------------------------------------------

B. Self-Regulatory Organization's Statement on Burden on Competition

    The Exchange does not believe that the proposed rule change will
impose any burden on competition that is not necessary or appropriate
in furtherance of the purposes of the Exchange Act.

C. Self-Regulatory Organization's Statement on Comments on the Proposed
Rule Change Received From Members, Participants or Others

    Written comments were neither solicited nor received.

III. Date of Effectiveness of the Proposed Rule Change and Timing for
Commission Action

    Because the foregoing proposed rule change: (1) Does not
significantly affect the protection of investors or the public
interest; (2) does not impose any significant burden on competition;
and (3) by its terms does not become operative for 30 days after the
date of this filing, or such shorter time as the Commission may
designate if consistent with the protection of investors and the public
interest, the proposed rule change has become effective pursuant to
Section 19(b)(3)(A) \12\ of the Act and Rule 19b-4(f)(6)
thereunder.\13\
---------------------------------------------------------------------------

    \12\ 15 U.S.C. 78s(b)(3)(A).
    \13\ 17 CFR 240.19b-4(f)(6). In addition, Rule 19b-4(f)(6)(iii)
requires a self-regulatory organization to provide the Commission
with written notice of its intent to file the proposed rule change,
along with a brief description and text of the proposed rule change,
at least five business days prior to the date of filing of the
proposed rule change, or such shorter time as designated by the
Commission. The Exchange has fulfilled this requirement.
---------------------------------------------------------------------------

    A proposed rule change filed under Rule 19b-4(f)(6) \14\ normally
may not become operative prior to 30 days after the date of filing.
However, Rule 19b-4(f)(6)(iii) \15\ permits the Commission to designate
a shorter time if such action is consistent with the protection of
investors and the public interest. The Exchange requests that the
Commission waive the 30-day operative delay, as specified in Rule 19b-
4(f)(6)(iii),\16\ which would make the rule change operative upon
filing.
---------------------------------------------------------------------------

    \14\ Id.
    \15\ 17 CFR 240.19b-4(f)(6)(iii).
    \16\ Id.
---------------------------------------------------------------------------

    The Commission believes that waiving the 30-day operative delay is
consistent with the protection of investors and the public interest
because such waiver will allow the current Pilot Program to continue
without interruption. The Commission notes that the standards under the
Pilot Program are identical, for those companies qualifying under the
Earnings Test, to those in effect on the Exchange prior to the adoption
of the current standards in 2005.\17\ The NYSE represents that the
continued listing standards proposed under the Pilot Program are higher
than similar standards currently in place on other exchanges. In
addition, the Commission notes that the pilot period will allow the
NYSE and the Commission to continue to assess the new continued listing
standards. Finally, the Commission notes that the deletion of the NYSE
Arca Transfer Standard from Section 102.01C is not a substantive
change, as that standard is no longer operative. For these reasons, the
Commission designates the proposed rule change operative upon
filing.\18\
---------------------------------------------------------------------------

    \17\ See Securities Exchange Act Release No. 51813 (June 9,
2005), 70 FR 35484 (June 20, 2005) (SR-NYSE-2004-20).
    \18\ For purposes only of waiving the operative delay for this
proposal, the Commission has considered the proposed rule's impact
on efficiency, competition, and capital formation. See 15 U.S.C.
78c(f).
---------------------------------------------------------------------------

    At any time within 60 days of the filing of such proposed rule
change, the Commission may summarily abrogate such rule change if it
appears to the Commission that such action is necessary or appropriate
in the public interest, for the protection of investors, or otherwise
in furtherance of the purposes of the Act.

IV. Solicitation of Comments

    Interested persons are invited to submit written data, views and
arguments concerning the foregoing, including whether the proposed rule
change is consistent with the Exchange Act. Comments may be submitted
by any of the following methods:

Electronic Comments

     Use the Commission's Internet comment form (http://
www.sec.gov/rules/sro.shtml); or
     Send an e-mail to<EMAIL_ADDRESS>Please include
File Number SR-NYSE-2009-109 on the subject line.

Paper Comments

     Send paper comments in triplicate to Secretary, Securities
and Exchange Commission, 100 F Street, NE., Washington, DC 20549-1090.

All submissions should refer to File Number SR-NYSE-2009-109. This file
number should be included on the subject line if e-mail is used. To
help the Commission process and review your comments more efficiently,
please use only one method. The Commission will post all comments on
the Commission's Internet Web site (http://www.sec.gov/rules/
sro.shtml). Copies of the submission, all subsequent amendments, all
written statements with respect to the proposed rule change that are
filed with the Commission, and all written communications relating to
the proposed rule change between the Commission and any person, other
than those that may be withheld from the public in accordance with the
provisions of 5 U.S.C. 552, will be available for inspection and
copying in the Commission's Public Reference Room, on official business
days between the hours of 10 a.m. and 3 p.m. Copies of the filing also
will be available for inspection and copying at the principal office of
the Exchange. All comments received will be posted without change; the
Commission does not edit personal identifying information from
submissions. You should submit only information that you wish to make
available publicly. All submissions should refer to File Number SR-
NYSE-2009-109 and should be submitted on or before November 30, 2009.

    For the Commission, by the Division of Trading and Markets,
pursuant to delegated authority.\19\
---------------------------------------------------------------------------

    \19\ 17 CFR 200.30-3(a)(12).
---------------------------------------------------------------------------

Florence E. Harmon,
Deputy Secretary.
[FR Doc. E9-26877 Filed 11-6-09; 8:45 am]

BILLING CODE 8011-01-P


[Federal Register Volume 79, Number 105 (Monday, June 2, 2014)]
[Notices]
[Page 31403]
[FR Doc No: 2014-12623]

-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

Federal Railroad Administration

[Docket Number FRA-2014-0013]

Petition for Waiver of Compliance

    In accordance with Part 211 of Title 49 Code of Federal Regulations
(CFR), this document provides the public notice that by a document
dated June 6, 2013, Montana Rail Link (MRL) petitioned the Federal
Railroad Administration (FRA) for a waiver of compliance from certain
provisions of the Federal railroad safety regulations contained at 49
CFR Part 232, Brake System Safety Standards for Freight and Other Non-
Passenger Trains and Equipment; End-of-Train Devices. FRA assigned the
petition Docket Number FRA-2014-0013.
    MRL seeks a waiver of compliance from 49 CFR 232.219, Double
heading and helper service. This section states that ``a Class III
brake test pursuant to [Section] 232.211 shall be made to ensure that
the brakes are operative from the automatic brake valve of the
locomotive taking control of the train.'' MRL petitions FRA for a
modified Class 3 brake test for the use of the Helper-Link[supreg]
equipped helper locomotive when pushing trains with one or more
distributed power (DP) locomotives on the rear of the train. Most of
MRL's traffic is bridge traffic for BNSF Railway (BNSF), which uses a
waiver for Helper-Link[supreg] (Docket Number FRA-2006-26435). MRL
seeks the use of identical conditions to BNSF's relief for its
operation of Helper-Link[supreg]-equipped trains. MRL's evaluation of
benefits includes increased safety due to the reduced need for train
service employees to couple and uncouple from trains twice for each
train assisted and operational benefits by reducing turnaround time for
helper consists, improving velocity and increasing fuel savings.
    A copy of the petition, as well as any written communications
concerning the petition, is available for review online at
www.regulations.gov and in person at the U.S. Department of
Transportation's (DOT) Docket Operations Facility, 1200 New Jersey
Avenue SE., W12-140, Washington, DC 20590. The Docket Operations
Facility is open from 9 a.m. to 5 p.m., Monday through Friday, except
Federal Holidays.
    Interested parties are invited to participate in these proceedings
by submitting written views, data, or comments. FRA does not anticipate
scheduling a public hearing in connection with these proceedings since
the facts do not appear to warrant a hearing. If any interested party
desires an opportunity for oral comment, they should notify FRA, in
writing, before the end of the comment period and specify the basis for
their request.
    All communications concerning these proceedings should identify the
appropriate docket number and may be submitted by any of the following
methods:
     Web site: http://www.regulations.gov. Follow the online
instructions for submitting comments.
     Fax:<PHONE_NUMBER>.
     Mail: Docket Operations Facility, U.S. Department of
Transportation, 1200 New Jersey Avenue SE., W12-140, Washington, DC
20590.
     Hand Delivery: 1200 New Jersey Avenue SE., Room W12-140,
Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday,
except Federal Holidays.
    Communications received by July 17, 2014 will be considered by FRA
before final action is taken. Comments received after that date will be
considered as far as practicable.
    Anyone is able to search the electronic form of any written
communications and comments received into any of our dockets by the
name of the individual submitting the comment (or signing the document,
if submitted on behalf of an association, business, labor union, etc.).
See http://www.regulations.gov/#!privacyNotice for the privacy notice
of regulations.gov or interested parties may review DOT's complete
Privacy Act Statement in the Federal Register published on April 11,
2000 (65 FR 19477).

    Issued in Washington, DC, on May 27, 2014.
Robert C. Lauby,
Associate Administrator for Railroad Safety, Chief Safety Officer.
[FR Doc. 2014-12623 Filed 5-30-14; 8:45 am]
BILLING CODE 4910-06-P


    ----- Original Message -----

    From: Robert Meyers

    Sent: 06/20/2007 10:40 PM

    To: Lydia Wegman

    Subject: record

----- Forwarded by Robert Meyers/DC/USEPA/US on 06/20/2007 10:40 PM -----

Robert Meyers/DC/USEPA/US

06/20/2007 05:14 PM

To

"Farrell, Amy L."<EMAIL_ADDRESS> cc

"Fraas, Arthur G."<EMAIL_ADDRESS> Subject

Re: where are we on the language?

we are putting together a file so we can have the text inserted in the preamble at the right place.  I have run through the changes here and we will have some edits which we can talk about when you recieve.  but it seemed appropriate to not just focus on separate text, but also its placement in the preamble.

"Farrell, Amy L."<EMAIL_ADDRESS> 06/20/2007 05:11 PM

To

Robert Meyers/DC/USEPA/US@EPA

cc

"Fraas, Arthur G."<EMAIL_ADDRESS> Subject

where are we on the language?


# Jessica Balukas, ICF, September 2021
# Script to process ORM data (2010-2019), calculate section 404 impacts with mitigation requirements and single-water permit counts for Rapanos, NWPR, and the change
# NOTE: TO ADJUST FOR DIFFERENT EMPLOYEE ID/FOLDER SYNCING, UPDATE CODE SIGNIFIED WITH #*# (search for combo to get all occurrences)
# NOTE: File paths assume syncing of entire WOTUS Reconsideration general folder

# Install Packages
install.packages("tidyverse")
install.packages("stringr")

# Load Packages
#library(tidyverse)
#library(stringr)

# Folder locations
var <- "40179" #*#
IN_DIR <- (paste0("C:/Users/",var,"/ICF/WOTUS Reconsideration - General/ORM Data Processing/Inputs")) #*#
OUT_DIR <- (paste0("C:/Users/",var,"/ICF/WOTUS Reconsideration - General/ORM Data Processing/Outputs")) #*#
QA_DIR <- (paste0("C:/Users/",var,"/ICF/WOTUS Reconsideration - General/ORM Data Processing/Outputs/QA")) #*#

# Read input files
ORM_Dataset <- read.csv(file.path(IN_DIR,"ORM_Data_2010-2019_ReducedFields.csv"))
CWR_Filter <- read.csv(file.path(IN_DIR,"filter_for_CWR_ICF_Edits.csv"))
Perc_Permitted_Waters <- read.csv(file.path(IN_DIR,"Perc_Permitted_Waters.csv"))
HUC12 <- read.delim(file.path(IN_DIR,"ORMPermit_Georef_0907.txt"))
HUC12_AK <- read.delim(file.path(IN_DIR,"ORMPermit_AK_Georef_0907.txt"))
Prop_10YrPeriod_NonCWR <- read.csv(file.path(IN_DIR,"Proportion10YrPeriod_NonCWR.csv"))

# QA - HUC12 obs. lower than ORM_Dataset obs.
HUC12_ID <- HUC12[c("PERMIT_ID")]
HUC12_ID$HUC12_Flag <- 1
ID_test <- merge(x=ORM_Dataset,y=HUC12_ID,by="PERMIT_ID",all.x=TRUE)
ID_test_QA <- ID_test[is.na(ID_test$HUC12_Flag), ]
write.csv(ID_test_QA,paste(QA_DIR,"HUC12_MissingIDs.csv",sep="/"),row.names=FALSE)
rm(list = c('HUC12_ID','ID_test','ID_test_QA'))

# Ensure that HUC12 values are always 12 digits (add leading zeros when necessary), add HUC4 variable
names(HUC12)[names(HUC12) == "WBD_HUC12"] <- "HUC12_Main"
HUC12$HUC12 <- str_pad(HUC12$HUC12_Main,12, pad = "0")
HUC12$HUC4 <- substr(HUC12$HUC12,start=1,stop=4)

# Convert HUC12 and HUC4 variables to character
HUC12$HUC12 <- as.character(HUC12$HUC12)
HUC12$HUC4 <- as.character(HUC12$HUC4)

# Merge HUC12 to ORM_Dataset
HUC12 <- HUC12[c("PERMIT_ID", "HUC12", "HUC4", "STUSPS")]
ORM_Dataset_Final <- merge(x=ORM_Dataset,y=HUC12,by="PERMIT_ID",all.x=TRUE)

# Create combined STATE variable (prioritize spatial state, then STATE_AR, then STATE)
ORM_Dataset_Final$STATE_FINAL <- ifelse(ORM_Dataset_Final$STUSPS=='' | is.na(ORM_Dataset_Final$STUSPS),ORM_Dataset_Final$STATE_AR,ORM_Dataset_Final$STUSPS)
ORM_Dataset_Final$STATE_FINAL <- ifelse(ORM_Dataset_Final$STATE_FINAL=='' | is.na(ORM_Dataset_Final$STATE_FINAL),ORM_Dataset_Final$STATE,ORM_Dataset_Final$STATE_FINAL)

# Check for remaining missing values in STATE_FINAL variable
STATE_QA  <- ORM_Dataset_Final[ which(ORM_Dataset_Final$STATE_FINAL ==''), ]
write.csv(STATE_QA,paste(QA_DIR,"STATE_MISSING.csv",sep="/"),row.names=FALSE)

# Merge HUC12_AK to ORM_Dataset_Final, replace HUC12 with AK value if STATE_FINAL=AK (Alaska HUC12 merge processed separately)
names(HUC12_AK)[names(HUC12_AK) == "WBD_HUC12"] <- "HUC12_AK"
HUC12_AK$HUC12_AK <- str_pad(HUC12_AK$HUC12_AK,12, pad = "0")
HUC12_AK$HUC4_AK <- substr(HUC12_AK$HUC12_AK,start=1,stop=4)
HUC12_AK$HUC12_AK <- as.character(HUC12_AK$HUC12_AK)
HUC12_AK$HUC4_AK <- as.character(HUC12_AK$HUC4_AK)
HUC12_AK <- HUC12_AK[c("PERMIT_ID", "HUC12_AK","HUC4_AK")]
ORM_Dataset_Final <- merge(x=ORM_Dataset_Final,y=HUC12_AK,by="PERMIT_ID",all.x=TRUE)
ORM_Dataset_Final$HUC12 <- ifelse(ORM_Dataset_Final$STATE_FINAL=='AK',ORM_Dataset_Final$HUC12_AK,ORM_Dataset_Final$HUC12)
ORM_Dataset_Final$HUC4 <- ifelse(ORM_Dataset_Final$STATE_FINAL=='AK',ORM_Dataset_Final$HUC4_AK,ORM_Dataset_Final$HUC4)

# QA - obs. with missing HUC12
HUC12_QA <- ORM_Dataset_Final[is.na(ORM_Dataset_Final$HUC12), ]
write.csv(HUC12_QA,paste(QA_DIR,"HUC12_MissingValue.csv",sep="/"),row.names=FALSE)
ORM_Dataset_Final[ ,c('HUC12_AK', 'HUC4_AK')] <- list(NULL)

### Merge remaining datasets to ORM_Dataset
# CWR Filter (to remove permits issued under Clean Water Rule Guidance)
CWR_Filter$State_Date <- paste(CWR_Filter$state,"_",CWR_Filter$END_DATE)
CWR_Filter <- CWR_Filter[c("State_Date","CWR")]
ORM_Dataset_Final$State_Date <- paste(ORM_Dataset_Final$STATE_FINAL,"_",ORM_Dataset_Final$END_DATE)
ORM_Dataset_Final <- merge(x=ORM_Dataset_Final,y=CWR_Filter,by="State_Date",all.x=TRUE)

# Check CWR Filter Merge
#write.csv(ORM_Dataset_Final,paste(QA_DIR,"CWR_Filter_Merge.csv",sep="/"),row.names=FALSE)
ORM_Dataset_Final$State_Date <- NULL

# Perc_Permitted_Waters (jurisdictional determination corrections)
ORM_Dataset_Final <- merge(x=ORM_Dataset_Final,y=Perc_Permitted_Waters,by="COWARDIN_FINAL",all.x=TRUE)
#write.csv(ORM_Dataset_Final,paste(QA_DIR,"Perc_Permitted_Waters_Merge.csv",sep="/"),row.names=FALSE)

# Prop_10YrPeriod_NonCWR
ORM_Dataset_Final <- merge(x=ORM_Dataset_Final,y=Prop_10YrPeriod_NonCWR,by="STATE_FINAL",all.x=TRUE)
#write.csv(ORM_Dataset_Final,paste(QA_DIR,"Prop_10YrPeriod_NonCWR_Merge.csv",sep="/"),row.names=FALSE)

# Drop intermediate datasets
rm(list = c('ORM_Dataset','CWR_Filter','Perc_Permitted_Waters','HUC12','HUC12_AK','HUC12_QA','Prop_10YrPeriod_NonCWR','STATE_QA'))

# Remove CWR permits and projects with a primarily mitigation-based purpose from analysis
ORM_Dataset_Final_NoCWR  <- ORM_Dataset_Final[ which(ORM_Dataset_Final$CWR==0), ]
ORM_Dataset_Final_NoCWRNoMit  <- ORM_Dataset_Final_NoCWR[ which(ORM_Dataset_Final_NoCWR$NonMitigation_Work_Type==1), ]

# Create binary variable to indicate permit type (1=individual permt, 0=general permit)
ORM_Dataset_Final_NoCWRNoMit %>% count(ACTION_TYPE)
ORM_Dataset_Final_NoCWRNoMit$Ind_Permit <- ifelse(ORM_Dataset_Final_NoCWRNoMit$ACTION_TYPE=='LOP',1,
                                           ifelse(ORM_Dataset_Final_NoCWRNoMit$ACTION_TYPE=='SP',1,0))

# Create binary variables to indicate single water permits (1=single water affected, 0=multiple waters affected)
PermitID_Count <- ORM_Dataset_Final_NoCWRNoMit %>% count(PERMIT_ID2)
ORM_Dataset_Final_NoCWRNoMit <- merge(x=ORM_Dataset_Final_NoCWRNoMit,y=PermitID_Count,by="PERMIT_ID2",all.x=TRUE)
rm(list = c('ORM_Dataset_Final','ORM_Dataset_Final_NoCWR','PermitID_Count'))
ORM_Dataset_Final_NoCWRNoMit$SingleWater <- ifelse(ORM_Dataset_Final_NoCWRNoMit$n>1,0,1)
ORM_Dataset_Final_NoCWRNoMit$n <- NULL

# Create SI, SG, MI, MG binary variables (described on EPA's technical direction)
ORM_Dataset_Final_NoCWRNoMit$SI <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Ind_Permit==1 & ORM_Dataset_Final_NoCWRNoMit$SingleWater==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$SG <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Ind_Permit==0 & ORM_Dataset_Final_NoCWRNoMit$SingleWater==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$MI <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Ind_Permit==1 & ORM_Dataset_Final_NoCWRNoMit$SingleWater==0,1,0)
ORM_Dataset_Final_NoCWRNoMit$MG <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Ind_Permit==0 & ORM_Dataset_Final_NoCWRNoMit$SingleWater==0,1,0)

# Calculate SI, SG, MI, MG percentages by HUC4/COWARDIN_FINAL (divide by # affected waters)
# Determine unique number of permits by HUC4/COWARDIN_FINAL for later permit analysis
count_SI_SG_MI_MG <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC4,COWARDIN_FINAL) %>%
  summarise(Permit_Count = n_distinct(PERMIT_ID2),
            Waters_Count = n(),
            SI_Count = sum(SI),
            SG_Count = sum(SG),
            MI_Count = sum(MI),
            MG_Count = sum(MG)) %>%
  mutate(SI_Perc = SI_Count/Waters_Count,
         SG_Perc = SG_Count/Waters_Count,
         MI_Perc = MI_Count/Waters_Count,
         MG_Perc = MG_Count/Waters_Count)
count_SI_SG_MI_MG$HUC4_COWARDIN <- paste(count_SI_SG_MI_MG$HUC4,"_",count_SI_SG_MI_MG$COWARDIN_FINAL)

count_SI_SG_MI_MG_2 <- count_SI_SG_MI_MG[c("HUC4_COWARDIN","Permit_Count","SI_Perc","SG_Perc","MI_Perc","MG_Perc")]

# Merge SI, SG, MI, MG percentages with ORM_Dataset_Final_NoCWRNoMit dataset
ORM_Dataset_Final_NoCWRNoMit$HUC4_COWARDIN <- paste(ORM_Dataset_Final_NoCWRNoMit$HUC4,"_",ORM_Dataset_Final_NoCWRNoMit$COWARDIN_FINAL)
ORM_Dataset_Final_NoCWRNoMit <- merge(x=ORM_Dataset_Final_NoCWRNoMit,y=count_SI_SG_MI_MG_2,by="HUC4_COWARDIN",all.x=TRUE)
rm(list = c('count_SI_SG_MI_MG','count_SI_SG_MI_MG_2'))

# Create dummy variable for mitigation (1=mitigation required, 0=mitigation NOT required)
ORM_Dataset_Final_NoCWRNoMit$MitReq <- ifelse(ORM_Dataset_Final_NoCWRNoMit$MITIGATION_TYPES!='',1,0)

# Create dummy variables for permanent and temporary impacts (1=has impacts, 0=no impacts)
ORM_Dataset_Final_NoCWRNoMit$Perm_Impact <- ifelse(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM>0 | ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM>0,1,0)
ORM_Dataset_Final_NoCWRNoMit$Temp_Impact <- ifelse(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP>0 | ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP>0,1,0)
ORM_Dataset_Final_NoCWRNoMit$PermTemp_Impact <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Perm_Impact==1 | ORM_Dataset_Final_NoCWRNoMit$Temp_Impact==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$Perm_Impact <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$Perm_Impact),0,ORM_Dataset_Final_NoCWRNoMit$Perm_Impact)
ORM_Dataset_Final_NoCWRNoMit$Temp_Impact <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$Temp_Impact),0,ORM_Dataset_Final_NoCWRNoMit$Temp_Impact)
ORM_Dataset_Final_NoCWRNoMit$PermTemp_Impact <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$PermTemp_Impact),0,ORM_Dataset_Final_NoCWRNoMit$PermTemp_Impact)
#write.csv(ORM_Dataset_Final_NoCWRNoMit,paste(QA_DIR,"PermTempImpactDummies.csv",sep="/"),row.names=FALSE)

# Create PM, TM, PN, TN binary variables (described on EPA's technical direction)
ORM_Dataset_Final_NoCWRNoMit$PM <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Perm_Impact==1 & ORM_Dataset_Final_NoCWRNoMit$MitReq==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$TM <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Temp_Impact==1 & ORM_Dataset_Final_NoCWRNoMit$MitReq==1,1,0)
ORM_Dataset_Final_NoCWRNoMit$PN <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Perm_Impact==1 & ORM_Dataset_Final_NoCWRNoMit$MitReq==0,1,0)
ORM_Dataset_Final_NoCWRNoMit$TN <- ifelse(ORM_Dataset_Final_NoCWRNoMit$Temp_Impact==1 & ORM_Dataset_Final_NoCWRNoMit$MitReq==0,1,0)
#write.csv(ORM_Dataset_Final_NoCWRNoMit,paste(QA_DIR,"PM_TM_PN_TN.csv",sep="/"),row.names=FALSE)

# Calculate PM, TM, PN, TN percentages by HUC4/COWARDIN_FINAL (divide by # affected waters)
count_PM_TM_PN_TN <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC4,COWARDIN_FINAL) %>%
  summarise(Waters_Count = n(),
            PM_Count = sum(PM),
            TM_Count = sum(TM),
            PN_Count = sum(PN),
            TN_Count = sum(TN)) %>%
  mutate(PM_Perc = PM_Count/Waters_Count,
         TM_Perc = TM_Count/Waters_Count,
         PN_Perc = PN_Count/Waters_Count,
         TN_Perc = TN_Count/Waters_Count)
count_PM_TM_PN_TN$HUC4_COWARDIN <- paste(count_PM_TM_PN_TN$HUC4,"_",count_PM_TM_PN_TN$COWARDIN_FINAL)

count_PM_TM_PN_TN_2 <- count_PM_TM_PN_TN[c("HUC4_COWARDIN","Waters_Count","PM_Perc","TM_Perc","PN_Perc","TN_Perc")]

# Merge PM, TM, PN, TN percentages with ORM_Dataset_Final_NoCWRNoMit dataset
ORM_Dataset_Final_NoCWRNoMit <- merge(x=ORM_Dataset_Final_NoCWRNoMit,y=count_PM_TM_PN_TN_2,by="HUC4_COWARDIN",all.x=TRUE)
rm(list = c('count_PM_TM_PN_TN','count_PM_TM_PN_TN_2'))

# Convert LF (permanent & temporary) to acres, using average buffer width of 50 ft. (25 ft. on each side of the stream)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV <- ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM*50*0.0000229568
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV <- ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP*50*0.0000229568

# Calculate total permanent and temporary impacts (acres + LF converted to acres)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM),0,ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV),0,ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_PERM_TOTAL <- ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_PERM+ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_PERM_ACRE_CONV

ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP),0,ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV <- ifelse(is.na(ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV),0,ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV)
ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_TEMP_TOTAL <- ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_ACRES_TEMP+ORM_Dataset_Final_NoCWRNoMit$IMPACT_AUTH_LF_TEMP_ACRE_CONV

################################################################
#Calculate impacts not covered by a permit under Rapanos & NWPR
################################################################

# Remove observations with HIST1, missing COWARDIN_FINAL, or missing HUC12
ORM_Dataset_Final_NoCWRNoMit  <- ORM_Dataset_Final_NoCWRNoMit[ which(ORM_Dataset_Final_NoCWRNoMit$COWARDIN_FINAL != "HIST1"), ]
ORM_Dataset_Final_NoCWRNoMit  <- ORM_Dataset_Final_NoCWRNoMit[ which(ORM_Dataset_Final_NoCWRNoMit$COWARDIN_FINAL != ''), ]
ORM_Dataset_Final_NoCWRNoMit <- ORM_Dataset_Final_NoCWRNoMit[!(is.na(ORM_Dataset_Final_NoCWRNoMit$HUC12)), ]

# Multiply impacts by Cowardin Code-level Rapanos and NWPR adjustments (to account for impacts not covered under Rapanos vs. NWPR)
# Multiply Rapanos/NWPR-corrected impacts by HUC4/Cowardin Code mitigation percentages (PM_Perc & TM_Perc)
# Divide Rapanos/NWPR- & PM/TM-corrected impacts by proportion of 10-year period that state followed Rapanos to get annual average
# Use the same methodology to count impacted waters not covered under Rapanos vs. NWPR
ORM_Dataset_Final_NoCWRNoMit <- ORM_Dataset_Final_NoCWRNoMit %>%
  mutate(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr = (((IMPACT_AUTH_ACRES_PERM/Rapanos_Perc_Permitted)-IMPACT_AUTH_ACRES_PERM)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr = (((IMPACT_AUTH_LF_PERM_ACRE_CONV/Rapanos_Perc_Permitted)-IMPACT_AUTH_LF_PERM_ACRE_CONV)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr = (((IMPACT_AUTH_PERM_TOTAL/Rapanos_Perc_Permitted)-IMPACT_AUTH_PERM_TOTAL)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr = (((IMPACT_AUTH_ACRES_TEMP/Rapanos_Perc_Permitted)-IMPACT_AUTH_ACRES_TEMP)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr = (((IMPACT_AUTH_LF_TEMP_ACRE_CONV/Rapanos_Perc_Permitted)-IMPACT_AUTH_LF_TEMP_ACRE_CONV)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr = (((IMPACT_AUTH_TEMP_TOTAL/Rapanos_Perc_Permitted)-IMPACT_AUTH_TEMP_TOTAL)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr = (((IMPACT_AUTH_ACRES_PERM/Rapanos_Perc_Permitted)-(IMPACT_AUTH_ACRES_PERM/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr = (((IMPACT_AUTH_LF_PERM_ACRE_CONV/Rapanos_Perc_Permitted)-(IMPACT_AUTH_LF_PERM_ACRE_CONV/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr = (((IMPACT_AUTH_PERM_TOTAL/Rapanos_Perc_Permitted)-(IMPACT_AUTH_PERM_TOTAL/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*PM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr = (((IMPACT_AUTH_ACRES_TEMP/Rapanos_Perc_Permitted)-(IMPACT_AUTH_ACRES_TEMP/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr = (((IMPACT_AUTH_LF_TEMP_ACRE_CONV/Rapanos_Perc_Permitted)-(IMPACT_AUTH_LF_TEMP_ACRE_CONV/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr = (((IMPACT_AUTH_TEMP_TOTAL/Rapanos_Perc_Permitted)-(IMPACT_AUTH_TEMP_TOTAL/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)*TM_Perc)/Prop_10YrPeriod_NonCWR,
         PERM_Count_Rapanos_10Yr = ((Perm_Impact/Rapanos_Perc_Permitted)-Perm_Impact)/Prop_10YrPeriod_NonCWR,
         PERM_Count_NWPR_10Yr = ((Perm_Impact/Rapanos_Perc_Permitted)-(Perm_Impact/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)/Prop_10YrPeriod_NonCWR,
         PERM_Count_Change_10Yr = (Perm_Impact-(Perm_Impact*(NWPR_Perc_Permitted/Rapanos_Perc_Permitted)))/Prop_10YrPeriod_NonCWR,
         TEMP_Count_Rapanos_10Yr = ((Temp_Impact/Rapanos_Perc_Permitted)-Temp_Impact)/Prop_10YrPeriod_NonCWR,
         TEMP_Count_NWPR_10Yr = ((Temp_Impact/Rapanos_Perc_Permitted)-(Temp_Impact/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)/Prop_10YrPeriod_NonCWR,
         TEMP_Count_Change_10Yr = (Temp_Impact-(Temp_Impact*(NWPR_Perc_Permitted/Rapanos_Perc_Permitted)))/Prop_10YrPeriod_NonCWR,
         ImpactedWater_Count_Rapanos_10Yr = ((PermTemp_Impact/Rapanos_Perc_Permitted)-PermTemp_Impact)/Prop_10YrPeriod_NonCWR,
         ImpactedWater_Count_NWPR_10Yr = ((PermTemp_Impact/Rapanos_Perc_Permitted)-(PermTemp_Impact/Rapanos_Perc_Permitted)*NWPR_Perc_Permitted)/Prop_10YrPeriod_NonCWR,
         ImpactedWater_Count_Change_10Yr = (PermTemp_Impact-(PermTemp_Impact*(NWPR_Perc_Permitted/Rapanos_Perc_Permitted)))/Prop_10YrPeriod_NonCWR)

# Aggregate permanent & temporary impacts at the HUC12 level
Impacts_HUC12 <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC12) %>%
  summarise(PERM_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr),
            PERM_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr),
            PERM_TOTAL_Rapanos = sum(IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr),
            TEMP_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr),
            TEMP_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr),
            TEMP_TOTAL_Rapanos = sum(IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr),
            PERM_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr),
            PERM_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr),
            PERM_TOTAL_NWPR = sum(IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr),
            TEMP_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr),
            TEMP_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr),
            TEMP_TOTAL_NWPR = sum(IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr)) %>%
  mutate(PERM_ACRES_CHANGE = PERM_ACRES_Rapanos - PERM_ACRES_NWPR,
         PERM_LF_ACRE_CONV_CHANGE = PERM_LF_ACRE_CONV_Rapanos - PERM_LF_ACRE_CONV_NWPR,
         PERM_TOTAL_CHANGE = PERM_TOTAL_Rapanos - PERM_TOTAL_NWPR,
         TEMP_ACRES_CHANGE = TEMP_ACRES_Rapanos - TEMP_ACRES_NWPR,
         TEMP_LF_ACRE_CONV_CHANGE = TEMP_LF_ACRE_CONV_Rapanos - TEMP_LF_ACRE_CONV_NWPR,
         TEMP_TOTAL_CHANGE = TEMP_TOTAL_Rapanos - TEMP_TOTAL_NWPR)
write.csv(Impacts_HUC12,paste(OUT_DIR,"Impacts_By_HUC12.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the HUC4 level
Impacts_HUC4 <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC4) %>%
  summarise(PERM_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr),
            PERM_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr),
            PERM_TOTAL_Rapanos = sum(IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr),
            TEMP_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr),
            TEMP_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr),
            TEMP_TOTAL_Rapanos = sum(IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr),
            PERM_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr),
            PERM_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr),
            PERM_TOTAL_NWPR = sum(IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr),
            TEMP_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr),
            TEMP_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr),
            TEMP_TOTAL_NWPR = sum(IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr)) %>%
  mutate(PERM_ACRES_CHANGE = PERM_ACRES_Rapanos - PERM_ACRES_NWPR,
         PERM_LF_ACRE_CONV_CHANGE = PERM_LF_ACRE_CONV_Rapanos - PERM_LF_ACRE_CONV_NWPR,
         PERM_TOTAL_CHANGE = PERM_TOTAL_Rapanos - PERM_TOTAL_NWPR,
         TEMP_ACRES_CHANGE = TEMP_ACRES_Rapanos - TEMP_ACRES_NWPR,
         TEMP_LF_ACRE_CONV_CHANGE = TEMP_LF_ACRE_CONV_Rapanos - TEMP_LF_ACRE_CONV_NWPR,
         TEMP_TOTAL_CHANGE = TEMP_TOTAL_Rapanos - TEMP_TOTAL_NWPR)
write.csv(Impacts_HUC4,paste(OUT_DIR,"Impacts_By_HUC4.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the STATE_FINAL level
Impacts_STATE <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(STATE_FINAL) %>%
  summarise(PERM_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr),
            PERM_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr),
            PERM_TOTAL_Rapanos = sum(IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr),
            TEMP_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr),
            TEMP_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr),
            TEMP_TOTAL_Rapanos = sum(IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr),
            PERM_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr),
            PERM_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr),
            PERM_TOTAL_NWPR = sum(IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr),
            TEMP_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr),
            TEMP_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr),
            TEMP_TOTAL_NWPR = sum(IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr)) %>%
  mutate(PERM_ACRES_CHANGE = PERM_ACRES_Rapanos - PERM_ACRES_NWPR,
         PERM_LF_ACRE_CONV_CHANGE = PERM_LF_ACRE_CONV_Rapanos - PERM_LF_ACRE_CONV_NWPR,
         PERM_TOTAL_CHANGE = PERM_TOTAL_Rapanos - PERM_TOTAL_NWPR,
         TEMP_ACRES_CHANGE = TEMP_ACRES_Rapanos - TEMP_ACRES_NWPR,
         TEMP_LF_ACRE_CONV_CHANGE = TEMP_LF_ACRE_CONV_Rapanos - TEMP_LF_ACRE_CONV_NWPR,
         TEMP_TOTAL_CHANGE = TEMP_TOTAL_Rapanos - TEMP_TOTAL_NWPR)
write.csv(Impacts_STATE,paste(OUT_DIR,"Impacts_By_STATE.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the Cowardin Code level
Impacts_Cowardin <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(COWARDIN_FINAL) %>%
  summarise(PERM_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_PERM_PM_Rapanos_10Yr),
            PERM_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_Rapanos_10Yr),
            PERM_TOTAL_Rapanos = sum(IMPACT_AUTH_PERM_TOTAL_PM_Rapanos_10Yr),
            TEMP_ACRES_Rapanos = sum(IMPACT_AUTH_ACRES_TEMP_TM_Rapanos_10Yr),
            TEMP_LF_ACRE_CONV_Rapanos = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_Rapanos_10Yr),
            TEMP_TOTAL_Rapanos = sum(IMPACT_AUTH_TEMP_TOTAL_TM_Rapanos_10Yr),
            PERM_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_PERM_PM_NWPR_10Yr),
            PERM_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_PERM_ACRE_CONV_PM_NWPR_10Yr),
            PERM_TOTAL_NWPR = sum(IMPACT_AUTH_PERM_TOTAL_PM_NWPR_10Yr),
            TEMP_ACRES_NWPR = sum(IMPACT_AUTH_ACRES_TEMP_TM_NWPR_10Yr),
            TEMP_LF_ACRE_CONV_NWPR = sum(IMPACT_AUTH_LF_TEMP_ACRE_CONV_TM_NWPR_10Yr),
            TEMP_TOTAL_NWPR = sum(IMPACT_AUTH_TEMP_TOTAL_TM_NWPR_10Yr)) %>%
  mutate(PERM_ACRES_CHANGE = PERM_ACRES_Rapanos - PERM_ACRES_NWPR,
         PERM_LF_ACRE_CONV_CHANGE = PERM_LF_ACRE_CONV_Rapanos - PERM_LF_ACRE_CONV_NWPR,
         PERM_TOTAL_CHANGE = PERM_TOTAL_Rapanos - PERM_TOTAL_NWPR,
         TEMP_ACRES_CHANGE = TEMP_ACRES_Rapanos - TEMP_ACRES_NWPR,
         TEMP_LF_ACRE_CONV_CHANGE = TEMP_LF_ACRE_CONV_Rapanos - TEMP_LF_ACRE_CONV_NWPR,
         TEMP_TOTAL_CHANGE = TEMP_TOTAL_Rapanos - TEMP_TOTAL_NWPR)
write.csv(Impacts_Cowardin,paste(OUT_DIR,"Impacts_By_Cowardin.csv",sep="/"),row.names=FALSE)

#################################################################################
#Calculate count of impacted waters not covered by a permit under Rapanos & NWPR
#################################################################################

# Aggregate permanent & temporary impacts at the HUC12 level
ImpactedWaters_HUC12 <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC12) %>%
  summarise(Waters_Count_PERM_Rapanos = sum(PERM_Count_Rapanos_10Yr),
            Waters_Count_PERM_NWPR = sum(PERM_Count_NWPR_10Yr),
            Waters_Count_PERM_Change = sum(PERM_Count_Change_10Yr),
            Waters_Count_TEMP_Rapanos = sum(TEMP_Count_Rapanos_10Yr),
            Waters_Count_TEMP_NWPR = sum(TEMP_Count_NWPR_10Yr),
            Waters_Count_TEMP_Change = sum(TEMP_Count_Change_10Yr),
            Waters_Count_Rapanos = sum(ImpactedWater_Count_Rapanos_10Yr),
            Waters_Count_NWPR = sum(ImpactedWater_Count_NWPR_10Yr),
            Waters_Count_Change = sum(ImpactedWater_Count_Change_10Yr))
write.csv(ImpactedWaters_HUC12,paste(OUT_DIR,"ImpactedWaters_By_HUC12.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the HUC4 level
ImpactedWaters_HUC4 <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(HUC4) %>%
  summarise(Waters_Count_PERM_Rapanos = sum(PERM_Count_Rapanos_10Yr),
            Waters_Count_PERM_NWPR = sum(PERM_Count_NWPR_10Yr),
            Waters_Count_PERM_Change = sum(PERM_Count_Change_10Yr),
            Waters_Count_TEMP_Rapanos = sum(TEMP_Count_Rapanos_10Yr),
            Waters_Count_TEMP_NWPR = sum(TEMP_Count_NWPR_10Yr),
            Waters_Count_TEMP_Change = sum(TEMP_Count_Change_10Yr),
            Waters_Count_Rapanos = sum(ImpactedWater_Count_Rapanos_10Yr),
            Waters_Count_NWPR = sum(ImpactedWater_Count_NWPR_10Yr),
            Waters_Count_Change = sum(ImpactedWater_Count_Change_10Yr))
write.csv(ImpactedWaters_HUC4,paste(OUT_DIR,"ImpactedWaters_By_HUC4.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the STATE_FINAL level
ImpactedWaters_STATE <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(STATE_FINAL) %>%
  summarise(Waters_Count_PERM_Rapanos = sum(PERM_Count_Rapanos_10Yr),
            Waters_Count_PERM_NWPR = sum(PERM_Count_NWPR_10Yr),
            Waters_Count_PERM_Change = sum(PERM_Count_Change_10Yr),
            Waters_Count_TEMP_Rapanos = sum(TEMP_Count_Rapanos_10Yr),
            Waters_Count_TEMP_NWPR = sum(TEMP_Count_NWPR_10Yr),
            Waters_Count_TEMP_Change = sum(TEMP_Count_Change_10Yr),
            Waters_Count_Rapanos = sum(ImpactedWater_Count_Rapanos_10Yr),
            Waters_Count_NWPR = sum(ImpactedWater_Count_NWPR_10Yr),
            Waters_Count_Change = sum(ImpactedWater_Count_Change_10Yr))
write.csv(ImpactedWaters_STATE,paste(OUT_DIR,"ImpactedWaters_By_STATE.csv",sep="/"),row.names=FALSE)

# Aggregate permanent & temporary impacts at the Cowardin Code level
ImpactedWaters_Cowardin <- ORM_Dataset_Final_NoCWRNoMit %>%
  group_by(COWARDIN_FINAL) %>%
  summarise(Waters_Count_PERM_Rapanos = sum(PERM_Count_Rapanos_10Yr),
            Waters_Count_PERM_NWPR = sum(PERM_Count_NWPR_10Yr),
            Waters_Count_PERM_Change = sum(PERM_Count_Change_10Yr),
            Waters_Count_TEMP_Rapanos = sum(TEMP_Count_Rapanos_10Yr),
            Waters_Count_TEMP_NWPR = sum(TEMP_Count_NWPR_10Yr),
            Waters_Count_TEMP_Change = sum(TEMP_Count_Change_10Yr),
            Waters_Count_Rapanos = sum(ImpactedWater_Count_Rapanos_10Yr),
            Waters_Count_NWPR = sum(ImpactedWater_Count_NWPR_10Yr),
            Waters_Count_Change = sum(ImpactedWater_Count_Change_10Yr))
write.csv(ImpactedWaters_Cowardin,paste(OUT_DIR,"ImpactedWaters_By_Cowardin.csv",sep="/"),row.names=FALSE)

####################################
#Calculate changes in permit counts
####################################

# Multiply Permit_Count by Cowardin Code-level (Rapanos_Perc - NWPR_Perc) adjustment (to calculate change in number of permits issued between the two scenarios)
# Multiply Permit_Count by SI_Perc and SG_Perc (calculate average number of Ind/Gen permits affecting one water at the HUC4/Cowardin Code level)
# Divide SI/SG- & Rapanos/NWPR-corrected Permit_Count by proportion of 10-year period that state followed Rapanos to get annual average
ORM_Dataset_Final_NoCWRNoMit <- ORM_Dataset_Final_NoCWRNoMit %>%
  mutate(Avg_SI_Count = (Permit_Count*SI_Perc*(Rapanos_Perc_Permitted-NWPR_Perc_Permitted))/Prop_10YrPeriod_NonCWR,
         Avg_SG_Count = (Permit_Count*SG_Perc*(Rapanos_Perc_Permitted-NWPR_Perc_Permitted))/Prop_10YrPeriod_NonCWR)

write.csv(ORM_Dataset_Final_NoCWRNoMit,paste(QA_DIR,"ORM_Dataset_Final.csv",sep="/"),row.names=FALSE)

# Subset dataset to retain permits affecting single waters only (permits affecting multiple waters will still need to be permitted)
Permit_Counts  <- ORM_Dataset_Final_NoCWRNoMit[ which(ORM_Dataset_Final_NoCWRNoMit$SingleWater==1), ]

# Subset dataset, count number of permits per HUC4/COWARDIN and HUC4/COWARDIN/STATE combo, merge with permit counts
Permit_Counts <- Permit_Counts[c("HUC4_COWARDIN","HUC4","STATE_FINAL","Avg_SI_Count","Avg_SG_Count")]
Permit_Counts$HUC4_COWARDIN_STATE <- paste(Permit_Counts$HUC4_COWARDIN,"_",Permit_Counts$STATE_FINAL)

Permit_Counts_HUC4_COWARDIN <- Permit_Counts %>%
  group_by(HUC4_COWARDIN) %>%
  summarise(Permit_Count_HUC4_COWARDIN = n())

Permit_Counts_HUC4_COWARDIN_STATE <- Permit_Counts %>%
  group_by(HUC4_COWARDIN_STATE) %>%
  summarise(Permit_Count_HUC4_COWARDIN_STATE = n())

Permit_Counts <- merge(x=Permit_Counts,y=Permit_Counts_HUC4_COWARDIN,by="HUC4_COWARDIN",all.x=TRUE)
Permit_Counts <- merge(x=Permit_Counts,y=Permit_Counts_HUC4_COWARDIN_STATE,by="HUC4_COWARDIN_STATE",all.x=TRUE)

# Weight adjust permit counts based on HUC4/COWARDIN/STATE divided by HUC4/COWARDIN
Permit_Counts <- Permit_Counts %>%
  mutate(Avg_SI_Count_Adj = Avg_SI_Count * (Permit_Count_HUC4_COWARDIN_STATE/Permit_Count_HUC4_COWARDIN),
         Avg_SG_Count_Adj = Avg_SG_Count * (Permit_Count_HUC4_COWARDIN_STATE/Permit_Count_HUC4_COWARDIN))

# Subset by unique HUC4/COWARDIN/STATE
Permit_Counts2 <- Permit_Counts[!duplicated(Permit_Counts[,c("HUC4_COWARDIN_STATE")]),]
write.csv(Permit_Counts2,paste(QA_DIR,"PermitCounts_QA.csv",sep="/"),row.names=FALSE)
rm(list = c('Permit_Counts','Permit_Counts_HUC4_COWARDIN','Permit_Counts_HUC4_COWARDIN_STATE'))

# Calculate change in average number of permits at the HUC4 level
Permits_HUC4 <- Permit_Counts2 %>%
  group_by(HUC4) %>%
  summarise(Avg_SI_Count = sum(Avg_SI_Count_Adj),
            Avg_SG_Count = sum(Avg_SG_Count_Adj))
write.csv(Permits_HUC4,paste(OUT_DIR,"PermitCounts_By_HUC4.csv",sep="/"),row.names=FALSE)

# Calculate change in average number of permits at the state level
Permits_State <- Permit_Counts2 %>%
  group_by(STATE_FINAL) %>%
  summarise(Avg_SI_Count = sum(Avg_SI_Count_Adj),
            Avg_SG_Count = sum(Avg_SG_Count_Adj))
write.csv(Permits_State,paste(OUT_DIR,"PermitCounts_By_State.csv",sep="/"),row.names=FALSE)


[Federal Register Volume 85, Number 240 (Monday, December 14, 2020)]
[Rules and Regulations]
[Pages 80589-80590]
[FR Doc No: 2020-27507]

=======================================================================
-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 39

[Docket No. FAA-2020-1031; Project Identifier AD-2020-00846-T;
Amendment 39-21334; AD 2020-24-04]
RIN 2120-AA64

Airworthiness Directives; The Boeing Company Airplanes

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Final rule; correction.

-----------------------------------------------------------------------

SUMMARY: The FAA is correcting an airworthiness directive (AD) that
published in the Federal Register. That AD applies to all The Boeing
Company Model 787-8, 787-9, and 787-10 airplanes. As published, the
regulatory text of the AD included errors in certain references to the
airplane flight manual (AFM) that is required to be revised. This
document corrects those errors. In all other respects, the original
document remains the same.

DATES: This correction is effective December 18, 2020. The effective
date of AD 2020-24-04 remains December 18, 2020.

ADDRESSES: You may examine the AD docket at https://www.regulations.gov; or in person at the Docket Management Facility
between 9 a.m. and 5 p.m., Monday through Friday, except Federal
holidays. The AD docket contains this final rule, any comments
received, and other information. The address for Docket Operations is
U.S. Department of Transportation, Docket Operations, M-30, West
Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE,
Washington, DC 20590.

FOR FURTHER INFORMATION CONTACT: Frank Carreras, Aerospace Engineer,
Systems and Equipment Section, FAA, Seattle ACO Branch, 2200 South
216th St., Des Moines, WA 98198; phone and fax:<PHONE_NUMBER>; email:
<EMAIL_ADDRESS>
SUPPLEMENTARY INFORMATION: As published, Airworthiness Directive 2020-
24-04, Amendment 39-21334 (85 FR 77991, December 3, 2020), requires
revising the existing AFM to incorporate procedures for conducting an
approach with a localizer-based navigation aid, monitoring localizer
raw data, calling out any significant deviations, and performing an
immediate go around if the airplane has not intercepted the final
approach course as shown by the localizer deviation. AD 2020-24-04
applies to all The Boeing Company Model 787-8, 787-9, and 787-10
airplanes.
    As published, the regulatory text included errors in certain
references to the AFM that is required to be revised. The location of
the AFM text to be revised is incorrectly identified as the
``Limitations section''; the correct location is the ``Operating
Procedures chapter.'' In addition, the figure incorrectly identified
the heading of the AFM text as ``Operating Instructions''; the correct
heading is ``Autopilot Flight Director System--Operating
Instructions.''

Correction of Publication

    This document corrects an error and correctly adds the AD as an
amendment to 14 CFR 39.13. Although no other part of the preamble or
regulatory information has been corrected, the FAA is publishing the
entire rule in the Federal Register.
    The effective date of this AD remains December 18, 2020.
    Since this action only corrects errors in certain AFM references,
it has no adverse economic impact and imposes no additional burden on
any person. Therefore, the FAA has determined that notice and public
comment procedures are unnecessary.

List of Subjects in 14 CFR Part 39

    Air transportation, Aircraft, Aviation safety, Incorporation by
reference, Safety.

Adoption of the Correction

    Accordingly, pursuant to the authority delegated to me by the
Administrator, the Federal Aviation Administration amends part 39 of
the Federal Aviation Regulations (14 CFR part 39) as follows:

PART 39--AIRWORTHINESS DIRECTIVES

0
1. The authority citation for part 39 continues to read as follows:

    Authority:  49 U.S.C. 106(g), 40113, 44701.

Sec.  39.13   [Corrected]

0
2. The FAA amends Sec.  39.13 by adding the following new airworthiness
directive (AD):

2020-24-04 The Boeing Company: Amendment 39-21334; Docket No. FAA-
2020-1031; Project Identifier AD-2020-00846-T.

(a) Effective Date

    This AD is effective December 18, 2020.

(b) Affected ADs

    None.

(c) Applicability

    This AD applies to all The Boeing Company Model 787-8, 787-9,
and 787-10 airplanes, certificated in any category.

(d) Subject

    Air Transport Association (ATA) of America Code 22, Auto flight.

(e) Unsafe Condition

    This AD was prompted by reports indicating that the autopilot
flight director system (AFDS) failed to transition to the instrument
landing system localizer (LOC) beam after the consistent localizer
capture function in the flight control modules initiated a
transition to capture LOC during approach. The FAA is issuing this
AD to address the AFDS failing to transition, which could result in
localizer overshoot leading to glideslope descent on the wrong
heading. Combined with a lack of flight deck effects for a
consistent localizer capture mode failure, this condition could
result in a controlled flight into terrain.

(f) Compliance

    Comply with this AD within the compliance times specified,
unless already done.

(g) Revise the Airplane Flight Manual (AFM)

    Within 14 days after the effective date of this AD, revise the
Operating Procedures chapter of the existing AFM and applicable
corresponding operational procedures to incorporate the procedures
specified in figure 1 to paragraph (g) of this AD. Revising the
existing AFM to include the changes specified in paragraph (g) of
this AD may be done by inserting a copy of figure 1 to paragraph (g)
of this AD into the existing AFM.
[GRAPHIC] [TIFF OMITTED] TR14DE20.092

(h) Alternative Methods of Compliance (AMOCs)

    (1) The Manager, Seattle ACO Branch, FAA, has the authority to
approve AMOCs for this AD, if requested using the procedures found
in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request
to your principal inspector or responsible Flight Standards Office,
as appropriate. If sending information directly to the manager of
the certification office, send it to the attention of the person
identified in paragraph (i) of this AD. Information may be emailed
to<EMAIL_ADDRESS>    (2) Before using any approved AMOC, notify your appropriate
principal inspector, or lacking a principal inspector, the manager
of the responsible Flight Standards Office.
    (3) An AMOC that provides an acceptable level of safety may be
used for any repair, modification, or alteration required by this AD
if it is approved by The Boeing Company Organization Designation
Authorization (ODA) that has been authorized by the Manager, Seattle
ACO Branch, FAA, to make those findings. To be approved, the repair
method, modification deviation, or alteration deviation must meet
the certification basis of the airplane, and the approval must
specifically refer to this AD.

(i) Related Information

    For more information about this AD, contact Frank Carreras,
Aerospace Engineer, Systems and Equipment Section, FAA, Seattle ACO
Branch, 2200 South 216th St., Des Moines, WA 98198; phone and fax:
206-231-3539; email<EMAIL_ADDRESS>
(j) Material Incorporated by Reference

    None.

    Issued on December 9, 2020.
Ross Landes,
Deputy Director for Regulatory Operations, Compliance & Airworthiness
Division, Aircraft Certification Service.
[FR Doc. 2020-27507 Filed 12-10-20; 11:15 am]
BILLING CODE 4910-13-P