- 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 Marine Boundaries - Shoreline
opendata.maryland.gov | Last Updated 2020-01-25T00:14:01.000ZThis is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. In 2000 - the Maryland Geological Survey (MGS) was awarded a Coastal ZoneManagement grant to complete the acquisition of a recent (ca. 1990) digital shoreline for the coastal regions of Maryland - the Chesapeake Bay - its tributaries - the coastal bays - and the Atlantic coast.MGS contracted the services of EarthData International - Inc. (EDI) of Gaithersburg - Md. - to extract shorelines from an existing wetlands delineation - which was based on photo interpretation of 3.75-minute digital orthophoto quarter quads (DOQQs). In areas where a wetlands coverage was not yet available - EDI interpreted shorelines directly from the orthophotography. DOQQ registration (Maryland State Plane Coordinate System - NAD 83 - meters) was transferred automatically to the shoreline vectors. Following shoreline extraction or interpretation - EDI assigned attributes to the vectors based on shoreline type: beach - vegetated - structure - or water's edge. This data set has been merged into a state wide file for ease of processing and decision making.Feature Service Link:http://geodata.md.gov/imap/rest/services/Boundaries/MD_MarineBoundaries/FeatureServer/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 Licensed Animal Plant Facilities - Animal Control Facilities
opendata.maryland.gov | Last Updated 2020-01-25T00:30:02.000ZThis is a MD iMAP hosted service. Find more information at http://imap.maryland.gov. Point layer of animal control facilities licensed by the Maryland Department of Agriculture (MDA).Last Update: 2012Feature Service Link:http://geodata.md.gov/imap/rest/services/Agriculture/MD_LicensedAnimalPlantFacilities/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
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 Annual Average Daily Traffic - Annual Average Daily Traffic (SHA Statewide AADT Points)
opendata.maryland.gov | Last Updated 2020-01-25T00:35:11.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. Traffic monitoring data is a strategic resource for SHA and Maryland's Department of Transportation. The data is essential in the planning - design and operation of the statewide road system and the development and implementation of state highway improvement and safety programs. TMS is a product of the ISTEA Act of 1991 - which required a traffic data program to effectively and efficiently meet SHA's long-term traffic data monitoring and reporting requirements. The quality control feature of the system allow data edit checks and validation for data from the 84 permanent - continuous automatic traffic recorders (ATRs) and short-term traffic counts.The Maryland Traffic Volume Maps depict the Annual Average Daily Traffic (AADT) at various locations on Maryland's roadways by county. Traffic Volume data is collected from over 8700 program count stations and 84 ATRs - located throughout Maryland. To date - four (4) ATRs have been removed from the ATR Program. Program count data is collected (both directions) at regular locations on either a three (3) year or six (6) year cycle depending on type of roadway. Growth Factors are applied to counts which were not taken during the current year and the counts are factored based on the past yearly growth of an associated ATR. Counters are placed for 48 hours on a Monday or Tuesday and are picked up that Thursday or Friday - respectively. The ATR and toll count data is collected on a continuous basis. Toll station data is provided by the Maryland Transportation Authority. A special numeric code was added to the AADT numbers - starting in 2006 - to identify the years when the count was actually taken. The last digit represents the number of years prior to the actual count. Where '0' represents the current year when data was collected (in 2014) - '1' represents the count taken in 2013 - '2' represents the count taken in 2012 - '3' represents the count taken in 2011 and so forth. Last Updated: Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Transportation/MD_AnnualAverageDailyTraffic/FeatureServer/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 Transit - WMATA Metro Bus Stops
opendata.maryland.gov | Last Updated 2020-01-25T00:33:59.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. Metrobus provides more than 400 - 000 trips each weekday serving 11 - 500 bus stops in the District of Columbia - Maryland - and Virginia. Metrobus is the sixth busiest bus agency in the United States - with a fleet of more than 1 - 500 buses operating on 325 routes Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Transportation/MD_Transit/FeatureServer/12 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 SSURGO Soils - SSURGO Soils
opendata.maryland.gov | Last Updated 2020-01-25T00:26:55.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. userdata and unzip the LayerFiles.zip folder.Data from the four SSURGO tables were assembled into the single table included in each map package. Data from the component table were aggregated using a dominant component model (listed below under Component Table - Dominant Component) or a weighted average model (listed below under Component Table - Weighted Average) using custom Python scripts. The the Mapunit table - the MUAGATTAT table and the processed Component table data were joined to the Mapunit Feature Class. Field aliases were added and indexes calculated. A field named Map Symbol was created and populated with random integers from 1-10 for symbolizing the soil units in the map package.For documentation of the SSURGO dataset see:http://soildatamart.nrcs.usda.gov/SSURGOMetadata.aspxFor documentation of the Watershed Boundary Dataset see: http://www.nrcs.usda.gov/wps/portal/nrcs/main/national/water/watersheds/datasetThe map packages contain the following attributes in the Map Units layer:Mapunit Feature Class:Survey AreaSpatial VersionMapunit SymbolMapunit KeyNational Mapunit SymbolMapunit Table:Mapunit NameMapunit KindFarmland ClassHighly Erodible Lands Classification - Wind and WaterHighly Erodible Lands Classification - WaterHighly Erodible Lands Classification - WindInterpretive FocusIntensity of MappingLegend KeyMapunit SequenceIowa Corn Suitability RatingLegend Table:Project ScaleTabular VersionMUAGGATT Table:Slope Gradient - Dominant ComponentSlope Gradient - Weighted AverageBedrock Depth - MinimumWater Table Depth - Annual MinimumWater Table Depth - April to June MinimumFlooding Frequency - Dominant ConditionFlooding Frequency - MaximumPonding Frequency - PresenceAvailable Water Storage 0-25 cm - Weighted AverageAvailable Water Storage 0-50 cm - Weighted AverageAvailable Water Storage 0-100 cm - Weighted AverageAvailable Water Storage 0-150 cm - Weighted AverageDrainage Class - Dominant ConditionDrainage Class - WettestHydrologic Group - Dominant ConditionIrrigated Capability Class - Dominant ConditionIrrigated Capability Class - Proportion of Mapunit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Mapunit with Dominant ConditionRating for Buildings without Basements - Dominant ConditionRating for Buildings with Basements - Dominant ConditionRating for Buildings with Basements - Least LimitingRating for Buildings with Basements - Most LimitingRating for Septic Tank Absorption Fields - Dominant ConditionRating for Septic Tank Absorption Fields - Least LimitingRating for Septic Tank Absorption Fields - Most LimitingRating for Sewage Lagoons - Dominant ConditionRating for Sewage Lagoons - Dominant ComponentRating for Roads and Streets - Dominant ConditionRating for Sand Source - Dominant ConditionRating for Sand Source - Most ProbableRating for Paths and Trails - Dominant ConditionRating for Paths and Trails - Weighted AverageErosion Hazard of Forest Roads and Trails - Dominant ComponentHydric Classification - PresenceRating for Manure and Food Processing Waste - Weighted AverageComponent Table - Weighted Average:Mean Annual Air Temperature - High Value Mean Annual Air Temperature - Low Value Mean Annual Air Temperature - Representative Value Albedo - High Value Albedo - Low Value Albedo - Representative Value Slope - High Value Slope - Low Value Slope - Representative Value Slope Length - High Value Slope Length - Low Value Slope Length - Representative Value Elevation - High Value Elevation - Low Value Elevation - Representative Value Mean Annual Precipitation - High Value Mean Annual Precipitation - Low Value Mean Annual Precipitation - Representative Value Days between Last and First Frost - High Value Days between Last and First Frost - Low Value Days between Last and First Frost - Representative Value Crop Production Index Range Forage Annual Potenti
- API
MD iMAP: Maryland Annual Average Daily Traffic - Annual Average Daily Traffic (SHA Statewide AADT Lines)
opendata.maryland.gov | Last Updated 2020-01-25T00:24:13.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. Traffic monitoring data is a strategic resource for SHA and Maryland's Department of Transportation. The data is essential in the planning - design and operation of the statewide road system and the development and implementation of state highway improvement and safety programs. TMS is a product of the ISTEA Act of 1991 - which required a traffic data program to effectively and efficiently meet SHA's long-term traffic data monitoring and reporting requirements. The quality control feature of the system allow data edit checks and validation for data from the 84 permanent - continuous automatic traffic recorders (ATRs) and short-term traffic counts.The Maryland Traffic Volume Maps depict the Annual Average Daily Traffic (AADT) at various locations on Maryland's roadways by county. Traffic Volume data is collected from over 8700 program count stations and 84 ATRs - located throughout Maryland. To date - four (4) ATRs have been removed from the ATR Program. Program count data is collected (both directions) at regular locations on either a three (3) year or six (6) year cycle depending on type of roadway. Growth Factors are applied to counts which were not taken during the current year and the counts are factored based on the past yearly growth of an associated ATR. Counters are placed for 48 hours on a Monday or Tuesday and are picked up that Thursday or Friday - respectively. The ATR and toll count data is collected on a continuous basis. Toll station data is provided by the Maryland Transportation Authority. A special numeric code was added to the AADT numbers - starting in 2006 - to identify the years when the count was actually taken. The last digit represents the number of years prior to the actual count. Where '0' represents the current year when data was collected (in 2014) - '1' represents the count taken in 2013 - '2' represents the count taken in 2012 - '3' represents the count taken in 2011 and so forth. Last Updated: Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Transportation/MD_AnnualAverageDailyTraffic/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
Railroad_Crossings_MD
opendata.maryland.gov | Last Updated 2024-04-24T21:15:54.000ZSummary Rail Crossings is a spatial file maintained by the Federal Railroad Administration (FRA) for use by States and railroads. Description FRA Grade Crossings is a spatial file that originates from the National Highway-Rail Crossing, Inventory Program. The program is to provide information to Federal, State, and local governments, as well as the railroad industry for the improvements of safety at highway-rail crossing. Credits Federal Railroad Administration (FRA) Use limitations There are no access and use limitations for this item. Extent West -79.491008 East -75.178954 North 39.733500 South 38.051719 Scale Range Maximum (zoomed in) 1:5,000 Minimum (zoomed out) 1:150,000,000 ArcGIS Metadata ▼►Topics and Keywords ▼►Themes or categories of the resource transportation * Content type Downloadable Data Export to FGDC CSDGM XML format as Resource Description No Temporal keywords 2013 Theme keywords Rail Theme keywords Grade Crossing Theme keywords Rail Crossings Citation ▼►Title rr_crossings Creation date 2013-03-15 00:00:00 Presentation formats * digital map Citation Contacts ▼►Responsible party Individual's name Raquel Hunt Organization's name Federal Railroad Administration (FRA) Contact's position GIS Program Manager Contact's role custodian Responsible party Organization's name Research and Innovative Technology Administration/Bureau of Transportation Statistics Individual's name National Transportation Atlas Database (NTAD) 2013 Contact's position Geospatial Information Systems Contact's role distributor Contact information ▼►Phone Voice 202-366-DATA Address Type Delivery point 1200 New Jersey Ave. SE City Washington Administrative area DC Postal code 20590 e-mail address answers@BTS.gov Resource Details ▼►Dataset languages * English (UNITED STATES) Dataset character set utf8 - 8 bit UCS Transfer Format Spatial representation type * vector * Processing environment Microsoft Windows 7 Version 6.1 (Build 7600) ; Esri ArcGIS 10.2.0.3348 Credits Federal Railroad Administration (FRA) ArcGIS item properties * Name USDOT_RRCROSSINGS_MD * Size 0.047 Location withheld * Access protocol Local Area Network Extents ▼►Extent Geographic extent Bounding rectangle Extent type Extent used for searching * West longitude -79.491008 * East longitude -75.178954 * North latitude 39.733500 * South latitude 38.051719 * Extent contains the resource Yes Extent in the item's coordinate system * West longitude 611522.170675 * East longitude 1824600.445629 * South latitude 149575.449134 * North latitude 752756.624659 * Extent contains the resource Yes Resource Points of Contact ▼►Point of contact Individual's name Raquel Hunt Organization's name Federal Railroad Administration (FRA) Contact's position GIS Program Manager Contact's role custodian Resource Maintenance ▼►Resource maintenance Update frequency annually Resource Constraints ▼►Constraints Limitations of use There are no access and use limitations for this item. Spatial Reference ▼►ArcGIS coordinate system * Type Projected * Geographic coordinate reference GCS_North_American_1983_HARN * Projection NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet * Coordinate reference details Projected coordinate system Well-known identifier 2893 X origin -120561100 Y origin -95444400 XY scale 36953082.294548117 Z origin -100000 Z scale 10000 M origin -100000 M scale 10000 XY tolerance 0.0032808333333333331 Z tolerance 0.001 M tolerance 0.001 High precision true Latest well-known identifier 2893 Well-known text PROJCS["NAD_1983_HARN_StatePlane_Maryland_FIPS_1900_Feet",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree"
- 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.