Through our database of over 230 million POI records and global coverage, we help businesses optimize their marketing efforts, due diligence, and company analysis with precise location-based targeting.

Business can customize their strategies according to specific industries and customer segments using our Location Data, which encompasses several categories, such as retail, hospitality, transportation, healthcare, and many others.

Here are 3 key features for our Location POI product:

➣ Coverage: We developed an AI and ML technology that helped us to get complete worldwide coverage.

➣ Recency: Our ML technology automatically prioritized different sources of data, based on their recency to gather data. By using this technology, we can receive updates up to once a week, per specific geography.

➣ Accuracy: Xverum aims to provide the most accurate and comprehensive data on each POI. We rank the diverse data sources to select the most suitable for each attribute such as Location, Contact Details, Opening hours, and much more.

Make strategic business decisions based on location-specific data, optimizing operations, mitigating risks, and maximizing opportunities. Unlock the power of location data with Xverum. Contact us today to learn how we can empower your business with location data to achieve goals.

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public open space and voluntarily provided, private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastral Theme (http://www.fgdc.gov/ngda-reports/NGDA_Datasets.html). PAD-US is an ongoing project with several published versions of a spatial database of areas dedicated to the preservation of biological diversity, and other natural, recreational or cultural uses, managed for these purposes through legal or other effective means. The geodatabase maps and describes public open space and other protected areas. Most areas are public lands owned in fee; however, long-term easements, leases, and agreements or administrative designations documented in agency management plans may be included. The PAD-US database strives to be a complete “best available” inventory of protected areas (lands and waters) including data provided by managing agencies and organizations. The dataset is built in collaboration with several partners and data providers (http://gapanalysis.usgs.gov/padus/stewards/). See Supplemental Information Section of this metadata record for more information on partnerships and links to major partner organizations. As this dataset is a compilation of many data sets; data completeness, accuracy, and scale may vary. Federal and state data are generally complete, while local government and private protected area coverage is about 50% complete, and depends on data management capacity in the state. For completeness estimates by state: http://www.protectedlands.net/partners. As the federal and state data are reasonably complete; focus is shifting to completing the inventory of local gov and voluntarily provided, private protected areas. The PAD-US geodatabase contains over twenty-five attributes and four feature classes to support data management, queries, web mapping services and analyses: Marine Protected Areas (MPA), Fee, Easements and Combined. The data contained in the MPA Feature class are provided directly by the National Oceanic and Atmospheric Administration (NOAA) Marine Protected Areas Center (MPA, http://marineprotectedareas.noaa.gov ) tracking the National Marine Protected Areas System. The Easements feature class contains data provided directly from the National Conservation Easement Database (NCED, http://conservationeasement.us ) The MPA and Easement feature classes contain some attributes unique to the sole source databases tracking them (e.g. Easement Holder Name from NCED, Protection Level from NOAA MPA Inventory). The "Combined" feature class integrates all fee, easement and MPA features as the best available national inventory of protected areas in the standard PAD-US framework. In addition to geographic boundaries, PAD-US describes the protection mechanism category (e.g. fee, easement, designation, other), owner and managing agency, designation type, unit name, area, public access and state name in a suite of standardized fields. An informative set of references (i.e. Aggregator Source, GIS Source, GIS Source Date) and "local" or source data fields provide a transparent link between standardized PAD-US fields and information from authoritative data sources. The areas in PAD-US are also assigned conservation measures that assess management intent to permanently protect biological diversity: the nationally relevant "GAP Status Code" and global "IUCN Category" standard. A wealth of attributes facilitates a wide variety of data analyses and creates a context for data to be used at local, regional, state, national and international scales. More information about specific updates and changes to this PAD-US version can be found in the Data Quality Information section of this metadata record as well as on the PAD-US website, http://gapanalysis.usgs.gov/padus/data/history/.) Due to the completeness and complexity of these data, it is highly recommended to review the Supplemental Information Section of the metadata record as well as the Data Use Constraints, to better understand data partnerships as well as see tips and ideas of appropriate uses of the data and how to parse out the data that you are looking for. For more information regarding the PAD-US dataset please visit, http://gapanalysis.usgs.gov/padus/. To find more data resources as well as view example analysis performed using PAD-US data visit, http://gapanalysis.usgs.gov/padus/resources/. The PAD-US dataset and data standard are compiled and maintained by the USGS Gap Analysis Program, http://gapanalysis.usgs.gov/ . For more information about data standards and how the data are aggregated please review the “Standards and Methods Manual for PAD-US,” http://gapanalysis.usgs.gov/padus/data/standards/ .

The Soil Data Management Toolbox consists of five toolsets organized within a single toolbox. Each toolset contains several ArcTools that can be used to acquire, assemble and manage individual SSURGO datasets and to create gSSURGO databases. It is recommended that the tools be run in foreground mode (not background) because a lot of useful status information is printed to the geoprocessing window. SSURGO datasets for an entire state or region can require a large amount of storage space and computer resources to process. These tools are designed to make the process of acquiring, managing and using SSURGO datasets for large land areas much easier and faster. Each tool contains detailed built-in help which can be displayed on the right side of the tool dialog box. Much of this information in the help is not available in this document, so it would be a good idea to read the help for each parameter before using the tool. If the Help window is not visible, click on the ‘Show Help>>’ button. Other Documents to Reference:gSSURGO FactsheetgSSURGO User Guide ArcMap version 2.4Soil Data Development Toolbox User Guide v5 for ArcMapgSSURGO Mapping Detailed GuidegSSURGO Valu1 table column descriptions

ssurgoOnDemandThe purpose of these tools are to give users the ability to get Soil Survey Geographic Database (SSURGO) properties and interpretations in an efficient manner. They are very similiar to the United States Department of Agriculture - Natural Resource Conservation Service's distributed Soil Data Viewer (SDV), although there are distinct differences. The most important difference is the data collected with the SSURGO On-Demand (SOD) tools are collected in real-time via web requests to Soil Data Access (https://sdmdataaccess.nrcs.usda.gov/). SOD tools do not require users to have the data found in a traditional SSURGO download from the NRCS's official repository, Web Soil Survey (https://websoilsurvey.sc.egov.usda.gov/App/HomePage.htm). The main intent of both SOD and SDV are to hide the complex relationships of the SSURGO tables and allow the users to focus on asking the question they need to get the information they want. This is accomplished in the user interface of the tools and the subsequent SQL is built and executed for the user. Currently, the tools packaged here are designed to run within the ESRI ArcGIS Desktop Application - ArcMap, version 10.1 or greater. However, much of the Python code is recyclable and could run within a Python intepreter or other GIS applications such as Quantum GIS with some modification.NOTE: The queries in these tools only consider the major components of soil map units.Within the SOD tools are 2 primary toolsets, descibed as follows:<1. AreasymbolThe Areasymbol tools collect SSURGO properties and interpretations based on a user supplied list of Soil Survey areasymbols (e.g. NC123). After the areasymbols have been collected, an aggregation method (see below) is selected . Tee aggregation method has no affect on interpretations other than how the SSURGO data aggregated. For soil properties, the aggregation method drives what properties can be run. For example, you can't run the weighted average aggregation method on Taxonomic Order. Similarly, for the same soil property, you wouldn't specify a depth range. The point here is the aggregation method affects what parameters need to be supplied for the SQL generation. It is important to note the user can specify any number of areasymbols and any number of interpretations. This is another distinct advantage of these tools. You could collect all of the SSURGO interpretations for every soil survey area (areasymbol) by executing the tool 1 time. This also demonstrates the flexibility SOD has in defining the geographic extent over which information is collected. The only constraint is the extent of soil survey areas selected to run (and these can be discontinuous).As SOD Areasymbol tools execute, 2 lists are collected from the tool dialog, a list of interpretations/properties and a list of areasymbols. As each interpretation/property is run, every areasymbol is run against the interpretation/property requested. For instance, suppose you wanted to collect the weighted average of sand, silt and clay for 5 soil survey areas. The sand property would run for all 5 soil survey areas and built into a table. Next the silt would run for all 5 soil survey areas and built into a table, and so on. In this example a total of 15 web request would have been sent and 3 tables are built. Two VERY IMPORTANT things here...A. All the areasymbol tools do is generate tables. They are not collecting spatial data.B. They are collecting stored information. They are not making calculations(with the exception of the weighted average aggregation method).<2. ExpressThe Express toolset is nearly identical to the Areasymbol toolset, with 2 exceptions.A. The area to collect SSURGO information over is defined by the user. The user digitizes coordinates into a 'feature set' after the tool is open. The points in the feature set are closed (first point is also the last) into a polygon. The polygon is sent to Soil Data Access and the features set points (polygon) are used to clip SSURGO spatial data. The geomotries of the clip operation are returned, along with the mapunit keys (unique identifier). It is best to keep the points in the feature set simple and beware of self intersections as they are fatal.B. Instead of running on a list of areasymbols, the SQL queries on a list of mapunit keys.The properties and interpretations options are identical to what was discussed for the Areasymbol toolset.The Express tools present the user the option of creating layer files (.lyr) where the the resultant interpretation/property are joined to the geometry and saved to disk as a virtual join. Additionally, for soil properties, an option exists to append all of the selected soil properties to a single table. In this case, if the user ran sand, silt, and clay properties, instead of 3 output tables, there is only 1 table with a sand column, a silt column, and a clay column.<Supplemental Information<sAggregation MethodAggregation is the process by which a set of component attribute values is reduced to a single value to represent the map unit as a whole.A map unit is typically composed of one or more "components". A component is either some type of soil or some nonsoil entity, e.g., rock outcrop. The components in the map unit name represent the major soils within a map unit delineation. Minor components make up the balance of the map unit. Great differences in soil properties can occur between map unit components and within short distances. Minor components may be very different from the major components. Such differences could significantly affect use and management of the map unit. Minor components may or may not be documented in the database. The results of aggregation do not reflect the presence or absence of limitations of the components which are not listed in the database. An on-site investigation is required to identify the location of individual map unit components. For queries of soil properties, only major components are considered for Dominant Component (numeric) and Weighted Average aggregation methods (see below). Additionally, the aggregation method selected drives the available properties to be queried. For queries of soil interpretations, all components are condisered.For each of a map unit's components, a corresponding percent composition is recorded. A percent composition of 60 indicates that the corresponding component typically makes up approximately 60% of the map unit. Percent composition is a critical factor in some, but not all, aggregation methods.For the attribute being aggregated, the first step of the aggregation process is to derive one attribute value for each of a map unit's components. From this set of component attributes, the next step of the aggregation process derives a single value that represents the map unit as a whole. Once a single value for each map unit is derived, a thematic map for soil map units can be generated. Aggregation must be done because, on any soil map, map units are delineated but components are not.The aggregation method "Dominant Component" returns the attribute value associated with the component with the highest percent composition in the map unit. If more than one component shares the highest percent composition, the value of the first named component is returned.The aggregation method "Dominant Condition" first groups like attribute values for the components in a map unit. For each group, percent composition is set to the sum of the percent composition of all components participating in that group. These groups now represent "conditions" rather than components. The attribute value associated with the group with the highest cumulative percent composition is returned. If more than one group shares the highest cumulative percent composition, the value of the group having the first named component of the mapunit is returned.The aggregation method "Weighted Average" computes a weighted average value for all components in the map unit. Percent composition is the weighting factor. The result returned by this aggregation method represents a weighted average value of the corresponding attribute throughout the map unit.The aggregation method "Minimum or Maximum" returns either the lowest or highest attribute value among all components of the map unit, depending on the corresponding "tie-break" rule. In this case, the "tie-break" rule indicates whether the lowest or highest value among all components should be returned. For this aggregation method, percent composition ties cannot occur. The result may correspond to a map unit component of very minor extent. This aggregation method is appropriate for either numeric attributes or attributes with a ranked or logically ordered domain.

The National Cooperative Soil Survey - Soil Characterization Database (NCSS-SCD) contains laboratory data for more than 65,000 locations (i.e. XY coordinates) throughout the United States and its Territories, and about 2,100 locations from other countries. It is a compilation of data from the Kellogg Soil Survey Laboratory (KSSL) and several cooperating laboratories. The data steward and distributor is the National Soil Survey Center (NSSC). Information contained within the database includes physical, chemical, biological, mineralogical, morphological, and mid infrared reflectance (MIR) soil measurements, as well a collection of calculated values. The intended use of the data is to support interpretations related to soil use and management.Data Usage Access to the data is provided via the following user interfaces:1. Interactive Web Map2. Lab Data Mart (LDM) interface for querying data and generating reports3. Soil Data Access (SDA) web services for querying data4. Direct download of the entire database in several formats.Data at each location includes measurements at multiple depths (e.g. soil horizons). However, not all analyses have been conducted for each location and depth. Typically, a suite of measurements was collected based upon assumed or known conditions regarding the soil being analyzed. For example, soils of arid environments are routinely analyzed for salts and carbonates as part of the standard analysis suite. Standard morphological soil descriptions are available for about 60,000 of these locations. Mid-infrared (MIR) spectroscopy is available for about 7,000 locations. Soil fertility measurements, such as those made by Agricultural Experiment Stations, were not made. Most of the data were obtained over the last 40 years, with about 4,000 locations before 1960, 25,000 from 1960-1990, 27,000 from 1990-2010, and 13,000 from 2010 to 2021. Generally, the number of measurements recorded per location has increased over time. Typically, the data were collected to represent a soil series or map unit component concept. They may also have been sampled to determine the range of variation within a given landscape.Individual Metadata [XML]

Web Soil Survey & Geospatial Data Gateway These requirements include:Provide a way to request data for an adhoc area of interest of any size.Provide a way to obtain data in real-time.Provide a way to request selected tabular and spatial attributes.Provide a way to return tabular and spatial data where the organization of that data doesn't hate to mirror that of the underlying source database.Provide a way to bundle results by request, rather tan by survey area.Click on Submit a custom request for soil tabular data, to input a query to extract data. For help click on:Creating my own custom database queries Index to SQL Library - Sample Scripts Using Soil Data Access website Using Soil Data Access web services

Land resource areas are used in the United States, Caribbean, and Pacific Basin. The “Major Land Resource Areas (MLRA) Geographic Database” serves as the geospatial expression of the map products presented and described in AH 296 (2022). Land resource categories historically used at State and National levels are land resource units, major land resource areas, and land resource regions (National Soil Survey Handbook, Part 649; Land Resource Hierarchy). Although AH 296 does not describe land resource units (LRUs) directly, they are the basic units from which major land resource areas are determined. They are also the basic units for State land resource maps. LRUs are commonly, but not necessarily, coextensive with State general soil map units. LRUs generally are several thousand acres in size. A unit can be one continuous area or several separate areas that are near each other. In 2005, these areas were designated as common resource areas (CRAs) within the NRCS. Like LRUs, CRAs are not described in AH 296 and are not shown on the National map but are mentioned for historical purposes. MLRAs are geographically associated LRUs at a broader scale and higher hierarchical level than LRUs. Land resource regions (LRR) are a group of geographically associated MLRAs at the highest hierarchical level shown at the continental scale. Identification of these large areas is important in statewide agricultural planning and has value in interstate, regional, and national planning. In AH 296, MLRAs are generally designated by numbers and identified by a descriptive geographic name. Examples are MLRA 1 (Northern Pacific Coast Range, Foothills, and Valleys), MLRA 154 (South-Central Florida Ridge), and MLRA 230 (Yukon-Kuskokwim Highlands). Some MLRAs are designated by a letter in addition to a number because a previously established MLRA has been divided into smaller, more homogeneous areas—for example, MLRAs 102A, 102B, and 102C. Other MLRAs, especially smaller ones approaching the LRU scale, have been recombined. The use of numbers and letters to identify newly created MLRAs requires fewer changes in existing information in records and in databases. A few MLRAs consist of two or more parts separated for short distances by other land resource areas. In some places, one of the parts is widely separated from the main body of the MLRA and is in an adjoining LRR. The description of the respective MLRA also applies to these outlying parts. The spatial illustration of the MLRAs has been smoothed for the contiguous United States and Alaska to better reflect the scale at which the MLRA resource attributes (climate, soils, land use, vegetation, geology, and physiography) were aggregated for delineation.Individual Metadata [XML]