This data was developed in response to citizens’ road maintenance requests from across the state as to whom to contact as the official maintenance authority - be it MDOT State Highway Administration, MDOT Transportation Authority, a county, or a municipality.MDOT SHA Website

The layer will be removed from the iMap Data Catalog in the near future. To access the most recent Baltimore City neighborhood data please visit https://data.baltimorecity.gov/datasets/baltimore::neighborhood-1.

This web map presents a vector basemap of OpenStreetMap (OSM) data hosted by Esri. Esri created this vector tile basemap from the Daylight map distribution of OSM data, which is supported by Facebook and supplemented with additional data from Microsoft. This version of the map is rendered using OSM cartography. The OSM Daylight map will be updated every month with the latest version of OSM Daylight data.OpenStreetMap is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap site:www.OpenStreetMap.org. Esri is a supporter of the OSM project and is excited to make this enhanced vector basemap available to the ArcGIS user and developer communities.

This dataset represents real property information within a parcel of land in the City of Baltimore. The data dictionary for this dataset can be accessed by visiting the following link.: Data Dictionary For Real Property Information | Open Baltimore (baltimorecity.gov). Data is updated on a weekly basis. To leave feedback or ask a question about this dataset, please fill out the following form: Real Property Information feedback form.

AT_2003_BACI_1 File Geodatabase Feature Class Thumbnail Not Available Tags There are no tags for this item. Summary There is no summary for this item. Description MD Property View 2003 A&T Database. For more information on the A&T Database refer to the enclosed documentation. This layer was edited to remove spatial outliers in the A&T Database. Spatial outliers are those points that were not geocoded and as a result fell outside of the Baltimore City Boundary; 416 spatial outliers were removed from this layer. The field BLOCKLOT2 can be used to join this layer with the Baltimore City parcel layer. Credits There are no credits for this item. Use limitations There are no access and use limitations for this item. Extent West -76.713418 East -76.526031 North 39.374429 South 39.197452

Parcels_PROW_LU_2003_BACI File Geodatabase Feature Class Thumbnail Not Available Tags BES, Parcel, Land Use, Urban, Land Summary BES research Description Parcel-based land use (LU) and public rights-of-way (PROW), for Baltimore City. Land use (LU) codes were obtained from the 2003 MD Property View A&Tdatabase. Credits Jarlath O'Neil-Dunne, UVM Spatial Analysis Lab Use limitations Approved BES research only Extent West -76.713449 East -76.525885 North 39.374474 South 39.195049 Scale Range There is no scale range for this item.

This feature class is a dataset based on liquor licenses as reported by Baltimore City Liquor License Board listing circa October 2004. This dataset includes the establishments that sell liquor in Baltimore, Maryland. Each establishment was geocoded by its street address. Those unable to be placed with a point by geocoding were given "U" for unmatched under the field "Status". Each establishment also has an associated liquor license particular to what type of alcohol is sold and the type of establishment. These liquor license types are defined by the Baltimore City Liquor License Board on their website, http://www.ci.baltimore.md.us/government/liquor. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

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

Parcels_2003_BACI File Geodatabase Feature Class Thumbnail Not Available Tags BES Summary There is no summary for this item. Description Parcel Data for Baltimore City obatined from BNIA will all extraneous fields removed. Editing in progress The following edits were performed: 1) Resolved edge matching issues with Baltimore County parcels that border it and fall within the Gwynns Falls Watershed. 2) BLOCKLOT errors were noted and if necessary corrected. The BLOCKLOT ID is used to link the parcel data to the MD Property View A&T database. It should be pointed out that in some instances a single BLOCKLOT ID in the Property View A&T database may correspond to more than one parcel. There are only 14 instances were a single BLOCKLOT ID corresponds to 4 or more parcels, these are typically railroads, utility, or government properties. In other cases a single BLOCKLOT ID may correspond to two separate parcels that are essentially one property bisected by a road. There are other instances where there appears no logical explanation for a single BLOCKLOT ID corresponding to multiple parcels. Credits UVM Spatial Analysis Lab Use limitations There are no access and use limitations for this item. Extent West -76.713328 East -76.525885 North 39.374474 South 39.195051 Scale Range There is no scale range for this item.

Property Variables for Baltimore City. The Property Variables dataset is a compilation of variables obtained from the MD Property View 2003 Database and derived from BES geospatial datasets. The points in this dataset were subsetted from the MD MD Property View 2003 A&T Database. The criteria used to select these points was: - Can be linked to parcel data using BLOCKLOT2 - LU = Residential (residential land use) - CONSIDR > 10,000 and < 1.5 million (purchase price greater than $10,000 and less than $1.5 million) - STRUDWEL = 01, 02 or 03 (single family home or townhome) - Sales Date after Jan 1 2001. - SQFTSTRUC > 100 (square footage of the structure greater than 100) - YEARBLT > 0 (valid year built). Please refer to the enclosed documentation for a complete data dictionary along with Austin Troy's original request document with comments by Jarlath O'Neil-Dunne.

Geospatial data about Baltimore Metro - City of Baltimore Boundary. Export to CAD, GIS, PDF, CSV and access via API.

This is a MD iMAP hosted service. Find more information on http://imap.maryland.gov. ' above published service description.A representation of the boundaries of Baltimore City neighborhoods. The data can be obtained from the Baltimore City Open Data Portal at https://data.baltimorecity.gov/Neighborhoods/Neighborhoods-Shape/ysi8-7icr. Map Service Link: http://geodata.md.gov/appdata/rest/services/ TrainingProgram/MD_BaltimoreCityNeighborhoods/FeatureServer ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

AT_2004_BACI File Geodatabase Feature Class Thumbnail Not Available Tags Socio-economic resources, Information, Social Institutions, Hierarchy, Territory, BES, Parcel, Property, Property View, A&T, Database, Assessors, Taxation Summary Serves as a basis for performing various analyses based on parcel data. Description Assessments & Taxation (A&T) Database from MD Property View 2004 for Baltimore City. The A&T Database contains parcel data from the State Department of Assessments and Taxation; it incorporates parcel ownership and address information, parcel valuation information and basic information about the land and structure(s) associated with a given parcel. These data form the basis for the 2004 Database, which also includes selected Computer Assisted Mass Appraisal (CAMA) characteristics, text descriptions to make parcel code field data more readily accessible and logical True/False fields which identify parcels with certain characteristics. Documentation for A&T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the A&T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A&T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the A&T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A&T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 379 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." Credits Maryland Department of Planning Use limitations BES use only. Extent West -76.713418 East -76.526031 North 39.374429 South 39.197452 Scale Range There is no scale range for this item.

Summary of Block Group level analyses for Baltimore City. This dataset contains block group level summary information for riparian vegetation, PROW (public right-of-way) vegetation, private land vegetation, and median age of homes. PRIZM codes are also present. The block group boundaries used in this dataset are from year 2000 GDT census data.

   The riparian analysis involved summarizing the riparian vegetation (forest and grass only) within a 100ft buffer of all 1:24K streams in Baltimore City for only those block groups that intersect the stream buffers. Vegetation data used in this analysis came from the 2001 MD DNR Forest Service IKONOS-derived Strategic Urban Forest Assessment (SUFA) vegetation layer. The amount of riparian forest, grass, and total vegetation was summarized on a block group level. In addition the percent riparian forest, grass, and total vegetation was summarized at block group level by dividing by the area of riparian land.


   The PROW analysis involved summarizing all PROW (non-parcel) vegetation (forest and grass) in Baltimore City. The PROW area consists of all roads and rights of way along roads. This area was delineated using Baltimore City parcel data by identifying all "non-parcel" areas. A cursory analysis of the "non-parcel" areas indicated that errors of omission were present due to insufficient parcel data. Vegetation data used in this analysis came from the 2001 MD DNR Forest Service IKONOS derived Strategic Urban Forest Assessment (SUFA) vegetation layer. The amount of urparian forest, grass, and total vegetation was summarized on a block group level. In addition the percent urparian forest, grass, and total vegetation was summarized at block group level by dividing by the area of urparian land.


   The private land area consists of all parcels not classified as "Exempt" or "Exempt Commerical." A cursory analysis of the parcel data indicated that errors of omission were present due to insufficient parcel data in certain block groups. Vegetation data used in this analysis came from the MD DNR Forest Service IKONOS derived Strategic Urban Forest Assessment (SUFA) vegetation layer. The amount of private land forest, grass, and total vegetation was summarized on a block group level. In addition the percent private land forest, grass, and total vegetation was summarized at block group level by dividing by the area of private land.


   PRIZM codes are generated from demographic and socioeconomic factors drawn from the U.S. Census data, the Claritas Company's PRIZM system classifies over 260,000 U.S. neighborhood markets into clusters. PRIZM codes can be linked with survey information. More information on PRIZM is available at http://www.clusterbigip1.claritas.com/claritas/Default.jsp?main=3&submenu=seg&subcat=segprizm.


   Median home age was summarized by block group from U.S. Census data.


   Credits

CAMA_2003_BACI_1

   File Geodatabase Feature Class


   Thumbnail Not Available

   Tags

   There are no tags for this item.




   Summary

   There is no summary for this item.


   Description


   MD Property View 2003 CAMA Database. For more information on the CAMA Database refer to the enclosed documentation. This layer was edited to remove spatial outliers in the CAMA Database. Spatial outliers are those points that were not geocoded and as a result fell outside of the Baltimore City Boundary. 254 spatial outliers were removed from this layer.


   Credits

   There are no credits for this item.


   Use limitations

   There are no access and use limitations for this item.


   Extent



   West -76.713415  East -76.526101 

   North 39.374324  South 39.200707 




   Scale Range

   There is no scale range for this item.

CAMA_2004_BACI File Geodatabase Feature Class Thumbnail Not Available Tags Socio-economic resources, Information, Social Institutions, Hierarchy, Territory, BES, Parcel, Property, Property View, CAMA, Database, Structure, Appraisal Summary Detailed structural information for parcels. Description The CAMA (Computer Assisted Mass Appraisal) Database is created on a yearly basis using data obtained from the State Department of Assessments and Taxation (SDAT). Each yearly download contains additional residential housing characteristics as available for parcels included in the CAMA Database and the CAMA supplementary databases for each jurisdiction.. Documentation for CAMA, including thorough definitions for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the CAMA Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the CAMA Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the CAMA Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the CAMA Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 235 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." Credits Maryland Department of Planning Use limitations BES use only. Extent West -76.713415 East -76.526101 North 39.374324 South 39.200707 Scale Range There is no scale range for this item.

Vegetation (trees and grass) for parcels defined as private land within Baltimore City. Private land parcels consisted of all those parcels with land use (LU) codes except for the category "Exempt Commercial" (EC). Roads had no LU codes. No parcels with the following LU codes were present in Baltimore City: agricultural (A), county club (CA), marsh land (MA), non-perc land (NP), and town house (TH). LU codes were determined from the Maryland Property View 2003 A&T database. A cursory analysis of the parcel data indicated that errors of omission were present due to insufficient parcel data in certain block groups. Vegetation data used in this analysis came from the MD DNR Forest Service IKONOS derived Strategic Urban Forest Assessment (SUFA) vegetation layer.

Areal summary of vegetation by census block group for Baltimore City. This dataset summarizes area occupied by vegetation (forest and grass) for every block group in Baltimore City. It also presents the normalized vegetaion area for each census block group. The area was normalized by taking the vegetation area and dividing it by the area of the block group. The vegetation data used in this dataset came from MD DNR's IKONOS derived SUFA vegetation layer. The census boundaries are from GDT's Dynamap census dataset.

SummaryThis data set shows building permits for the Baltimore metropolitan region. The data goes back to 2000 and is updated approximately once every two months. Expanded building permit data can be found at https://www.baltometro.org/community/data-maps/building-permit-data.DescriptionThe permits include any permit that is use code 40-48 (most new residential), 60-65 (mixed use), or is greater than or equal to $50,000. Historically, BMC receives the permits from participating jurisdictions and geocodes them. In recent years, some jurisdictions have started geocoding their own permits. When this is the case, BMC incorporates the geocoded points as given, and does not include them in its own geocoding process.Expanded building permit data can be found at https://www.baltometro.org/community/data-maps/building-permit-data.Layers:BPDS_Residential_New_ConstructionBPDS_Residential_AlterationsBPDS_Non_Residential_New_ConstructionBPDS_ Non_Residential _AlterationsBPDS_Mixed_Use_New_ConstructionThere is no layer for Mixed Use alterations; alterations to Mixed Use always get classified as Residential or Non-Residential.Field NamesField Name (alias)Descriptionpermit_no (County Permit ID)Original permit ID provided by the jurisdictionissue_dt (Date Permit Was Issued)Date the permit was issuedxcoord (X Coordinate)Longitude, in NAD 1983 decimal degreesycoord (Y Coordinate)Latitude, in NAD 1983 decimal degreessite_addr (Site Address)Address of the constructionzipcode (Site Zipcode)Zipcode of the constructionoffice (Office Number)This number corresponds to a jurisdiction and is used for BMC administrative recordspmt_use (Permit Use)Permit use code. A list of the values can be found at https://gis.baltometro.org/Application/BPDS/docs/BPDS_Permit_Use_Codes.pdfpmt_type (Permit Type)Permit type code. A list of the values can be found at https://gis.baltometro.org/Application/BPDS/docs/BPDS_Permit_Use_Codes.pdfdevelopment_name (Development Name / Subdivision)Subdivision name, if providedunit_count (Number of Units)Number of units, if provided. Only found in residential recordstenure (Tenure)If provided, indicates whether building is expected to be for rent or for sale after construction is complete. 1=For Rent, 2=For Saleamount (Amount)Estimated cost of constructionpmt_cat (Permit Category)Simplified classification of the pmt_use and pmt_type fieldsdescrip (Description)Description of construction, if providedJurisdiction (Jurisdiction)Jurisdiction (a county or city)Update CycleThe data is updated approximately once every three months.User NoteOver the years, building permit points were geocoded using a variety of software and reference data. The Baltimore Metropolitan Council made every effort to ensure accurate geocoding however there may be inaccuracies or inconsistencies in how the points were placed. For best results, the Baltimore Metropolitan Council recommends aggregating the building permit points to a larger geography (ex. Census tract, zip code) when analyzing the data.Data Access InstructionsTo download the data or access it via API, visit https://gisdata.baltometro.org/.Technical ContactFor questions or comments, contact Erin Bolton, GIS Coordinator, at ebolton@baltometro.org or 410-732-0500.

Baltimore City boundary limits. This is the "official" city boundary used by many Baltimore agencies. It DOES NOT agree with the universal MSA boundaries dervied from GDT census data.

   This is part of a collection of Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase itself is available online at beslter.org or lternet.edu. It is considerably large. Upon request, it can be shipped to you on media, such as a flash drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.