Line feature showing the political boundary of Baltimore City. Last Updated 2008

Looking for information on a construction project near you? Project Portal offers a comprehensive view of all current, funded, and planned projects occurring across the State of Maryland. You can quickly and easily access specific project information, including a general overview, interactive map, news, schedule, pictures and video, supporting documents, and upcoming public meetings. It’s easy to search by location for a specific project, or by county for a list of all projects in your jurisdiction.(MDOT SHA Project Portal Individual Project Page Web Map)MDOT SHA WebsiteContact Us

This dataset represents computer generated intermediate contours at an interval of 2'. Feature capture rules: Intermediate Contours- Contour lines at the 2-foot interval. Intermediate Depression- Depression contour lines at the 2-foot interval Intermediate Indefinite - Intermediate contours obscured by vegetation, shadows or tall structures. Also includes contours in areas under disturbance Intermediate Depression Indefinite- Depression intermediate contours obscured by vegetation, shadows or tall structures Intermediate Hidden Contour lines behind index labels or inside buildings or bridges. Intermediate Hidden Depression - Contour Depression lines behind index labels or inside buildings or bridges. Intermediate Hidden Indefinite - Contour lines behind index labels or inside buildings or bridges and obscured by vegetation, shadows or tall structures. Intermediate Hidden Depression - Indefinite Contour depression lines behind index labels or inside buildings or bridges and obscured by vegetation, shadows or tall structures. Intermediate Non-Contour - Intermediate contours that fall in building structures and are estimated by the surrounding dtm. Intermediate Depression - Non-Contour Intermediate depression contours that fall in building structures and are estimated by the surrounding dtm. To leave feedback or ask a question about this dataset, please fill out the following form: Contours 2ft feedback form.

State of Maryland municipality boundary dataset.Maryland Department of Planning (MDP) maps annexations from municipalities. This dataset is created and maintained by the Maryland Department of Planning. These boundaries are not intended to serve as a legal description. Fields:MUN_NAME (Municipality Name): Name of Municipality located in Maryland.RESOLUTION_NUMBER (Resolution Number): Local Municipality Annexation Resolution Number.ANNEXATION_DATE (Annexation Date) (DD/MM/YYYY): The Annexation Date field shows when there's been a change in the boundary. This date is known as the “Effective Date” from the municipality. The date 1/1/1997 is used as a default date of when annexation changes were first indicated in the GIS layer and not necessarily of when it was actually annexed. If there's a date of 1/1/1997, it can be assumed that the annexation occurred on this date or before. For example, for Baltimore City, the city boundary was determined hundreds of years ago. Other than that default date, the date will show when the property was annexed. ACRES (GIS Acres): GIS calculated acres.JURSCODE (Jurisdiction Code) – Four letter county code: ALLE (Allegany), ANNE (Anne Arundel), BACI (Baltimore City), BACO (Baltimore County), CALV (Calvert), CARO (Caroline), CARR (Carroll), CECI (Cecil), CHAR (Charles), DORC (Dorchester), FRED (Frederick), GARR (Garrett), HARF (Harford), HOWA (Howard), KENT (Kent), MONT (Montgomery), PRIN (Prince George’s) QUEE (Queen Anne’s), SOME (Somerset), STMA (St. Mary’s), TALB (Talbot), WASH (Washington), WICO (Wicomico), WORC (Worcester).This is a MD iMAP hosted service. Find more information on https://imap.maryland.govhttps://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/FeatureServer/5

This map features satellite imagery for the world and high-resolution aerial imagery for many areas. The map is intended to support the ArcGIS Online basemap gallery. For more details on the map, please visit the World Imagery map service description.

Baltimore City’s Freight Network consists of linear features which represent the street centerlines of the official truck routes in the City of Baltimore, Maryland. The purpose of this data is to identify through, local, and restricted truck routes within Baltimore City. These routes specify where large trucks are allowed to drive, for the use by truck operators, trucking companies, and City transportation offices. The linear geometric features of this dataset were created by merging the National Highway Freight Network (NHFN) (https://ops.fhwa.dot.gov/freight/infrastructure/nfn/index.htm) with Baltimore City's Freight Network (data provided by the Baltimore City Department of Transportation). A “NHFN_ID” field is provided to distinguish City freight routes that are also a part of the NHFN. Annual Average Daily Traffic (AADT) values from 2017 are provided for each line segment where applicable. AADT values and percent utilization are provided for each vehicle classification (Motorcycle, Car, Light Truck, Single Unit Truck and Combination Unit Truck). A “Freight AADT” field and a “Freight Percent Utilization” field are also provided. Freight AADT was calculated by summing Single Unit Truck (FHWA Class 5 to 7) and Combination Unit Truck (FHWA Class 8 to 13) AADT values. Freight Percent Utilization was calculated by dividing the Freight AADT by the total AADT. Light Trucks (FHWA Class 3) were intentionally excluded from the Freight AADT and Freight Percent Utilization as these vehicles are not restricted to traversing on the City’s freight network. AADT data was obtained from the “Annual Average Daily Traffic - MDOT SHA Statewide AADT Lines” layer on MD iMAP (https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_AnnualAverageDailyTraffic/FeatureServer/1).

Every reasonable effort has been made to ensure the accuracy of these data. The City of Baltimore, Maryland makes no representations nor warranties, either expressed or implied, regarding the accuracy of this information or its suitability for any particular purpose whatsoever. The data is licensed "as is" and the City of Baltimore will not be liable for its use or misuse by any party. Reliance of these data is at the risk of the user.

Last updated: 10/07/2019

Qualified Census Tract geometries within Baltimore City Limits. Based on data from HUD published September 2024.Change Log2022-2-15:- Added FY2022 data- Metadata added- Columns renamed to a standard format- Agency names reformatted with Workday conventions2024-8-27:update the dataset and metadata to reflect the current data and descriptionData Dictionaryfield_namedescriptiondata_typerange_of_possible_valuesexample_valuessearchableCensus Tract 2010 The ID of the US census tract from 2010 Census results. Only Qualified Census tracts are includedTextIDs of QCT's in Baltimore city range from 24510030100 to 24510280500, but not by regular intervals since only tracts designated QCT are listed. The values are not integers, they are numerical IDs.24510070200NogeometryMulti-polygon shapes for each census tractThese are shape polygons, thus don't have a single value or expected rangeNo To leave feedback or ask a question about this dataset, please fill out the following form: Baltimore City Qualified Census Tracts feedback form.

This data set is a digital soil survey and generally is the most detailed level of soil geographic data developed by the National Cooperative Soil Survey. The information was prepared by digitizing maps, by compiling information onto a planimetric correct base and digitizing, or by revising digitized maps using remotely sensed and other information. This data set consists of georeferenced digital map data and computerized attribute data. The map data are in a 3.75 minute quadrangle format and include a detailed, field verified inventory of soils and nonsoil areas that normally occur in a repeatable pattern on the landscape and that can be cartographically shown at the scale mapped. A special soil features layer (point and line features) is optional. This layer displays the location of features too small to delineate at the mapping scale, but they are large enough and contrasting enough to significantly influence use and management. The soil map units are linked to attributes in the National Soil Information System relational database, which gives the proportionate extent of the component soils and their properties.

These data provide an accurate high-resolution shoreline compiled from imagery of Port of Baltimore, MD . This vector shoreline data is based on an office interpretation of imagery that may be suitable as a geographic information system (GIS) data layer. This metadata describes information for both the line and point shapefiles. The NGS attribution scheme 'Coastal Cartographic Object Attribut...

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.

This EnviroAtlas dataset shows the Baltimore, MD EnviroAtlas community boundary. It represents the outside edge of all the block groups included in the EnviroAtlas Community. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

The Colored Pencil Map (World Edition) web map provides a detailed vector basemap for the world symbolized with the appearance of being hand-drawn by colored pencils. The map includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, trees, and administrative boundaries. This basemap, included in the ArcGIS Living Atlas of the World, uses the Colored Pencil vector tile layer. The vector tile layer in this web map is built using the same data sources used for other Esri Vector Basemaps. For details on data sources contributed by the GIS community, view the map of Community Maps Basemap Contributors. Esri Vector Basemaps are updated monthly.Use this MapThis map is designed to be used as a basemap for overlaying other layers of information or as a stand-alone reference map. You can add layers to this web map and save as your own map. If you like, you can add this web map to a custom basemap gallery for others in your organization to use in creating web maps. If you would like to add this map as a layer in other maps you are creating, you may use the layer items referenced in this map.

This GIS dataset contains growth tier maps adopted by local (county and municipal) jurisdictions under SB236. Data are generally collected from county and municipal jurisdictions by the Maryland Department of Planning (Planning) or digitized by Planning in coordination with local jurisdictions. For more information about SB236, see Planning’s Septics Law Implementation Website at https://planning.maryland.gov/Pages/OurWork/SB236Implementation.aspxThis document describes standard operating procedures for aggregating growth tier map GIS data. These procedures may not apply to historical data (i.e. records for which both the SRC_DATE and GIS_SRC fields are blank). For example, Planning may have realigned historical data from local jurisdictions to parcel polygon boundaries or used different procedures to represent municipal tiers when municipalities concurred with county tier maps.Planning generally requests updated GIS data once a jurisdiction notifies Planning that a growth tier map has been amended. Aggregated data may be outdated or incomplete if Planning has not yet received or processed GIS updates from jurisdictions. Planning generally does not alter geometries received from the local jurisdictions except to divide municipal tiers at the county boundary (see JURSCODE field description). This dataset may contain overlap where multiple jurisdictions designate tiers in the same area.Fields include:JURSCODE – MdProperty Viewjurisdiction code (four-letter county or Baltimore City code). For tiers designated by counties, this is the jurisdiction responsible for designating the growth tier. For tiers designated by municipalities, this is the jurisdiction in which the growth tier is physically located. Municipal tiers that cross counties are divided at the county boundary so this field can be populated. See the MUNI field for the municipality responsible for designating a municipal tier.County – Full name of the jurisdiction represented by the JURSCODE.MUNI – The name of the municipality responsible for designating the tier. This field will be blank (‘ ‘) if the tier has been designated by a county. The MUNI field is formatted consistently with municipality names in the Planning’s municipal boundary datasets. When municipalities adopt tier maps by concurring with county tiers instead of submitting tier data independently, the MUNI field remains blank within the entire county tier map dataset. Depending on internal needs, an independent municipal tier dataset may or may not be generated by Planning and included within the aggregated tiers.TIER – Growth tier identifier used by the source jurisdiction and standardized as Tier 1, Tier 1A, Tier 2, Tier 2A, Tier 3, and Tier 4. May include additional alphabetical annotations used by the jurisdictions such as Tier 2B. If the TIER_CODE field is 99, the TIER field retains the descriptor provided by the jurisdiction, which may be a blank or null value.TIER_CODE – Integer field containing the growth tier standardized by Planning: 1 (Tier I); 11 (Tier IA or any other annotated version of Tier I, such as IB, etc.); 2 (Tier II), 22 (Tier IIA or any other annotated version of Tier II, such as IIB, etc.); 3 (Tier III); 4 (Tier IV); 44 (Areas annotated as Tier IVA for municipal greenbelts or any other annotated version of Tier IV); 99 – Areas included in the jurisdiction’s growth tier GIS data that are not assigned a tier, such as rights-of-way or water.Adopt_Date – Date growth tier map was adopted or amended. When a local jurisdiction updates its growth tier map, Planning generally requests a comprehensive GIS update to replace all existing data for the jurisdiction.Acres – GIS acres calculated by Planning in NAD83 Meters (EPSG 26985)GIS_SRC (GIS Source) – The original source of the GIS spatial and attribute information Planning obtained, which concatenates the JURSCODE field (or MUNI field for municipal tier maps), followed by a space, followed by the name of the shapefile or feature class received from the jurisdiction. Field contains “MDP” if tiers were digitized by Planning, and is blank (‘ ‘) for historical data.SRC_DATE (GIS Source Date) – The date (YYYYMMDD) the GIS data were obtained by Planning from the local jurisdiction. If the month or day is unknown, the date is YYYY0000. If Planning digitized the growth tier map in coordination with a local jurisdiction, this should be the date Planning’s edits are verified by the jurisdiction. This field will be blank (‘ ’) if Planning’s edits have not been verified or if the dataset is historical and the source is unknown.NOTE – Text field containing additional notes about the dataLast Updated: 7/26/2023This is a Maryland Department of Planning hosted service. Find more information on https://imap.maryland.govMap Service Link: https://mdpgis.mdp.state.md.us/arcgis/rest/services/PlanningCadastre/Septic_Growth_Tiers/MapServer

Maryland Transit Administration METRO routes. The 15.5-mile, 14-station Metro Subway system operates every. 8-10 minutes during the morning and evening peak periods; 11 minutes during weekday evenings; 15 minutes on Saturdays, Sundays and holidays. See http://mta.maryland.gov/metro-subway for more information.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_Transit/FeatureServer/5

This is the 2020 vintage of the 2020 TIGER/Line county boundary. It includes Anne Arundel County, Baltimore County, Baltimore City, Carroll County, Harford County, Howard County, and Queen Anne's County. Note this boundary is a new vintage of the TIGER file but is otherwise identical the the Census 2010 county boundary.Date: 1/21/2021 Update: Update: Irregular. While Census boundaries are updated every 10 years, the Census Bureau makes annual corrections to the geographies as needed. These updates are usually minor and BMC reviews them every few years.Source: Census TIGER/Line. More information on Census geography can be found at https://www.census.gov/geo/maps-data/data/tiger-line.html.

In 1984, the General Assembly enacted the Chesapeake Bay Critical Area Act to regulate development, manage land use and conserve natural resources on land in those areas designated as Critical Area. For this document, the Critical Area is all land and water areas within 1000 feet of the tidal waters' edge or from the landward edge of adjacent tidal wetlands and the lands under them. Georeferenced digital data files of the critical Area have been produced for Baltimore City and the 16 Maryland counties with land located within the Critical Area. The digital maps produced for each jurisdiction are polygons depicting the Critical Area and the land use classifications recognized by the Chesapeake Bay Critical Area Commission (CBCAC). Each jurisdiction is a separate file. The data were produced from hard copy parcel maps originally submitted by the counties as part of the requirements for developing their Critical Area Program. For the purpose of the MD iMap web service the Critical Area Data is displayed by two data layers, one general layer and one layer showing the available critical area data for local towns.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link: https://mdgeodata.md.gov/imap/rest/services/Environment/MD_CriticalAreas/MapServer/1

Urban area boundaries for 1801, part of the Baltimore-Washington Spatial Dynamics and Human Impacts dataset. The Baltimore-Washington Spatial Dynamics and Human Impacts dataset is an integrated and flexible temporal urban land characteristics database for the Baltimore-Washington metropolitan area. The compilation of this data is a collaborative effort led by the U.S. Geological Survey and the University of Maryland Baltimore County. The database provides visual and historical perspective of the urban growth experienced in the area between 1792 and 1992. Data on built-up areas exists as separate geographic layers for the dates: 1792, 1801, 1822, 1850, 1878, 1900, 1925, 1938, 1953, 1966, 1972, 1982, and 1992. Temporal urban mapping reconstructs past landscapes by incorporating historic maps, census statistics, and commerce records to generate a progressive geo-referenced picture of the past changes in a region. Contemporary mapping focuses on the use of remotely sensed data, existing digital land use data, digital census information, and a variety of earth science infrastructure data, such as Digital Line Graphs, Digital Elevation Models, and key ancillary demographic information. Different procedures were used for different time periods, more fully described for each file in the Process Step Section 2.5.2. The resulting database of temporal urban land use/land cover and demographic changes provides an ideal source of test data and information for both urban geographers and global change research scientists. While this dataset was developed by the University of Maryland Baltimore County final quality control and metadata generation was performed by the University of Vermont's Spatial Analysis Lab. Two significant problems were noted regarding this dataset. The first anomoly is that the 1801, 1822, and 1878 layers have a much smaller extent, and contain data only for Baltimore City. The second discrepancy is that there are also some very obvious positional errors causing misalignments between layers of different dates (i.e. urban areas become non-urban in a very short time period, an unlikely occurance). 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.

This EnviroAtlas dataset shows the Baltimore, MD EnviroAtlas community boundary. It represents the outside edge of all the block groups included in the EnviroAtlas Community. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

Urban area boundaries for 1966, part of the Baltimore-Washington Spatial Dynamics and Human Impacts dataset. The Baltimore-Washington Spatial Dynamics and Human Impacts dataset is an integrated and flexible temporal urban land characteristics database for the Baltimore-Washington metropolitan area. The compilation of this data is a collaborative effort led by the U.S. Geological Survey and the University of Maryland Baltimore County. The database provides visual and historical perspective of the urban growth experienced in the area between 1792 and 1992. Data on built-up areas exists as separate geographic layers for the dates: 1792, 1801, 1822, 1850, 1878, 1900, 1925, 1938, 1953, 1966, 1972, 1982, and 1992. Temporal urban mapping reconstructs past landscapes by incorporating historic maps, census statistics, and commerce records to generate a progressive geo-referenced picture of the past changes in a region. Contemporary mapping focuses on the use of remotely sensed data, existing digital land use data, digital census information, and a variety of earth science infrastructure data, such as Digital Line Graphs, Digital Elevation Models, and key ancillary demographic information. Different procedures were used for different time periods, more fully described for each file in the Process Step Section 2.5.2. The resulting database of temporal urban land use/land cover and demographic changes provides an ideal source of test data and information for both urban geographers and global change research scientists. While this dataset was developed by the University of Maryland Baltimore County final quality control and metadata generation was performed by the University of Vermont's Spatial Analysis Lab. Two significant problems were noted regarding this dataset. The first anomoly is that the 1801, 1822, and 1878 layers have a much smaller extent, and contain data only for Baltimore City. The second discrepancy is that there are also some very obvious positional errors causing misalignments between layers of different dates (i.e. urban areas become non-urban in a very short time period, an unlikely occurance). 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.

Tags

   soil survey, soils, Soil Survey Geographic, SSURGO




   Summary


   SSURGO depicts information about the kinds and distribution of

   soils on the landscape. The soil map and data used in the SSURGO

   product were prepared by soil scientists as part of the National

   Cooperative Soil Survey.


   Description


   This data set is a digital soil survey and generally is the most

   detailed level of soil geographic data developed by the National

   Cooperative Soil Survey. The information was prepared by digitizing

   maps, by compiling information onto a planimetric correct base

   and digitizing, or by revising digitized maps using remotely

   sensed and other information.


   This data set consists of georeferenced digital map data and

   computerized attribute data. The map data are in a 3.75 minute

   quadrangle format and include a detailed, field verified inventory

   of soils and nonsoil areas that normally occur in a repeatable

   pattern on the landscape and that can be cartographically shown at

   the scale mapped. A special soil features layer (point and line

   features) is optional. This layer displays the location of features

   too small to delineate at the mapping scale, but they are large

   enough and contrasting enough to significantly influence use and

   management. The soil map units are linked to attributes in the

   National Soil Information System relational database, which gives

   the proportionate extent of the component soils and their properties.


   Credits

   There are no credits for this item.


   Use limitations


   The U.S. Department of Agriculture, Natural Resources Conservation

   Service, should be acknowledged as the data source in products

   derived from these data.


   This data set is not designed for use as a primary regulatory tool

   in permitting or citing decisions, but may be used as a reference

   source. This is public information and may be interpreted by

   organizations, agencies, units of government, or others based on

   needs; however, they are responsible for the appropriate

   application. Federal, State, or local regulatory bodies are not to

   reassign to the Natural Resources Conservation Service any

   authority for the decisions that they make. The Natural Resources

   Conservation Service will not perform any evaluations of these maps

   for purposes related solely to State or local regulatory programs.


   Photographic or digital enlargement of these maps to scales greater

   than at which they were originally mapped can cause misinterpretation

   of the data. If enlarged, maps do not show the small areas of

   contrasting soils that could have been shown at a larger scale. The

   depicted soil boundaries, interpretations, and analysis derived from

   them do not eliminate the need for onsite sampling, testing, and

   detailed study of specific sites for intensive uses. Thus, these data

   and their interpretations are intended for planning purposes only.

   Digital data files are periodically updated. Files are dated, and

   users are responsible for obtaining the latest version of the data.


   Extent



   West -76.713689  East -76.526117 

   North 39.374398  South 39.194856 




   Scale Range

   There is no scale range for this item.