Lower Triangle Watershed DEM Feb 6 2018 /scratch/sft/tam/IDEAS/East_River/Lower_Triangle/data Source Data From LBNL Zexuan Xu zexuanxu@lbl.gov USGS 10 meter DEM product, not the Lidar DEM which has small differences USGS_DEM_LT10_XYZ.xyz 296173 points USGS_DEM_LT50_XYZ.xyz 11759 points Note these xyz points are not the correct orientation for meshing. The 10m DEM Data is Processed so orientation is correct. This DEM file has xyz coordinates with correct orientaion and with NULLS removed: USGS_DEM_LT10_points.csv 148190 points INPUT DEM for meshing: 10m DEM connected into triangle surface cropped at boundary. dem_tri_crop.inp 147920 nodes 294150 triangles NAME MIN MAX DIFFERENCE LENGTH xic 3.259128385E+05 3.311760044E+05 5.263165929E+03 147920 yic 4.314867400E+06 4.320370711E+06 5.503310380E+03 147920 zic 2.759333252E+03 3.775072021E+03 1.015738770E+03 147920 50m Boundary Points for DEM: USGS_DEM_LT10_boundary_50m.csv 368 points INPUT BOUNDARY POLYGON for meshing: 50m Boundary Polygon with overlapping points at tip removed: dem_poly_50m.inp 364 nodes 364 lines INPUT REGION LINES for meshing: river_line.inp north_line.inp =========================================================================== From: "Livingston, Daniel Reece" Subject: Re: Lower Triangle DEM Date: February 6, 2018 at 3:32:56 PM MST To: "Miller, Terry Ann" Hi Terry, Attached is the boundary file. Take a look at the close up image the sharp peak at the bottom of the DEM might cause some problems. Daniel Livingston Computational Earth Science, EES-16 Los Alamos National Laboratory livingston@lanl. gov | 505-667-3467 From: "Livingston, Daniel Reece" Subject: Re: Lower Triangle DEM Date: February 6, 2018 at 10:31:02 AM MST To: "Miller, Terry Ann" Hi Terry, Using GDAL, Dave's files open up with no issue: from matplotlib import pyplot as plt from osgeo import gdal geo = gdal.Open('USGS_DEM_LT10_XYZ.xyz') arr = geo.ReadAsArray() plt.imshow(arr) plt.show() Daniel Livingston Computational Earth Science, EES-16 Los Alamos National Laboratory livingston@lanl. gov | 505-667-3467 From: Zexuan Xu Date: Thursday, February 1, 2018 at 12:49 PM To: "Moulton, J. David" , Erica Woodburn Subject: Lower Triangle DEM Hi David and Erica, I prepared the DEM GTiff and XYZ files for the Lower Triangle at 10 m and 50 m resolution in attached. Please see if it works for you, and feel free to let me know if you need other formats and/or resolution. This is the USGS 10 meter DEM product, not the Lidar DEM. I didn't use Lidar DEM because Rosemary draw the subbasin map based on USGS DEM, so I simply keep consistent. Rosemary and I checked and confirmed that the difference between USGS and Lidar at Lower Triangle is small, so we should be good. David, could you generate both Copper Creek and Lower Triangle 50 m mesh for me? Since ultimately we will only need 50 m. It really takes too long to test ATS with the 10 m Copper Creek mesh (I mean the one you created and share with me last week). Thanks Zexuan -- Zexuan Xu, Ph.D Postdoctoral Fellow Climate & Ecosystem Sciences Division Lawrence Berkeley National Laboratory 1 Cyclotron Road, MS 84-0122 Berkeley, CA 94720 BIDS CREC-WET Data Science Fellow Berkeley Institute for Data Science University of California, Berkeley 190 Doe Library Berkeley, CA 94720 DATA PROCESSING: 1) REFORMAT and VIEW DEM DATA Convert points to AVS UCD point format (for paraview) awk -f coords2avsucd.awk USGS_DEM_LT10_boundary_50m.csv > USGS_DEM_LT10_boundary_50m.inp Connect ordered points into AVS UCD line format awk -f ucdpt2lines.awk dem_bndry_50m.inp > dem_poly_50m.inp 2) CONNECT DEM into surface CREATE Triangulation and interpolate elevations lagrit < mk_dem_surface.lgi 3) CREATE BOUNDARY POLYGON Remove tip where points overlap and are closer than 20 from each other lagrit < bndry_rmpoint.lgi awk -f ucdpt2lines.awk dem_bndry_50m.inp > dem_poly_50m.inp NOTES these csv are not comma deliminated and paraview is not reading them without the commas awk -f fixcvs.awk USGS_DEM_LT10_boundary_50m.csv > dem_bndry_50m.csv