- What is the Land Area?
- What is the Population Count?
- What is the Population Density?
- What is the Percent who did not finish the 9th grade?
- What is the Median Earnings?
- What is the Number of Employees?
- What is the Crime incident count?
- What is the Population Rate of Change?
- What is the High School Graduation Rate?
- What is the Median Female Earnings?
The water area of District Heights, MD was 0 in 2018.
Land area is a measurement providing the size, in square miles, of the land portions of geographic entities for which the Census Bureau tabulates and disseminates data. Area is calculated from the specific boundary recorded for each entity in the Census Bureau's geographic database. Land area is based on current information in the TIGER® data base, calculated for use with Census 2010.
Water Area figures include inland, coastal, Great Lakes, and territorial sea water. Inland water consists of any lake, reservoir, pond, or similar body of water that is recorded in the Census Bureau's geographic database. It also includes any river, creek, canal, stream, or similar feature that is recorded in that database as a two- dimensional feature (rather than as a single line). The portions of the oceans and related large embayments (such as Chesapeake Bay and Puget Sound), the Gulf of Mexico, and the Caribbean Sea that belong to the United States and its territories are classified as coastal and territorial waters; the Great Lakes are treated as a separate water entity. Rivers and bays that empty into these bodies of water are treated as inland water from the point beyond which they are narrower than 1 nautical mile across. Identification of land and inland, coastal, territorial, and Great Lakes waters is for data presentation purposes only and does not necessarily reflect their legal definitions.
Geographic and Area Datasets Involving District Heights, MD
- API data.cityofchicago.org | Last Updated 2021-08-01T07:45:11.000Z
The Chicago Park District maintains sensors in the water at beaches along Chicago's Lake Michigan lakefront. These sensors generally capture the indicated measurements hourly while the sensors are in operation during the summer. During other seasons and at some other times, information from the sensors may not be available. See https://data.cityofchicago.org/d/k7hf-8y75 for a dataset with land-based weather measurements at selected beaches. The sensor locations are listed at https://data.cityofchicago.org/d/g3ip-u8rb. Please note that sensor locations change with the Park District’s operational needs, primarily related to water quality. For more information on beach operations, please see https://www.chicagoparkdistrict.com/parks-facilities/beaches.
- API data.montgomerycountymd.gov | Last Updated 2021-08-01T05:17:19.000Z
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.
- API data.montgomerycountymd.gov | Last Updated 2021-07-30T09:45:30.000Z
The purpose of a floodplain study is to establish the 100-year floodplain limits within or near a development in order to preserve the natural resources within the 100-year floodplain, to protect property and persons, and to apply a unified, comprehensive approach to floodplain management. Update Frequency - Daily
- API data.montgomerycountymd.gov | Last Updated 2021-07-30T09:53:41.000Z
The purpose of a Floodplain District Permit (FPDP) is to control floodplain development in order to protect persons and property from danger and destruction and to preserve environmental quality. Floodplain district: Any area specified in Executive regulations that is subject to inundation in a 100-year storm. This includes any waterway with a drainage area of 30 acres or larger. Floodplain district permit: A permit issued by the Department under this article authorizing land-disturbing and construction activities. Floodplain district permit plan: A set of representational drawings or other documents submitted by an applicant to obtain a floodplain district permit that contains the information and specifications the Department requires minimizing the safety hazards of or the negative hydraulic and environmental impacts associated with development in or near a floodplain." Update Frequency : Daily
- API data.montgomerycountymd.gov | Last Updated 2021-07-30T05:41:25.000Z
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
- API opendata.maryland.gov | Last Updated 2018-08-13T20:15:11.000Z
This is the 2014 Integrated Report. EPA approved this submission in accordance with Sections 303(d), 305(b), and 314(l) of the Clean Water Act, on October 16, 2015. The Integrated Report (IR) combines two water quality reports required under sections 305(b) and 303(d) of the federal Clean Water Act. Section 305(b) requires states, territories and authorized tribes to perform annual water quality assessments to determine the status of jurisdictional waters. Section 303(d) requires states, territories and authorized tribes to identify waters assessed as not meeting water quality standards(see Code of Maryland Regulations 26.08.02). Waters that do not meet standards may require a Total Maximum Daily Load to determine the maximum amount of an impairing substance or pollutant that a particular water body can assimilate and still meet water quality criteria. Historically, the 303(d) List and the 305(b) report were submitted to the Environmental Protection Agency (EPA) as separate documents but more recent guidance has called for combining these two reports into a single biennial publication. More information is available at http://www.mde.state.md.us/PROGRAMS/WATER/TMDL/INTEGRATED303DREPORTS/Pages/Programs/WaterPrograms/TMDL/Maryland%20303%20dlist/index.aspx A searchable version of this data is available at http://www.mde.state.md.us/programs/Water/TMDL/Integrated303dReports/Pages/303d.aspx
- API data.colorado.gov | Last Updated 2021-08-01T06:19:41.000Z
A Jurisdictional Dam is a dam creating a reservoir with a capacity of more than 100 acre-feet, or creates a reservoir with a surface area in excess of 20 acres at the high-water line, or exceeds 10 feet in height measured vertically from the elevation of the lowest point of the natural surface of the ground where that point occurs along the longitudinal centerline of the dam up to the crest of the emergency spillway of the dam. For reservoirs created by excavation, or where the invert of the outlet conduit is placed below the surface of the natural ground at its lowest point beneath the dam, the jurisdictional height shall be measured from the invert of the outlet at the longitudinal centerline of the embankment or from the bottom of the excavation at the longitudinal centerline of the dam, whichever is greatest. Jurisdictional height is defined in Rule 4.2.19. The State Engineer shall have final authority over determination of the jurisdictional height of the dam.
- API data.montgomerycountymd.gov | Last Updated 2021-08-01T07:30:44.000Z
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
- API opendata.maryland.gov | Last Updated 2020-01-24T19:19:02.000Z
This data set shows four sources of grant funding for the Governor's Office of Homeland Security (GOHS) and respective awards from 2003 to 2014.
- API data.cdc.gov | Last Updated 2020-06-05T17:27:46.000Z
This dataset includes crude birth rates and general fertility rates in the United States since 1909. The number of states in the reporting area differ historically. In 1915 (when the birth registration area was established), 10 states and the District of Columbia reported births; by 1933, 48 states and the District of Columbia were reporting births, with the last two states, Alaska and Hawaii, added to the registration area in 1959 and 1960, when these regions gained statehood. Reporting area information is detailed in references 1 and 2 below. Trend lines for 1909–1958 are based on live births adjusted for under-registration; beginning with 1959, trend lines are based on registered live births. SOURCES NCHS, National Vital Statistics System, birth data (see https://www.cdc.gov/nchs/births.htm); public-use data files (see https://www.cdc.gov/nchs/data_access/VitalStatsOnline.htm); and CDC WONDER (see http://wonder.cdc.gov/). REFERENCES 1. National Office of Vital Statistics. Vital Statistics of the United States, 1950, Volume I. 1954. Available from: https://www.cdc.gov/nchs/data/vsus/vsus_1950_1.pdf. 2. Hetzel AM. U.S. vital statistics system: major activities and developments, 1950-95. National Center for Health Statistics. 1997. Available from: https://www.cdc.gov/nchs/data/misc/usvss.pdf. 3. National Center for Health Statistics. Vital Statistics of the United States, 1967, Volume I–Natality. 1969. Available from: https://www.cdc.gov/nchs/data/vsus/nat67_1.pdf. 4. Martin JA, Hamilton BE, Osterman MJK, et al. Births: Final data for 2015. National vital statistics reports; vol 66 no 1. Hyattsville, MD: National Center for Health Statistics. 2017. Available from: https://www.cdc.gov/nchs/data/nvsr/nvsr66/nvsr66_01.pdf. 5. Martin JA, Hamilton BE, Osterman MJK, Driscoll AK, Drake P. Births: Final data for 2016. National Vital Statistics Reports; vol 67 no 1. Hyattsville, MD: National Center for Health Statistics. 2018. Available from: https://www.cdc.gov/nvsr/nvsr67/nvsr67_01.pdf. 6. Martin JA, Hamilton BE, Osterman MJK, Driscoll AK, Births: Final data for 2018. National vital statistics reports; vol 68 no 13. Hyattsville, MD: National Center for Health Statistics. 2019. Available from: https://www.cdc.gov/nchs/data/nvsr/nvsr68/nvsr68_13.pdf.