Readme: 2004 303D List Shapefile

2004 303(d) List Shapefile Information

Filenames: 303d_epa2004_streams 303d_epa2004_lakes

Created by: Jody Arthur, 305(b)/303(d) Coordinator Indiana Department of Environmental Management 100 N. Senate Ave., P.O. box 6015 Indianapolis, IN 46206-6015 317-234-1424 [email protected]

These shapefiles, one for 303d-listed streams and one for 303d-listed lakes, were created from the 2004 303d list approved by U.S. EPA. The Microsoft Excel spreadsheet containing the approved list was downloaded on July 23, 2004 from IDEM’s TMDL web site (http://www.in.gov/idem/water/planbr/wqs/303d.html), converted to a database file and imported into ArcView 3.2. A summary of the steps involved in the process of creating this shapefile is available upon request from the 305(b)/303(d) coordinator.

Note to Users: The geodatabases for these shapefiles have been extensively reviewed for quality control. However, for the purposes of providing the most accurate and useful information for the widest variety of potential users, some differences necessarily remain between the published list and these shapefiles. These differences are summarized below. If you get questionable results when querying the geodatabases associated with these shapefiles, review the summary first to determine if the segment(s) in question are addressed. If you still have questions, contact the 305(b)/303(d) coordinator.

General differences between the published list and the information in the geodatabases for these shapefiles  In the Excel version of the list (i.e. the published list), many waterbody segments are listed separately for different parameters. In the geodatabases, each waterbody appears as a single record with all the impairments associated with it in the same record.  In the published list, many waterbody segments have more than one county associated with them. This is an artifact from the 2002 303d list in which several waterbody segments were included in a single entry. This has been corrected in the geodatabases so that each waterbody record is associated with the single county in which it is located.  Waterbody size, which does not appear in the finalized list, has been added to the geodatabases.

Waterbody-specific differences between the published list and the information in the geodatabase Some stream segments that appear on the published list do not show up on the streams shapefile because they have not yet been reached indexed and, as a result, do not have topological (i.e. geographical) information associated with them. Records for each of these stream segments (including the waterbody name and segment ID, 14-digit HUC, county, mileage, and impairment information) have been added to the geodatabase for the streams shapefile. However, lacking the necessary topology, they will not display on the shapefile when queried in the GIS:

1 303d # State Basin HUC Waterbody ID Waterbody Name

2 59 UPPER ILLINOIS 7120001050030 INK0153_T1016 UNNAMED DITCH 111 WEST FORK WHITE 5120202020100 INW022A_T1060 UNNAMED BRANCH EAST FORK FISH CREEK 141 WEST FORK WHITE 5120202080060 INW0286_T1166 ANTIOCH CREEK 141 WEST FORK WHITE 5120202080060 INW0286_T1167 EAGAN DITCH BASIN 142 WEST FORK WHITE 5120202040010 INW0241_T1164 LITTLE RICHLAND CREEK 143 WEST FORK WHITE 5120202010070 INW0217_T1015 SOUTH FORK GRIFFY CREEK 144 WEST FORK WHITE 5120201130070 INW01D7_T1120 MARS DITCH 162 WEST FORK WHITE 5120201010010 INW0111_T1221 OWL CREEK AND TRIBUTARY 162 WEST FORK WHITE 5120201010010 INW0111_T1222 WHITE RIVER HEADWATER TRIBUTARIES 163 WEST FORK WHITE 5120201150100 INW01FA_T1224 WEST FORK WHITE LICK CREEK 168 EAST FORK WHITE 5120208090010 INW0891_T1019 EAST FORK JACKSON CREEK 184 EAST FORK WHITE 5120204060080 INW0468_T1033 SUGAR CREEK-SUGAR CREEK (TOWN) 205 OHIO RIVER 5140101 INH3_M01 OHIO RIVER – BATTLE CREEK TO MCALPINE DAM 205 OHIO RIVER 5140101 INH4_M01 OHIO RIVER – GREENWOOD, KY TO SALT CR 205 OHIO RIVER 5140202 INH8_M01 OHIO RIVER – EVANSVILLE TO UNIONTOWN 328 UPPER WABASH 5120107020020 INB0722_T1035 UNNAMED TRIBUTARY 356 LOWER WABASH 5120111160050 INB11G5_T1034 BIG BRANCH TRIBUTARY – GILMOUR 378 EAST FORK WHITE* 5140202090030 INW0493_T1050 BREWER DITCH 487 PATOKA 5120209050030 INP0953_T1066 UNNAMED TRIBUTARY (HOBBS CEMETERY) 487 PATOKA 5120209050030 INP0953_T1065 LITTLE FLAT CREEK 516 WEST FORK WHITE 5120201060020 INW0162_T1228 BIG DUCK CREEK 516 WEST FORK WHITE 5120201060060 INW0166_T1227 LONG BRANCH 524 OHIO TRIBUTARIES 5140201140110 INE01EB_T1051 UNNAMED TRIB BARREN FORK 527 OHIO TRIBUTARIES 5090203180030 INV03J3_T1040 THURSTON CREEK *Shown incorrectly as West Fork White in published 303d list.

The following waterbody segment will not show up on the streams shapefile because it has not been reached indexed and does not appear in the Indiana 305(b) Assessment Database (ADB). This waterbody segment was not included in the geodatabase because, with no information in the ADB to support its listing, its inclusion in the 2004 303(d) list needs to be investigated further:

303d # State Basin HUC Waterbody ID Waterbody Name 142 WEST FORK WHITE 5120202040030 INW0243_T1020 RICHLAND CREEK

The following waterbody segment ID on the published list contains a typographical error and has been corrected in the geodatabase:

303d # Segment ID shown in 303d list Segment ID shown in geodatabase 92 INB0686_T1028 INB0686_M1028

Some waterbodies appear under two different 303d numbers in the published list. To avoid duplication of segment size and impairment information, each of these waterbodies appears as a single record in the geodatabase with a single 303d number as shown in the following table:

Segment ID Waterbody Name 303d #s shown in list 303d # used in geodatabase

3 INW08P1017_00 YELLOWWOOD LAKE 186 and 471 186 INW039C_1024 EEL RIVER 112 and 113 112 INW039D_1025 EEL RIVER 112 and 113 112 INW0397_T1018 EEL RIVER 112 and 113 112

The published 303d list contains a number of waterbody IDs that are known as “artificial paths.” These are linear segments created through the reach indexing process for the purposes of connecting the inlet and outlet streams for each lake. Artificial paths, which appear in the geodatabase for the streams shapefile, do not represent real waterbodies. Assessments made on artificial paths actually apply to their associated lakes and were assigned to the artificial paths in error resulting in duplicated assessments and added mileage. The changes necessary to correct this in the geodatabases are described in the table below:

303d Waterbody Name Waterbody ID for Waterbody ID for Changes made in the geodatabases artificial path in associated lake in streams geodatabase lakes geodatabase 194 MIDDLE FORK ING0374_P1012 ING03P1012_00 Artificial path deleted from streams geodatabase; RESERVOIR impairment information for artificial path transferred to the record for associated lake in lakes geodatabase. 198 BISCHOFF INV0366_P1003 INV03P1003_00 Artificial path deleted from streams geodatabase; RESERVOIR impairment information for associated lake retained in lakes geodatabase as 303d #474. 201 DEAM LAKE INN01D5_P1001 INN01P1001_00 Artificial path deleted from streams geodatabase; impairment information for associated lake retained in lakes geodatabase.

The following artificial path could not be deleted from the geodatabase because attempts to do so resulted in a segmentation violation error:

303d Waterbody Name Waterbody ID for Waterbody ID for Note artificial path in associated lake in streams geodatabase lakes geodatabase 195 PATOKA LAKE DAM - INP091B_P1001 INP09P1001_00 Artificial path could not be deleted from stream LICK CREEK geodatabase; impairment information for artificial path duplicates record for associated lake (Patoka Reservoir) in lakes geodatabase.