The land area of Calverton, MD was 5 in 2017. The land area of Takoma Park, MD was 2 in 2017.
Land Area
Water Area
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.
Above charts are based on data from the U.S. Census American Community Survey | ODN Dataset | API -
Geographic and Area Datasets Involving Calverton, MD or Takoma Park, MD
- API
Power Outages - Zipcode
opendata.maryland.gov | Last Updated 2024-09-21T17:45:34.000ZContains aggregated power outage data by ZIP Code. Limited historical record inventory. Designed for and consumed by the MEMA Power Outage web application.
- API
Power Outages - County
opendata.maryland.gov | Last Updated 2024-09-21T17:45:34.000ZContains aggregated power outage data by County. Limited historical record inventory. Designed for and consumed by the MEMA Power Outage web application.
- API
Homeland Security Grant Awards 2003 - 2014
opendata.maryland.gov | Last Updated 2020-01-24T19:19:02.000ZThis 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
Crash Reporting - Incidents Data
data.montgomerycountymd.gov | Last Updated 2024-09-20T05:41:55.000ZThis 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
MDOT Performance Dashboard - Annual Data
opendata.maryland.gov | Last Updated 2016-11-23T16:13:04.000ZSet of annual MDOT perfromance data including port, transit, bridge and highway condition, and MVA branch office wait time data.
- API
MC311 Service Requests
data.montgomerycountymd.gov | Last Updated 2024-09-21T05:17:25.000ZInformation 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
Floodplain Study
data.montgomerycountymd.gov | Last Updated 2024-09-09T09:45:19.000ZThe 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
Crash Reporting - Drivers Data
data.montgomerycountymd.gov | Last Updated 2024-09-20T05:46:26.000ZThis dataset provides information on motor vehicle operators (drivers) involved in traffic collisions occurring on county and local roadways. The dataset reports 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. This dataset shows each collision data recorded and the drivers involved. 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 - Incidents Data at https://data.montgomerycountymd.gov/Public-Safety/Crash-Reporting-Incidents-Data/bhju-22kf * Crash Reporting - Non-Motorists Data at https://data.montgomerycountymd.gov/Public-Safety/Crash-Reporting-Non-Motorists-Data/n7fk-dce5 Update Frequency : Weekly
- API
Greenhouse Gas Emissions
data.montgomerycountymd.gov | Last Updated 2024-09-16T12:01:48.000ZThe monthly Greenhouse Gas (GHG) emission data represents Montgomery County Facilities and Fleet by month beginning July 2019. Facilities: The Facilities GHG data represents physical structures used by County residents and County staff who provide services for County residents. Examples include recreation, libraries, theater and arts, health and human services, liquor retail, courthouses, general services, maintenance facilities, correctional facilities, police stations, fire stations, volunteer fire stations, garages, parking lots, bus shelters and park & ride locations. Facilities use the following fuel sources: grid electricity, natural gas, propane and diesel fuel. Facilities GHG data DOES NOT include Montgomery County Public Schools, Montgomery College and Montgomery Parks Maryland-National Capital Park and Planning Commission (M-NCPPC). Fleet: The Fleet GHG data represents Montgomery County vehicles used by County staff who provide services for County residents. Examples include mass transit buses, snowplows, liquor trucks, light duty trucks, police cars, fire engines and fire service equipment, etc. Each County vehicle use different fuel sources (i.e. diesel, mobil diesel, compressed natural gas, unleaded and E-85). Fleet GHG data DOES NOT include Montgomery County Public School buses, Montgomery College and Montgomery Parks Maryland-National Capital Park and Planning Commission (M-NCPPC) vehicles. GHG Calculation Method: Facilities and Fleet fuel sources are converted into one common unit of energy- 1 Million British thermal units (MMBtu) which are then used with emissions factors and 100-year global warming potential (GWP) to calculate GHG emissions into one common unit of measure- Metric Tons of CO2 Equivalent (MTCO2e). For more information go to: • How to Calculate GHG emissions at https://www.youtube.com/watch?v=zq5wTjvLqnY&t=186s • Emissions & Generation Resource Integrated Database (eGRID) at https://www.epa.gov/energy/emissions-generation-resource-integrated-database-egrid • Emission Factors for GHG Inventories at https://www.epa.gov/sites/production/files/2018-03/documents/emission-factors_mar_2018_0.pdf Update Frequency : Monthly
- API
MTA Transit Oriented Development (TOD) Data
opendata.maryland.gov | Last Updated 2024-03-25T15:38:10.000Z*** DISCLAIMER - This web page is a public resource of general information. The Maryland Mass Transit Administration (MTA) makes no warranty, representation, or guarantee as to the content, sequence, accuracy, timeliness, or completeness of any of the spatial data or database information provided herein. MTA and partner state, local, and other agencies shall assume no liability for errors, omissions, or inaccuracies in the information provided regardless of how caused; or any decision made or action taken or not taken by any person relying on any information or data furnished within. *** This dataset assesses rail station potential for different forms of transit oriented development (TOD). A key driver of increased transit ridership in Maryland, TOD capitalizes on existing rapid transit infrastructure. The online tool focuses on the MTA’s existing MARC Commuter Rail, Metro Subway, and Central Light Rail lines and includes information specific to each station. The goal of this dataset is to give MTA planning staff, developers, local governments, and transit riders a picture of how each MTA rail station could attract TOD investment. In order to make this assessment, MTA staff gathered data on characteristics that are likely to influence TOD potential. The station-specific data is organized into 6 different categories referring to transit activity; station facilities; parking provision and utilization; bicycle and pedestrian access; and local zoning and land availability around each station. As a publicly shared resource, this dataset can be used by local communities to identify and prioritize area improvements in coordination with the MTA that can help attract investment around rail stations. You can view an interactive version of this dataset at geodata.md.gov/tod. ** Ridership is calculated the following ways: Metro Rail ridership is based on Metro gate exit counts. Light Rail ridership is estimated using a statistical sampling process in line with FTA established guidelines, and approved by the FTA. MARC ridership is calculated using two (2) independent methods: Monthly Line level ridership is estimated using a statistical sampling process in line with FTA established guidelines, and approved by the FTA. This method of ridership calculation is used by the MTA for official reporting purposes to State level and Federal level reporting. Station level ridership is estimated by using person counts completed by the third party vendor. This method of calculation has not been verified by the FTA for statistical reporting and is used for scheduling purposes only. However, because of the granularity of detail, this information is useful for TOD applications. *Please note that the monthly level ridership and the station level ridership are calculated using two (2) independent methods that are not interchangeable and should not be compared for analysis purposes.