The specifications and guidelines in this Data Management Plan will improve data consistency and availability of information. It will ensure that all levels of government and the public have access to the most up-to-date information; reduce or eliminate overlapping data requests and redundant data maintenance; ensure metadata is consistently created; and ensure that data services can be displayed by the consumer with the output of its choice.

The MPIA dataset will contain a list of MPIA requests that contain information about the MPIA request as well as a web link to the MPIA response packet created by the owning departments. Each request will contain the following information:

Requestor First Name Requestor Last Name Requestor Organization Description Intake (ie email) Lead Department Data Owning Departments Date Response Posted Who Published the Response Link to the Response Document(s) on a public Web Site

Update Frequency: Daily

Information on all MC311 Service Requests received (via email or phone) since July 1, 2012. This data is updated daily. The PIO’s business requirement includes adding the following data elements to the new and enhanced open data site being proposed by DTS. This data is derived from requests for service which originate in the CSC, from the County’s web portal, and via “walk-ins” from county departments including but not limited to DHCA. • SLA – to indicate the number of days in county business days the department has to fulfill the request. County business days must exclude weekends, county holidays and days when the county is closed due to inclement weather (snow days, etc) per CountyStat’s business requirement. This field has been published in the existing MC311 Service Requests dataset with the field name ‘Attached Solution SLA Days’. • +/- SLA –to indicate the number of days a service request is over or under SLA as is currently measured by CountyStat. The following 4 fields will be added to fulfill this line item  # of days open – Number of County Business days the Service Request has been opened.  Within SLA Window? - To indicate the number of days a service request is over or under SLA as is currently measured by CountyStat.  SLA Yes – Number of days to fulfill the service request is under the SLA window.  SLA No -– Number of days to fulfill the service request is over the SLA window.

This dataset includes all issued permits by the City of Frederick from 1/1/12 to 6/6/14. We are no longer updating this dataset, but if there is demand for updated data then please contact the Open Data Portal Team and we will look into it.

The MPIA dataset will contain a list of MPIA requests that contain information about the MPIA request as well as a web link to the MPIA response packet created by the owning departments. Each request will contain the following information:

Requestor First Name Requestor Last Name Requestor Organization Description Intake (ie email) Lead Department Data Owning Departments Date Response Posted Who Published the Response Link to the Response Document(s) on a public Web Site

Update Frequency: Daily

This dataset includes the City of Frederick code enforcement violations from 1/1/14 to 6/6/14. This dataset is no longer being updated, but if there is demand to keep updating it then please contact the Open Data Portal Team.

This dataset shows all data which Maryland Correctional Enterprises reported from May 2007 through July 2015. After which time the Performance Improvement Office asked the Dept of Public Safety and Corrections (DPSCS) to stop reporting it because there was plenty of historical data and marginal utility in continuing to report in on the Portal unless they have a need to. DPSCS will start reporting on it again if there is demand for updated data.

This 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 Potential Production - High Value Range Forage Annual Potential Production - Low Value Range Forage Annual Potential Production - Representative Value Initial Subsidence - High Value Initial Subsidence - Low Value Initial Subsidence - Representative Value Total Subsidence - High ValueTotal Subsidence - Low Value Total Subsidence - Representative Value Component Table - Dominant Component:Component KeyComponent Percentage - Low ValueComponent Percentage - Representative ValueComponent Percentage - High ValueComponent NameComponent KindOther Criteria Used to Identify ComponentsCriteria Used to Identify Components at the Local LevelRunoffSoil Loss Tolerance FactorWind Erodibility IndexWind Erodibility GroupErosion ClassEarth Cover 1Earth Cover 2Hydric ConditionAspect Range - Counter Clockwise LimitAspect - Representative ValueAspect Range - Clockwise LimitGeomorphic DescriptionNon-Irrigated Capability SubclassNon-Irrigated Unit Capability ClassIrrigated Capability SubclassIrrigated Unit Capability ClassConservation Tree Shrub GroupForage Suitability GroupGrain Wildlife HabitatGrass Wildlife HabitatHerbaceous Wildlife HabitatShrub Wildlife HabitatConifer Wildlife HabitatHardwood Wildlife HabitatWetland Wildlife HabitatShallow Water Wildlife HabitatRangeland Wildlife HabitatOpenland Wildlife HabitatWoodland Wildlife HabitatWetland Wildlife HabitatSoil Slip PotentialSusceptibility to Frost HeavingConcrete CorrosionSteel CorrosionTaxonomic Class NameOrderSuborderGreat GroupSubgroupParticle SizeParticle Size ModifierCation Exchange Activity ClassCarbonate ReactionTemperature ClassMoisture SubclassSoil Temperature RegimeEdition of Keys to Soil Taxonomy Used to Classify SoilThe U.S. Department of Agriculture - Natural Resources Conservation Service - should be acknowledged as the data source in products derived from these data. This data set is not designed for use as a primary regulatory tool in permitting or citing decisions - but may be used as a reference source. This is public information and may be interpreted by organizations - agencies - units of government - or others based on needs; however - they are responsible for the appropriate application. Federal - State - or local regulatory bodies are not to reassign to the Natural Resources Conservation Service any authority for the decisions that they make. The Natural Resources Conservation Service will not perform any evaluations of these maps for purposes related solely to State or local regulatory programs. Photographic or digital enlargement of these maps to scales greater than at which they were originally mapped can cause misinterpretation of the data. If enlarged - maps do not show the small areas of contrasting soils that could have been shown at a larger scale. The depicted soil boundaries - interpretations - and analysis derived from them do not eliminate the need for onsite sampling - testing - and detailed study of specific sites for intensive uses. Thus - these data and their interpretations are intended for planning purposes only. Digital data files are periodically updated. Files are dated - and users are responsible for obtaining the latest version of the data.The attribute accuracy is tested by manual comparison of the source with hard copy plots and/or symbolized display of the map data on an interactive computer graphic system. Selected attributes that cannot be visually verified on plots or on screen are interactively queried and verified on screen. In addition - the attributes are tested against a master set of valid attributes. All attribute data conform to the attribute codes in the signed classification and correlation document and amendment(s). Last Updated: Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Geoscientific/MD_SSURGOSoils/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.

EXERCISE ONLYPurpose and AudienceThis web application is designed to serve as a situational awareness map for flood response (or training for flood response) in Montgomery County, Maryland. The map shows flood hazard areas and includes critical infrastructure (such as police and fire stations, hospitals, and schools). There is also Social Vulnerability Index layer, and live feeds from stream gauges and world traffic. This map is for use by emergency management staff and first responders to maintain situational awareness during a flood event or training.Data SourcesThe live feeds were obtained through Esri's Living Atlas. The flood hazard layer was derived from FEMA's National Flood Hazard Layer. The infrastructure layers were obtained from the Homeland Infrastructure Foundation Level Data (HIFLD) Open Data Portal (Hospitals, Schools, Fire Stations) and the Maryland Open Data Portal (Police Stations).

Information on all MC311 Service Requests received (via email or phone) since July 1, 2012. This data is updated daily. The PIO’s business requirement includes adding the following data elements to the new and enhanced open data site being proposed by DTS. This data is derived from requests for service which originate in the CSC, from the County’s web portal, and via “walk-ins” from county departments including but not limited to DHCA. • SLA – to indicate the number of days in county business days the department has to fulfill the request. County business days must exclude weekends, county holidays and days when the county is closed due to inclement weather (snow days, etc) per CountyStat’s business requirement. This field has been published in the existing MC311 Service Requests dataset with the field name ‘Attached Solution SLA Days’. • +/- SLA –to indicate the number of days a service request is over or under SLA as is currently measured by CountyStat. The following 4 fields will be added to fulfill this line item  # of days open – Number of County Business days the Service Request has been opened.  Within SLA Window? - To indicate the number of days a service request is over or under SLA as is currently measured by CountyStat.  SLA Yes – Number of days to fulfill the service request is under the SLA window.  SLA No -– Number of days to fulfill the service request is over the SLA window.

The dataset used in this study comprises 7,790 rows of daily water quality readings collected over 15 years (2007–2023) from Cork Harbour, Ireland. Cork Harbour, located at approximately 51.8410° N latitude and -8.2940° W longitude, is a large natural harbor influenced by both river and coastal factors, making it an important site for environmental monitoring and water quality assessment. The dataset includes measurements for 11 water quality parameters: Alkalinity, Ammonia, Biochemical Oxygen Demand, Chloride, Conductivity, Dissolved Oxygen, Orthophosphate, pH, Temperature, Total Hardness, and True Colour. These parameters provide comprehensive insights into water quality trends and variability in the region. This dataset is collected from the Environmental Open Data Portal (EPA), Ireland, the dataset is presented in a structured format and offers a valuable resource for developing and evaluating machine learning and deep learning models for Surface Water Quality Index (WQI) forecasting.

This feature class is a dataset based on liquor licenses as reported by Baltimore City Liquor License Board listing circa October 2004. This dataset includes the establishments that sell liquor in Baltimore, Maryland. Each establishment was geocoded by its street address. Those unable to be placed with a point by geocoding were given "U" for unmatched under the field "Status". Each establishment also has an associated liquor license particular to what type of alcohol is sold and the type of establishment. These liquor license types are defined by the Baltimore City Liquor License Board on their website, http://www.ci.baltimore.md.us/government/liquor.

   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.

Active Rental Licenses - Issued timeframe: 4/11/2021 - 11/30/2024

Publish Cable Office Facilities Application Status & Location Information on transmission towers and antennas. Updated weekly.

Information on all MC311 Service Requests received (via email or phone) since July 1, 2012. This data is updated daily. The PIO’s business requirement includes adding the following data elements to the new and enhanced open data site being proposed by DTS. This data is derived from requests for service which originate in the CSC, from the County’s web portal, and via “walk-ins” from county departments including but not limited to DHCA. • SLA – to indicate the number of days in county business days the department has to fulfill the request. County business days must exclude weekends, county holidays and days when the county is closed due to inclement weather (snow days, etc) per CountyStat’s business requirement. This field has been published in the existing MC311 Service Requests dataset with the field name ‘Attached Solution SLA Days’. • +/- SLA –to indicate the number of days a service request is over or under SLA as is currently measured by CountyStat. The following 4 fields will be added to fulfill this line item  # of days open – Number of County Business days the Service Request has been opened.  Within SLA Window? - To indicate the number of days a service request is over or under SLA as is currently measured by CountyStat.  SLA Yes – Number of days to fulfill the service request is under the SLA window.  SLA No -– Number of days to fulfill the service request is over the SLA window.

A list of disruptive behavior cases initiated and reported by County Departments and Offices. Updated monthly.

Information on all MC311 Service Requests received (via email or phone) since July 1, 2012. This data is updated daily. The PIO’s business requirement includes adding the following data elements to the new and enhanced open data site being proposed by DTS. This data is derived from requests for service which originate in the CSC, from the County’s web portal, and via “walk-ins” from county departments including but not limited to DHCA. • SLA – to indicate the number of days in county business days the department has to fulfill the request. County business days must exclude weekends, county holidays and days when the county is closed due to inclement weather (snow days, etc) per CountyStat’s business requirement. This field has been published in the existing MC311 Service Requests dataset with the field name ‘Attached Solution SLA Days’. • +/- SLA –to indicate the number of days a service request is over or under SLA as is currently measured by CountyStat. The following 4 fields will be added to fulfill this line item  # of days open – Number of County Business days the Service Request has been opened.  Within SLA Window? - To indicate the number of days a service request is over or under SLA as is currently measured by CountyStat.  SLA Yes – Number of days to fulfill the service request is under the SLA window.  SLA No -– Number of days to fulfill the service request is over the SLA window.

Information on all MC311 Service Requests received (via email or phone) since July 1, 2012. This data is updated daily.

Information on all MC311 Service Requests received (via email or phone) since July 1, 2012. This data is updated daily.

This dataset provides the public with arrest information from the Montgomery County Central Processing Unit (CPU) systems. The data presented is derived from every booking; criminal, civil and motor vehicle entered through CPU. The data is compiled by “CRIMS”, a respected jail records-management system used by the Montgomery County Corrections and many other law enforcement agencies. To protect arrestee’s privacy, personal information is redacted. Residential addresses are rounded to the nearest hundred block. All data is refreshed on 2 hour basis to reflect any additions or changes. -Information that may include mechanical or human error -Arrest information [Note: all arrested persons are presumed innocent until proven guilty in a court of law - Records will be removed after 30 days. Update Frequency - every 2 hours