Sam Rayburn 2004 SamRayburn.mdb geodatabase bndy_stpl83 (feature dataset of all boundaries projected in NAD83 state plane) bndy180: polygon feature class of lake boundary at elev. 180 ft from hypsography bndy180hypso: line feature class, contour 180 ft pulled from hypsography doq04_162_67: line lake boundary digitized from 2004 DOQs elevation 162.67 ft doq04_167_28: line lake boundary digitized from 2004 DOQs elevation 167.28 ft doq95_156_6: line lake boundary digitized from 1995 DOQs elevation 156.5 ft doq95_168_77: line lake boundary digitized from 1995 DOQs elevation 168.77 ft Note:The TIN model use to calculate the area volume tables was constructed using all the feature classes in the bndy_stpln83 geodatabase except the168.77 line. It didn't appear to match the water surface elevations or rather the water surface elevation associated with the date of the photographs did not seem to jive with the photographs. Additionally, the 168.77 lines are an interpolation of two separate water surface elevations in the aerial photography. The water surface elevations were actually 168.65 and 168.88. While the park contours provided by the COE where not used in the TIN generation they were used as guides when digitizing the other lines around them. hi_res_163_6: line lake boundary digitized from high resolution aerial photos provided by USACE elev. 163.6 ft is_poly_180: 180 ft hypspgraphy polygon islands: 180 ft hypsography line Pk_contours_COE: contours of lake parks provided by Corps of Engineers lk164 cont164: polygon of lake at elevation 164 ft, likely pulled from contours cont_164: line of lake at elevation 164 ft, likely pulled from contours cont_1_filt4: 1 ft contours Note: The 1 foot contours in the shape file named cont1_filt4.shp were derived from the sam_tin by converting to a raster with 10 ft cell size the filtering that raster 4 times to smooth the contours. survey_pts_sp: 2004 survey data points (sp= projected in state plane) SR_bndy180_poly.shp: polygon feature class of lake boundary at elev. 180 ft from hypsography SR_bndy180hypso_line.shp: line feature class, contour 180 ft pulled from hypsography SR_doq04_162_67.shp: line lake boundary digitized from 2004 DOQs elevation 162.67 ft SR_doq04_167_28.shp: line lake boundary digitized from 2004 DOQs elevation 167.28 ft SR_doq95_156_6.shp: line lake boundary digitized from 1995 DOQs elevation 156.5 ft SR_doq95_168_77.shp: line lake boundary digitized from 1995 DOQs elevation 168.77 ft Note:The TIN model use to calculate the area volume tables was constructed using all the feature classes in the bndy_stpln83 geodatabase except the168.77 line. It didn't appear to match the water surface elevations or rather the water surface elevation associated with the date of the photographs did not seem to jive with the photographs. Additionally, the 168.77 lines are an interpolation of two separate water surface elevations in the aerial photography. The water surface elevations were actually 168.65 and 168.88. While the park contours provided by the COE where not used in the TIN generation they were used as guides when digitizing the other lines around them. SR_hi_res_163_6.shp: line lake boundary digitized from high resolution aerial photos provided by USACE elev. 163.6 ft SR_is_poly_180.shp: 180 ft hypspgraphy polygon SR_islands180_line.shp: 180 ft hypsography line SR_Pk_contours_COE.shp: contours of lake parks provided by Corps of Engineers SR_cont164_poly.shp: polygon of lake at elevation 164 ft, likely pulled from contours SR_cont_164_line.shp: line of lake at elevation 164 ft, likely pulled from contours cont_1_filt4: 1 ft contours Note: The 1 foot contours in the shape file named cont1_filt4.shp were derived from the sam_tin by converting to a raster with 10 ft cell size the filtering that raster 4 times to smooth the contours. SR_survey_pts_sp: 2004 survey data points (sp= projected in state plane) dtxyz.txt: comma delimited txt file of 2004 survey data points (date,time,x,y,z(elevation))