- 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 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 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 Land Use Land Cover - Land Use Land Cover 2010
opendata.maryland.gov | Last Updated 2020-01-25T00:34:30.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. The purpose of the 2010 land use/land cover data set is to provide a generalized view of how developed land has changed throughout the state - primarily capturing the conversion of resource land to development and characterizing the type of development (e.g. very low density - low density - medium density or high density residential development - commercial - industrial - institutional). Urban Land Uses: 11 Low-density residential - Detached single-family/duplex dwelling units - yards and associated areas. Areas of more than 90 percent single-family/duplex dwelling units - with lot sizes of less than five acres but at least one-half acre (.2 dwelling units/acre to 2 dwelling units/acre). 12 Medium-density residential - Detached single-family/duplex - attached single-unit row housing - yards - and associated areas. Areas of more than 90 percent single-family/duplex units and attached single-unit row housing - with lot sizes of less than one-half acre but at least one-eighth acre (2 dwelling units/acre to 8 dwelling units/acre). 13 High-density residential - Attached single-unit row housing - garden apartments - high-rise apartments/condominiums - mobile home and trailer parks; areas of more than 90 percent high-density residential units - with more than 8 dwelling units per acre. 14 Commercial - Retail and wholesale services. Areas used primarily for the sale of products and services - including associated yards and parking areas. 15 Industrial - Manufacturing and industrial parks - including associated warehouses - storage yards - research laboratories - and parking areas. 16 Institutional - Elementary and secondary schools - middle schools - junior and senior high schools - public and private colleges and universities - military installations (built-up areas only - including buildings and storage - training - and similar areas) - churches - medical and health facilities - correctional facilities - and government offices and facilities that are clearly separable from the surrounding land cover. 17 Extractive - Surface mining operations - including sand and gravel pits - quarries - coal surface mines - and deep coal mines. Status of activity (active vs. abandoned) is not distinguished. 18 Open urban land - Urban areas whose use does not require structures - or urban areas where non-conforming uses characterized by open land have become isolated. Included are golf courses - parks - recreation areas (except areas associated with schools or other institutions) - cemeteries - and entrapped agricultural and undeveloped land within urban areas. 191 Large lot subdivision (agriculture) - Residential subdivisions with lot sizes of less than 20 acres but at least 5 acres - with a dominant land cover of open fields or pasture. 192 Large lot subdivision (forest) - Residential subdivisions with lot sizes of less than 20 acres but at least 5 acres - with a dominant land cover of deciduous - evergreen or mixed forest. Agriculture: 21 Cropland - Field crops and forage crops. 22 Pasture - Land used for pasture - both permanent and rotated; grass. 23 Orchards/vineyards/horticulture - Areas of intensively managed commercial bush and tree crops - including areas used for fruit production - vineyards - sod and seed farms - nurseries - and green houses. 24 Feeding operations - Cattle feed lots - holding lots for animals - hog feeding lots - poultry houses - and commercial fishing areas (including oyster beds). 241 Feeding operations - Cattle feed lots - holding lots for animals - hog feeding lots - poultry houses. 242 Agricultural building breeding and training facilities - storage facilities - built-up areas associated with a farmstead - small farm ponds - commercial fishing areas. 25 Row and garden crops - Intensively managed truck and vegetable farms and associated areas. Forest: 41 Deciduous fore
- API
Section Heatmap of MDTA Accidents
opendata.maryland.gov | Last Updated 2023-12-13T02:53:46.000ZIncludes accidents that occured on MD Transportation Authority (MDTA) facilities, or were within a concurrent jurisdiction and were responded to by MDTA Police. MDTA facilities are the Francis Scott Key Bridge (I-695), John F. Kennedy Memorial Highway (I-95), Thomas J. Hatem Memorial Bridge (US 40), Fort McHenry Tunnel (I-95), Baltimore Harbor Tunnel (I-895), the Bay Bridge (US 50/301), Governor Harry W. Nice Memorial Bridge (US 301), and Intercounty Connector (ICC/MD200). MDTA Police are also responsible for accidents at BWI Airport and the Port of Baltimore. This dataset will be updated monthly by the MD Transportation Authority
- API
MDTA Accidents
opendata.maryland.gov | Last Updated 2023-04-12T13:22:44.000ZIncludes accidents that occured on MD Transportation Authority (MDTA) facilities, or were within a concurrent jurisdiction and were responded to by MDTA Police. MDTA facilities are the Francis Scott Key Bridge (I-695), John F. Kennedy Memorial Highway (I-95), Thomas J. Hatem Memorial Bridge (US 40), Fort McHenry Tunnel (I-95), Baltimore Harbor Tunnel (I-895), the Bay Bridge (US 50/301), Governor Harry W. Nice Memorial Bridge (US 301), and Intercounty Connector (ICC/MD200). MDTA Police are also responsible for accidents at BWI Airport and the Port of Baltimore. This dataset will be updated monthly by the MD Transportation Authority
- API
BLS Jobs by Industry Category
opendata.maryland.gov | Last Updated 2020-03-19T12:57:04.000ZData from the Bureau of Labor Statistics (BLS) Current Employment Statistics (CES) program. CES data represents businesses and government agencies, providing detailed industry data on employment on nonfarm payrolls.
- API
MD iMAP: Maryland Transit - Baltimore Metro Subway Parking
opendata.maryland.gov | Last Updated 2020-01-25T00:33:49.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. Maryland Transit Administration METRO Parking Facilities. The 15.5-mile - 14-station Metro Subway system operates every. 8-10 minutes during the morning and evening peak periods; 11 minutes during weekday evenings; 15 minutes on Saturdays - Sundays and holidays. For more information see http://mta.maryland.gov/metro-subway. Last Updated: 03/01/2013 Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Transportation/MD_Transit/FeatureServer/14 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 - Baltimore Metro Subway Stops
opendata.maryland.gov | Last Updated 2020-01-25T00:18:07.000ZThis is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. Maryland Transit Administration Metro Subway Stops. This data is based upon the Winter 2014 schedule. See http://mta.maryland.gov/metro-subway for more information. Last Updated: 04/2015 Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Transportation/MD_Transit/FeatureServer/4 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.