The Database & Directory Publishing industry in Oklahoma is expected to decline an annualized -x.x% to $x.x million over the five years to 2025, while the national industry will likely decline at -x.x% during the same period. Industry establishments decreased an annualized -x.x% to x locations. Industry employment has decreased an annualized -x.x% to xx workers, while industry wages have decreased an annualized -x.x% to $x.x million.

The Database, Storage & Backup Software Publishing industry in Oklahoma is expected to grow an annualized x.x% to $x.x million over the five years to 2025, while the national industry will likely grow at x.x% during the same period. Industry establishments increased an annualized x.x% to xx locations. Industry employment has decreased an annualized -x.x% to xxx workers, while industry wages have decreased an annualized -x% to $x.x million.

The gravity station data (710 records) were compiled by Professor Ahern. This data base was received in June 1992. Principal gravity parameters include latitude, longitude, elevation, and observed gravity. The data are randomly distributed within northern Oklahoma.

Building permit data for Oklahoma including Oklahoma City, Tulsa, Norman, and more (where available).

The Pacific Rainfall Database (PACRAIN) dataset contains daily and monthly precipitation from stations in the tropical Pacific Ocean. The most up to date versions of this data can be downloaded directly from the PACRAIN web site

PACRAIN was significantly improved in 2008. Please see the home web site

The payroll data represents the amount paid to an employee during the reported time period. In addition to regular pay, these amounts may include other pay types such as overtime, longevity, shift differential or terminal pay. This amount does not include any state share costs associated with the payroll i.e. FICA, state share retirement, etc. This amount may vary from an employee’s ‘salary’ due to pay adjustments or pay period timing. The payroll information will be updated monthly after the end of the month. For example, July information will be added in August after the 15th of the month.

The database contains uniformly processed ground motion intensity measurements (peak horizontal ground motions and 5-percent-damped pseudospectral accelerations for oscillator periods 0.1–10 s). The earthquake event set includes more than 3,800 M≥3 earthquakes in Oklahoma and Kansas from January 2009 to December 2016. Ground motion time series were collected out to 500 km. We also relocated the majority of the earthquake hypocenters using a multiple-event relocation algorithm to produce a set of near-uniformly processed hypocentral locations. Details about data processing are reported in the accompanying article. First posted - October 11, 2017 Revised - December 18, 2017, ver. 1.1

From Oklahoma Geological Survey:A preliminary fault map has been compiled from oil and gas industry data and published literature and published as an Open-File Report (OF3-2015). Most of the faults from the published literature are documented in the supplement to this Open-File Report. This map is compiled from the Oklahoma fault database, which continues to be updated as additional fault information is available. This map should be considered preliminary. The faults shown here represent one interpretation of all the faults in the Oklahoma fault database being compiled by the OGS. This preliminary version identifies surface and subsurface faults on one map.

.OK.US Whois Database, discover comprehensive ownership details, registration dates, and more for .OK.US TLD with Whois Data Center.

The Crude Oil Analysis (COA) database contains the digital data compilation of 9,076 crude oil analyses from samples collected from 1920 through 1983 from the United States and around the world and analyzed by the United States Bureau of Mines (National Institute for Petroleum and Energy Research, 1995). Two laboratories (Bartlesville, Oklahoma, and Laramie, Wyoming) performed routine crude oil analyses by a standardized method, and the data were originally reported in more than 50 reports by the Bureau of Mines. Analyses include specific gravity, API gravity, pour point, viscosity, sulfur content, nitrogen content, and color of the crude oil, as well as the bulk properties of the distillation cuts. The data were digitized in the late 1970s and a database retrieval system was implemented in 1980 and made available to the public. The Department of Energy (DOE) updated this system in 1995-96 with public access through a dial-up bulletin board system. The database was operated by the National Institute for Petroleum and Energy Research (NIPER) in Bartlesville, Oklahoma. A stand-alone version of the database (COADB) was available in 1995 in the form of a series of tables in Foxpro (.dbf) format. In 1998, an updated version of COADB was available on the NIPER website that included a Microsoft Access 97 version of the database called "coadb.mdb". The file contains more tables than the original 1995 version but we believe the number of oil samples and the amount of raw data are the same. The additional tables contain text translations for codes used in other tables regarding color, county, laboratory, formation, geologic age, lithology, and state name. Sample location information is generally inadequate to identify the specific well in most cases. The sample location information lacks lease name and in many cases well number and section-township-range. In rare cases, the latitude and longitude are given. A 2002 version was provided by the National Energy Technology Laboratory.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA).The file is georeferenced to earth's surface using the State Plane projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

This resource is a member of a series. 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) System (MTS). The MTS 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 All Roads shapefile includes all features within the MTS Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in the MTS that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

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 Address Ranges Feature Shapefile (ADDRFEAT.dbf) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. The ADDRFEAT shapefile contains a record for each address range to street name combination. Address range associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that the ADDRFEAT shapefile includes all unsuppressed address ranges compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefile contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA).The file is georeferenced to earth's surface using the State Plane projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

Comprehensive database of 4.2M+ U.S. motor carriers with safety ratings, insurance renewal dates, VIN-decoded fleet equipment details, and DOT compliance data. Updated multiple times daily from FMCSA and insurance filings.

The payroll data represents the amount paid to an employee during the reported time period. In addition to regular pay, these amounts may include other pay types such as overtime, longevity, shift differential or terminal pay. This amount does not include any state share costs associated with the payroll i.e. FICA, state share retirement, etc. This amount may vary from an employee’s ‘salary’ due to pay adjustments or pay period timing. The payroll information will be updated monthly after the end of the month. For example, July information will be added in August after the 15th of the month.

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. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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 TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2022, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census, but some CDPs were added or updated through the 2022 BAS as well.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau' 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. School Districts are single-purpose administrative units within which local officials provide public educational services for the area's residents. The Census Bureau obtains the boundaries, names, local education agency codes, grade ranges, and school district levels for school districts from State officials for the primary purpose of providing the U.S. Department of Education with estimates of the number of children in poverty within each school district. This information serves as the basis for the Department of Education to determine the annual allocation of Title I funding to States and school districts. TIGER/Line Shapefiles include separate shapefiles for elementary, secondary and unified school districts. The school district boundaries are those in effect for the 2018-2019 school year, i.e., in operation as of January 1, 2019.