Detroit Street View (DSV) is an urban remote sensing program run by the Enterprise Geographic Information Systems (EGIS) Team within the Department of Innovation and Technology at the City of Detroit. The mission of Detroit Street View is ‘To continuously observe and document Detroit’s changing physical environment through remote sensing, resulting in freely available foundational data that empowers effective city operations, informed decision making, awareness, and innovation.’ LiDAR (as well as panoramic imagery) is collected using a vehicle-mounted mobile mapping system.
Due to variations in processing, index lines are not currently available for all existing LiDAR datasets, including all data collected before September 2020. Index lines represent the approximate path of the vehicle within the time extent of the given LiDAR file. The actual geographic extent of the LiDAR point cloud varies dependent on line-of-sight.
Compressed (LAZ format) point cloud files may be requested by emailing gis@detroitmi.gov with a description of the desired geographic area, any specific dates/file names, and an explanation of interest and/or intended use. Requests will be filled at the discretion and availability of the Enterprise GIS Team. Deliverable file size limitations may apply and requestors may be asked to provide their own online location or physical media for transfer.
LiDAR was collected using an uncalibrated Trimble MX2 mobile mapping system. The data is not quality controlled, and no accuracy assessment is provided or implied. Results are known to vary significantly. Users should exercise caution and conduct their own comprehensive suitability assessments before requesting and applying this data.
Sample Dataset: https://detroitmi.maps.arcgis.com/home/item.html?id=69853441d944442f9e79199b57f26fe3
This grid provides blocks for the download of LAZ files for Maryland Point Cloud data. The download for each grid will not exceed 10 GB.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link:https://mdgeodata.md.gov/lidar/rest/services/Status/MD_DownloadBlocks/FeatureServer/0
These 5000 foot tile index polygons define the boundaries of individual point cloud (.laz) files, originally produced for the New Jersey Orthophoto Mapping Program 2007-2008. The tile scheme is in New Jersey State Plane coordinates, NAD83, in units of US Survey feet. This index is the same as the index for the 2002 - 2003 New Jersey Orthophoto Mapping Program. Attributes include tile names, file size in KB & MB, and links to download.
Points spaced 50 feet apart representing ground surface were derived from classified LiDAR flown by Digital Aerial Surveys LLC between May 7, 2018 and March 1, 2019. The Lee County portion was flown May 8 to October 29, 2018.Compressed LAS files (Albers meters) were downloaded from USGS' ftp site. LAZ were decompressed using rapidlasso's LASzip. GeoCue's LP360 for ArcMap tools were utilized to extract point coordinates from the LAS surface using points classes Ground (2), Water (9) and Bridge Deck (17). The points generated from these coordinates were projected to Florida State Plane West, feet using ArcGIS' Project tool and the elevation converted from meters to feet (m * 3.28084). The X and Y coordinates in this dataset are in State Plane feet. Elevation is in feet NAVD 88 vertical datum.The horizontal accuracy is +/-0.783 meters or +/-2.57 feet (at the 95% confidence level) and the vertical accuracy is +/-0.175 meters (+/-0.57 feet) for nonvegetated and +/-0.190 meters (+/- 0.62 feet) for vegetated areas. See the report, LiDAR Project Report 140G0218F0179, FL SOUTHWEST 2018 D18, prepared by Digital Aerial Solutions, LLC for United States Geological Survey, for full accuracy details.Additional information can be found here: https://coast.noaa.gov/htdata/raster2/elevation/USGS_FL_Southwest_2018_9049/2018_swfl_m9049_met_forHumans.html.
These 5000 foot tile index polygons define the boundaries of individual point cloud (.laz) files, originally produced for the New Jersey Orthophoto Mapping Program 2007-2008. The tile scheme is in New Jersey State Plane coordinates, NAD83, in units of US Survey feet. This index is the same as the index for the 2002 - 2003 New Jersey Orthophoto Mapping Program. Attributes include tile names, file size in KB & MB, and links to download.
The Virginia LiDAR Inventory Web Mapping Application provides access to LiDAR point cloud and individual project metadata collected in the Commonwealth of Virginia according to the USGS 3DEP specification. Data is obtained from NOAA, USGS, and VGIN data portals. LiDAR Point Clouds are compressed for file storage and transfer. USGS and NOAA utilize the compressed .LAZ format. This dataset will provide the end user a necessary set of geographic extents that can be used with an ArcGIS Desktop or Pro session to select by location specific areas of download. The downloads can either be batch processed by the analysis with scripting and modeling or individual tiles can be downloaded. This is the tile data powering VGIN ArcGIS server services utilized in the VGIN LiDAR Download Application.
This web map provides an index for identifying subsets of LiDAR data acquired for the greater metropolitan Phoenix region in 2014 via a (non-3DEP) USGS LiDAR program.Two index layers are included in this web map: (1) Point Cloud Index, (2) Raster Index. Another layer, Maricopa County Municipalities, is included as an additional geographic reference aid. LiDAR Point Cloud Index The Point Cloud Index layer indexes the raw LiDAR point cloud data (available in las/laz file formats). Each tile's file name can be identified by clicking on a particular tile.DEM Raster IndexThe Raster Index layer indexes the LiDAR-derived bare earth digital elevation model (DEM) surface data (available in tif file format). Users can click on a particular tile within the index to identify its ID.Once you have identified your file name or ID of interest, please submit a quick service request through the Map and Geospatial Hub's Service Request Form.Technical SpecificationsHorizontal Projection: UTM 12N WGS 84 (meters)Vertical Datum: NAVD 1988 (meters) Geoid 12APoint Spacing (minimum): 0.5 m / 1.64 ftAbove Ground Level (AGL) average flight height: 1700 m / 5,579 ftMean Sea Level (MSL) average flying height: 1981 m / 6500 ftAverage Ground Speed: 140 knots / 161 mphField of View (full): 28 degreesPulse Rate: 312.2 kHzScan Rate: 54.8 HzSide Lap (Minimum): 25%
These 500 m x 500 m tile index polygons define the boundaries of individual point cloud (.laz) files. The tile scheme is in NAD 1983 (NSRS 2007) geographic coordinate system. Attributes include tile names and links to download.
On November 7, 2021, NV5 collected Quality Level 1 (QL1) lidar data across the preliminary CAL FIRE defined fire perimeter for the CZU lightning complex fire in San Mateo and Santa Cruz counties. The technical report for the lidar data collection is available here: https://fuelsmapping.com/czu_postfire_lidar_report From the QL1 postfire lidar, NV5 and Tukman Geospatial developed a set of derivatives. These derivatives are a Digital Terrain Model (DTM), a Digital Surface Model (DSM), a Hillshade derived from the DTM, a lidar intensity image, a Normalized Digital Surface Model (nDSM), a Canopy Cover raster, and a lidar intensity image. The derivatives will be used to study the effects of the CZU wildfire on the natural landscape, forests, and shrublands of Santa Cruz and San Mateo Counties. The lidar derivatives are provided as GeoTiffs available for download from ArcGIS Online and as dynamic image services. Table 1 provides more information (including download information) for the derivatives produced. The GeoTiffs can be used in desktop GIS software packages such as ArcGIS Pro and ERDAS Imagine; the image services can be used in web maps and web mapping applications by both GIS users and non-GIS users. Table 1. lidar derivatives for the CZU lightning fire footprint in San Mateo and Santa Cruz Counties
Dataset
Description
Link to GeoTiff
Link to Image Service
Digital Terrain Model (DTM)
Hydroflattened digital terrain model. Pixel values represent elevation above sea level of the ground.
https://vegmap.press/czu_postfire_dtm_tif
https://vegmap.press/czu_postfire_dtm
Digital Surface Model (DSM)
Pixel values in the DSM represent elevations above sea level of the ‘highest hit’ surface. The DSM provides elevation above sea level of the top of the tree canopy, the top of buildings, and the top of other features.
https://vegmap.press/czu_postfire_dsm_tif
https://vegmap.press/czu_postfire_dsm
Hillshade
The hillshade is derived from the DTM and provides a ‘shaded relief’ visualization of the earth’s surface.
https://vegmap.press/czu_postfire_hillshade_tif
https://vegmap.press/czu_postfire_hillshade
Lidar Intensity
Lidar intensity, scaled to 8-bit resolution.
https://vegmap.press/czu_postfire_intensity_tif
https://vegmap.press/czu_postfire_lidar_intensity
Normalized Digital Surface Model (nDSM)
In the nDSM, pixel values represent the maximum normalized height in feet of features such as vegetation and structures. For areas with aboveground features, pixel values represent the aboveground height of the tallest part of the feature in the 3x3 foot pixel. For areas with no aboveground features, the nDSM has pixel values of 0.
https://vegmap.press/czu_postfire_nDSM_tif
https://vegmap.press/czu_postfire_nDSM
Canopy Height Model
The canopy height model is the normalized digital surface model, with building footprints and a small buffer surrounding them set to 0 normalized height. Building footprint data came from the prefire CHM. The datasheet for the prefire CHM is available here: https://vegmap.press/sc_chm As such, this raster mostly represents the aboveground height of the vegetation canopy. Note that it also includes some noise (e.g., powerlines and other objects that are not vegetation), as well as some structures that weren't captured as building footprints.
https://vegmap.press/czu_postfire_chm_tif
https://vegmap.press/czu_postfire_chm
Canopy Cover
This is the Canopy Height Model, thresholded to show pixel values greater than or equal to 15 feet aboveground as 1, and all other areas as 0. As such, it is a proxy for tree canopy cover.
https://vegmap.press/czu_postfire_cc_tif
https://vegmap.press/czu_postfire_cc
Related Datasets: The QL1 point cloud, from which these deliverables were acquired, is available as laz files. The laz files are downloadable by tile. See this datasheet for more information: CZU postfire QL1 point cloudCZU postfire 4-band imagery
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Detroit Street View (DSV) is an urban remote sensing program run by the Enterprise Geographic Information Systems (EGIS) Team within the Department of Innovation and Technology at the City of Detroit. The mission of Detroit Street View is ‘To continuously observe and document Detroit’s changing physical environment through remote sensing, resulting in freely available foundational data that empowers effective city operations, informed decision making, awareness, and innovation.’ LiDAR (as well as panoramic imagery) is collected using a vehicle-mounted mobile mapping system.
Due to variations in processing, index lines are not currently available for all existing LiDAR datasets, including all data collected before September 2020. Index lines represent the approximate path of the vehicle within the time extent of the given LiDAR file. The actual geographic extent of the LiDAR point cloud varies dependent on line-of-sight.
Compressed (LAZ format) point cloud files may be requested by emailing gis@detroitmi.gov with a description of the desired geographic area, any specific dates/file names, and an explanation of interest and/or intended use. Requests will be filled at the discretion and availability of the Enterprise GIS Team. Deliverable file size limitations may apply and requestors may be asked to provide their own online location or physical media for transfer.
LiDAR was collected using an uncalibrated Trimble MX2 mobile mapping system. The data is not quality controlled, and no accuracy assessment is provided or implied. Results are known to vary significantly. Users should exercise caution and conduct their own comprehensive suitability assessments before requesting and applying this data.
Sample Dataset: https://detroitmi.maps.arcgis.com/home/item.html?id=69853441d944442f9e79199b57f26fe3