The population density of Little Rock, AR was 1,662 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 http://opendatanetwork.com. 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. http://opendatanetwork.com/region/1600000US5363000/Seattle_WA

Geographic and Population Datasets Involving Little Rock, AR

  • API

    Central Arkansas Library Locations WiFi

    data.littlerock.gov | Last Updated 2021-02-12T16:11:14.000Z

    This dataset contains the names and locations of Central Arkansas Library branches in Little Rock that have WiFi access available. CALS-Guest1

  • API

    Minority Owned Business Enterprise

    data.littlerock.gov | Last Updated 2023-08-15T14:48:07.000Z

    This data set provides a list of Minority Owned Business in the City of Little Rock.

  • API

    NeighborhoodStatisticalAreas

    data.richmondgov.com | Last Updated 2024-04-10T19:12:34.000Z

    The City needed geographical area definitions that were homogenous and non-political. The preexisting Neighborhoods feature class was defined to maintain homogenous areas of the City, but they were determined to be too discrete and numerous. Pertaining to size as well, it was believed that the geographical areas should not be so large, as to group together areas of the City that were dissimilar in character. Of particular importance, it was also a requirement that NSA geography was designed to permit analysis using Census data. It was decided by the Planning Dept that adhering to Census Block Groups was the best approach. It was also determined that attempts to approximate the Planning Districts would also be beneficial. The approach to defining the NSAs was as follows: a) 2010 Census Block Groups were merged together to create each individual NSA, b) they were grouped in ways to maximize the ability to share boundaries with existing Planning Districts were ever possible. While most NSAs lie almost entirely within one Planning District, some NSAs are pretty equally split between two planning districts (notably D-1). In the case of D-1, PDR arbitrarily decided to put it with the other ‘Downtown’ NSAs. The identification/naming of the NSAs was based upon the Planning Districts they most corresponded to, along with a sequential numbering assignment. Most NSA lie almost entirely within one Planning District, and where named from that Planning District. Names starting with "NO" are mostly in the North planning district; "NW" are mostly in the Near West planning district; "BR" are mostly in the Broad Rock planning district, etc... There’s no significance for the number following the planning district lettering used by NSAs (NO-1, NO-2, NO-3, etc). The number was just randomly assigned to further uniquely define the area subdivided within the Planning District, and has no relationship in terms to square area, population density, or anything.

  • API

    Tracts 2020

    data.delaware.gov | Last Updated 2024-03-01T14:44:49.000Z

    <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.</SPAN></P><P><SPAN>Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2020 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2010 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area.</SPAN></P></DIV></DIV></DIV>

  • API

    National Community Based Survey of Supports for Healthy Eating and Active Living (CBS HEAL)

    data.cdc.gov | Last Updated 2023-08-25T15:08:48.000Z

    Community-Based Survey of Supports for Healthy Eating and Active Living (CBS HEAL) is a CDC survey of a nationally representative sample of U.S. municipalities to better understand existing community-level policies and practices that support healthy eating and active living. The survey collects information about policies such as nutrition standards, incentives for healthy food retail, bike/pedestrian-friendly design, and Complete Streets. About 2,000 municipalities respond to the survey. Participating municipalities receive a report that allows them to compare their policies and practices with other municipalities of similar geography, population size, and urban status. The CBS HEAL survey was first administered in 2014 and was administered again in 2021. Data is provided in multiple formats for download including as a SAS file. A methods report and a SAS program for formatting the data are also provided.