The Agency for Toxic Substances and Disease Registry (ATSDR) Hazardous Waste Site Polygon Data with CIESIN Modifications, Version 2 is a database providing georeferenced data for 1,572 National Priorities List (NPL) Superfund sites. These were selected from the larger set of the ATSDR Hazardous Waste Site Polygon Data, Version 2 data set with polygons from May 26, 2010. The modified data set contains only sites that have been proposed, currently on, or deleted from the final NPL as of October 25, 2013. Of the 2,080 ATSDR polygons from 2010, 1,575 were NPL sites but three sites were excluded - 2 in the Virgin Islands and 1 in Guam. This data set is modified by the Columbia University Center for International Earth Science Information Network (CIESIN). The modified polygon database includes all the attributes for these NPL sites provided in the ATSDR GRASP Hazardous Waste Site Polygon database and selected attributes from the EPA List 9 Active CERCLIS sites and SCAP 12 NPL sites databases. These polygons represent sites considered for cleanup under the Comprehensive Environmental Response, Compensation and Liability Act (CERCLA or Superfund). The Geospatial Research, Analysis, and Services Program (GRASP, Division of Health Studies, Agency for Toxic Substances and Disease Registry, Centers for Disease Control and Prevention) has created site boundary data using the best available information for those sites where health assessments or consultations have been requested.

Overview

Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.

Our self-hosted GIS data cover administrative and postal divisions with up to 6 precision levels: a zip code layer and up to 5 administrative levels. All levels follow a seamless hierarchical structure with no gaps or overlaps.

The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.

Use cases for the Global Boundaries Database (GIS data, Geospatial data)

• In-depth spatial analysis

• Clustering

• Geofencing

• Reverse Geocoding

• Reporting and Business Intelligence (BI)

Product Features

• Coherence and precision at every level

• Edge-matched polygons

• High-precision shapes for spatial analysis

• Fast-loading polygons for reporting and BI

• Multi-language support

For additional insights, you can combine the GIS data with:

• Population data: Historical and future trends

• UNLOCODE and IATA codes

• Time zones and Daylight Saving Time (DST)

Data export methodology

Our geospatial data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson

All GIS data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Why companies choose our map data

• Precision at every level

• Coverage of difficult geographies

• No gaps, nor overlaps

Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

Overview

Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.

Our self-hosted geospatial data cover postal divisions for the whole world. The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.

Use cases for the Global Boundaries Database (Geospatial data, Map data, Polygon daa)

• In-depth spatial analysis

• Clustering

• Geofencing

• Reverse Geocoding

• Reporting and Business Intelligence (BI)

Product Features

• Coherence and precision at every level

• Edge-matched polygons

• High-precision shapes for spatial analysis

• Fast-loading polygons for reporting and BI

• Multi-language support

For additional insights, you can combine the map data with:

• Population data: Historical and future trends

• UNLOCODE and IATA codes

• Time zones and Daylight Saving Time (DST)

Data export methodology

Our location data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson

All geospatial data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Why companies choose our map data

• Precision at every level

• Coverage of difficult geographies

• No gaps, nor overlaps

Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

Overview

Empower your location data visualizations with our edge-matched polygons, even in difficult geographies.

Our self-hosted geospatial data cover administrative and postal divisions with up to 5 precision levels. All levels follow a seamless hierarchical structure with no gaps or overlaps.

The geospatial data shapes are offered in high-precision and visualization resolution and are easily customized on-premise.

Use cases for the Global Administrative Boundaries Database (Geospatial data, Map data)

• In-depth spatial analysis

• Clustering

• Geofencing

• Reverse Geocoding

• Reporting and Business Intelligence (BI)

Product Features

• Coherence and precision at every level

• Edge-matched polygons

• High-precision shapes for spatial analysis

• Fast-loading polygons for reporting and BI

• Multi-language support

For additional insights, you can combine the map data with:

• Population data: Historical and future trends

• UNLOCODE and IATA codes

• Time zones and Daylight Saving Time (DST)

Data export methodology

Our location data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson

All geospatial data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Why companies choose our map data

• Precision at every level

• Coverage of difficult geographies

• No gaps, nor overlaps

Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

The Agency for Toxic Substances and Disease Registry (ATSDR) Hazardous Waste Site Polygon Data, Version 2 consists of 2,080 polygons for selected hazardous waste sites that were compiled on May 26, 2010. Most polygons represent sites considered for cleanup under the Comprehensive Environmental Response, Compensation and Liability Act (CERCLA or Superfund). Typical sites are either on the EPA National Priorities List (NPL) or are being considered for inclusion on the NPL. The hazardous waste site boundaries maintained by the Geospatial Research, Analysis, and Services Program (GRASP, Division of Health Studies, Agency for Toxic Substances and Disease Registry, Centers for Disease Control and Prevention) contain NPL and non-NPL hazardous waste site boundaries for which health assessments or consultations have been requested.

Jurisdictional Unit, 2022-05-21. For use with WFDSS, IFTDSS, IRWIN, and InFORM.This is a feature service which provides Identify and Copy Feature capabilities. If fast-drawing at coarse zoom levels is a requirement, consider using the tile (map) service layer located at https://nifc.maps.arcgis.com/home/item.html?id=3b2c5daad00742cd9f9b676c09d03d13.OverviewThe Jurisdictional Agencies dataset is developed as a national land management geospatial layer, focused on representing wildland fire jurisdictional responsibility, for interagency wildland fire applications, including WFDSS (Wildland Fire Decision Support System), IFTDSS (Interagency Fuels Treatment Decision Support System), IRWIN (Interagency Reporting of Wildland Fire Information), and InFORM (Interagency Fire Occurrence Reporting Modules). It is intended to provide federal wildland fire jurisdictional boundaries on a national scale. The agency and unit names are an indication of the primary manager name and unit name, respectively, recognizing that:There may be multiple owner names.Jurisdiction may be held jointly by agencies at different levels of government (ie State and Local), especially on private lands, Some owner names may be blocked for security reasons.Some jurisdictions may not allow the distribution of owner names. Private ownerships are shown in this layer with JurisdictionalUnitIdentifier=null,JurisdictionalUnitAgency=null, JurisdictionalUnitKind=null, and LandownerKind="Private", LandownerCategory="Private". All land inside the US country boundary is covered by a polygon.Jurisdiction for privately owned land varies widely depending on state, county, or local laws and ordinances, fire workload, and other factors, and is not available in a national dataset in most cases.For publicly held lands the agency name is the surface managing agency, such as Bureau of Land Management, United States Forest Service, etc. The unit name refers to the descriptive name of the polygon (i.e. Northern California District, Boise National Forest, etc.).These data are used to automatically populate fields on the WFDSS Incident Information page.This data layer implements the NWCG Jurisdictional Unit Polygon Geospatial Data Layer Standard.Relevant NWCG Definitions and StandardsUnit2. A generic term that represents an organizational entity that only has meaning when it is contextualized by a descriptor, e.g. jurisdictional.Definition Extension: When referring to an organizational entity, a unit refers to the smallest area or lowest level. Higher levels of an organization (region, agency, department, etc) can be derived from a unit based on organization hierarchy.Unit, JurisdictionalThe governmental entity having overall land and resource management responsibility for a specific geographical area as provided by law.Definition Extension: 1) Ultimately responsible for the fire report to account for statistical fire occurrence; 2) Responsible for setting fire management objectives; 3) Jurisdiction cannot be re-assigned by agreement; 4) The nature and extent of the incident determines jurisdiction (for example, Wildfire vs. All Hazard); 5) Responsible for signing a Delegation of Authority to the Incident Commander.See also: Unit, Protecting; LandownerUnit IdentifierThis data standard specifies the standard format and rules for Unit Identifier, a code used within the wildland fire community to uniquely identify a particular government organizational unit.Landowner Kind & CategoryThis data standard provides a two-tier classification (kind and category) of landownership. Attribute Fields JurisdictionalAgencyKind Describes the type of unit Jurisdiction using the NWCG Landowner Kind data standard. There are two valid values: Federal, and Other. A value may not be populated for all polygons.JurisdictionalAgencyCategoryDescribes the type of unit Jurisdiction using the NWCG Landowner Category data standard. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State. A value may not be populated for all polygons.JurisdictionalUnitNameThe name of the Jurisdictional Unit. Where an NWCG Unit ID exists for a polygon, this is the name used in the Name field from the NWCG Unit ID database. Where no NWCG Unit ID exists, this is the “Unit Name” or other specific, descriptive unit name field from the source dataset. A value is populated for all polygons.JurisdictionalUnitIDWhere it could be determined, this is the NWCG Standard Unit Identifier (Unit ID). Where it is unknown, the value is ‘Null’. Null Unit IDs can occur because a unit may not have a Unit ID, or because one could not be reliably determined from the source data. Not every land ownership has an NWCG Unit ID. Unit ID assignment rules are available from the Unit ID standard, linked above.LandownerKindThe landowner category value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. There are three valid values: Federal, Private, or Other.LandownerCategoryThe landowner kind value associated with the polygon. May be inferred from jurisdictional agency, or by lack of a jurisdictional agency. A value is populated for all polygons. Valid values include: ANCSA, BIA, BLM, BOR, DOD, DOE, NPS, USFS, USFWS, Foreign, Tribal, City, County, OtherLoc (other local, not in the standard), State, Private.DataSourceThe database from which the polygon originated. Be as specific as possible, identify the geodatabase name and feature class in which the polygon originated.SecondaryDataSourceIf the Data Source is an aggregation from other sources, use this field to specify the source that supplied data to the aggregation. For example, if Data Source is "PAD-US 2.1", then for a USDA Forest Service polygon, the Secondary Data Source would be "USDA FS Automated Lands Program (ALP)". For a BLM polygon in the same dataset, Secondary Source would be "Surface Management Agency (SMA)."SourceUniqueIDIdentifier (GUID or ObjectID) in the data source. Used to trace the polygon back to its authoritative source.MapMethod:Controlled vocabulary to define how the geospatial feature was derived. Map method may help define data quality. MapMethod will be Mixed Method by default for this layer as the data are from mixed sources. Valid Values include: GPS-Driven; GPS-Flight; GPS-Walked; GPS-Walked/Driven; GPS-Unknown Travel Method; Hand Sketch; Digitized-Image; DigitizedTopo; Digitized-Other; Image Interpretation; Infrared Image; Modeled; Mixed Methods; Remote Sensing Derived; Survey/GCDB/Cadastral; Vector; Phone/Tablet; OtherDateCurrentThe last edit, update, of this GIS record. Date should follow the assigned NWCG Date Time data standard, using 24 hour clock, YYYY-MM-DDhh.mm.ssZ, ISO8601 Standard.CommentsAdditional information describing the feature. GeometryIDPrimary key for linking geospatial objects with other database systems. Required for every feature. This field may be renamed for each standard to fit the feature.JurisdictionalUnitID_sansUSNWCG Unit ID with the "US" characters removed from the beginning. Provided for backwards compatibility.JoinMethodAdditional information on how the polygon was matched information in the NWCG Unit ID database.LocalNameLocalName for the polygon provided from PADUS or other source.LegendJurisdictionalAgencyJurisdictional Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.LegendLandownerAgencyLandowner Agency but smaller landholding agencies, or agencies of indeterminate status are grouped for more intuitive use in a map legend or summary table.DataSourceYearYear that the source data for the polygon were acquired.Data InputThis dataset is based on an aggregation of 4 spatial data sources: Protected Areas Database US (PAD-US 2.1), data from Bureau of Indian Affairs regional offices, the BLM Alaska Fire Service/State of Alaska, and Census Block-Group Geometry. NWCG Unit ID and Agency Kind/Category data are tabular and sourced from UnitIDActive.txt, in the WFMI Unit ID application (https://wfmi.nifc.gov/unit_id/Publish.html). Areas of with unknown Landowner Kind/Category and Jurisdictional Agency Kind/Category are assigned LandownerKind and LandownerCategory values of "Private" by use of the non-water polygons from the Census Block-Group geometry.PAD-US 2.1:This dataset is based in large part on the USGS Protected Areas Database of the United States - PAD-US 2.`. PAD-US is a compilation of authoritative protected areas data between agencies and organizations that ultimately results in a comprehensive and accurate inventory of protected areas for the United States to meet a variety of needs (e.g. conservation, recreation, public health, transportation, energy siting, ecological, or watershed assessments and planning). Extensive documentation on PAD-US processes and data sources is available.How these data were aggregated:Boundaries, and their descriptors, available in spatial databases (i.e. shapefiles or geodatabase feature classes) from land management agencies are the desired and primary data sources in PAD-US. If these authoritative sources are unavailable, or the agency recommends another source, data may be incorporated by other aggregators such as non-governmental organizations. Data sources are tracked for each record in the PAD-US geodatabase (see below).BIA and Tribal Data:BIA and Tribal land management data are not available in PAD-US. As such, data were aggregated from BIA regional offices. These data date from 2012 and were substantially updated in 2022. Indian Trust Land affiliated with Tribes, Reservations, or BIA Agencies: These data are not considered the system of record and are not intended to be used as such. The Bureau of Indian Affairs (BIA), Branch of Wildland Fire Management (BWFM) is not the originator of these data. The

Integrated terrain models covering 16,357 square kilometers of the Massachusetts coastal zone and offshore waters were built to provide a continuous elevation and bathymetry terrain model for ocean planning purposes. The area is divided into the following four geographical areas to reduce file size and facilitate publishing: Massachusetts Bay from the Massachusetts-New Hampshire border south to Provincetown and Scituate and east to Stellwagen Bank; Cape Cod Bay from Provincetown to Scituate and south to Hyannis; Buzzards Bay from the Cape Cod Canal southwest to the State border including the Elizabeth Islands and extending north to Fall River and Mount Hope Bay; and Nantucket and Vineyard Sounds, from Hyannis south to the border of the Massachusetts Coastal zone approximately 8 kilometers south of Nantucket. A Triangulated Irregular Network was created from public-domain bathymetric and LiDAR data using the ArcGIS terrain-model framework and then interpolated into a 32-bit GeoTiff of 10 meter resolution. The grids for each of the four geographical areas are referenced to the Universal Transverse Mercator, Zone 19, North American Datum of 1983 coordinate system, and the North American Vertical Datum of 1988. A polygon shapefile recording the source datasets accompanies each of the four grids.

In June 2022, Thailand legalized recreational cannabis. Currently, cannabis is now the most consumed drug. Cannabis usage can increase inflammatory responses in the respiratory tract. Sharing of cannabis waterpipes has been linked to increased tuberculosis risks. Using a national in-patient databank, we aimed to 1) describe the spatiotemporal correlation between cannabis-related and tuberculosis hospital admissions, and 2) compare the rate of subsequent pulmonary tuberculosis admission between those with prior admissions for cannabis-related causes and those without. Both admission types were aggregated to the number of admissions in monthly and provincial units. Temporal and spatial patterns were visualized using line plots and choropleth maps, respectively. A matched cohort analysis was conducted to compare the incidence density rate of subsequent tuberculosis admission and the hazard ratio. Throughout 2017–2022, we observed a gradual decline in tuberculosis admissions, in contrast to the increase in cannabis-related admissions. Both admissions shared a hotspot in Northeastern Thailand. Between matched cohorts of 6,773 in-patients, the incidence density rate per 100,000 person–years of subsequent tuberculosis admissions was 267.6 and 165.9 in in-patients with and without past cannabis-admission, respectively. After adjusting for covariates, we found that a cannabis-related admission history was associated with a hazard ratio of 1.48 (P = 0.268) for subsequent tuberculosis admission. Our findings failed to support the evidence that cannabis consumption increased pulmonary tuberculosis risk. Other study types are needed to further assess the association between cannabis consumption and pulmonary tuberculosis.

The World Database on Protected Areas (WDPA) is the most comprehensive global database of marine and terrestrial protected areas and is one of the key global biodiversity datasets being widely used by scientists, businesses, governments, International secretariats and others to inform planning, policy decisions and management.The WDPA is a joint project between the United Nations Environment Programme (UNEP) and the International Union for Conservation of Nature (IUCN). The compilation and management of the WDPA is carried out by UNEP World Conservation Monitoring Centre (UNEP-WCMC), in collaboration with governments, non-governmental organisations, academia and industry. There are monthly updates of the data which are made available online through the Protected Planet website where the data is both viewable and downloadable.Data and information on the world's protected areas compiled in the WDPA are used for reporting to the Convention on Biological Diversity on progress towards reaching the Aichi Biodiversity Targets (particularly Target 11), to the UN to track progress towards the 2030 Sustainable Development Goals, to some of the Intergovernmental Science-Policy Platform on Biodiversity and Ecosystem Services (IPBES) core indicators, and other international assessments and reports including the Global Biodiversity Outlook, as well as for the publication of the United Nations List of Protected Areas. Every two years, UNEP-WCMC releases the Protected Planet Report on the status of the world's protected areas and recommendations on how to meet international goals and targets.Many platforms are incorporating the WDPA to provide integrated information to diverse users, including businesses and governments, in a range of sectors including mining, oil and gas, and finance. For example, the WDPA is included in the Integrated Biodiversity Assessment Tool, an innovative decision support tool that gives users easy access to up-to-date information that allows them to identify biodiversity risks and opportunities within a project boundary.The reach of the WDPA is further enhanced in services developed by other parties, such as theGlobal Forest Watch and the Digital Observatory for Protected Areas, which provide decision makers with access to monitoring and alert systems that allow whole landscapes to be managed better. Together, these applications of the WDPA demonstrate the growing value and significance of the Protected Planet initiative.For more details on the WDPA please read through the WDPA User Manual.

Extensive polygon dataset for marinas across the US and Canada. Includes custom-drawn boundaries and precise location information. Valuable for marine industry analysis, recreational planning, and coastal development projects.

This geodatabase of point, line and polygon features is an effort to consolidate all of the range improvement locations on BLM-managed land in Idaho into one database. Currently, the polygon feature class has some data for all of the BLM field offices except the Coeur d'Alene and Cottonwood field offices. Range improvements are structures intended to enhance rangeland resources, including wildlife, watershed, and livestock management. Examples of range improvements include water troughs, spring headboxes, culverts, fences, water pipelines, gates, wildlife guzzlers, artificial nest structures, reservoirs, developed springs, corrals, exclosures, etc. These structures were first tracked by the Bureau of Land Management (BLM) in the Job Documentation Report (JDR) System in the early 1960s, which was predominately a paper-based tracking system. In 1988 the JDRs were migrated into and replaced by the automated Range Improvement Project System (RIPS), and version 2.0 is currently being used today. It tracks inventory, status, objectives, treatment, maintenance cycle, maintenance inspection, monetary contributions and reporting. Not all range improvements are documented in the RIPS database; there may be some older range improvements that were built before the JDR tracking system was established. There also may be unauthorized projects that are not in RIPS. Official project files of paper maps, reports, NEPA documents, checklists, etc., document the status of each project and are physically kept in the office with management authority for that project area. In addition, project data is entered into the RIPS system to enable managers to access the data to track progress, run reports, analyze the data, etc. Before Geographic Information System technology most offices kept paper atlases or overlay systems that mapped the locations of the range improvements. The objective of this geodatabase is to migrate the location of historic range improvement projects into a GIS for geospatial use with other data and to centralize the range improvement data for the state. This data set is a work in progress and does not have all range improvement projects that are on BLM lands. Some field offices have not migrated their data into this database, and others are partially completed. New projects may have been built but have not been entered into the system. Historic or unauthorized projects may not have case files and are being mapped and documented as they are found. Many field offices are trying to verify the locations and status of range improvements with GPS, and locations may change or projects that have been abandoned or removed on the ground may be deleted. Attributes may be incomplete or inaccurate. This data was created using the standard for range improvements set forth in Idaho IM 2009-044, dated 6/30/2009. However, it does not have all of the fields the standard requires. Fields that are missing from the polygon feature class that are in the standard are: ALLOT_NO, POLY_TYPE, MGMT_AGCY, ADMIN_ST, and ADMIN_OFF. The polygon feature class also does not have a coincident line feature class, so some of the fields from the polygon arc feature class are included in the polygon feature class: COORD_SRC, COORD_SRC2, DEF_FET, DEF_FEAT2, ACCURACY, CREATE_DT, CREATE_BY, MODIFY_DT, MODIFY_BY, GPS_DATE, and DATAFILE. There is no National BLM standard for GIS range improvement data at this time.

The Global Urban Polygons and Points Dataset (GUPPD), Version 1 is a global data set of 123,034 urban settlements with place names and population for the years 1975-2030 in five-year increments. The data set builds on and expands the European Commission, Joint Research Centre's (JRC) 2015 Global Human Settlement (GHS) Urban Centre Database (UCDB). The JRC Settlement Model (GHS-SMOD) data set includes a hierarchy of urban settlements, from urban centre (level 30), to dense urban cluster (level 23), to semi-dense urban cluster (level 22). The UCDB only includes level 30, whereas the GUPPDv1 adds levels 23 and 22, and uses open data sources to both check and validate the names that JRC assigned to its UCDB polygons and to label the newly added settlements. The methodology described in the documentation was able to consistently label a greater percentage of UCDB polygons than were previously labeled by JRC.

Comprehensive global POI data and polygon datasets featuring 6M+ worldwide locations across 11 industries. Includes international location data with detailed geospatial coverage and custom geofence insights. Ideal for global market analysis and international expansion across multiple countries.

Overview

Empower your location data visualizations with our edge-matched polygons, even in difficult geographies (China, India, and Brazil).

Our self-hosted geospatial data displays clean shapes with no gaps or overlaps over your base map of choice.

The geospatial data shapes are offered in high-precision resolution and are easily customized on-premise.

Use cases for the Global Postal Boundaries Database (Geospatial data, Map data)

• In-depth spatial analysis

• Clustering

• Geofencing

• Reverse Geocoding

Product Features

• Coherence and precision at every level

• Edge-matched polygons

• High-precision shapes for spatial analysis

• Multi-language support

For additional insights, you can combine the map data with:

• Population data: Historical and future trends

• UNLOCODE and IATA codes

• Time zones and Daylight Saving Time (DST)

Data export methodology

Our location data packages are offered in variable formats, including - .shp - .gpkg - .kml - .shp - .gpkg - .kml - .geojson

All geospatial data are optimized for seamless integration with popular systems like Esri ArcGIS, Snowflake, QGIS, and more.

Why companies choose our map data

• Precision at every level

• Coverage of difficult geographies

• No gaps, nor overlaps

Note: Custom geospatial data packages are available. Please submit a request via the above contact button for more details.

Data available online through the Arkansas Spatial Data Infrastructure (http://gis.arkansas.gov). The subject file represents Civil Divisions 2000 for the State of Arkansas. It is a registered trademark of the Bureau of the Census and an extract of selected geographic and cartographic information from the Census TIGER database. The geographic coverage for a single TIGER/Line file is a county or statistical equivalent entity, based on January 1, 2000 legal boundaries. A complete set of files includes all counties and statistically equivalent entities in the United States and Puerto Rico. Files for the Island Areas are not included. The Census TIGER database represents a seamless national file with no overlaps or gaps between parts. However, each county-based TIGER/Line file is designed to stand alone as an independent data set or the files can be combined to cover the whole Nation. The files consist of line segments representing physical features and governmental and statistical boundaries. They do NOT contain the ZIP Code Tabulation Areas (ZCTAs) and the address ranges are of approximately the same vintage as those appearing in the 1999 TIGER/Line files. That is, the Census Bureau is producing these files in advance of the computer processing that will ensure that the address ranges in the TIGER/Line files agree with the final Master Address File (MAF) used for tabulating Census 2000. The files contain information distributed over a series of record types for the spatial objects of a county. There are 17 record types, including the basic data record, the shape coordinate points, and geographic codes that can be used with appropriate software to prepare maps. Other geographic information contained in the files includes attributes such as feature identifiers/census feature class codes (CFCC) used to differentiate feature types, address ranges and ZIP Codes codes for legal and statistical entities, latitude/longitude coordinates of linear and point features, landmark point features, area landmarks, key geographic features, and area boundaries.

This specialized location dataset delivers detailed information about marina establishments. Maritime industry professionals, coastal planners, and tourism researchers can leverage precise location insights to understand maritime infrastructure, analyze recreational boating landscapes, and develop targeted strategies.

How Do We Create Polygons?

-All our polygons are manually crafted using advanced GIS tools like QGIS, ArcGIS, and similar applications. This involves leveraging aerial imagery, satellite data, and street-level views to ensure precision. -Beyond visual data, our expert GIS data engineers integrate venue layout/elevation plans sourced from official company websites to construct highly detailed polygons. This meticulous process ensures maximum accuracy and consistency. -We verify our polygons through multiple quality assurance checks, focusing on accuracy, relevance, and completeness.

What's More?

-Custom Polygon Creation: Our team can build polygons for any location or category based on your requirements. Whether it’s a new retail chain, transportation hub, or niche point of interest, we’ve got you covered. -Enhanced Customization: In addition to polygons, we capture critical details such as entry and exit points, parking areas, and adjacent pathways, adding greater context to your geospatial data. -Flexible Data Delivery Formats: We provide datasets in industry-standard GIS formats like WKT, GeoJSON, Shapefile, and GDB, making them compatible with various systems and tools. -Regular Data Updates: Stay ahead with our customizable refresh schedules, ensuring your polygon data is always up-to-date for evolving business needs.

Unlock the Power of POI and Geospatial Data

With our robust polygon datasets and point-of-interest data, you can: -Perform detailed market and location analyses to identify growth opportunities. -Pinpoint the ideal locations for your next store or business expansion. -Decode consumer behavior patterns using geospatial insights. -Execute location-based marketing campaigns for better ROI. -Gain an edge over competitors by leveraging geofencing and spatial intelligence.

Why Choose LocationsXYZ?

LocationsXYZ is trusted by leading brands to unlock actionable business insights with our accurate and comprehensive spatial data solutions. Join our growing network of successful clients who have scaled their operations with precise polygon and POI datasets. Request your free sample today and explore how we can help accelerate your business growth.

Water body features within the City of Boston.

Polygon for cities in the state of Texas

BodyParts3D organ model data with the polygon reduction rate of 99%. The zip-compressed download files contain multiple files of ELEMENT file ID-specific polygon data in Wavefront OBJ format.

This cadastral polygon dataset is a digital representation of all land parcel boundaries within Western Australia. It represents all crown land (land owned by the State) and freehold land (land held in fee simple) and is sourced from the Spatial Cadastral Database (SCDB) which is the official digital cadastral map base of all crown and freehold land parcels within the State of Western Australia. The dataset covers the State of Western Australia and the Commonwealth jurisdictions of Cocos Keeling Island and Christmas Island. NOTE: This product is for information purposes only and is not guaranteed. The information may be out of date and should not be relied upon without further verification from the original documents. Where the information is being used for legal purposes then the original documents must be searched for all legal requirements. © Western Australian Land Information Authority (Landgate). Use of Landgate data is subject to Personal Use License terms and conditions unless otherwise authorised under approved License terms and conditions. For further information please contact your Landgate Customer Experience Consultant or email customerexperience@landgate.wa.gov.au.