The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.
Line feature showing the political boundary of Baltimore City. Last Updated 2008
This vector web map features outline maps of the World. The maps can be used for coloring and other fun activities by budding cartographers. These outline maps are great for teaching children about our World. Have them color and label countries, regions and bodies of water. Limited labels appear on the map at large scales. After coloring the city maps, children can do further research to learn more about these places. These maps are also available in a printable PDF format. See this blog with more details on how to work with the vector maps in ArcGIS Pro.For other creatively designed Esri vector basemaps, see the ArcGIS Living Atlas of the World gallery.
Geospatial data about Baltimore Metro - City of Baltimore Boundary. Export to CAD, GIS, PDF, CSV and access via API.
Line feature showing the political boundary of Baltimore City. Last Updated 2008
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2010 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
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.
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.
Neighborhoods within Baltimore City limits. This dataset was sourced from Baltimore Neighborhood Indicators Alliance (BNIA). No additional
metadata was provided with the dataset.
This is part of a collection of 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.
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
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
A map of all Baltimore City government entitie
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
Detailed street boundaries for Baltimore City. No metadata was provided with this dataset; the UVM Spatial Analysis Lab has attempted to evaluate this dataset and generate metadata. This dataset depicts the linear boundaries for street and paved areas in Baltimore City and has an extremely high degree of positional accuracy. For the best available transportation data use the Roads_GDT_MSA dataset. 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 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.
This map shows environmental resources and hazards in Baltimore City. Environmental resources may include parks, community gardens, food pantries, waterfront access points, and public transit stops, among others. Environmental hazards may include landfills, powerplants, Superfund sites, and combined sewer outfalls. This map also includes educational resources, community associations, environmental organizations, and coalitions which contribute to sustainability and community in Baltimore City.
This map is a project of the Living Classrooms Foundation. The Living Classrooms Foundation's mission is to strengthen communities and inspire children, youth, and adults to achieve their potential through hands-on education, workforce development, health and wellness, and community safety programs that use urban, natural, and maritime resources as "living classrooms." To learn more about LCF, visit https://livingclassrooms.org/. To make a comment or request an addition to the map, please contact bugs@livingclassrooms.org and GIS@baltimorecity.gov.Additionally, to leave feedback or ask a question, please fill out the following form: Baltimore Green Resource Map feedback form.Data compiled and mapped by Reilly Grzywacz on behalf of the Living Classrooms Foundation. Data sourced from Baltimore City, ArcGIS Public, US EPA, and web research.
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 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.
Attribution 3.0 (CC BY 3.0)https://creativecommons.org/licenses/by/3.0/
License information was derived automatically
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.
Detailed street boundaries for Baltimore City. No metadata was provided with this dataset; the UVM Spatial Analysis Lab has attempted to evaluate this dataset and generate metadata. This dataset depicts the linear boundaries for street and paved areas in Baltimore City and has an extremely high degree of positional accuracy. For the best available transportation data use the Roads_GDT_MSA dataset. 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.
Attribution 3.0 (CC BY 3.0)https://creativecommons.org/licenses/by/3.0/
License information was derived automatically
Line feature showing the political boundary of Baltimore City. Last Updated 2008
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.