This dataset includes parking spaces availability for Montgomery County Public Parking Facilities. This dataset only includes facilities that are equipped with vehicle counting systems.

Update frequency: Every few minutes

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

This dataset contains leaf collection dates for area and subarea where leaf collection service is provided by Montgomery County Department of Transportation. Update Frequency - Daily (September through December). Monthly update (January through August) on the first day of each month.

Updated daily postings on Montgomery County’s open data website, dataMontgomery, provide the public with direct access to crime statistic databases - including raw data and search functions – of reported County crime. The data presented is derived from reported crimes classified according to the National Incident-Based Reporting System (NIBRS) of the Criminal Justice Information Services (CJIS) Division Uniform Crime Reporting (UCR) Program and documented by approved police incident reports. The data is compiled by “EJustice”, a respected law enforcement records-management system used by the Montgomery County Police Department and many other law enforcement agencies. To protect victims’ privacy, no names or other personal information are released. All data is refreshed on a quarterly basis to reflect any changes in status due to on-going police investigation.

dataMontgomery allows the public to query the Montgomery County Police Department's database of founded crime. The information contained herein includes all founded crimes reported after July 1st 2016 and entered to-date utilizing Uniform Crime Reporting (UCR) rules. Please note that under UCR rules multiple offenses may appear as part of a single founded reported incident, and each offense may have multiple victims. Please note that these crime reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the crime data available on this web page may reflect:

-Information not yet verified by further investigation
-Information that may include attempted and reported crime
-Preliminary crime classifications that may be changed at a later date based upon further investigation
-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.]

Update Frequency: Daily

The Licensure & Regulatory Services Program inspects all licensed retail food establishments in Montgomery County for a variety of reasons (e.g. obtaining a permit, regular check-ups, or in response to complaints.) Included in this overall surveillance are two types of inspections that are conducted on a routine basis. The first type, a comprehensive inspection, is a thorough inspection that evaluates the sanitation, maintenance, and food service operations for the facility. This inspection includes many of the items found in the monitoring inspection, such as critical temperatures and food handling procedures. The second type, a monitoring inspection, involves checking the food service operation for critical food temperatures, equipment temperatures, and general food handling / cleanliness practices. While monitoring inspections are not as detailed as environmental inspections, they help ensure that the facility is operating safely throughout the year.

The frequency of inspections is based on the food-borne illness risks associated with the food being processed at a facility. Based on the risk each facility is designated as high, medium, or low priority. High priority risk facilities prepare food products a day or more in advance or utilize any combination of two or more processes such as a cooking, cooling, reheating and hot holding food over four hours. Moderate priority risk facilities prepare and cook food products which are served immediately or within four hours. A low priority risk facility serve prepackage foods that are not potentially hazardous.

For high risk facilities, a monitoring inspection is conducted at least twice a year, and moderate risk facilities are inspected at least once a year. High and moderate risk facilities also receive at least one comprehensive inspection every year. Low risk priority facilities typically receive one comprehensive inspection every two years.

(C) Denotes a Critical Violation. A Critical Violation means a food safety requirement that requires immediate correction. Failure for immediate correction results in cessation of some or all food operations or closure of the facility until violation is able to be corrected.

Update Frequency: Daily

The dataset view shows a list of newly open Invitation for Bid (IFB) solicitations.
Data Update Frequency : Daily.

This dataset contains traffic violation information from all electronic traffic violations issued in the County. Any information that can be used to uniquely identify the vehicle, the vehicle owner or the officer issuing the violation will not be published.

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 provides general information about each collision and details of all traffic collisions occurring on county and local roadways within Montgomery County, as collected via the Automated Crash Reporting System (ACRS) of the Maryland State Police, and reported by the Montgomery County Police, Gaithersburg Police, Rockville Police, or the Maryland-National Capital Park Police.

Please note that these collision reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the collision data available on this web page may reflect:

-Information not yet verified by further investigation
-Information that may include verified and unverified collision data
-Preliminary collision classifications may be changed at a later date based upon further investigation
-Information may include mechanical or human error

This dataset can be joined with the other 2 Crash Reporting datasets (see URLs below) by the State Report Number.
* Crash Reporting - Drivers Data at https://data.montgomerycountymd.gov/Public-Safety/Crash-Reporting-Drivers-Data/mmzv-x632
* Crash Reporting - Non-Motorists Data at https://data.montgomerycountymd.gov/Public-Safety/Crash-Reporting-Non-Motorists-Data/n7fk-dce5
Update Frequency : Weekly

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