MD/PA Sandy Supplemental Lidar Data Acquisition and Processing Production Task USGS Contract No. G10PC00057 Task Order No. G14PD00397 Woolpert Order No. 74333 CONTRACTOR: Woolpert, Inc. This task is for a high resolution data set of lidar covering approximately 1,845 square miles. The lidar data was acquired and processed under the requirements identified in this task order. Lidar data is a remotely sensed high resolution elevation data collected by an airborne platform. The lidar sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. The final products include classified LAS, one (1) meter pixel raster DEMs of the bare-earth surface in ERDAS IMG Format, and 8-bit intensity images. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Additional deliverables include hydrologic breakline data, control data, tile index, lidar processing and survey reports in PDF format, FGDC metadata files for each data deliverable in .xml format, and LAS swath data. Ground conditions: Water at normal levels; no unusual inundation; no snow; leaf off. Coastal tiles 18SVH065720 and 8SVH095690 contain no lidar points as they exist completely in water. A DEM IMG was generated for these two tiles as the digitized hydro breakline assumed the data extent in the area. As such only 2568 LAS and Intensity files will be delivered along with 2570 DEM IMG's.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/BaltimoreCity/MD_baltimorecity_dem_ft/ImageServer

These data sets represent 23 geographic 5-minute indexes for the counties of Maryland, one 2 1/2-minute index for Washington D.C., and 1-mile square index for Baltimore City. There are 25 vector polygon data sets covered by this metadata report.

MD/PA Sandy Supplemental Lidar Data Acquisition and Processing Production Task USGS Contract No. G10PC00057 Task Order No. G14PD00397 Woolpert Order No. 74333 CONTRACTOR: Woolpert, Inc. This task is for a high resolution data set of lidar covering approximately 1,845 square miles. The lidar data was acquired and processed under the requirements identified in this task order. Lidar data is a remotely sensed high resolution elevation data collected by an airborne platform. The lidar sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. The final products include classified LAS, one (1) meter pixel raster DEMs of the bare-earth surface in ERDAS IMG Format, and 8-bit intensity images. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Additional deliverables include hydrologic breakline data, control data, tile index, lidar processing and survey reports in PDF format, FGDC metadata files for each data deliverable in .xml format, and LAS swath data. Ground conditions: Water at normal levels; no unusual inundation; no snow; leaf off. Coastal tiles 18SVH065720 and 8SVH095690 contain no lidar points as they exist completely in water. A DEM IMG was generated for these two tiles as the digitized hydro breakline assumed the data extent in the area. As such only 2568 LAS and Intensity files will be delivered along with 2570 DEM IMG's.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/BaltimoreCity/MD_baltimorecity_slope_m/ImageServer

Aerial Cartographics of America (ACA) collected 750 square miles covering Baltimore County. The nominal pulse spacing for this project was 1 point every 0.7 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 0-Never Classified, 1-Unclassified, 2-Ground, 7-Low Noise, 9-Water, 10-Ignored Ground due to breakline proximity. Dewberry produced 3D breaklines and combined these with the final LiDAR data to produce seamless hydro-conditioned DEMs for the project area. The data was formatted according to the Baltimore County tile naming convention.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/Baltimore/MD_baltimore_shadedRelief_RGB/ImageServer

In the spring of 2008, the City of Baltimore expressed an interest to upgrade the City GIS Database with mapping quality airborne LiDAR data. The City of Baltimore currently had in place a contract for mapping GIS/services with the KCI/Sanborn Joint Venture Partnership, L.L.C. under Project 1051. The City of Baltimore issued Change Order #1 on on Project 1051 for the LiDAR acquisition and processing. KCI/Sanborn acquired the LiDAR data over the City of Baltimore (approximately 90 square miles) during one long mission on 15 April 2008. A Leica Airborne Airborne Laser Scanner Model ALS 50 was used in a Sanborn Aero Commander 500B (Registration N6172X) to acquire the data. The airborne mission was flown 15 April 2008. The LiDAR system acquired calibration data the same day by conducting flight passes over a known ground surface before and the LiDAR mission. During final data processing, the calibration parameters were used in the final post-processing software. The acquired LiDAR data were processed to obtain the following deliverables: -DEMs of first and last returns and bare earth (all point data) -LAS format data in a tile grid provided by the City/KCI -Gridded DEM in ESRI format (Arc Binary Grid -Arc/INFO Lattice ) produced from Bare Earth Mass Points in 1-meter resolution (Grid size) -Associated FGDC compliant metadata in XML format The project specifications called for the LiDAR survey to comply with industry standard FEMA guidelines for accuracy. The FEMA requirement for this type of mapping calls for vertical errors not to exceed 0.185 meter (0.61 feet) RMSE when compared with ground check points over open flat terrain and 0.370 meter (1.22 feet) for other types of terrain. This accuracy requirement was comfortably met with comparing LiDAR derived elevations against 50 ground control check points provided by KCI Technologies. These control points were photo control points used as part of the photogrammetric mapping project and independent LiDAR checkpoints surveyed by KCI and Mercado after the data was delivered. The RMSE error observed was 0.058 meter (0.189 feet) over all 50 check points.

Aerial Cartographics of America (ACA) collected 750 square miles covering Baltimore County. The nominal pulse spacing for this project was 1 point every 0.7 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 0-Never Classified, 1-Unclassified, 2-Ground, 7-Low Noise, 9-Water, 10-Ignored Ground due to breakline proximity. Dewberry produced 3D breaklines and combined these with the final LiDAR data to produce seamless hydro-conditioned DEMs for the project area. The data was formatted according to the Baltimore County tile naming convention.This is a MD iMAP hosted service. Find more information athttps://imap.maryland.gov.Image Service Link:https://lidar.geodata.md.gov/imap/rest/services/Baltimore/MD_baltimore_hillshade_m/ImageServer

Aerial Cartographics of America (ACA) collected 750 square miles covering Baltimore County. The nominal pulse spacing for this project was 1 point every 0.7 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 0-Never Classified, 1-Unclassified, 2-Ground, 7-Low Noise, 9-Water, 10-Ignored Ground due to breakline proximity. Dewberry produced 3D breaklines and combined these with the final LiDAR data to produce seamless hydro-conditioned DEMs for the project area. The data was formatted according to the Baltimore County tile naming convention.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/Baltimore/MD_baltimore_slope_m/ImageServer

MD/PA Sandy Supplemental Lidar Data Acquisition and Processing Production Task USGS Contract No. G10PC00057 Task Order No. G14PD00397 Woolpert Order No. 74333 CONTRACTOR: Woolpert, Inc. This task is for a high resolution data set of lidar covering approximately 1,845 square miles. The lidar data was acquired and processed under the requirements identified in this task order. Lidar data is a remotely sensed high resolution elevation data collected by an airborne platform. The lidar sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. The final products include classified LAS, one (1) meter pixel raster DEMs of the bare-earth surface in ERDAS IMG Format, and 8-bit intensity images. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Additional deliverables include hydrologic breakline data, control data, tile index, lidar processing and survey reports in PDF format, FGDC metadata files for each data deliverable in .xml format, and LAS swath data. Ground conditions: Water at normal levels; no unusual inundation; no snow; leaf off. Coastal tiles 18SVH065720 and 8SVH095690 contain no lidar points as they exist completely in water. A DEM IMG was generated for these two tiles as the digitized hydro breakline assumed the data extent in the area. As such only 2568 LAS and Intensity files will be delivered along with 2570 DEM IMG's.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/BaltimoreCity/MD_baltimorecity_dem_m/ImageServer

Aerial Cartographics of America (ACA) collected 750 square miles covering Baltimore County. The nominal pulse spacing for this project was 1 point every 0.7 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 0-Never Classified, 1-Unclassified, 2-Ground, 7-Low Noise, 9-Water, 10-Ignored Ground due to breakline proximity. Dewberry produced 3D breaklines and combined these with the final LiDAR data to produce seamless hydro-conditioned DEMs for the project area. The data was formatted according to the Baltimore County tile naming convention.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/Baltimore/MD_baltimore_aspect_m/ImageServer

MD/PA Sandy Supplemental Lidar Data Acquisition and Processing Production Task USGS Contract No. G10PC00057 Task Order No. G14PD00397 Woolpert Order No. 74333 CONTRACTOR: Woolpert, Inc. This task is for a high resolution data set of lidar covering approximately 1,845 square miles. The lidar data was acquired and processed under the requirements identified in this task order. Lidar data is a remotely sensed high resolution elevation data collected by an airborne platform. The lidar sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. The final products include classified LAS, one (1) meter pixel raster DEMs of the bare-earth surface in ERDAS IMG Format, and 8-bit intensity images. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Additional deliverables include hydrologic breakline data, control data, tile index, lidar processing and survey reports in PDF format, FGDC metadata files for each data deliverable in .xml format, and LAS swath data. Ground conditions: Water at normal levels; no unusual inundation; no snow; leaf off. Coastal tiles 18SVH065720 and 8SVH095690 contain no lidar points as they exist completely in water. A DEM IMG was generated for these two tiles as the digitized hydro breakline assumed the data extent in the area. As such only 2568 LAS and Intensity files will be delivered along with 2570 DEM IMG's.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/BaltimoreCity/MD_baltimorecity_shadedRelief_RGB/ImageServer

In the spring of 2005, Sanborn as part of the Dewberry team was contracted to execute a LiDAR (Light Detection and Ranging) survey campaign to collect the 3-dimensional positions of a dense set of masspoints for the entire 689 plus square mile project area of Baltimore County, Maryland. These data are suitable for the development of a digital elevation model (DEM) to support orthometric photo rectification and contouring. The lidar first and Last Return value data were obtained from the post processed data and provided in separate files containing all georeferenced First Return and Last Return data in an ASCII comma delimited format to the NOAA Coastal Services Center. For data storage and Digital Coast provisioning purposes, the NOAA Coastal Services Center converted the ascii data to geographic coordinates, ellipsoid heights in meters, and las format and created a bare earth data set using an automated algorithm.

Aerial Cartographics of America (ACA) collected 750 square miles covering Baltimore County. The nominal pulse spacing for this project was 1 point every 0.7 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 0-Never Classified, 1-Unclassified, 2-Ground, 7-Low Noise, 9-Water, 10-Ignored Ground due to breakline proximity. Dewberry produced 3D breaklines and combined these with the final LiDAR data to produce seamless hydro-conditioned DEMs for the project area. The data was formatted according to the Baltimore County tile naming convention.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/Baltimore/MD_baltimore_dem_m/ImageServer

Disclaimer: These data are updated by the author and are not an official product of the Federal Reserve Bank of Cleveland.This project provides two sets of migration estimates for the major US metro areas. The first series measures net migration of people to and from the urban neighborhoods of the metro areas. The second series covers all neighborhoods but breaks down net migration to other regions by four region types: (1) high-cost metros, (2) affordable, large metros, (3) midsized metros, and (4) small metros and rural areas. These series were introduced in a Cleveland Fed District Data Brief entitled “Urban and Regional Migration Estimates: Will Your City Recover from the Pandemic?"The migration estimates in this project are created with data from the Federal Reserve Bank of New York/Equifax Consumer Credit Panel (CCP). The CCP is a 5 percent random sample of the credit histories maintained by Equifax. The CCP reports the census block of residence for over 10 million individuals each quarter. Each month, Equifax receives individuals’ addresses, along with reports of debt balances and payments, from creditors (mortgage lenders, credit card issuers, student loan servicers, etc.). An algorithm maintained by Equifax considers all of the addresses reported for an individual and identifies the individual’s most likely current address. Equifax anonymizes the data before they are added to the CCP, removing names, addresses, and Social Security numbers (SSNs). In lieu of mailing addresses, the census block of the address is added to the CCP. Equifax creates a unique, anonymous identifier to enable researchers to build individuals’ panels. The panel nature of the data allows us to observe when someone has migrated and is living in a census block different from the one they lived in at the end of the preceding quarter. For more details about the CCP and its use in measuring migration, see Lee and Van der Klaauw (2010) and DeWaard, Johnson and Whitaker (2019). DefinitionsMetropolitan areaThe metropolitan areas in these data are combined statistical areas. This is the most aggregate definition of metro areas, and it combines Washington DC with Baltimore, San Jose with San Francisco, Akron with Cleveland, etc. Metro areas are combinations of counties that are tightly linked by worker commutes and other economic activity. All counties outside of metropolitan areas are tracked as parts of a rural commuting zone (CZ). CZs are also groups of counties linked by commuting, but CZ definitions cover all counties, both metropolitan and non-metropolitan. High-cost metropolitan areasHigh-cost metro areas are those where the median list price for a house was more than $200 per square foot on average between April 2017 and April 2022. These areas include San Francisco-San Jose, New York, San Diego, Los Angeles, Seattle, Boston, Miami, Sacramento, Denver, Salt Lake City, Portland, and Washington-Baltimore. Other Types of RegionsMetro areas with populations above 2 million and house price averages below $200 per square foot are categorized as affordable, large metros. Metro areas with populations between 500,000 and 2 million are categorized as mid-sized metros, regardless of house prices. All remaining counties are in the small metro and rural category.To obtain a metro area's total net migration, sum the four net migration values for the the four types of regions.Urban neighborhoodCensus tracts are designated as urban if they have a population density above 7,000 people per square mile. High density neighborhoods can support walkable retail districts and high-frequency public transportation. They are more likely to have the “street life” that people associate with living in an urban rather than a suburban area. The threshold of 7,000 people per square mile was selected because it was the average density in the largest US cities in the 1930 census. Before World War II, workplaces, shopping, schools and parks had to be accessible on foot. Tracts are also designated as urban if more than half of their housing units were built before WWII and they have a population density above 2,000 people per square mile. The lower population density threshold for the pre-war neighborhoods recognizes that many urban tracts have lost population since the 1960s. While the street grids usually remain, the area also needs su

The Historical Urban Ecological (HUE) data project was created for exploring and analyzing the urban health environments of seven major United States cities - Baltimore, Boston, Brooklyn, Chicago, Cincinnati, Manhattan, and Philidelphia - from 1830 through 1930. The data for each city includes ward boundary changes, street networks, and ward-level data on disease, mortality, crime, and other variables reported by municipal departments. The HUE data set was produced for the "Early Indicators of Later Work Levels, Disease and Death" project, funded by the National Institute of Aging. This collection represents the GIS data for each of the seven American cities, and in addition to ward boundary changes and street networks, includes in-street sewer and water sanitation systems coverage. All cities except Cincinnati include sanitation infrastructure data, and for Baltimore only water infrastructure is available. The city of Chicago includes supplemental GIS layers which reflect a reconstruction of two of Homer Hoyt's maps of average land value (1933 dollars) in the City of Chicago for 1873 and 1892. The square mile areas defined by Hoyt using Chicago's system of mile streets have been fit to the HUE street centerlines for Chicago. The Excel data tables include information about deaths in each ward broken down by cause of death, age, race, gender, as well as information about live births and deliveries.

Aerial Cartographics of America (ACA) collected 750 square miles covering Baltimore County. The nominal pulse spacing for this project was 1 point every 0.7 meters. Dewberry used proprietary procedures to classify the LAS according to project specifications: 0-Never Classified, 1-Unclassified, 2-Ground, 7-Low Noise, 9-Water, 10-Ignored Ground due to breakline proximity. Dewberry produced 3D breaklines and combined these with the final LiDAR data to produce seamless hydro-conditioned DEMs for the project area. The data was formatted according to the Baltimore County tile naming convention.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/lidar/rest/services/Baltimore/MD_baltimore_dem_ft/ImageServer