The water area of Little Rock, AR was 2 in 2018.

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 - 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 Area 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

    Annexations

    data.littlerock.gov | Last Updated 2021-09-24T21:21:59.000Z

    This dataset contains the Geographic Information Systems (GIS) data for the City of Little Rock Annexation boundaries.

  • API

    Austin's Small Scale Green Infrastructure

    data.austintexas.gov | Last Updated 2021-04-14T22:10:43.000Z

    A rain garden is a low area that absorbs and filters rain water runoff that comes from roofs, sidewalks, and driveways. Rain runs off the hard surfaces, collects in the shallow depression, and slowly soaks into the soil. They are usually planted with colorful native plants and grasses. Every little bit helps to conserve water. Currently we are tracking rain garden bioswale, cistern, and green roofs.

  • API

    Fire Atoms

    data.littlerock.gov | Last Updated 2021-09-24T21:18:14.000Z

    Little Rock Fire Department's Atoms represent the detailed response areas for each of our Fire Districts. Each polygon represents a dispatch code, or "Atom", for a unique dispatch sequence, an ordered list of the nearest patrol districts, used for reference by the Fire Dispatcher.

  • API

    CDPH Environmental Inspections

    data.cityofchicago.org | Last Updated 2022-05-18T12:21:56.000Z

    Inspections conducted by the Department of Environment (DOE) from April, 1997 to December 31, 2011 and by the Department of Public Health (CDPH) since January 1, 2012. On January 1, 2012, the Department of Environment was disbanded and all its inspection, permitting, and enforcement authorities were transferred to the CDPH. Data fields requiring description are detailed below. INSPECTION ID: This is the unique identifier of the inspection. DOE inspection records are prefixed with “DOEINS.” CDPH inspections are numeric. INSPECTION NAME: This is the name of the site that was inspected. This is usually the company/owner name, address, or building name. MAPPED LOCATION: Contains the latitude/longitude coordinates of the facility. The latitude/longitude coordinate is determined through the Chicago Open Data Portal’s geocoding process. INSPECTOR: Contains the name of the inspector or engineer who conducted the inspection. INSPECTION CATEGORY: Describes the type of inspection performed. Generally, inspection types can be organized into the following categories: “COMPLAINT RESPONSE” Inspections conducted in response to citizen complaints. See CDPH Environmental Complaints dataset for type of environmental complaints. “SOLID WASTE INSPECTIONS” Inspections of permitted waste facilities and inspections conducted as part of a delegation agreement with the Illinois Environmental Protection Agency. These inspections include inspections of solid and liquid waste handling facilities, recycling facilities, junkyards, compost facilities, temporary and permanent rock crushing facilities and illegal dump sites. “AIR QUALITY INSPECTION”: Inspections of all permitted industrial facilities with potential to emit pollutants into the air, including area sources such as dry cleaners, motor vehicle repair facilities and architectural surface cleaning. “HAZMATS” Inspections conducted in response to a hazardous material incident and typically conducted with the Fire Department’s HAZMAT units. Also includes inspection audits of facilities subject to Tier II reporting under the Emergency Planning and Community Right-to-Know Act (EPCRA) . “NOISE” Inspections conducted in response to noise-related complaints. “TANK INSPECTIONS” Underground Storage Tank (UST) inspections conducted in conjunction with a UST permit and as part of a delegation agreement with the Illinois Office of the State of Fire Marshall (OSFM).These inspections include including UST Removal, UST Abandon, UST Install, UST Upgrade, UST Reline, UST Repair, Stage II and UST Green Decal. This Inspection Type also includes non-OSFM inspections for Aboveground Storage Tank (AST) permits, Abandoned Gas Stations, Leaking Underground Storage Tanks (LUST), UST Emergency Response, historic Filling Station Licenses, and miscellaneous tank inspections. “DEMOLITION/ASBESTOS” Inspections associated with Demolition or NESHAP Notice of Intents (NOIs). See Chapter 11-4 Article XVIII (see http://tinyurl.com/crvyb29). “MISC INSPECTIONS” Other inspections including but not limited Water Pollution, Site Assessment, historic Bus Facility and historic Invasive Species inspections per Chapter 11-4 Article XXII (see http://tinyurl.com/crvyb29) of the Municipal Code. INSPECTION SUB CATEGORY: More specific inspection type under an Inspection Category. INSPECTION DATE: Date when inspection occurred. NARRATIVE: Contains the inspector’s narrative log of the inspection. DATA SOURCE: The city department that collected the data.

  • API

    Oil and Gas Annual Production: Beginning 2001

    data.ny.gov | Last Updated 2022-02-15T22:11:24.000Z

    This dataset contains annual production information of oil and gas wells in New York State from 2001 to present.

  • API

    ART Bay Area Inundation Scenario - 77" Sea Level Rise

    data.bayareametro.gov | Last Updated 2021-03-15T18:07:55.000Z

    Inundation feature set representing areas vulnerable to a 77 inch rise in sea level for the San Francisco Bay Region. This is a derivative feature set, assembled by the Metropolitan Transportation Commission (MTC), created by merging county-specific, land-only inundation feature sets. The source, county-level feature sets were produced for Adapting to Rising Tides (ART), a program led by the San Francisco Bay Conservation and Development Commission (BCDC), in September 2017. The sea level rise (SLR) scenario used to produce this data represents 77 inches (a little less than six and one-half feet) of water level above the current mean higher high water (MHHW) tidal datum. This is also considered equivalent to 36 inches of SLR plus a 100-year extreme tide. The polygons contain the extent and depth of land-only inundation (in feet) flooding of the bayside shoreline. Depth of flooding were created by subtracting a land surface Digital Elevation Model (DEM) from the water surface DEM representing the SLR scenario (MHHW + SLR). Extent of flooding were created by employing a two rule assessment to determine if an area is inundated. It must be below the assigned water surface DEM elevation value, and it must be connected to an adjacent area that was either flooded or open water. This method applies an "eight-side rule" for connectedness, where the area is considered "connected" if any of its cardinal or diagonal directions is connected to a flooded area or open water. Hydraulic connectivity assessment removes areas from the inundation zone if they are protected by levees or other topographic features that prevent inland inundation. This assessment also removed areas that are low lying but inland and not directly connected to an adjacent inundated area. The 77 inch SLR scenario can be used to approximate all extreme tide/sea level rise combinations that produce a water level in the range of MHHW + 74 inches to MHHW + 80 inches, including: - 77 inches of SLR; - 1-year extreme tide event coupled with 66 inches of SLR; - 2-year extreme tide event coupled with 60 inches of SLR; - 5-year extreme tide event coupled with 54 inches of SLR; - 10-year extreme tide event coupled with 52 inches of SLR; - 25-year extreme tide event coupled with 48 inches of SLR; - 50-year extreme tide event coupled with 42 inches of SLR, and - 100-year extreme tide event coupled with 36 inches of SLR. **In 2019, The San Francisco Bay Conservation and Development Commission released additional data to add East Contra Costa and Solano areas to the existing, 2017 data that focused on San Francisco Bay. This update did not include all the sea level scenarios produced in 2017. The 77-inch scenario was one of the ones for which data for East Contra Costa and Solano was not produced.** Source Data Produced: September 2017 MTC Publication Date: June 2019 Status: Progress: Complete Maintenance and Update Frequency: None planned Contact Information: Contact Organization: Metropolitan Transportation Commission Contact Person: Data & Visualization Contact Address: Address Type: mailing and physical Address: 375 Beale Street, Suite 800 City: San Francisco State or Province: California Postal Code: 94105 Country: United States of America Contact Voice Telephone: (415) 778-6700 Contact Electronic Mail Address: dataviz@bayareametro.gov Hours: 9:00 AM - 5:00 PM (PST) Monday through Friday

  • API

    Flood Hazard Areas (DFIRM Statewide)

    highways.hidot.hawaii.gov | Last Updated 2022-05-01T10:02:20.000Z

  • API

    Beach Report Card Scores (2013-2018)

    data.lacounty.gov | Last Updated 2019-12-06T22:39:37.000Z

    Grades, beach location and analysis from Heal the Bay's Beach Report Card was used (2013-2018), which uses a 12-month grading period from April to March. Seasonal patterns of the most recent year’s grades (2017-2018), as well as trends over the last five years were used. As defined in Assembly Bill 411 in California, the summer dry grading period is from April through October. The winter dry weather grading period is from November through March. The year-round wet weather conditions are graded from April through March. Values may not add up to exactly 100% due to rounding.

  • API

    BREATHE: Edmonton's Green Network Strategy - 2016 Survey Results

    data.edmonton.ca | Last Updated 2022-02-25T21:39:48.000Z

    Setting Priorities for Edmonton’s Green Network Strategy What is Open Space? Open spaces include all outdoor land and water that is publicly owned, and/or publicly accessible. Open spaces can be parks, plazas, boulevards, main streets, ceremonial spaces, natural and protected areas, community gardens, sports fields, and green infrastructure. What is the Green Network Strategy? Edmonton’s Green Network Strategy will examine how open space in the City of Edmonton functions as an integrated network of public spaces that provide real, measureable value to Edmontonians. Open spaces contribute to human health and wellness, improve the urban environment, and provide places for people to come together. These contributions are the central themes of the Green Network Strategy, and provide the organizing framework for assessing open space: • Ecology: Supports and enhances the environment • Wellness: Promotes healthy living • Celebration: Connects people to each other and builds a sense of place. The Survey By completing this survey, you are providing valuable information that will help the City of Edmonton develop an integrated network of open spaces that meets the needs and priorities of Edmontonians. **** This was single topic of particular interest to the City, which was conducted in 2016. To view the survey questions, click on the following link: https://www.edmontoninsightcommunity.ca/R.aspx?a=1011&as=ct4cG2Cs8X&t=1 Open from May 2 through to September 2, 2016. At the time the survey was launched survey invitations were sent to 7,233 Insight Community Members. 1,541 members completed the survey which represents a completion rate of 21%. A total of 2,274 respondents completed the survey: 1,541 Insight Community Members and 733 from the call to action button on our web page or from using the anonymous link(s) on edmonton.ca/surveys. The demographics from external/anonymous link has been captured and is combined with the demographics of the Community Members. Column definitions can be found as an attachment to this dataset (under the About option, in the Attachment section).