Download .zipThe A Law Coal Permit Maps county coverage sets were developed using the original mine maps for coal mining and reclamation permits issued under Ohio law from approximately 1966 through 1973. Approximately 1111 A-Permits were issued during this time period, however, only 350 records could be located and captured at this time. The Division of Mineral Resources Management will continue to search for missing A permit archival records as resources allow; additional A permit data may be added to this existing coverage in the future.

Ohio started issuing coal mining licenses in the 1940s. The earliest license and permit requirements were minimal and sometimes did not include submittal of a map or other delineation of the mined area. Significant changes to legal requirements are reflected by the alphabetical designation of each subsequent law revision, i.e., earlier A-law permits (circa 1966) through contemporary D-law permits. The ODNR-Division of Mineral Resources Management (DMRM) has attempted to create as complete a database as possible from available archive records, however, research has identified missing permit files. Thus, this GIS data is known to be incomplete due to the loss of archival records.

The A law permit maps were scanned at a density of 200 dots per inch (dpi). The scanned image was then heads-up digitized using Microstation computer aided design software (CAD) to create design files grouped by county location. Data captured within the design file includes permit boundary and affected boundary and associated attributes. When available, test hole locations and associated attributes were also captured. The design file was then "placed-to-ground" using ODNR Division of Geological Survey's "ODNR Land Subdivision Background Design Files" NAD83 State Plane coverages and DOQQ aerial images obtained through the Ohio Geographically Referenced Information Program (OGRIP)/Ohio Department of Administrative Services. The design file was then converted to ARC/INFO coverage and projected to State Plane Ohio Coordinates, NAD83:

Projected coordinate system name: NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet or NAD_1983_StatePlane_Ohio_North_FIPS_3401_Feet

Geographic coordinate system name: GCS_North_American_1983

A complete county coverage set consists of three data files for the permit area, affected area, and test hole locations. For example, the coverage for Harrison County includes:

harrison_a_permitted (Harrison County, A-permit area polygons) harrison_a _affected (Harrison County, A-permit affected area polygons) harrison_testholes_a (Harrison County, Test Hole points)

In addition to the ArcView shape files in the county data sets, the scanned TIF images for source documents are available at DMRM. The scanned mine map depicts information about the operations conducted, environmental resources, and extracted coal resources. If more detailed information is desired, the available archival record for each captured permit can be accessed at either the State Archives at the Ohio Historical Society or the ODNR-DMRM central office.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Mineral Resources ManagementAbandoned Mine Land Program2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

AT_2004_CARR 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 Carroll County. 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 848 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 -77.306843 East -76.779275 North 39.727017 South 39.342858 Scale Range There is no scale range for this item.

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. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

CAMA_2004_CARR 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 399 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 -77.306843 East -76.779379 North 39.727017 South 39.346946 Scale Range There is no scale range for this item.

Download .zipA potentiometric surface map is a contour map that represents the top of the ground water surface in an aquifer. The contour lines illustrate the potentiometric surface much like the contour lines of a topographic map represent a visual model of the ground surface. A potentiometric surface map is very similar to a water table map in that both show the horizontal direction and gradient of ground water flow.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Geological Survey2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6693Email: gis.support@dnr.ohio.gov

FEMA Framework Basemap datasets comprise six of the seven FGDC themes of geospatial data that are used by most GIS applications (Note: the seventh framework theme, orthographic imagery, is packaged in a separate NFIP Metadata Profile): cadastral, geodetic control, governmental unit, transportation, general structures, hydrography (water areas & lines). These data include an encoding of the geographic extent of the features and a minimal number of attributes needed to identify and describe the features. (Source: Circular A16, p. 13)

Download .zipThe B Law Coal Permit Maps county coverage sets were developed using the original mine maps for coal mining and reclamation permits issued under Ohio law from 1973 through 1976. Approximately 1285 B-Permits were issued during this time period, however, only approximately 414 records could be located and captured at this time. The Division of Mineral Resources Management will continue to search for missing B permit archival records as resources allow; additional B permit data may be added to this existing coverage in the future.

Ohio started issuing coal mining licenses in the 1940s. The earliest license and permit requirements were minimal and sometimes did not include submittal of a map or other delineation of the mined area. Significant changes to legal requirements are reflected by the alphabetical designation of each subsequent law revision, i.e., earlier A-law permits (circa 1966) through contemporary D-law permits. The ODNR-Division of Mineral Resources Management (DMRM) has attempted to create as complete a database as possible from available archive records, however, research has identified missing permit files. Thus, this GIS data is known to be incomplete due to the loss of archival records.

The B law permit maps were scanned at a density of 200 dots per inch (dpi). The scanned image was then heads-up digitized using Microstation computer aided design software (CAD) to create design files grouped by county location. Data captured within the design file includes permit boundary, affected boundary, test hole locations, and associated attributes. The design file was then "placed-to-ground" using ODNR Division of Geological Survey's "ODNR Land Subdivision Background Design Files" NAD83 State Plane coverages and DOQQ aerial images obtained through the Ohio Geographically Referenced Information Program (OGRIP)/Ohio Department of Administrative Services. The design file was then converted to ARC/INFO coverage and projected to State Plane Ohio Coordinates, NAD83:

Projected coordinate system name: NAD_1983_StatePlane_Ohio_South_FIPS_3402_Feet

Geographic coordinate system name: GCS_North_American_1983

A complete county coverage set consists of three data files for the permit area, affected area, and test hole locations. For example, the coverage for Belmont County includes:

belmont_b_permitted (Belmont County, B-permit area polygons) belmont_b _affected (Belmont County, B-permit affected area polygons) belmont_testholes_b (Belmont County, Test Hole points)

In addition to the ArcView shape files in the county data sets, the scanned TIF images for source documents are available at DMRM. The scanned mine map depicts information about the operations conducted, environmental resources, and extracted coal resources. If more detailed information is desired, the available archival record for each captured permit can be accessed at either the State Archives at the Ohio Historical Society or the ODNR-DMRM central office.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Mineral Resources ManagementAbandoned Mine Land Program2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Carroll County Developments In Process

Assessments and Taxation (A and T) Database from MD Property View 2004 for Carroll County. The A and 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 and 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 and T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A and 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 and 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 and 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 848 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." 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.

Parcels subject to residenital development plans currently under review in Carroll County, Maryland

Park Sites and Trails in Carroll County, Maryland

Download .zipA potentiometric surface map is a contour map that represents the top of the ground water surface in an aquifer. The contour lines illustrate the potentiometric surface much like the contour lines of a topographic map represent a visual model of the ground surface. A potentiometric surface map is very similar to a water table map in that both show the horizontal direction and gradient of ground water flow.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Geological Survey2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6693Email: gis.support@dnr.ohio.gov

Download .zipMaps and data associated with oil-and-gas wells represent one of the largest datasets at the Ohio Department of Natural Resources. This GIS data layer contains all the locatable oil-and-gas wells in Ohio. The feature is derived from coordinates obtained from the Division of Oil and Gas Resources Management (DOGRM) oil and gas well database – Risk Based Data Management System (RBDMS). The RBDMS database has a long history and is a comprehensive collection of well data from historic pre-1980 paper well records (digitized by the Division of Geological Survey (DGS)) to post-1980 DOGRM database solutions.Since 1860, it is estimated that more than 267,000 oil-and-gas wells have been drilled in Ohio. The compressed file also includes a feature used to connect the surface location to the bottom location of a well that has been drilled directionally or horizontally. This feature is NOT the actual wellbore path, it is simply a graphical representation indicating the relationship between the two well points.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Oil & Gas ResourcesOil and Gas Resources Management2045 Morse Road Bldg F-2Columbus, OH, 43229-6693Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Tags survey, environmental behaviors, lifestyle, status, PRIZM, Baltimore Ecosystem Study, LTER, BES Summary BES Research, Applications, and Education Description XY Positions for BES telephone survey. The BES Household Survey 2003 is a telephone survey of metropolitan Baltimore residents consisting of 29 questions. The survey research firm, Hollander, Cohen, and McBride conducted the survey, asking respondents questions about their outdoor recreation activities, watershed knowledge, environmental behavior, neighborhood characteristics and quality of life, lawn maintenance, satisfaction with life, neighborhood, and the environment, and demographic information. The data from each respondent is also associated with a PRIZM� classification, census block group, and latitude-longitude. PRIZM� classifications categorize the American population using Census data, market research surveys, public opinion polls, and point-of-purchase receipts. The PRIZM� classification is spatially explicit allowing the survey data to be viewed and analyzed spatially and allowing specific neighborhood types to be identified and compared based on the survey data. The census block group and latitude-longitude data also allow us additional methods of presenting and analyzing the data spatially. The household survey is part of the core data collection of the Baltimore Ecosystem Study to classify and characterize social and ecological dimensions of neighborhoods (patches) over time and across space. This survey is linked to other core data including US Census data, remotely-sensed data, and field data collection, including the BES DemSoc Field Observation Survey. The BES 2003 telephone survey was conducted by Hollander, Cohen, and McBride from September 1-30, 2003. The sample was obtained from the professional sampling firm Claritas, in order that their "PRIZM" encoding would be appended to each piece of sample (telephone number) supplied. Mailing addresses were also obtained so that a postcard could be sent in advance of interviewers calling. The postcard briefly informed potential respondents about the survey, who was conducting it, and that they might receive a phone call in the next few weeks. A stratified sampling method was used to obtain between 50 - 150 respondents in each of the 15 main PRIZM classifications. This allows direct comparison of PRIZM classifications. Analysis of the data for the general metropolitan Baltimore area must be weighted to match the population proportions normally found in the region. They obtained a total of 9000 telephone numbers in the sample. All 9,000 numbers were dialed but contact was only made on 4,880. 1508 completed an interview, 2524 refused immediately, 147 broke off/incomplete, 84 respondents had moved and were no longer in the correct location, and a qualified respondent was not available on 617 calls. This resulted in a response rate of 36.1% compared with a response rate of 28.2% in 2000. The CATI software (Computer Assisted Terminal Interviewing) randomized the random sample supplied, and was programmed for at least 3 attempted callbacks per number, with emphasis on pulling available callback sample prior to accessing uncalled numbers. Calling was conducted only during evening and weekend hours, when most head of households are home. The use of CATI facilitated stratified sampling on PRIZM classifications, centralized data collection, standardized interviewer training, and reduced the overall cost of primary data collection. Additionally, to reduce respondent burden, the questionnaire was revised to be concise, easy to understand, minimize the use of open-ended responses, and require an average of 15 minutes to complete. The household survey is part of the core data collection of the Baltimore Ecosystem Study to classify and characterize social and ecological dimensions of neighborhoods (patches) over time and across space. This survey is linked to other core data, including US Census data, remotely-sensed data, and field data collection, including the BES DemSoc Field Observation Survey. Additional documentation of this database is attached to this metadata and includes 4 documents, 1) the telephone survey, 2) documentation of the telephone survey, 3) metadata for the telephone survey, and 4) a description of the attribute data in the BES survey 2003 survey. This database was created by joining the GDT geographic database of US Census Block Group geographies for the Baltimore Metropolitan Statisticsal Area (MSA), with the Claritas PRIZM database, 2003, of unique classifications of each Census Block Group, and the unique PRIZM code for each respondent from the BES Household Telephone Survey, 2003. The GDT database is preferred and used because of its higher spatial accuracy than other databases describin... Visit https://dataone.org/datasets/https%3A%2F%2Fpasta.lternet.edu%2Fpackage%2Fmetadata%2Feml%2Fknb-lter-bes%2F337%2F610 for complete metadata about this dataset.

Download .zipThis coverage was extracted from the 1994 statewide land cover inventory of Ohio produced by Bruce R. Motsch and Gary M. Schaal of the Ohio Department of Natural Resources.

The land cover inventory for the State of Ohio was produced by the digital image processing of Landsat Thematic Mapper Data. The Thematic Mapper is a multi-spectral scanner that collects electromagnetic radiation reflected from the earth's surface in the visible, near infrared and mid-infrared wavelength bands. The resolution of the Thematic Mapper data is a 30 meter by 30 meter cell. The computer analysis of the data isolates unique spectral classes that relate to land cover characteristics.

The land cover inventory was produced from Thematic Mapper data acquired in September and October 1994. The data was classified into the general land cover categories of urban, agriculture/open urban areas, shrub/scrub, wooded, open water, non-forested wetlands and barren.

The land cover information reflects the conditions of the satellite data during the specific year and season the data was acquired. The Thematic Mapper data was processed using ERDAS image processing software. The data was originally created in raster format and georeferenced to Universal Transverse Mercator (UTM) zone 17 coordinates NAD27. The data can be combined with other georeferenced digital data layers.

The data is also available in its original ERDAS image format.

Original coverage data was converted from the .e00 file to a more standard ESRI shapefile(s) in November 2014.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesReal Estate & Land ManagementReal Estate and Lands Management2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

Download .zipThis coverage land represents an interpretation of land use and land cover types done from aerial photography by Tom Eller, Remote Sensing Unit, Division of Soil and Water Conservation. For an explanation of categories see Ohio Land Use/ Cover Classifications System, Misc. Report 17 available upon request, or at http://apps.ohiodnr.gov/geodata/documents/Ohio_LULC_Misc_Report17.pdf . This publication is keyed to the four digit code found in the OCAPCODE item name code description.

This coverage was digitized from Land Use/ Land Cover drafted onto USGS quadrangle maps utilizing a run length encoding technique sampling along horizontal lines which represent the midline of cells with a height of 250 feet . The measurement increment along these horizontal lines was one decafoot (10 feet) the quadrangle files were then merged into a county file which was subsequently converted to ARC / Info format.

The user should bear in mind that this coverage is only an approximation of the Land Use / Land Cover as drafted. Blue line copies of the original Land Use / Land Cover interpretation can be provided for a nominal charge.

Additional details on the digitizing process are available on request.

Original coverage data was converted from the .e00 file to a more standard ESRI shapefile(s) in November 2014.Contact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesReal Estate & Land ManagementReal Estate and Lands Management2045 Morse Rd, Bldg I-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov

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

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/Carroll/MD_carroll_shadedRelief_RGB/ImageServer

Polygon features that represent the political boundaries of Metropolitan Planning Organizations (MPO) that exist in Maryland and for which the Maryland Department of Transportation (MDOT) is a member. In several instances, these MPO boundaries extend beyond Maryland’s borders into neighboring states as well as the District of Columbia. MPO Boundaries’ data includes information on each boundary's name, geographic location, and the total size / extent of each area. MPO Boundaries data was intended to be used for planning purposes within governments at the National and State level. Maryland's MPO Boundaries data is a sub-set of the U.S. Department of Transportation (USDOT) Office of the Assistant Secretary for Research and Technology's Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). A metropolitan planning organization (MPO) is a federally-mandated and federally-funded transportation policy-making organization that is made up of representatives from local governments and governmental transportation authorities. Federal law requires the formation of an MPO for any urbanized area (UZA) with a population greater than 50,000. Federal funding for transportation projects and programs are channeled through this planning process. Congress created MPOs to ensure that existing and future expenditures of federal funds for transportation projects and programs are based on a continuing, cooperative, and comprehensive (“3‑C”) planning process. MPOs are charged with developing a 20-year long-range transportation plan (LRTP) and a short-term (usually 2-6 years) program called the transportation improvement program (TIP) for each of their respective regions. The seven MPOs of which Maryland jurisdictions and agencies are members are listed below. The Maryland member jurisdictions are listed under each MPO (note that some MPOs cover multi-State regions). The Maryland Department of Transportation is a member of each of the MPOs listed. Each of the listed member jurisdictions has a different level of involvement with its MPO.Maryland's MPOs are as follows: National Capital Region Transportation Planning Board (TPB)https://www.mwcog.org/tpb/- Charles County, Maryland- Frederick County, Maryland- Montgomery County, Maryland- Prince George's County, Maryland- City of Bowie, Maryland- City of College Park, Maryland- City of Frederick, Maryland- City of Gaithersburg, Maryland- City of Greenbelt, Maryland- City of Laurel, Maryland- City of Rockville, Maryland- City of Takoma Park, Maryland- Maryland Department of Transportation (MDOT)Baltimore Regional Transportation Board (BRTB)https://baltometro.org/- Anne Arundel County, Maryland- Baltimore County, Maryland- Carroll County, Maryland- Harford County, Maryland- Howard County, Maryland- Queen Anne's County, Maryland- City of Annapolis, Maryland- City of Baltimore, Maryland- Maryland Department of Transportation (MDOT)Cumberland Area Metropolitan Planning Organization (CAMPO)https://alleganygov.org/473/Metropolitan-Planning-Organization- Allegany County, Maryland- City of Cumberland, Maryland- City of Frostburg, Maryland- Maryland Department of Transportation (MDOT)Hagerstown / Eastern Panhandle Metropolitan Planning Organization (HEPMPO)https://www.hepmpo.net/- Washington County, Maryland- City of Hagerstown, Maryland- Maryland Department of Transportation (MDOT)Wilmington Area Planning Council (WILMAPCO)https://www.wilmapco.org/- Cecil County, Maryland- Maryland Department of Transportation (MDOT)Salisbury / Wicomico Metropolitan Planning Organization (S / WMPO)https://www.swmpo.org/- Wicomico County, Maryland- City of Fruitland, Maryland- City of Salisbury, Maryland- Town of Delmar, Maryland- Maryland Department of Transportation (MDOT)Calvert-St. Mary’s Metropolitan Planning Organization (C - SMMPO)https://www.calvert-stmarysmpo.com/- Calvert County, Maryland- St. Mary's County, Maryland- Maryland Department of Transportation (MDOT)Maryland's MPO Boundaries data is owned and maintained by the Transportation Secretary's Office (TSO) of the Maryland Department of Transportation (MDOT). Being a subset of the USDOT's NTAD, an annual update of Maryland's MPO Boundaries data is performed by TSO in close coordination with each MPO, the Maryland Department of Transportation State Highway Administration (MDOT SHA) and the Federal Highway Administration (FHWA). MPO Boundaries data is a strategic resource for the USDOT, FHWA, MDOT, as well as many other Federal, State, and local government agencies. Maryland's MPO Boundaries data is updated on an annual basis. For additional MPO information, contact MDOT's Office of Planning and Capital Programming:MDOTGIS@mdot.state.md.usFor additional data information, contact the MDOT SHA Geospatial Technologies Team:GIS@sha.state.md.usFor additional information related to the Maryland Department of Transportation (MDOT):https://www.mdot.maryland.gov/For additional information related to the Maryland Department of Transportation State Highway Administration (MDOT SHA):https://www.roads.maryland.gov/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/BusinessEconomy/MD_IncentiveZones/FeatureServer/13