The land area of Nome Census Area, AK was 22,962 in 2018. The land area of Boundary County, ID was 1,269 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 -
Geographic and Area Datasets Involving Boundary County, ID or Nome Census Area, AK
- API
Waste Tire Abatement Sites
data.ny.gov | Last Updated 2022-08-12T17:59:04.000ZInformation on designated waste tire abatement sites in New York State, including approximate size, location, and abatement status.
- API
Assessor [Archived 05-31-2023] - Parcel Universe
datacatalog.cookcountyil.gov | Last Updated 2023-05-31T21:51:45.000ZA complete, historic universe of Cook County parcels with attached geographic, governmental, and spatial data. When working with Parcel Index Numbers (PINs) make sure to zero-pad them to 14 digits. Some datasets may lose leading zeros for PINs when downloaded. Additional notes:<ul><li>Data is attached via spatial join (st_contains) to each parcel's centroid.</li> <li>Centroids are based on <a href="https://datacatalog.cookcountyil.gov/Property-Taxation/ccgisdata-Parcel-2021/77tz-riq7">Cook County parcel shapefiles</a>.</li> <li>Older properties may be missing coordinates and thus also missing attached spatial data (usually they are missing a parcel boundary in the shapefile).</li> <li>Newer properties may be missing a mailing or property address, as they need to be assigned one by the postal service.</li> <li>Attached spatial data does NOT go all the way back to 1999. It is only available for more recent years, primarily those after 2012.</li> <li>The universe contains data for the current tax year, which may not be complete or final. PINs can still be added and removed to the universe up until the Board of Review closes appeals.</li> <li>Data will be updated monthly.</li> <li>Rowcount and characteristics for a given year are final once the Assessor <a href="https://www.cookcountyassessor.com/assessment-calendar-and-deadlines">has certified the assessment roll</a> for all townships.</li> <li>Depending on the time of year, some third-party and internal data will be missing for the most recent year. Assessments mailed this year represent values from last year, so this isn't an issue. By the time the Data Department models values for this year, those data will have populated.</li> <li>Current property class codes, their levels of assessment, and descriptions can be found <a href="https://prodassets.cookcountyassessor.com/s3fs-public/form_documents/classcode.pdf">on the Assessor's website</a>. Note that class codes details can change across time.</li> <li>Due to decrepencies between the systems used by the Assessor and Clerk's offices, <i>tax_district_code</i> is not currently up-to-date in this table.</li></ul> For more information on the sourcing of attached data and the preparation of this dataset, see the <a href="https://gitlab.com/ccao-data-science---modeling/data-architecture">Assessor's data architecture repo</a> on GitLab. <a href="https://datacatalog.cookcountyil.gov/stories/s/i22y-9sd2">Read about the Assessor's 2022 Open Data Refresh.</a>
- API
National Incorporated Places and Counties
mydata.iowa.gov | Last Updated 2023-08-30T17:36:07.000ZThis dataset contains a listing of incorporated places (cities and towns) and counties within the United States including the GNIS code, FIPS code, name, entity type and primary point (location) for the entity. The types of entities listed in this dataset are based on codes provided by the U.S. Census Bureau, and include the following: 1. C1 - An active incorporated place that does not serve as a county subdivision equivalent; 2. C2 - An active incorporated place legally coextensive with a county subdivision but treated as independent of any county subdivision; 3. C3 - A consolidated city; 4. C4 - An active incorporated place with an alternate official common name; 5. C5 - An active incorporated place that is independent of any county subdivision and serves as a county subdivision equivalent; 6. C6 - An active incorporated place that partially is independent of any county subdivision and serves as a county subdivision equivalent or partially coextensive with a county subdivision but treated as independent of any county subdivision; 7. C7 - An incorporated place that is independent of any county; 8. C8 - The balance of a consolidated city excluding the separately incorporated place(s) within that consolidated government; 9. C9 - An inactive or nonfunctioning incorporated place; 10. H1 - An active county or statistically equivalent entity; 11. H4 - A legally defined inactive or nonfunctioning county or statistically equivalent entity; 12. H5 - A census areas in Alaska, a statistical county equivalent entity; and 13. H6 - A county or statistically equivalent entity that is areally coextensive or governmentally consolidated with an incorporated place, part of an incorporated place, or a consolidated city.
- API
Census Tracts 2010 Centroids
data.bayareametro.gov | Last Updated 2021-11-19T16:27:25.000ZCentroid of 2010 census tracts. Provides 2010 census tracts for the San Francisco Bay Region, clipped by the Metropolitan Transportation Commission to remove major coastal and bay water areas. 2010 Census tracts for the San Francisco Bay Region, clipped to remove major coastal and bay water areas. Features were extracted from, and clipped using, California 2018 TIGER/Line shapefiles by the Metropolitan Transportation Commission. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and are reviewed and updated by local participants prior to each decennial census as part of the Census Bureau’s Participant Statistical Areas Program (PSAP). The Census Bureau updates census tracts in situations where no local participant existed or where local or tribal governments declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of decennial census data. Census tracts generally have a population size between 1,200 and 8,000 people with an optimum size of 4,000 people. The spatial size of census tracts varies widely depending on the density of settlement. Ideally, census tract boundaries remain stable over time to facilitate statistical comparisons from census to census. However, physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, significant changes in population may result in splitting or combining census tracts. 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 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. Census Tract Codes and Numbers—Census tract numbers have up to a 4-character basic number and may have an optional 2-character suffix; for example, 1457.02. The census tract numbers (used as names) eliminate any leading zeroes and append a suffix only if required. The 6-character numeric census tract codes, however, include leading zeroes and have an implied decimal point for the suffix. Census tract codes range from 000100 to 998999 and are unique within a county or equivalent area. The Census Bureau assigned a census tract code of 9900 to represent census tracts delineated to cover large bodies of water. In addition, census tract codes in the 9400s represent American Indian Areas and codes in the 9800s represent special land use areas. The Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Local participants have an opportunity to review the existing census tracts before each census. If local participants split a census tract, the split parts usually retain the basic number, but receive different suffixes. In a few counties, local participants request major changes to, and renumbering of, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes. Relationship to Other Geographic Entities—Within the standard census geographic hierarchy, census tracts never cross state or county boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian, Alaska Native, and Native Hawaiian areas.
- API
2020 Census Tracts to 2020 NTAs and CDTAs Equivalency
data.cityofnewyork.us | Last Updated 2022-05-09T22:20:51.000ZThis file shows the relationship between New York City’s 2020 census tracts, 2020 Neighborhood Tabulation Areas (NTAs), and Community District Tabulation Areas (CDTAs). 2020 census tracts nest within 2020 NTAs, and 2020 NTAs nest within CDTAs, so each census tract is listed only once. Note that CDTAs sometimes cross borough boundaries, and therefore will not add up to borough totals for the Bronx, Queens, and Manhattan. As they are nested within CDTAs, NTAs will likewise not add up to borough totals. Also note that census tracts in New York City’s water areas are excluded from this file.
- API
Iowa Geographic Names
mydata.iowa.gov | Last Updated 2024-05-17T22:00:20.000ZThis dataset provides the geographic names data for Iowa. All names data products are extracted from the Geographic Names Information System (GNIS), the Federal Government's repository of official geographic names. The GNIS contains the federally recognized name of each feature and defines its location by State, county, USGS topographic map, and geographic coordinates. GNIS also lists variant names, which are non-official names by which a feature is or was known. Other attributes include unique Feature ID and feature class. Feature classes under the purview of the U.S. Board on Geographic Names include natural features, unincorporated populated places, canals, channels, reservoirs, and more.
- API
Intercity Air, Bus, and Rail Transportation Facilities
data.bts.gov | Last Updated 2024-02-23T21:43:55.000ZAirports with scheduled service and intercity bus and intercity rail (Amtrak/Alaska rail) facilities for years 2006, 2012, 2018, and 2021. Used to find rural areas with access to one or more of these transportation modes: https://data.transportation.gov/Research-and-Statistics/Access-to-Intercity-Transportation-in-Rural-Areas/29cj-8s4a . Airports with scheduled service and intercity bus and intercity rail (Amtrak/Alaska rail) facilities for years 2006, 2012, 2018, and 2023. Used to find rural areas with access to one or more of these transportation modes: https://data.transportation.gov/Research-and-Statistics/Access-to-Intercity-Transportation-in-Rural-Areas/29cj-8s4a . In 2021, bus stops are from the Intercity Bus Atlas (https://geodata.bts.gov/datasets/usdot::intercity-bus-atlas-stops/explore). To allow the use of the Intercity Bus Atlas (ICBA) datasets, intercity bus providers grant the USDOT a Creative Commons Attribution – Non-commercial 4.0 International (CC-BY-NC 4.0) license. The CC-BY-NC 4.0 license is available at, https://creativecommons.org/licenses/by-nc/4.0/legalcode. For more information about the memorandum of understanding between partner intercity bus providers and BTS underlying the ICBA, please consult https://www.bts.gov/national-intercity-bus-atlas-partnerships. ICBA data are permitted and encouraged for research, analysis, and planning. The data are not intended for trip planning, scheduling, navigation, or any real-time or near real-time use by passengers, transportation operators, service providers, or transportation planners. Commercial and all other reuse of the data is prohibited. As part of the license agreement for the data, BTS are also not permitted to make substantive material alterations to the submitted GTFS data. All other uses or re-uses of the data are prohibited. Finally, BTS expressly disclaims all liability for the unauthorized use of or misuse of any data collected as a part of this effort by third parties. BTS furthermore does not guarantee the real-time or near real-time accuracy or quality of the data as route service information, bus stop location information and other data collected may change over time. Interactive map showing access to intercity transportation in rural areas: https://datahub.transportation.gov/stories/s/Rural-Access-to-Intercity-Transportation/gr9y-9gjq/edit Methodology: https://datahub.transportation.gov/stories/s/dbb4-pr2c
- API
Safe Drinking Water Facilities Information System for Pennsylvania 2018 - Current Environmental Protection
data.pa.gov | Last Updated 2022-10-24T13:20:24.000ZSafe Drinking Water Information System (SDWIS) is EPA’s national database that manages and collects public water system information from states, including reports of drinking water standard violations, reporting and monitoring violations, and other basic information. The data derived in the State of Pennsylvania is published and searchable online on the www.pa.gov website. This set contains the Water System Facility data, which will be updated annually for the prior calendar year in the first Quarter of the following year.
- API
Final Disadvantaged Communities (DAC) 2023
data.ny.gov | Last Updated 2023-10-11T02:17:42.000ZThe Climate Leadership and Community Protection Act (CLCPA) directs the Climate Justice Working Group (CJWG) to establish criteria for defining disadvantaged communities. This dataset identifies areas throughout the State that meet the final disadvantaged community definition as voted on by the Climate Justice Working Group. The New York State Energy Research and Development Authority (NYSERDA) offers objective information and analysis, innovative programs, technical expertise, and support to help New Yorkers increase energy efficiency, save money, use renewable energy, accelerate economic growth, and reduce reliance on fossil fuels. To learn more about NYSERDA’s programs, visit nyserda.ny.gov or follow us on Twitter, Facebook, YouTube, or Instagram.
- API
ACS 5-Year Demographic Characteristics of DC Census Tracts
fusioncenter.nhit.org | Last Updated 2024-05-17T15:48:05.000Z<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Age, Sex, Race, Ethnicity, Total Housing Units, and Voting Age Population. This service is updated annually with American Community Survey (ACS) 5-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: Census Tracts. </SPAN><SPAN STYLE="font-weight:bold;">Current Vintage: 2018-2022. ACS Table(s): DP05. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: January 2, 2024.</SPAN><SPAN> National Figures: data.census.gov. Please cite the Census and ACS when using this data. Data Note from the Census: Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables. Data Processing Notes: This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2020 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>