- API
MD iMAP: Maryland Shoreline Changes - Transects
opendata.maryland.gov | Last Updated 2020-01-25T00:14:41.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. To quantify rates of change (erosion or accretion) along coastal and estuarine shorelines in Maryland - the Maryland Geological Survey (MGS) - in conjunction with Towson University's Center for Geographic Information Sciences (CGIS) and the U.S. Geological Survey (USGS) - installed and ran a computer program - the Digital Shoreline Analysis System (DSAS) - using as input a series of digital shoreline vectors dating from 1841-1995. Shorelines were derived from three sources: (1) maps from a Historical Shorelines and Erosion Rates Atlas (Conkwright - 1975) - (2) Coastal Survey maps (topographic or T-sheets) produced by the National Ocean Service (NOS) - a branch of the National Oceanic and Atmospheric Administration (NOAA) - and (3) a digital wetlands delineation based on photo interpretation of digital orthophoto quarter quads. DSAS constructed a 'baseline' landward of and approximately parallel to the shorelines - inserted nodes every 20 m along the baseline - and cast straight-line transects from each node - perpendicular to the baseline - across the shorelines. Based on the time elapsed and the along-transect distance between shoreline pairs - DSAS calculated rates of change for each transect. Last Updated: Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Hydrology/MD_ShorelineChanges/MapServer/0 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.
- API
MD iMAP: Maryland Finfish - Fishing Grounds
opendata.maryland.gov | Last Updated 2020-01-25T00:31:36.000ZThis is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. Dataset shows popular recreational fishing spots in the Maryland portion of the Chesapeake Bay. Fishing areas were derived from the publication Anglers' Guide to the United States Atlantic Coast - Fish - Fishing Grounds & Fishing Facilities""and from personal communication with Keith Lockwood - MDNR - Fisheries Service in June 2000.Last Update: 05/2014Feature Service Link:http://geodata.md.gov/imap/rest/services/Biota/MD_Finfish/FeatureServer/10 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.
- API
MD iMAP: Maryland Recreational Uses - Winter Sports
opendata.maryland.gov | Last Updated 2020-01-25T00:19:42.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. These baseline recreational use data will inform planning efforts being undertaken by the Maryland Department of Natural Resources to help inform public access - land acquisition - future planning and decision-making. Collecting data on the variety of ways the Chesapeake waters and surrounding lands are used will help us plan for reducing use conflicts in our coastal waters - maximizing efficiency - and enhancing environmental and economic productivity. Chesapeake Bay waters are used in many ways: commercial fishing - aquaculture - transport - habitat for wildlife - and recreation - among others. With new and expanding coastal and marine uses - as well as Maryland's growing coastal population - the pressure is mounting to ensure that there is space for both traditional and new uses and that conflicts are minimized. Some mapped human use data exist - but Maryland has limited recreational water use data for the Chesapeake waters. Basic data on how we use our coastal waters was collected by inviting residents and experts to share their knowledge about recreational uses at workshops using geographical information systems technology. Last Updated: 07/01/2014 Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Society/MD_RecreationalUses/FeatureServer/51 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.
- API
MD iMAP: Maryland Offshore Wind Energy Planning - Waterbird Habitat and Density
opendata.maryland.gov | Last Updated 2020-01-25T00:23:31.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. This data layer contains waterbird density blocks extracted from the Minerals Management Service's Mid-Atlantic Waterbird Data Beta Version 1.0. This application is based on their Marine Mammal and Seabird Computer Database Analysis System (MMS-CDAS). The origin of the underlying data is a U.S. Fish & Wildlife Service aerial survey conducted between December - 2001 and March - 2003. The source data were collected on-transect (120m width - 60 m each side) for transects conducted in the mouth of Chesapeake Bay - in Delaware Bay - and in offshore waters from the beach outward. Aerial surveys of waterbirds were flown to at least 12 nautical miles (22.2 km) offshore from northern New Jersey to the Virginia / North Carolina border. All waterbird species in the USFWS database from winter surveys only were exported to density blocks. Information in the MMS application suggests the winter surveys only are valid for calculating densities because they were flown on specific transects. The spatial extent of the database (and thus of this data set) is from the Virginia/North Carolina border to the Hudson Canyon (including Delaware Bay and the lowest part of Chesapeake Bay). Last Updated: Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/UtilityTelecom/MD_OffshoreWindEnergyPlanning/FeatureServer/3 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.
- API
GOPI Resource: Percentage of Current Support Paid
opendata.maryland.gov | Last Updated 2023-11-20T17:35:34.000ZCHILD SUPPORT ENFORCEMENT ADMINISTRATION The performance measures are used to evaluate each State's performance and measure results in the Child Support Enforcement program. These measures emphasize paternity establishment, support order establishment, collection of current support, collection of arrearages, and cost effectiveness. The performance measures, except cost effectiveness which can only be measured annually, are calculated from data which is reported on federal form OCSE 157. CASES WITH SUPPORT ORDERS This metric measures the proportion of IV-D cases with support orders established. Equation: Number of IV-D Cases with Support Orders divided by Total Number of IV-D Cases IV-D Paternity Establishment Percentage: This metric measures the proportion of children in the IV-D caseload as of the end of the preceding FFY who were born out of wedlock is the total number of children in the IV-D caseload in the federal fiscal year born out of wedlock with paternity established or acknowledged divided by the total number of children in the IV-D caseload as of the end of the preceding FFY who were born out of wedlock. . Equation: Total # of Children in IV-D Caseload in the Federal Fiscal Year or, as of the end of the Fiscal Year who were born out of wedlock with Paternity Established or Acknowledged divided by Total # of Children in IV-D Caseload as of the end of the preceding Federal Fiscal Year who were Born Out of Wedlock COLLECTIONS ON CURRENT SUPPORT This measure focuses on the proportion of current support due that is collected on IV-D cases. Equation: Total Dollars Collected for Current Support in IV-D Cases during the Federal Fiscal Year divided by Total Dollars Owed for Current Support in IV-D Cases during the Federal Fiscal Year COLLECTIONS ON ARREARS The measure assesses efforts to collect money from those cases with an arrearage due. The measure specifically counts paying cases, and not total arrears dollars collected. Equation: Total number of IV-D cases paying toward arrears during the Federal Fiscal Year divided by Total number of IV-D cases with arrears due
- API
Total Acres Preserved in Maryland Counties by Program
opendata.maryland.gov | Last Updated 2024-02-29T15:09:22.000ZLand preservation data shows acres preserved by federal, state, and local programs that either acquire land preservation easements or acquire land in fee; data for each program is provided for each of Maryland’s 23 counties and Baltimore City.
- API
Department of Human Services(DHS): Child Support Enforcement Administration Performance Measures
opendata.maryland.gov | Last Updated 2023-11-20T17:35:34.000ZCHILD SUPPORT ENFORCEMENT ADMINISTRATION The performance measures are used to evaluate each State's performance and measure results in the Child Support Enforcement program. These measures emphasize paternity establishment, support order establishment, collection of current support, collection of arrearages, and cost effectiveness. The performance measures, except cost effectiveness which can only be measured annually, are calculated from data which is reported on federal form OCSE 157. CASES WITH SUPPORT ORDERS This metric measures the proportion of IV-D cases with support orders established. Equation: Number of IV-D Cases with Support Orders divided by Total Number of IV-D Cases IV-D Paternity Establishment Percentage: This metric measures the proportion of children in the IV-D caseload as of the end of the preceding FFY who were born out of wedlock is the total number of children in the IV-D caseload in the federal fiscal year born out of wedlock with paternity established or acknowledged divided by the total number of children in the IV-D caseload as of the end of the preceding FFY who were born out of wedlock. . Equation: Total # of Children in IV-D Caseload in the Federal Fiscal Year or, as of the end of the Fiscal Year who were born out of wedlock with Paternity Established or Acknowledged divided by Total # of Children in IV-D Caseload as of the end of the preceding Federal Fiscal Year who were Born Out of Wedlock COLLECTIONS ON CURRENT SUPPORT This measure focuses on the proportion of current support due that is collected on IV-D cases. Equation: Total Dollars Collected for Current Support in IV-D Cases during the Federal Fiscal Year divided by Total Dollars Owed for Current Support in IV-D Cases during the Federal Fiscal Year COLLECTIONS ON ARREARS The measure assesses efforts to collect money from those cases with an arrearage due. The measure specifically counts paying cases, and not total arrears dollars collected. Equation: Total number of IV-D cases paying toward arrears during the Federal Fiscal Year divided by Total number of IV-D cases with arrears due
- API
GOPI Resource: Percentage of Child Support Cases in Arrears for Which a Payment is Received
opendata.maryland.gov | Last Updated 2023-11-20T17:35:34.000ZCHILD SUPPORT ENFORCEMENT ADMINISTRATION The performance measures are used to evaluate each State's performance and measure results in the Child Support Enforcement program. These measures emphasize paternity establishment, support order establishment, collection of current support, collection of arrearages, and cost effectiveness. The performance measures, except cost effectiveness which can only be measured annually, are calculated from data which is reported on federal form OCSE 157. CASES WITH SUPPORT ORDERS This metric measures the proportion of IV-D cases with support orders established. Equation: Number of IV-D Cases with Support Orders divided by Total Number of IV-D Cases IV-D Paternity Establishment Percentage: This metric measures the proportion of children in the IV-D caseload as of the end of the preceding FFY who were born out of wedlock is the total number of children in the IV-D caseload in the federal fiscal year born out of wedlock with paternity established or acknowledged divided by the total number of children in the IV-D caseload as of the end of the preceding FFY who were born out of wedlock. . Equation: Total # of Children in IV-D Caseload in the Federal Fiscal Year or, as of the end of the Fiscal Year who were born out of wedlock with Paternity Established or Acknowledged divided by Total # of Children in IV-D Caseload as of the end of the preceding Federal Fiscal Year who were Born Out of Wedlock COLLECTIONS ON CURRENT SUPPORT This measure focuses on the proportion of current support due that is collected on IV-D cases. Equation: Total Dollars Collected for Current Support in IV-D Cases during the Federal Fiscal Year divided by Total Dollars Owed for Current Support in IV-D Cases during the Federal Fiscal Year COLLECTIONS ON ARREARS The measure assesses efforts to collect money from those cases with an arrearage due. The measure specifically counts paying cases, and not total arrears dollars collected. Equation: Total number of IV-D cases paying toward arrears during the Federal Fiscal Year divided by Total number of IV-D cases with arrears due
- API
MD iMAP: Maryland Shoreline Hazard Index
opendata.maryland.gov | Last Updated 2020-01-25T00:15:40.000ZThis is a MD iMAP hosted service. Find more information on http://imap.maryland.gov. Each point in Coastal Resiliency Assessment Shoreline Points represents a 250 meter segment of the Maryland coast - including Atlantic - Chesapeake Bay and Coastal Bay shorelines. The Natural Capital Project's Coastal Vulnerability model was used to calculate a Shoreline Hazard Index - representing the relative exposure of each segment to storm-induced erosion and flooding. Inputs to the model included 6 physical variables (geomorphology - elevation - sea level rise - wave power - storm surge height and erosion rates) and 5 habitat types (forest - marsh - dune - oyster reef and underwater grass). Two scenarios of the model were run: one scenario incorporating the protective role of all existing coastal habitats and the other scenario simulating the complete loss of habitats. The difference between the two scenarios indicates the potential magnitude of coastal hazard reduction by habitats at each location. Model results were integrated with MD DNR's Community Flood Risk Areas (March - 2016) in order to highlight areas where hazard reduction by habitats is most likely to benefit at-risk coastal communities.This dataset was produced under award number NA13NOS4190136 from the Office of Ocean and Coastal Resource Management (OCRM) - National Oceanic and Atmospheric Administration (NOAA) through the Maryland Department of Natural Resources Chesapeake and Coastal Services (CCS). The statements - finding and recommendations are those of the authors and do not necessarily reflect the views of NOAA or the U.S. Department of Commerce. The Natural Capital Project (NatCap) - CCS and The Nature Conservancy (TNC) all contributed to the production of this dataset. Last Updated: 3/31/2016Feature Service Link: http://geodata.md.gov/imap/rest/services/Environment/MD_CoastalResiliencyAssessment/FeatureServer/1 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.
- API
Maryland Green Infrastructure Hubs and Corridors
opendata.maryland.gov | Last Updated 2024-04-24T21:16:26.000ZMaryland's green infrastructure is a network of undeveloped lands that provide the bulk of the state's natural support system. These data map hub and corridor elements within the green infrastructure. The Green Infrastructure Assessment was developed to provide decision support for Maryland's Department of Natural Resources land conservation programs. Ecosystem services, such as cleaning the air, filtering water, storing and cycling nutrients, conserving soils, regulating climate, and maintaining hydrologic function, are all provided by the existing expanses of forests, wetlands, and other natural lands. These ecologically valuable lands also provide marketable goods and services, like forest products, fish and wildlife, and recreation. The Green Infrastructure serves as vital habitat for wild species and contributes in many ways to the health and quality of life for Maryland residents. To identify and prioritize Maryland's green infrastructure, we developed a tool called the Green Infrastructure Assessment (GIA). The GIA was based on principles of landscape ecology and conservation biology, and provides a consistent approach to evaluating land conservation and restoration efforts in Maryland. It specifically attempts to recognize: a variety of natural resource values (as opposed to a single species of wildlife, for example), how a given place fits into a larger system, the ecological importance of natural open space in rural and developed areas, the importance of coordinating local, state and even interstate planning, and the need for a regional or landscape-level view for wildlife conservation. The GIA identified two types of important resource lands - "hubs" and "corridors." Hubs typically large contiguous areas, separated by major roads and/or human land uses, that contain one or more of the following: Large blocks of contiguous interior forest (containing at least 250 acres, plus a transition zone of 300 feet) Large wetland complexes, with at least 250 acres of unmodified wetlands; Important animal and plant habitats of at least 100 acres, including rare, threatened, and endangered species locations, unique ecological communities, and migratory bird habitats; relatively pristine stream and river segments (which, when considered with adjacent forests and wetlands, are at least 100 acres) that support trout, mussels, and other sensitive aquatic organisms; and existing protected natural resource lands which contain one or more of the above (for example, state parks and forests, National Wildlife Refuges, locally owned reservoir properties, major stream valley parks, and Nature Conservancy preserves). In the GIA model, the above features were identified from Geographic Information Systems (GIS) spatial data that covered the entire state. Developed areas and major roads were excluded, areas less than 100 contiguous acres were dropped, adjacent forest and wetland were added to the remaining hubs, and the edges were smoothed. The average size of all hubs in the state is approximately 2200 acres. Corridors are linear features connecting hubs together to help animals and plant propagules to move between hubs. Corridors were identified using many sets of data, including land cover, roads, streams, slope, flood plains, aquatic resource data, and fish blockages. Generally speaking, corridors connect hubs of similar type (hubs containing forests are connected to one another; while those consisting primarily of wetlands are connected to others containing wetlands). Corridors generally follow the best ecological or "most natural" routes between hubs. Typically these are streams with wide riparian buffers and healthy fish communities. Other good wildlife corridors include ridge lines or forested valleys. Developed areas, major roads, and other unsuitable features were avoided.