This API returns a geography of a specified geography type by the geography id.

This dataset was created to help users to go between County - State Name, State-County FIPS, City, or to ZIP Code. Most importantly, this dataset was created because we shouldn't have to pay for free & public data.

Assumptions - HUD uses the most up to date Zip Code boundaries from the USPS when they post their new Quarterly data. *ZIP Codes are updated on a regular basis. Here is an example announcement from the USPS. - City data only available from 2018 onward.

Data Sources

US HUD https://www.huduser.gov/portal/datasets/usps.html

Census Bureau The table data, direct link. This data is only updated once every census, 10 years. The details of the National County text file can be found here

USPS Zip to City Lookup More information can be found here. It's a free API from the USPS. Need to create a username to pull the data.

Data Dictionary

Files 2018 -> Newer - ZIP ZIP Code - STCOUNTFP US State & County FIPS ID - CITY City for that Zip/Fips Code - STATE US State - COUNTYNAME US County Name - CLASSFP FIPS Class Code, as defined by the Census

Files 2010-2017 - ZIP ZIP Code - COUNTYNAME US County Name - STATE US State - STCOUNTFP US State & County FIPS ID - CLASSFP FIPS Class Code, as defined by the Census

FIPS Class Code Details Source Copied 7/29/17

• H1 identifies an active county or statistically equivalent entity that does not qualify under subclass C7 or H6.
• H4 identifies a legally defined inactive or nonfunctioning county or statistically equivalent entity that does not qualify under subclass H6.
• H5 identifies census areas in Alaska, a statistical county equivalent entity.
• H6 identifies a county or statistically equivalent entity that is a really coextensive or governmentally consolidated with an incorporated place, part of an incorporated place, or a consolidated city.
• C7 identifies an incorporated place that is an independent city; that is, it also serves as a county equivalent because it is not part of any county, and a minor civil division (MCD) equivalent because it is not part of any MCD.

Acknowlegement

Foto von Annie Spratt auf Unsplash

🇺🇸 미국

USA Census Block Groups (CBG) for Urban Search and Rescue. This layer can be used for search segment planning. Block groups generally contain between 600 and 5,000 people and the boundaries generally follow existing roads and waterways. The field segment_designation is the last 6 digits of the unique identifier and matches the field in the SARCOP Segment layer.Data download date: August 12, 2021Census tables: P1, P2, P3, P4, H1, P5, HeaderDownloaded from: Census FTP siteProcessing Notes:Data was downloaded from the U.S. Census Bureau FTP site, imported into SAS format and joined to the 2020 TIGER boundaries. Boundaries are sourced from the 2020 TIGER/Line Geodatabases. Boundaries have been projected into Web Mercator and each attribute has been given a clear descriptive alias name. No alterations have been made to the vertices of the data.Each attribute maintains it's specified name from Census, but also has a descriptive alias name and long description derived from the technical documentation provided by the Census. For a detailed list of the attributes contained in this layer, view the Data tab and select "Fields". The following alterations have been made to the tabular data:Joined all tables to create one wide attribute table:P1 - RaceP2 - Hispanic or Latino, and not Hispanic or Latino by RaceP3 - Race for the Population 18 Years and OverP4 - Hispanic or Latino, and not Hispanic or Latino by Race for the Population 18 Years and OverH1 - Occupancy Status (Housing)P5 - Group Quarters Population by Group Quarters Type (correctional institutions, juvenile facilities, nursing facilities/skilled nursing, college/university student housing, military quarters, etc.)HeaderAfter joining, dropped fields: FILEID, STUSAB, CHARITER, CIFSN, LOGRECNO, GEOVAR, GEOCOMP, LSADC, and BLOCK.GEOCOMP was renamed to GEOID and moved be the first column in the table, the original GEOID was dropped.Placeholder fields for future legislative districts have been dropped: CD118, CD119, CD120, CD121, SLDU22, SLDU24, SLDU26, SLDU28, SLDL22, SLDL24 SLDL26, SLDL28.P0020001 was dropped, as it is duplicative of P0010001. Similarly, P0040001 was dropped, as it is duplicative of P0030001.In addition to calculated fields, County_Name and State_Name were added.The following calculated fields have been added (see long field descriptions in the Data tab for formulas used): PCT_P0030001: Percent of Population 18 Years and OverPCT_P0020002: Percent Hispanic or LatinoPCT_P0020005: Percent White alone, not Hispanic or LatinoPCT_P0020006: Percent Black or African American alone, not Hispanic or LatinoPCT_P0020007: Percent American Indian and Alaska Native alone, not Hispanic or LatinoPCT_P0020008: Percent Asian alone, Not Hispanic or LatinoPCT_P0020009: Percent Native Hawaiian and Other Pacific Islander alone, not Hispanic or LatinoPCT_P0020010: Percent Some Other Race alone, not Hispanic or LatinoPCT_P0020011: Percent Population of Two or More Races, not Hispanic or LatinoPCT_H0010002: Percent of Housing Units that are OccupiedPCT_H0010003: Percent of Housing Units that are VacantPlease note these percentages might look strange at the individual block group level, since this data has been protected using differential privacy.* *To protect the privacy and confidentiality of respondents, data has been protected using differential privacy techniques by the U.S. Census Bureau. This means that some individual block groups will have values that are inconsistent or improbable. However, when aggregated up, these issues become minimized. The pop-up on this layer uses Arcade to display aggregated values for the surrounding area rather than values for the block group itself.Download Census redistricting data in this layer as a file geodatabase.Additional links:U.S. Census BureauU.S. Census Bureau Decennial CensusAbout the 2020 Census2020 Census2020 Census data qualityDecennial Census P.L. 94-171 Redistricting Data Program

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. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

The documentation below is in reference to this items placement in the NM Supply Chain Data Hub. The documentation is of use to understanding the source of this item, and how to reproduce it for updatesTitle: Soil Survey Geographic Database (SSURGO) DownloaderItem Type: Web Mapping Application URLSummary: Download ready-to-use project packages with over 170 attributes derived from the SSURGO (Soil Survey Geographic Database) dataset.Notes: Prepared by: Uploaded by EMcRae_NMCDCSource: https://nmcdc.maps.arcgis.com/home/item.html?id=cdc49bd63ea54dd2977f3f2853e07fff link to Esri web mapping applicationFeature Service: https://nmcdc.maps.arcgis.com/home/item.html?id=305ef916da574a71877edb15c3f47f08#overviewUID: 26Data Requested: Ag CensusMethod of Acquisition: Esri web mapDate Acquired: 6/16/22Priority rank as Identified in 2022 (scale of 1 being the highest priority, to 11 being the lowest priority): 8Tags: PENDINGDOCUMENTATION FROM DATA SOURCE URL: This application provides quick access to ready-to-use project packages filled with useful soil data derived from the SSURGO dataset.To use this application, navigate to your study area and click the map. A pop-up window will open. Click download and the project package will be copied to your computer. Double click the downloaded package to open it in ArcGIS Pro. Alt + click on the layer in the table of contents to zoom to the subbasin.Soil map units are the basic geographic unit of the Soil Survey Geographic Database (SSURGO). The SSURGO dataset is a compilation of soils information collected over the last century by the Natural Resources Conservation Service (NRCS). Map units delineate the extent of different soils. Data for each map unit contains descriptions of the soil’s components, productivity, unique properties, and suitability interpretations.Each soil type has a unique combination of physical, chemical, nutrient and moisture properties. Soil type has ramifications for engineering and construction activities, natural hazards such as landslides, agricultural productivity, the distribution of native plant and animal life and hydrologic and other physical processes. Soil types in the context of climate and terrain can be used as a general indicator of engineering constraints, agriculture suitability, biological productivity and the natural distribution of plants and animals.Dataset SummaryThe map packages were created from the October 2021 SSURGO snapshot. The dataset covers the 48 contiguous United States plus Hawaii and portions of Alaska. Map packages are available for Puerto Rico and the US Virgin Islands. A project package for US Island Territories and associated states of the Pacific Ocean can be downloaded by clicking one of the included areas in the map. The Pacific Project Package includes: Guam, the Marshall Islands, the Northern Marianas Islands, Palau, the Federated States of Micronesia, and American Samoa.Not all areas within SSURGO have completed soil surveys and many attributes have areas with no data. The soil data in the packages is also available as a feature layer in the ArcGIS Living Atlas of the World.AttributesKey fields from nine commonly used SSURGO tables were compiled to create the 173 attribute fields in this layer. Some fields were joined directly to the SSURGO Map Unit polygon feature class while others required summarization and other processing to create a 1:1 relationship between the attributes and polygons prior to joining the tables. Attributes of this layer are listed below in their order of occurrence in the attribute table and are organized by the SSURGO table they originated from and the processing methods used on them.Map Unit Polygon Feature Class Attribute TableThe fields in this table are from the attribute table of the Map Unit polygon feature class which provides the geographic extent of the map units.Area SymbolSpatial VersionMap Unit SymbolMap Unit TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the table using the Map Unit Key field.Map Unit NameMap Unit KindFarmland ClassInterpretive FocusIntensity of MappingIowa Corn Suitability RatingLegend TableThis table has 1:1 relationship with the Map Unit table and was joined using the Legend Key field.Project ScaleSurvey Area Catalog TableThe fields in this table have a 1:1 relationship with the polygons and were joined to the Map Unit table using the Survey Area Catalog Key and Legend Key fields.Survey Area VersionTabular VersionMap Unit Aggregated Attribute TableThe fields in this table have a 1:1 relationship with the map unit polygons and were joined to the Map Unit attribute table using the Map Unit Key field.Slope Gradient - Dominant ComponentSlope Gradient - Weighted AverageBedrock Depth - MinimumWater Table Depth - Annual MinimumWater Table Depth - April to June MinimumFlooding Frequency - Dominant ConditionFlooding Frequency - MaximumPonding Frequency - PresenceAvailable Water Storage 0-25 cm - Weighted AverageAvailable Water Storage 0-50 cm - Weighted AverageAvailable Water Storage 0-100 cm - Weighted AverageAvailable Water Storage 0-150 cm - Weighted AverageDrainage Class - Dominant ConditionDrainage Class - WettestHydrologic Group - Dominant ConditionIrrigated Capability Class - Dominant ConditionIrrigated Capability Class - Proportion of Map Unit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Map Unit with Dominant ConditionRating for Buildings without Basements - Dominant ConditionRating for Buildings with Basements - Dominant ConditionRating for Buildings with Basements - Least LimitingRating for Buildings with Basements - Most LimitingRating for Septic Tank Absorption Fields - Dominant ConditionRating for Septic Tank Absorption Fields - Least LimitingRating for Septic Tank Absorption Fields - Most LimitingRating for Sewage Lagoons - Dominant ConditionRating for Sewage Lagoons - Dominant ComponentRating for Roads and Streets - Dominant ConditionRating for Sand Source - Dominant ConditionRating for Sand Source - Most ProbableRating for Paths and Trails - Dominant ConditionRating for Paths and Trails - Weighted AverageErosion Hazard of Forest Roads and Trails - Dominant ComponentHydric Classification - PresenceRating for Manure and Food Processing Waste - Weighted AverageComponent Table – Dominant ComponentMap units have one or more components. To create a 1:1 join component data must be summarized by map unit. For these fields a custom script was used to select the component with the highest value for the Component Percentage Representative Value field (comppct_r). Ties were broken with the Slope Representative Value field (slope_r). Components with lower average slope were selected as dominant. If both soil order and slope were tied, the first value in the table was selected.Component Percentage - Low ValueComponent Percentage - Representative ValueComponent Percentage - High ValueComponent NameComponent KindOther Criteria Used to Identify ComponentsCriteria Used to Identify Components at the Local LevelRunoff ClassSoil loss tolerance factorWind Erodibility IndexWind Erodibility GroupErosion ClassEarth Cover 1Earth Cover 2Hydric ConditionHydric RatingAspect Range - Counter Clockwise LimitAspect - Representative ValueAspect Range - Clockwise LimitGeomorphic DescriptionNon-Irrigated Capability SubclassNon-Irrigated Unit Capability ClassIrrigated Capability SubclassIrrigated Unit Capability ClassConservation Tree Shrub GroupGrain Wildlife HabitatGrass Wildlife HabitatHerbaceous Wildlife HabitatShrub Wildlife HabitatConifer Wildlife HabitatHardwood Wildlife HabitatWetland Wildlife HabitatShallow Water Wildlife HabitatRangeland Wildlife HabitatOpenland Wildlife HabitatWoodland Wildlife HabitatWetland Wildlife HabitatSoil Slip PotentialSusceptibility to Frost HeavingConcrete CorrosionSteel CorrosionTaxonomic ClassTaxonomic OrderTaxonomic SuborderGreat GroupSubgroupParticle SizeParticle Size ModCation Exchange Activity ClassCarbonate ReactionTemperature ClassMoist SubclassSoil Temperature RegimeEdition of Keys to Soil Taxonomy Used to Classify SoilCalifornia Storie IndexComponent KeyComponent Table – Weighted AverageMap units may have one or more soil components. To create a 1:1 join, data from the Component table must be summarized by map unit. For these fields a custom script was used to calculate an average value for each map unit weighted by the Component Percentage Representative Value field (comppct_r).Slope Gradient - Low ValueSlope Gradient - Representative ValueSlope Gradient - High ValueSlope Length USLE - Low ValueSlope Length USLE - Representative ValueSlope Length USLE - High ValueElevation - Low ValueElevation - Representative ValueElevation - High ValueAlbedo - Low ValueAlbedo - Representative ValueAlbedo - High ValueMean Annual Air Temperature - Low ValueMean Annual Air Temperature - Representative ValueMean Annual Air Temperature - High ValueMean Annual Precipitation - Low ValueMean Annual Precipitation - Representative ValueMean Annual Precipitation - High ValueRelative Effective Annual Precipitation - Low ValueRelative Effective Annual Precipitation - Representative ValueRelative Effective Annual Precipitation - High ValueDays between Last and First Frost - Low ValueDays between Last and First Frost - Representative ValueDays between Last and First Frost - High ValueRange Forage Annual Potential Production - Low ValueRange Forage Annual Potential Production - Representative ValueRange Forage Annual Potential Production - High ValueInitial Subsidence - Low ValueInitial Subsidence - Representative ValueInitial Subsidence - High ValueTotal Subsidence - Low ValueTotal Subsidence - Representative ValueTotal Subsidence - High ValueCrop Productivity IndexEsri SymbologyThis field was created to provide symbology based on the Taxonomic Order field (taxorder). Because some map units have a null value for soil order, a

This dataset is part of an article entitled "ORTHOMETRIC, NORMAL AND GEOID HEIGHTS IN THE CONTEXT OF THE BRAZILIAN ALTIMETRIC NETWORK" (https://doi.org/10.1590/s1982-21702022000100003), published in the Bulletin of Geodesic Sciences.

This dataset includes 569 stations whose values for geodetic and normal height, gravity and geopotential numbers are provided by the IBGE (Brazilian Institute of Geography and Statistics). In addition, we included orthometric height data and differences between orthometric and normal height data calculated from the Hemlert and Mader methods, using constant and variable density data provided by Medeiros et al. (2021) (https://doi.org/10.1016/j.jsames.2021.103425) and Sheng et al. (2019) (https://doi.org/10.1016/j.tecto.2019.04.005).

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. This data set represents the boundaries of the 2020 Census Blocks, extracted from the MTDB in 2020. The feature class was re-projected from the Census Bureau shapefile tl_2020_34_tabblock20.shp . The statewide re-allocated P1 block count table was then joined to the polygons on GEOID.Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. All 2020 Census blocks nest within every other 2020 Census geographic area. For additional references to explain the data, see Supplemental Information.

This layer contains a Vermont-only subset of block group level 2020 Decennial Census redistricting data as reported by the U.S. Census Bureau for all states plus DC and Puerto Rico. The attributes come from the 2020 Public Law 94-171 (P.L. 94-171) tables.Data download date: August 12, 2021Census tables: P1, P2, P3, P4, H1, P5, HeaderDownloaded from: Census FTP siteProcessing Notes:Data was downloaded from the U.S. Census Bureau FTP site, imported into SAS format and joined to the 2020 TIGER boundaries. Boundaries are sourced from the 2020 TIGER/Line Geodatabases. Boundaries have been projected into Web Mercator and each attribute has been given a clear descriptive alias name. No alterations have been made to the vertices of the data.Each attribute maintains it's specified name from Census, but also has a descriptive alias name and long description derived from the technical documentation provided by the Census. For a detailed list of the attributes contained in this layer, view the Data tab and select "Fields". The following alterations have been made to the tabular data:Joined all tables to create one wide attribute table:P1 - RaceP2 - Hispanic or Latino, and not Hispanic or Latino by RaceP3 - Race for the Population 18 Years and OverP4 - Hispanic or Latino, and not Hispanic or Latino by Race for the Population 18 Years and OverH1 - Occupancy Status (Housing)P5 - Group Quarters Population by Group Quarters Type (correctional institutions, juvenile facilities, nursing facilities/skilled nursing, college/university student housing, military quarters, etc.)HeaderAfter joining, dropped fields: FILEID, STUSAB, CHARITER, CIFSN, LOGRECNO, GEOVAR, GEOCOMP, LSADC, and BLOCK.GEOCOMP was renamed to GEOID and moved be the first column in the table, the original GEOID was dropped.Placeholder fields for future legislative districts have been dropped: CD118, CD119, CD120, CD121, SLDU22, SLDU24, SLDU26, SLDU28, SLDL22, SLDL24 SLDL26, SLDL28.P0020001 was dropped, as it is duplicative of P0010001. Similarly, P0040001 was dropped, as it is duplicative of P0030001.In addition to calculated fields, County_Name and State_Name were added.The following calculated fields have been added (see long field descriptions in the Data tab for formulas used): PCT_P0030001: Percent of Population 18 Years and OverPCT_P0020002: Percent Hispanic or LatinoPCT_P0020005: Percent White alone, not Hispanic or LatinoPCT_P0020006: Percent Black or African American alone, not Hispanic or LatinoPCT_P0020007: Percent American Indian and Alaska Native alone, not Hispanic or LatinoPCT_P0020008: Percent Asian alone, Not Hispanic or LatinoPCT_P0020009: Percent Native Hawaiian and Other Pacific Islander alone, not Hispanic or LatinoPCT_P0020010: Percent Some Other Race alone, not Hispanic or LatinoPCT_P0020011: Percent Population of Two or More Races, not Hispanic or LatinoPCT_H0010002: Percent of Housing Units that are OccupiedPCT_H0010003: Percent of Housing Units that are VacantPlease note these percentages might look strange at the individual block group level, since this data has been protected using differential privacy.*VCGI exported a Vermont-only subset of the nation-wide layer to produce this layer--with fields limited to this popular subset: OBJECTID: OBJECTID GEOID: Geographic Record Identifier NAME: Area Name-Legal/Statistical Area Description (LSAD) Term-Part Indicator County_Name: County Name State_Name: State Name P0010001: Total Population P0010003: Population of one race: White alone P0010004: Population of one race: Black or African American alone P0010005: Population of one race: American Indian and Alaska Native alone P0010006: Population of one race: Asian alone P0010007: Population of one race: Native Hawaiian and Other Pacific Islander alone P0010008: Population of one race: Some Other Race alone P0020002: Hispanic or Latino Population P0020003: Non-Hispanic or Latino Population P0030001: Total population 18 years and over H0010001: Total housing units H0010002: Total occupied housing units H0010003: Total vacant housing units P0050001: Total group quarters population PCT_P0030001: Percent of Population 18 Years and Over PCT_P0020002: Percent Hispanic or Latino PCT_P0020005: Percent White alone, not Hispanic or Latino PCT_P0020006: Percent Black or African American alone, not Hispanic or Latino PCT_P0020007: Percent American Indian and Alaska Native alone, not Hispanic or Latino PCT_P0020008: Percent Asian alone, not Hispanic or Latino PCT_P0020009: Percent Native Hawaiian and Other Pacific Islander alone, not Hispanic or Latino PCT_P0020010: Percent Some Other Race alone, not Hispanic or Latino PCT_P0020011: Percent Population of two or more races, not Hispanic or Latino PCT_H0010002: Percent of Housing Units that are Occupied PCT_H0010003: Percent of Housing Units that are Vacant SUMLEV: Summary Level REGION: Region DIVISION: Division COUNTY: County (FIPS) COUNTYNS: County (NS) TRACT: Census Tract BLKGRP: Block Group AREALAND: Area (Land) AREAWATR: Area (Water) INTPTLAT: Internal Point (Latitude) INTPTLON: Internal Point (Longitude) BASENAME: Area Base Name POP100: Total Population Count HU100: Total Housing Count *To protect the privacy and confidentiality of respondents, data has been protected using differential privacy techniques by the U.S. Census Bureau. This means that some individual block groups will have values that are inconsistent or improbable. However, when aggregated up, these issues become minimized.Download Census redistricting data in this layer as a file geodatabase.Additional links:U.S. Census BureauU.S. Census Bureau Decennial CensusAbout the 2020 Census2020 Census2020 Census data qualityDecennial Census P.L. 94-171 Redistricting Data Program

USA Census Block Groups (CBG) for Urban Search and Rescue. This layer can be used for search segment planning. Block groups generally contain between 600 and 5,000 people and the boundaries generally follow existing roads and waterways. The field segment_designation is the last 6 digits of the unique identifier and matches the field in the SARCOP Segment layer.Data download date: August 12, 2021Census tables: P1, P2, P3, P4, H1, P5, HeaderDownloaded from: Census FTP siteProcessing Notes:Data was downloaded from the U.S. Census Bureau FTP site, imported into SAS format and joined to the 2020 TIGER boundaries. Boundaries are sourced from the 2020 TIGER/Line Geodatabases. Boundaries have been projected into Web Mercator and each attribute has been given a clear descriptive alias name. No alterations have been made to the vertices of the data.Each attribute maintains it's specified name from Census, but also has a descriptive alias name and long description derived from the technical documentation provided by the Census. For a detailed list of the attributes contained in this layer, view the Data tab and select "Fields". The following alterations have been made to the tabular data:Joined all tables to create one wide attribute table:P1 - RaceP2 - Hispanic or Latino, and not Hispanic or Latino by RaceP3 - Race for the Population 18 Years and OverP4 - Hispanic or Latino, and not Hispanic or Latino by Race for the Population 18 Years and OverH1 - Occupancy Status (Housing)P5 - Group Quarters Population by Group Quarters Type (correctional institutions, juvenile facilities, nursing facilities/skilled nursing, college/university student housing, military quarters, etc.)HeaderAfter joining, dropped fields: FILEID, STUSAB, CHARITER, CIFSN, LOGRECNO, GEOVAR, GEOCOMP, LSADC, and BLOCK.GEOCOMP was renamed to GEOID and moved be the first column in the table, the original GEOID was dropped.Placeholder fields for future legislative districts have been dropped: CD118, CD119, CD120, CD121, SLDU22, SLDU24, SLDU26, SLDU28, SLDL22, SLDL24 SLDL26, SLDL28.P0020001 was dropped, as it is duplicative of P0010001. Similarly, P0040001 was dropped, as it is duplicative of P0030001.In addition to calculated fields, County_Name and State_Name were added.The following calculated fields have been added (see long field descriptions in the Data tab for formulas used): PCT_P0030001: Percent of Population 18 Years and OverPCT_P0020002: Percent Hispanic or LatinoPCT_P0020005: Percent White alone, not Hispanic or LatinoPCT_P0020006: Percent Black or African American alone, not Hispanic or LatinoPCT_P0020007: Percent American Indian and Alaska Native alone, not Hispanic or LatinoPCT_P0020008: Percent Asian alone, Not Hispanic or LatinoPCT_P0020009: Percent Native Hawaiian and Other Pacific Islander alone, not Hispanic or LatinoPCT_P0020010: Percent Some Other Race alone, not Hispanic or LatinoPCT_P0020011: Percent Population of Two or More Races, not Hispanic or LatinoPCT_H0010002: Percent of Housing Units that are OccupiedPCT_H0010003: Percent of Housing Units that are VacantPlease note these percentages might look strange at the individual block group level, since this data has been protected using differential privacy.* *To protect the privacy and confidentiality of respondents, data has been protected using differential privacy techniques by the U.S. Census Bureau. This means that some individual block groups will have values that are inconsistent or improbable. However, when aggregated up, these issues become minimized. The pop-up on this layer uses Arcade to display aggregated values for the surrounding area rather than values for the block group itself.Download Census redistricting data in this layer as a file geodatabase.Additional links:U.S. Census BureauU.S. Census Bureau Decennial CensusAbout the 2020 Census2020 Census2020 Census data qualityDecennial Census P.L. 94-171 Redistricting Data Program

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. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

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. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

This 2' geoid height grid for Mexico, and North-Central America, is the MEXICO97 geoid model. The computation used about one million terrestrial and marine gravity measurements held in the NGS database as of March 1997. These gravity measurements were augmented by data contributions from NGA (former National Imagery and Mapping Agency), and satellite altimeter-derived gravity anomalies computed by Sandwell and Smith (1997). Large data gaps south of 20 degrees North latitude were filled with 15'x15' gravity values derived from the EGM96 global geopotential model. This helped control interpolation errors across the data gaps during the gridding of terrain corrected Bouguer anomalies. After gridding of the Bouguer anomalies, the Bouguer plate was restored, a degree 360 model of gravity anomalies (from EGM96) was removed, and the residual free-air anomalies in the data gaps (south of 20 degrees North Latitude) were zeroed. (This zeroing was found to be the best way currently available to yield a reasonable geoid in the data gaps). The residual Faye anomalies were converted to residual co-geoid undulations through a 1-D FFT formulation of Stokes' integral, and finally the EGM96 undulation model was restored, and the indirect effect applied. This means that in the data gaps, long wavelength information is provided by EGM96, short wavelength information is provided by the 2'x2' DTED (during the application of the indirect effect), but medium wavelength information (usually provided by gravity measurements) is missing altogether. Although the exact accuracy of the geoid in the data gaps is difficult to ascertain, the quoted accuracy for EGM96 (which is the primary source of geoid information in the data gaps) is below 50 cm in these areas. The gravity values are based on the International Gravity Standardization Net 1971 (IGSN71). The geoid heights are referred to the Geodetic Reference System 1980 (GRS80) ellipsoid, centered at the origin of the International Terrestrial Reference Frame 1994 (ITRF94(1996.0)). Additional information is available at: http://www.ngs.noaa.gov/GEOID/MEXICO97/ We are particularly grateful to NGA (former National Imagery and Mapping Agency) for their assistance and their data contributions.

We present a regional geoid model for the area of Lake Vostok, Antarctica, from a combination of local airborne gravity, ice-surface and ice-thickness data and a lake bathymetry model. The topography data are used for residual terrain modelling (RTM) in a remove-compute-restore approach together with the GOCE satellite model GOCO03S. The disturbing potential at the Earth's surface, i.e. the quasigeoid, is predicted by least-squares collocation (LSC) and subsequently converted to geoid heights. Compared to GOCO03S our regional solution provides an additional short-wavelength signal of up to 1.48 m, or 0.56 m standard deviation, respectively. More details can be found in Schwabe et. al (2014).

LOJIC produced the MetroTract_2010 polygon feature class as a subset of 2010 Census Tiger/Line Files that is comprised of counties relevant to the Louisville- Jefferson County Metropolitan area and relevant surrounding Indiana and Kentucky counties. Attribution for this feature class consists of selected fields from the original shapefile, Geographic Header file and 2010 Redisticting population summary files, Part 1 and Part 2. Field naming conventions comply with those set forth by the U.S. Census. This is discussed to a greater degree below. The geographic coverage of MetroTract_2010 includes census tracts for Indiana and Kentucky counties that are tangent or within relevant proximity to Louisville-Jefferson County Metro Area. Indiana counties include Clark, Floyd and Harrison. Kentucky counties include Bullitt, Hardin, Henry, Jefferson, Meade, Oldham, Shelby, Spencer and Trimble. LOJIC census feature classes have been populated with a selected subset of relevant Census geographic and jurisdictional information derived from the Census Geographic Header file. A selected subset of population statistics from the Redistricting data summary files has also been incorporated. Please note that the included geographic header and population counts are not comprehensive. More specifically, not all fields from from the original shape, geographic header or summary files is contained in the feature class. Geographic Header, Part 1 and Part 2 tables that constitute the previously listed Indiana and Kentucky counties have been published in their entirety for any additional information that the end user may desire. This will require the end user to join the feature class to these tables. Feature classes can be joined to the Geographic Header table (PL_GEO_H_2010) with the [GEOID] field. To insure a 1:1 relationship and correct population data, the [GEOID] has been calculated only for relevant Census summary levels. Feature classes can be joined to the Part 1 (PL_PART1_2010) and Part 2 (PL_PART2_2010) tables with the [LOGRECSTID] field. This field insures a 1:1 relationship between the geography and its accurate population statistics. Part 1 includes categorizations of Populaton by Race (P001 fields) and Population by Hispanic or Latino Ethnicity and Race (P002 fields). Part 2 includes categorizations of Population by Race and Age 18 and Over (P003 fields), Population by Hispanic or Latino Ethnicity and Race and Ages 18 and Over (P004 fields), and finally, Occupancy Status (H001 fields). Currently, 2010 Census population counts are limited to what has been released by the U.S. Census Bureau, namely 2010 Redistricting Data. Full documentation for all Census Geographic Headerand Population fields can be referenced in the published tables, HEADER_DESCRIPT_2010 and POP_DESCRIPT_2010 respectively. These tables indicate field names and their respective descriptions. Please familiarize yourself with the Census abstract information that follows. The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.The attribute field "SQ_MILES" contains the area calculated to the thousandth (0.001) square mile. For entries showing 0, refer to the SHAPE_Area field for values in square feet.

Abstract

A crosswalk table from US postal ZIP codes to geo-points (latitude, longitude)

Documentation

Data source: public.opendatasoft.

The ZIP code database contained in 'zipcode.csv' contains 43204 ZIP codes for the continental United States, Alaska, Hawaii, Puerto Rico, and American Samoa. The database is in comma separated value format, with columns for ZIP code, city, state, latitude, longitude, timezone (offset from GMT), and daylight savings time flag (1 if DST is observed in this ZIP code and 0 if not).

This database was composed using ZIP code gazetteers from the US Census Bureau from 1999 and 2000, augmented with additional ZIP code information The database is believed to contain over 98% of the ZIP Codes in current use in the United States. The remaining ZIP Codes absent from this database are entirely PO Box or Firm ZIP codes added in the last five years, which are no longer published by the Census Bureau, but in any event serve a very small minority of the population (probably on the order of .1% or less). Although every attempt has been made to filter them out, this data set may contain up to .5% false positives, that is, ZIP codes that do not exist or are no longer in use but are included due to erroneous data sources. The latitude and longitude given for each ZIP code is typically (though not always) the geographic centroid of the ZIP code; in any event, the location given can generally be expected to lie somewhere within the ZIP code's "boundaries".The ZIP code database contained in 'zipcode.csv' contains 43204 ZIP codes for the continental United States, Alaska, Hawaii, Puerto Rico, and American Samoa. The database is in comma separated value format, with columns for ZIP code, city, state, latitude, longitude, timezone (offset from GMT), and daylight savings time flag (1 if DST is observed in this ZIP code and 0 if not). This database was composed using ZIP code gazetteers from the US Census Bureau from 1999 and 2000, augmented with additional ZIP code information The database is believed to contain over 98% of the ZIP Codes in current use in the United States. The remaining ZIP Codes absent from this database are entirely PO Box or Firm ZIP codes added in the last five years, which are no longer published by the Census Bureau, but in any event serve a very small minority of the population (probably on the order of .1% or less). Although every attempt has been made to filter them out, this data set may contain up to .5% false positives, that is, ZIP codes that do not exist or are no longer in use but are included due to erroneous data sources. The latitude and longitude given for each ZIP code is typically (though not always) the geographic centroid of the ZIP code; in any event, the location given can generally be expected to lie somewhere within the ZIP code's "boundaries".

The database and this README are copyright 2004 CivicSpace Labs, Inc., and are published under a Creative Commons Attribution-ShareAlike license, which requires that all updates must be released under the same license. See http://creativecommons.org/licenses/by-sa/2.0/ for more details. Please contact schuyler@geocoder.us if you are interested in receiving updates to this database as they become available.The database and this README are copyright 2004 CivicSpace Labs, Inc., and are published under a Creative Commons Attribution-ShareAlike license, which requires that all updates must be released under the same license. See http://creativecommons.org/licenses/by-sa/2.0/ for more details. Please contact schuyler@geocoder.us if you are interested in receiving updates to this database as they become available.

This API returns a search for the demographic information for a particular geography type and geography ID

The geoid model for Taiwan, including the Kinmen and Matzu islands, covers the area 118°E–125°E and 21°N–27°N with a grid resolution of 30" x 30". The gravimetric model is based on land, shipborne and airborne gravity data, as well as marine gravity derived from satellite altimetry. After merging data by least-squares collocation, a remove-restore procedure is applied. First height anomalies are computed by 1D FFT with Wong-Gore modification of the Stokes kernel and then they are converted into the geoid heights. The reference global gravity model is EGM2008 up to degree and order 2190. The used digital terrain model is derived from several photogrammetric surveys at a resolution of 3"×3" and 9"×9" for the inner and outer zone, respectively. The gravimetric model fits the GPS/levelling control points with a standard deviation of 7.9 cm (and a mean difference of 21.9 cm). The geoid model is provided in ISG format 2.0 (ISG Format Specifications), while the file in its original data format is available at the model ISG webpage.

Geoscape G-NAF is the geocoded address database for Australian businesses and governments. It’s the trusted source of geocoded address data for Australia with over 50 million contributed addresses distilled into 15.4 million G-NAF addresses. It is built and maintained by Geoscape Australia using independently examined and validated government data.

From 22 August 2022, Geoscape Australia is making G-NAF available in an additional simplified table format. G-NAF Core makes accessing geocoded addresses easier by utilising less technical effort.

G-NAF Core will be updated on a quarterly basis along with G-NAF.

Further information about contributors to G-NAF is available here.

With more than 15 million Australian physical address record, G-NAF is one of the most ubiquitous and powerful spatial datasets. The records include geocodes, which are latitude and longitude map coordinates. G-NAF does not contain personal information or details relating to individuals.

Updated versions of G-NAF are published on a quarterly basis. Previous versions are available here

Users have the option to download datasets with feature coordinates referencing either GDA94 or GDA2020 datums.

Changes in the May 2025 release

• Nationally, the May 2025 update of G-NAF shows an overall increase of 47,194 addresses (0.30%). The total number of addresses in G-NAF now stands at 15,753,927 of which 14,909,770 or 94.64% are principal.

• At some locations, there are unit-numbered addresses that appear to be duplicate addresses. Geoscape is working to identify these locations and include these addresses as separate addresses in G-NAF. To facilitate this process, some secondary addresses have had the word RETAIL added to their building names. In the first instance, this process is being progressively rolled out to identified locations, but it is expected that the requirement for this will become ongoing.

• There is one new locality in G-NAF: Keswick Island, QLD.

• The source data used for generating G-NAF STREET_LOCALITY_POINT data in New South Wales has an updated datum and changed from GDA94 to GDA2020. This has resulted in updates to the STREET_LOCALITY_POINT geometry for approximately 91,000 records, however, more than 95% of these have moved less than a metre.

• Geoscape has moved product descriptions, guides and reports online to https://docs.geoscape.com.au.

Further information on G-NAF, including FAQs on the data, is available here or through Geoscape Australia’s network of partners. They provide a range of commercial products based on G-NAF, including software solutions, consultancy and support.

Additional information: On 1 October 2020, PSMA Australia Limited began trading as Geoscape Australia.

License Information

Use of the G-NAF downloaded from data.gov.au is subject to the End User Licence Agreement (EULA)

The EULA terms are based on the Creative Commons Attribution 4.0 International license (CC BY 4.0). However, an important restriction relating to the use of the open G-NAF for the sending of mail has been added.

The open G-NAF data must not be used for the generation of an address or the compilation of an address for the sending of mail unless the user has verified that each address to be used for the sending of mail is capable of receiving mail by reference to a secondary source of information. Further information on this use restriction is available here.

End users must only use the data in ways that are consistent with the Australian Privacy Principles issued under the Privacy Act 1988 (Cth).

Users must also note the following attribution requirements:

Preferred attribution for the Licensed Material:

_G-NAF © Geoscape Australia licensed by the Commonwealth of Australia under the _Open Geo-coded National Address File (G-NAF) End User Licence Agreement.

Preferred attribution for Adapted Material:

Incorporates or developed using G-NAF © Geoscape Australia licensed by the Commonwealth of Australia under the Open Geo-coded National Address File (G-NAF) End User Licence Agreement.

What to Expect When You Download G-NAF

G-NAF is a complex and large dataset (approximately 5GB unpacked), consisting of multiple tables that will need to be joined prior to use. The dataset is primarily designed for application developers and large-scale spatial integration. Users are advised to read the technical documentation, including product change notices and the individual product descriptions before downloading and using the product. A quick reference guide on unpacking the G-NAF is also available.