The Digital Geologic-GIS Map of the Port Tobacco Quadrangle, Maryland is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (poto_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (poto_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (poto_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (thst_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (thst_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (poto_geology_metadata_faq.pdf). Please read the thst_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Maryland Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (poto_geology_metadata.txt or poto_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

This is a comprehensive point theme that incorporates parcel ownership and address information, parcel valuation information and basic information about the land and structure(s) associated with a given tax assessment account. Data for the Parcel point theme are obtained from the State Department of Assessments and Taxation with added data from Maryland Department of Planning. The date the point was most recently published in Planning's data products MdProperty View and FINDER Quantum is contained in the mdpvdate field. The date of the most recent Assessments data linkage to MdProperty View/FINDER Quantum points is contained in the sdatdate field. Accounts deleted between those two dates are no longer represented as points. For more information on the attribute definitions please see the MdProperty View User's Guide, available for download at https://planning.maryland.gov/Pages/OurProducts/DownloadFiles.aspx . Please Note: Due to the extensive size of the parcel points file, download is recommended from the REST endpoint (https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/MapServer/exts/MDiMapDataDownload/customLayers/0)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/PlanningCadastre/MD_PropertyData/MapServer/0**Please note, due to the size of this dataset, you may receive an error message when trying to download the dataset. You can download this dataset directly from MD iMAP Services at: https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/MapServer/exts/MDiMAPDataDownload/customLayers/0**

This is a publicly available map image service with limited GIS attributes. A downloadable version of this data is now available through the MDOT GIS Open Data Portal: Download MDOT SHA Right-of-Way Polygons (Open Data Portal) The following related versions of this data are available here:MDOT SHA Right-of-Way (Secured)Line dataFull attribute tableAccessible to only MDOT employees and contractors upon requestMDOT SHA Right-of-Way (Map Image Service)Read-only map serviceLine dataLimited attributes (quality level)Accessible to publicMDOT SHA Right-of-Way data is a composite layer of PSD field-collected survey sources, PSD in-house computations, traced PSD hardcopy materials, and historical Maryland Department of Planning (MDP) parcel boundaries.This data product was intended to replace MDOT SHA Planning Level Right-of-Way (Tax Map Legacy), which is an increasingly obsolete legacy product for MDOT SHA Right-of-Way information that in some areas remains the most comprehensive. For continuity, many MDP parcel boundaries found in MDOT SHA Planning Level Right-of-Way (Tax Map Legacy) have been incorporated into MDOT SHA Right-of-Way data with an "Estimated" quality level. Please see below for a description of the primary attribute.-----------------------------------------------------The polygons in this layer are divided into 318 arbitrary grid zones across the State of Maryland. Updates to the parent ROW boundary line data set [MDOT SHA Right-of-Way (Secured)] are made by grid and reflected in this polygon layer.For more information or to report errors in this data, please contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

This Image Service of Maryland Property Data allows for the manipulation of the display properties of the Statewide Tax Maps dataset. This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Image Service Link: https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/ImageServer

This is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. This layer contains the boundaries and IDs of the Maryland tax maps produced by Maryland Department of Planning. Tax maps - also known as assessment maps - property maps or parcel maps - are a graphic representation of real property showing and defining individual property boundaries in relationship to contiguous real property. Last Updated: Feature Service Layer Link: https://mdgeodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/MapServer 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 is a link to the SpiresGIS General Map on Frederick City's website.

This is a MD iMAP hosted service. Find more information on http://imap.maryland.gov. The MD_Surface_Waters Feature Dataset includes 7 feature classes that geospatially depict the surface water bodies of Maryland. These feature classes are being provided so that data from the 2012 Integrated Report of Surface Water Quality can be displayed in geographic form for users of all levels. These different feature classes represent the different assessment unit scales utilized on the 2012 IR - some of which overlap in space. In addition - provided in the attribute tables for the Impoundments - Rivers_Streams - and Tidal_Waters feature classes is the use class designation as specified in COMAR Section 26.08.02.08. More information about these feature classes is contained in the metadata for each feature class. Map Service Link: http://mdewin64.mde.state.md.us/arcgis/rest/services/ MDE_Water_Quality/MD_IntegratedReportSurfaceWaterQuality_2013/MapServer 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 is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. In 1993 - the Maryland Department of Planning and the Maryland State Highway Administration entered into a Data Base Usage Agreement with Bell Atlantic and Data Chromatics - Inc. to develop an enhanced street address map for Maryland. ZIP Code boundary area files were one of the products derived from this partnership. The resulting boundary area files were intended to improve the cartographic quality and accuracy of the ZIP code boundary area files derived from the U.S. Census Bureau's post 1990 Census TIGER\Line Files (based on the Census Bureau's ZIP code tabulation areas - ZCTAs). Subsequent iterative improvements to the ZIP Code boundary area files have been made using premise address information associated with mapped parcel records as provided in the Maryland Department of Planning's MdProperty View GIS tax map and parcel record DVD product. The resulting files are meant to serve as a good approximation"" of ZIP codes as polygons (which in reality they are not) but are not official ZIP Code maps and are not meant to be a substitute for any products offered by the U.S. Postal Service - the official source for ZIP code information. While there are no restrictions on their use we do recommend that they are best used with MdProperty View and that MDP makes no guarantee or warranty regarding the files. Last Updated: 2012Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/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.

The Digital Geologic Map of Antietam National Battlefield and Vicinity, Maryland is composed of GIS data layers complete with ArcMap 9.3 layer (.LYR) files, two ancillary GIS tables, a Map PDF document with ancillary map text, figures and tables, a FGDC metadata record and a 9.3 ArcMap (.MXD) Document that displays the digital map in 9.3 ArcGIS. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey and Maryland Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation sections(s) of this metadata record (anti_metadata.txt; available at http://nrdata.nps.gov/anti/nrdata/geology/gis/anti_metadata.xml). All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.1. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.3 personal geodatabase (anti_geology.mdb), and as shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 18N. The data is within the area of interest of Antietam National Battlefield, as well as Chesapeake and Ohio Canal National Historical Park.

The Digital Geologic-GIS Map of Thomas Stone National Historic Site and Vicinity, Maryland and Virginia is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (thst_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (thst_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (thst_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) A GIS readme file (thst_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (thst_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (thst_geology_metadata_faq.pdf). Please read the thst_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey and Maryland Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (thst_geology_metadata.txt or thst_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

The Digital Geomorphic Map of Assateague Island National Seashore, Maryland and Virginia is composed of GIS data layers complete with ArcMap 9.3 layer (.LYR) files, two ancillary GIS tables, a Map PDF document with ancillary map text, figures and tables, a FGDC metadata record and a 9.3 ArcMap (.MXD) Document that displays the digital map in 9.3 ArcGIS. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation sections(s) of this metadata record (asis_metadata.txt; available at http://nrdata.nps.gov/asis/nrdata/geology/gis/asis_metadata.xml). All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.1. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.3 personal geodatabase (asis_geology.mdb), and as shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 18N. That data is within the area of interest of Assateague Island National Seashore.

Esri ArcGIS Online (AGOL) Feature Layer which provides access to the MDOT SHA Mile Points (1000th) data product.MDOT SHA Mile Points data consists of point geometric features which represent the measures that have been calibrated along each roadway throughout the State of Maryland. This layer specifically includes roadway segments that have been calibrated with measures that increase for every 1000th (0.001) of a mile along the roadway.MDOT SHA Mile Points data is owned and maintained by the MDOT SHA Office of Planning & Preliminary Engineering (OPPE), under the MDOT SHA Data Services Division (DSD). MDOT SHA Mile Points data is updated and published on an annual basis including data for the prior year.For more information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

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:Municipality Name: Name of Municipality located in Maryland.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). Last updated: 9/5/2024This is an MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_PoliticalBoundaries/FeatureServer/2

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.

The watershed data set contains areas of land that contribute runoff and groundwater into a specific stream system. This data set shows the Baltimore County portion of the State-defined Maryland "8-digit" watersheds*. There are 14 major watersheds in Baltimore County. The data was interpreted from Baltimore County's 1953 topographic maps and was delineated at 1:2400 scale.

*These features are not identical to the State-defined Maryland "8-digit" watersheds. The features were refined using 1953 topographic data and a larger delineation scale.

Road centerlines for Baltimore County, Maryland. Includes road names and road ranges.

These data were automated to provide an accurate high-resolution historical shoreline of Chesapeake Bay, Maryland suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://www.fisheries.noaa.gov/inport/item/39808

The Digital Geologic Map of Chesapeake and Ohio Canal National Historical Park and Vicinity, District of Columbia, Virginia, Maryland and West Virginia is composed of GIS data layers complete with ArcMap 9.3 layer (.LYR) files, two ancillary GIS tables, a Map PDF document with ancillary map text, figures and tables, a FGDC metadata record and a 9.3 ArcMap (.MXD) Document that displays the digital map in 9.3 ArcGIS. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey and Maryland Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation sections(s) of this metadata record (choh_metadata.txt; available at http://nrdata.nps.gov/choh/nrdata/geology/gis/choh_metadata.xml). All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.1. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.3 personal geodatabase (choh_geology.mdb), and as shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 18N. The data is within the area of interest of Chesapeake and Ohio Canal National Historical Park, as well as Antietam National Battlefield, Harpers Ferry National Historical Park, and George Washington Memorial Parkway.

The Digital Geologic Map of George Washington Memorial Parkway and parks in the National Capital Area, Virginia, Maryland, and the District of Columbia is composed of GIS data layers complete with ArcMap 9.3 layer (.LYR) files, two ancillary GIS tables, a Map PDF document with ancillary map text, figures and tables, a FGDC metadata record and a 9.3 ArcMap (.MXD) Document that displays the digital map in 9.3 ArcGIS. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey and Maryland Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation sections(s) of this metadata record (gwmp_metadata.txt; available at http://nrdata.nps.gov/gwmp/nrdata/geology/gis/gwmp_metadata.xml). All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.1. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.3 personal geodatabase (gwmp_geology.mdb), and as shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 18N. That data is within the area of interest of George Washington Memorial Parkway, Rock Creek Park, National Capital Parks-East, Greenbelt Park and Chesapeake and Ohio Canal National Historical Park.

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