The population density of Aspen Hill, MD was 5,491 in 2018. The population density of Frederick, MD was 3,191 in 2018. The population density of Dale City, VA was 5,167 in 2018.

Population Density

Population Density is computed by dividing the total population by Land Area Per Square Mile.

Above charts are based on data from the U.S. Census American Community Survey | ODN Dataset | API - Notes:

1. ODN datasets and APIs are subject to change and may differ in format from the original source data in order to provide a user-friendly experience on this site.

2. To build your own apps using this data, see the ODN Dataset and API links.

3. If you use this derived data in an app, we ask that you provide a link somewhere in your applications to the Open Data Network with a citation that states: "Data for this application was provided by the Open Data Network" where "Open Data Network" links to Where an application has a region specific module, we ask that you add an additional line that states: "Data about REGIONX was provided by the Open Data Network." where REGIONX is an HREF with a name for a geographical region like "Seattle, WA" and the link points to this page URL, e.g.

Geographic and Population Datasets Involving Frederick, MD or Dale City, VA or Aspen Hill, MD

  • API

    MD COVID-19 - Total Population Tested by County | Last Updated 2022-01-04T16:51:38.000Z

    <b>Summary</b> The total number of residents who have been administered at least one COVID-19 test in each Maryland jurisdiction. <b>Description</b> Data represent the number of Maryland residents, both in number and by percent of the population, who have been tested for COVID-19 at least once each Maryland jurisdiction. <b>Terms of Use</b> 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

    MTA Transit Oriented Development (TOD) Data | Last Updated 2019-08-26T14:17:07.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 ** 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.