Simple municipal name/GEOID lookup table.The table combines GEOID with census county names and municipal names. Stored as view in the demographics schema.

This data layer is an element of the Oregon GIS Framework. 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.

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 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 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, no land area.

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

U.S. Census BlocksThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), displays Census Blocks in the United States. A brief description of Census Blocks, per USCB, is that "Census blocks are statistical areas bounded by visible features such as roads, streams, and railroad tracks, and by nonvisible boundaries such as property lines, city, township, school district, county limits and short line-of-sight extensions of roads." Also, "the smallest level of geography you can get basic demographic data for, such as total population by age, sex, and race."Census Block 1007Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Census Blocks) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 69 (Series Information for 2020 Census Block State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (U.S. Census Blocks - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: What are census blocksFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

Census Tracts from the 2020 US Census for New York City clipped to the shoreline. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. Because some census tracts are under water not all census tracts are contained in this file, only census tracts that are partially or totally located on land have been mapped in this file.

All previously released versions of this data are available on the DCP Website: BYTES of the BIG APPLE. Current version: 25d

US Northeast Census Tracts contains the US Census tract geometries used as the unit of analysis for network metrics. The file "northeast_tracts.shp" includes a merged dataset with the borders of all census tracts in Connecticut, Maine, Massachusetts, New Hampshire, New York, Rhode Island, and Vermont. All other files in this repository are the original state-by-state sources used to create the final merged dataset. Census Tracts The 2020 census tract file is based on the 2020 Census. The following fields are included: USPS: United States Postal Service state abbreviation. GEOID: Geographic identifier — fully concatenated geographic code (State FIPS, County FIPS, Census Tract number). GEOIDFQ: Fully qualified geographic identifier — used to join with data.census.gov data tables. ALAND: Land area (square meters) — created for statistical purposes only. AWATER: Water area (square meters) — created for statistical purposes only. ALAND_SQMI: Land area (square miles) — created for statistical purposes only. AWATER_SQMI: Water area (square miles) — created for statistical purposes only. INTPTLAT: Latitude (decimal degrees). The first character is blank or “–” denoting North or South latitude respectively. INTPTLONG: Longitude (decimal degrees). The first character is blank or “–” denoting East or West longitude respectively. The .shp file in this repository includes its required companion files for correct GIS operation: .shx (spatial index), .dbf (attribute table), .prj (projection information), and .cpg (character encoding).

This complements our article “Sea-level fingerprints emergent from GRACE mission data” submitted to Earth System Science Data (https://doi.org/10.5194/essd-2019-3). Based on CSR, GFZ, and JPL Stokes coefficients, we derive spherical harmonic coefficients and spatial maps for relative sea level, geoid height change, and vertical bedrock motion. We provide monthly solutions with and without Earth’s rotational feedback included, both in the center-of-mass (CM) and center-of-figure (CF) reference frames.

This dataset contains annual mean geostrophic velocity calculated at depth corresponding to negative values of the marine geoid. It is calculated from two open sources from the geodetic (EIGEN-6C4) and oceanographic (NCEI) communities. The first source EIGEN-6C4 is a static global combined gravity field model developed by GFZ Potsdam and GRGS Toulouse up to degree and order 2190. The second source is the “World ocean geostrophic velocity inverted from World Ocean Atlas 2013 with the P-vector method†(NCEI accession 0121576). With the given non-positive values of the geoid, N, (i.e., for the oceans), the absolute geostrophic currents (u, v) are easily identified on N with 1 degree resolution from the second dataset except the equatorial zone (5oS – 5oN) due to the non-existence of the geostrophic balance. Altogether, the dataset contains 15,481 (u, v) data pairs. While there is no geostrophic motion at the surface if it coincided with the geoid, the opposite is not valid. This dataset shows that ocean geostrophic velocity doesn't zero at z=N. Data are in netcdf format.

In the ILRS network, there are mobile systems and permanent systems. Mobile ILRS systems usually occupy (i.e. are referenced to) a ground monument/mark and have an associated set of non-zero eccentricities. System eccentricities are defined as the offsets (usually less than 15 meters) from the ground monument/mark to the optical reference point of the system (i.e. intersection of axes) and are measured in North, East, and Up or in Cartesian coordinates, X, Y, and Z. Mobile systems are assigned a CDP number for the monument that it is occupying. In turn, the IERS assigns a DOMES number for the monument containing a 'M'. The 'M' indicates the presence of a physical Monument. A given monument may be occupied by more than one system or may be occupied by the same system multiple times, but never during the same time period. Therefore, for a given monument and time period, there will be a unique set of eccentricities.

Permanent systems were designed to stay in one place and usually do not occupy a ground monument/mark. In this case, the CDP number is assigned to the optical axes of intersection. In turn, the IERS assigns a DOMES number containing a 'S'. The 'S' indicates the reference to the System's optical axes. In this case, the system eccentricities are by definition ZERO. In the rare occasion that a permanent system or its intersection of axes is relocated, then a new CDP and IERS DOMES number will be assigned for each relocation.

This dataset is about: Free air anomalies, Bouguer anomalies and geoid undulations of the Eltanin impact area.

This file contains a list of geodetic bench marks, identified by a Permanent Identifier (PID), each of which have a precise orthometric height determined by geodetic leveling, a precise ellipsoid height determined by GPS surveying, and a precise modeled hybrid geoid height. The observations were used to constrain a gravimetric geoid model to the surface of a current vertical datum to produce a hybrid geoid model and associated performance metrics. The data is primarily from the US, however some data from Canada and Mexico is included as well.

Expanded set of SLR station positions and velocities in the ITRF2020 frame, includes historical sites NOT part of ITRF2020 and some very recently installed sites that came online in 2022. A small number of sites require special treatment with the addition of corrections to their "mean" positions (in this file) from the ITRS-distributed PSD model, due to "events" (e.g. earthquakes) or changes at the site. Users must apply these corrections cumulatively, to the linearly propagated positions from this file, by themselves. For more details, s/w and relevant correction files please visit the official ITRS site on ITRF2020 at: https://itrf.ign.fr/en/solutions/ITRF2020

The daily solution files are an analysis product that provides estimates of Earth orientation and site positions for each 24-hour session, the covariance matrix of the estimates, and decomposed normal equations. The solution files are in SINEX format. The SINEX product files are available on the same frequency as the EOP-S products: 24 hours after each new session data base is available.

Corrections to SLR tracking data collected from various tables on CDDIS, resolutions from the ILRS/ASC (AWG) meetings, the T2L2 @ Jason-2 project (July 2008 to December 2017), the final results of the ILRS Station Systematic Error Monitoring--SSEM project, amended with results from its 2023 extension as an ongoing project, SSEM-X.

“The ILRS contribution to ITRF2020 consists of a pair of time series of weekly and bi-weekly station position estimates along with daily and 3-day averaged Earth Orientation Parameters (X-pole, Y-pole and excess Length-Of-Day (LOD)) estimated over 7-day arcs (1993.0 – 2021.0) and 15-day arcs for the period 1983.0-1993.0, aligned to the calendar weeks (Sunday to Saturday), starting from January 1983. Each solution is obtained through the combination of loosely constrained weekly/biweekly solutions submitted by each of the seven official ILRS Analysis Centers. Both, the individual and combined solutions have followed strict standards agreed upon within the ILRS Analysis Standing Committee (ASC) to provide ITRS products of the highest possible quality.” (The ILRS contribution to ITRF2020, E. C. Pavlis (GESTAR II/UMBC & NASA Goddard 61A) and V. Luceri (e-GEOS S.p.A., ASI/CGS))

The VIIRS/JPSS1 Moderate Resolution Terrain Corrected Geolocation 6-Min L1 Swath 750m Near Real Time (NRT) product, short-name VJ103MOD_NRT includes the geolocation fields that are calculated for each VIIRS moderate resolution band (M-band) Line of sight (LOS) for all orbits at the nominal resolution of 750 m. The locations and ancillary information correspond to the intersection of the centers of each Field of View (FOV) from 16 detectors in an ideal M-band on the Earth's surface. A digital terrain model is used to model the Earth's surface. The main inputs are the spacecraft attitude and orbit ephemeris data, the instrument telemetry and the digital elevation model. The geolocation fields contained within the VNP03MOD Geolocation files include geodetic latitude, longitude, surface height above the geoid, solar zenith and azimuth angles, satellite zenith and azimuth angles, and a land/water mask for each 750m sample. Additional information is included in the header to enable the calculation of the approximate location of the center of the detectors for any of the VIIRS bands. This product is used as input by subsequent VIIRS Moderate Resolution products, particularly those produced by the Land team.

The NRSC's Regional Geoid Product offers the most accurate satellite derived measurement of the marine geoid, providing an inexpensive base dataset for rapid geophysical screening of off-shore sedimentary basins. The product consists of corrected mean sea surface heights referenced to an Earth Ellipsoid. Vertical accuracy's of better than 10cm are achieved through the application of NRSC's waveform-retracking process.

 Accurate measurement of the marine geoid is important for exploration
 companies who use the information to derive gravitational fields over
 offshore basins. These are used to map potential oil-bearing structures
 beneath the ocean floor.

 The geoid is generated from Altimeter data acquired by the European Space
 Agency's ERS-1 satellite, from both the 35-day repeat cycle phase or the
 168-day repeat cycle (geodetic phase). The unique retracked dataset
 produced by the NRSC enables the derivation of precise high frequency
 geoid information for the first time.

 Features of the 35-day repeat cycle product include:

 > Five repeat orbits are used to reduce errors
 > Vertical accuracy is better than 10cm
 > Along track resolution is 7km
 > Across track resolution at 60 degrees latitude is 39km. This is
  four times more dense than available from previous altimeter-derived
  datasets such as the Haxby global geoid
 > Data for the Arctic basin is available for the first time

 Features of the 168-day repeat cycle product include:

 > Along track resolution is 2km (resolutions up to 0.5km are available,
  however the location accuracy of the altimeter sensor is limited to 2km)
 > Across track resolution at 60 degrees latitude is 4km
 > Vertical accuracy is around 10cm

 The Regional Geoid Product consists of geoid undulation heights referenced
 to a long wavelength geoid model. These are available as a series of
 points along the original satellite tracks or as a regular gridded
 dataset. Products are available 'off-the-shelf' for major sedimentary
 basins including: North East Europe, the Falklands shelf, South East Asia
 and the Barents and Kara Seas. Products for any other area between 80N and
 80S can be generated on demand.

 The data is supplied in digital form on Exabyte, CD-ROM or CCT. Further
 details and pricing are available from the National Remote Sensing Centre
 (NRSC).