20201217
14195700
1.0
FALSE
CreateMosaicDataset E:\DCGIS\Projects\Lidar_2020\Final\Lidar_2020.gdb DTM PROJCS['NAD_1983_StatePlane_Maryland_FIPS_1900',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Lambert_Conformal_Conic'],PARAMETER['False_Easting',400000.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-77.0],PARAMETER['Standard_Parallel_1',38.3],PARAMETER['Standard_Parallel_2',39.45],PARAMETER['Latitude_Of_Origin',37.66666666666666],UNIT['Meter',1.0]],VERTCS['NAVD_1988_Geoid_12B',VDATUM['North_American_Vertical_Datum_1988'],PARAMETER['Vertical_Shift',0.0],PARAMETER['Direction',1.0],UNIT['Meter',1.0]] # # None #
AddRastersToMosaicDataset E:\DCGIS\Projects\Lidar_2020\Final\Lidar_2020.gdb\DTM "Raster Dataset" E:\DCGIS\Projects\Lidar_2020\Final\DTM UPDATE_CELL_SIZES UPDATE_BOUNDARY NO_OVERVIEWS # 0 1500 # # SUBFOLDERS "Allow duplicates" NO_PYRAMIDS NO_STATISTICS NO_THUMBNAILS # NO_FORCE_SPATIAL_REFERENCE NO_STATISTICS # NO_PIXEL_CACHE C:\Users\brian.putz\AppData\Local\ESRI\rasterproxies\DTM
CalculateStatistics E:\DCGIS\Projects\Lidar_2020\Final\Lidar_2020.gdb\DTM 1 1 # OVERWRITE "Feature Set"
AnalyzeMosaicDataset \\Gisimgprd1\e\Productionfiles\Lidar_2020\Lidar_2020.gdb\DTM # FOOTPRINT;FUNCTION;RASTER;PATHS
RemoveRastersFromMosaicDataset \\Gisimgprd1\e\Productionfiles\Lidar_2020\Lidar_2020.gdb\DTM "OBJECTID >=0" UPDATE_BOUNDARY MARK_OVERVIEW_ITEMS DELETE_OVERVIEW_IMAGES DELETE_ITEM_CACHE REMOVE_MOSAICDATASET_ITEMS UPDATE_CELL_SIZES
CalculateStatistics \\Gisimgprd1\e\Productionfiles\Lidar_2020\Lidar_2020.gdb\DTM 1 1 # OVERWRITE "Feature Set"
BuildMosaicDatasetItemCache \\Gisimgprd1\e\Productionfiles\Lidar_2020\Lidar_2020.gdb\DTM # DEFINE_CACHE GENERATE_CACHE \\Gisimgprd1\e\Productionfiles\Lidar_2020\Lidar_2020.Cache\DTM.Cache LOSSLESS 80 200000 200000 PIXEL_SIZE_FACTOR 1
BuildOverviews \\Gisimgprd1\e\Productionfiles\Lidar_2020\Lidar_2020.gdb\DTM # DEFINE_MISSING_TILES GENERATE_OVERVIEWS GENERATE_MISSING_IMAGES REGENERATE_STALE_IMAGES
BuildMosaicDatasetItemCache \\Gisimgprd1\e\Productionfiles\Lidar_2020\Lidar_2020.gdb\DTM # DEFINE_CACHE GENERATE_CACHE \\Gisimgprd1\e\Productionfiles\Lidar_2020\Lidar_2020.Cache\DTM.Cache LOSSLESS 80 200000 200000 PIXEL_SIZE_FACTOR 1
DTM
file://\\Gisimgprd1\e\Productionfiles\Lidar_2020\Lidar_2020.gdb
Local Area Network
389400.000000
408600.000000
124200.000000
148200.000000
1
Projected
GCS_North_American_1983
Linear Unit: Meter (1.000000)
NAD_1983_StatePlane_Maryland_FIPS_1900
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'><WKT>PROJCS["NAD_1983_StatePlane_Maryland_FIPS_1900",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",400000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-77.0],PARAMETER["Standard_Parallel_1",38.3],PARAMETER["Standard_Parallel_2",39.45],PARAMETER["Latitude_Of_Origin",37.66666666666666],UNIT["Meter",1.0]],VERTCS["NAVD_1988_Geoid_12B",VDATUM["North_American_Vertical_Datum_1988"],PARAMETER["Vertical_Shift",0.0],PARAMETER["Direction",1.0],UNIT["Meter",1.0]]</WKT><XOrigin>-36747100</XOrigin><YOrigin>-29091500</YOrigin><XYScale>121236910.21292362</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>26985</WKID><LatestWKID>26985</LatestWKID></ProjectedCoordinateSystem>
8
FALSE
None
1
AMD
TRUE
continuous
unsigned integer
4100
15000
1000
20
2048
20
75
0.01
10
600
300
Basic
1
NorthWest,Center,LockRaster,ByAttribute,Nadir,Viewpoint,Seamline,None
None,JPEG,LZ77,LERC
None
None,Basic,Base-Top Height,Top-Top Shadow Height,Base-Top Shadow Height,3D
-1
-1
0.8
1
NorthWest,Center,LockRaster,ByAttribute,Nadir,Viewpoint,Seamline,None
None,JPEG,LZ77,LERC
None,Basic,Full
NONE
<_docversion_ Sync="TRUE">10
Name,MinPS,MaxPS,LowPS,HighPS,Tag,GroupName,ProductName,CenterX,CenterY,ZOrder,Shape_Length,Shape_Area
4050
1
81
C:\Users\brian.putz\AppData\Local\ESRI\rasterproxies\DTM
0
44232.7971078704
20210205
14584400
20210205
14584400
150000000
5000
FGDC
GIS Data Coordinator
D.C. Office of the Chief Technology Officer
(202) 727-5660
200 I Street SE, 5th Floor
Washington
DC
20003
US
dcgis@dc.gov
20210205
ArcGIS Metadata
1.0
GIS Data Coordinator
D.C. Office of the Chief Technology Officer
(202) 727-5660
200 I Street SE, 5th Floor
Washington
DC
20003
US
dcgis@dc.gov
DC datasets can be downloaded from " http://opendata.dc.gov ".
Hydro_Enforced_DTM_2020
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Hydro-Flattened Bare Earth DTM - 1m resolution. The dataset contains the 1m Digital Surface Model for the District of ColumbiaSome areas have limited data. The lidar dataset redaction was conducted under the guidance of the United States Secret Service. Except for classified ground points and classified water points, all lidar data returns and collected data were removed from the dataset within the United States Secret Service 1m redaction boundary generated for the 2017 orthophoto flight</SPAN></P></DIV></DIV></DIV>
1 meter resolution Hydro-Flattened Bare Earth DTM from lidar flown on 6/26/2020, 6/29/2020, and 6/30/2020. This data is used for the planning and management of Washington, D.C. by local government agencies.
GIS Data Coordinator
D.C. Office of the Chief Technology Officer
(202) 727-5660
200 I Street SE, 5th Floor
Washington
DC
20003
US
dcgis@dc.gov
Washington D.C., DC, District of Columbia
lidar, 2020, dtm, topography, bare earth, elevation, DC GIS, DCGIS
lidar
2020
dtm
topography
bare earth
elevation
DC GIS
DCGIS
Washington D.C.
DC
District of Columbia
See access and use constraints information.
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This work is licensed under a Creative Commons Attribution 4.0 International License.</SPAN></P></DIV></DIV></DIV>
Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362
-77.122373
-76.900716
38.785481
39.001746
1
-77.122373
-76.900716
39.001746
38.785481
The hydro-flattened bare earth DEM was generated using the lidar bare earth points and 3D hydro breaklines to a resolution of 1 m. The bare earth points that fell within 1NPS along the hydro breaklines were excluded from the DEM generation process and put into class 20 – ignored ground. This is analogous to the removal of mass points for the same reason in a traditional photogrammetrically compiled DTM. This process was done in batch using proprietary software. The technicians then used Fugro proprietary software for the production of the lidar-derived hydro-flattened bare earth DEM surface in initial grid format at 1 m GSD. Water bodies (inland ponds and lakes), inland streams and rivers, and island holes were hydro-flattened within the DEM. Once the initial, hydro-flattened bare earth DEM was generated, the tiles were checked to ensure that the grid spacing met specifications. The surface was also checked to ensure proper hydro-flattening. The entire dataset was reviewed for complete project coverage and then converted to Geotiffs.
Fugro Geospatial. Inc.
(301) 948-8550
7320 Executive Way # 107
Frederick
MD
21704
US
The hydro-breaklines were collected in 2D as vector line work, using a combination of classified lidar dataset, intensity images, shaded relief TIN and contours. The hydro features were collected to the following specifications: double line rivers and streams greater than 10’ in width, ponds or lakes greater than .5 acre, and islands greater than .25 acre. After the breaklines have been collected, vertex elevation values were assigned using a distance weighted distribution of the lidar points closest to each vertex (similar to draping the 2D linework to a surface modelled from the lidar points). The linework elevation values were further adjusted based on the following rules: 1) lake feature vertices were re-assigned (flattened) to the lowest draped vertex value, and 2) double stream bank line vertices were re-assigned based on the vertices of the closest adjusted double stream connector line. Fugro proprietary software was used to create profiles to ensure bank-to-bank flatness, monotonicity check and lake flatness.
The lidar acquisition was flown on 6/26/2020, 6/29/2020, and 6/30/2020, at an altitude of 9,022 feet above mean sea level and composed of 28 flight lines, 26 primary lines and two cross ties. All lidar data was collected with a Cessna 441, tail# N93HC and a Leica ALS80 lidar sensor, #130. Due to the known difficulties flying over DC, the ALS80 sensor was selected to take advantage of its flight altitude and speed, minimizing the number of lifts for the various flight restrictions. All lidar was collected in conjunction with airborne GPS.
ground condition
2020-06-26
2020-06-30
2
1
24000.000000
1
19200.000000
1
0
389400.000000 124200.000000
389400.000000 148200.000000
408600.000000 148200.000000
408600.000000 124200.000000
399000.000000 136200.000000
EPSG
4.5(3.0.1)
Band_1
130.852005
-9.877000
8