Last update: October 16, 2025 OverviewThis point data was generated and filtered from OpenStreetMap and is intended to represent places of interest in the state of Utah. These may include businesses, restaurants, places of worship, airports, parks, schools, event centers, apartment complexes, hotels, car dealerships…almost anything that you can find in OpenStreetMap (OSM). There are over 23,000 features in the original dataset (March 2022) and users can directly contribute to it through openstreetmap.org. This data is updated approximately once every month and will likely continue to grow over time with user activity. Data SourcesThe original bulk set of OSM data for the state of Utah is downloaded from Geofabrik: https://download.geofabrik.de/north-america/us/utah-latest-free.shp.zipAdditional attributes for the Utah features are gathered via the Overpass API using the following query: https://overpass-turbo.eu/s/1geRData Creation ProcessThe Open Source Places layer is created by a Python script that pulls statewide OSM data from a nightly archive provided by Geofabrik (https://www.geofabrik.de/data/download.html). The archive data contains nearly 20 shapefiles, some that are relevant to this dataset and some that aren't. The Open Source Places layer is built by filtering the polygon and point data in those shapefiles down to a single point feature class with specific categories and attributes that UGRC determines would be of widest interest. The polygon features (buildings, areas, complexes, etc.) are converted to points using an internal centroid. Spatial filtering is done as the data from multiple shapefiles is combined into a single layer to minimize the occurrence of duplicate features. (For example, a restaurant can be represented in OSM as both a point of interest and as a building polygon. The spatial filtering helps reduce the chances that both of these features are present in the final dataset.) Additional de-duplication is performed by using the 'block_id' field as a spatial index, to ensure that no two features of the same name exist within a census block. Then, additional fields are created and assigned from UGRC's SGID data (county, city, zip, nearby address, etc.) via point-in-polygon and near analyses. A numeric check is done on the 'name' field to remove features where the name is less than 3 characters long or more than 50% numeric characters. This eliminates several features derived from the buildings layer where the 'name' is simply an apartment complex building number (ex: 3A) or house number (ex: 1612). Finally, additional attributes (osm_addr, opening_hours, phone, website, cuisine, etc.) are pulled from the Overpass API (https://wiki.openstreetmap.org/wiki/Overpass_API) and joined to the filtered data using the 'osm_id' field as the join key. Field Descriptionsaddr_dist - the distance (m) to the nearest UGRC address point within 25 mosm_id - the feature ID in the OSM databasecategory - the feature's data class based on the 4-digit code and tags in the OSM databasename - the name of the feature in the OSM databasecounty - the county the feature is located in (assigned from UGRC's county boundaries)city - the city the feature is located in (assigned from UGRC's municipal boundaries)zip - the zip code of the feature (assigned from UGRC's approximation of zip code boundaries)block_id - the census block the feature is located in (assigned from UGRC's census block boundaries)ugrc_addr - the nearest address (within 25 m) from the UGRC address point databasedisclaimer - a note from UGRC about the ugrc_near_addr fieldlon - the approximate longitude of the feature, calculated in WGS84 EPSG:4326lat - the approximate latitude of the feature, calculated in WGS84 EPSG:4326amenity - the amenity available at the feature (if applicable), often similar to the categorycuisine - the type of food available (if applicable), multiple types are separated by semicolons (;)tourism - the type of tourist location, if applicable (zoo, viewpoint, hotel, attraction, etc.)shop - the type of shop, if applicablewebsite - the feature's website in the OSM database, if availablephone - the feature's phone number(s) in the OSM database, if availableopen_hours - the feature's operating hours in the OSM database, if availableosm_addr - the feature's address in the OSM database, if availableMore information can be found on the UGRC data page for this layer:https://gis.utah.gov/data/society/open-source-places/

Overview The Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.4 (published 24 February 2025). The 11.4 release contains updated boundary lines and data refinements designed to extend the functionality of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control. National Geospatial Data Asset This dataset is a National Geospatial Data Asset (NGDAID 194) managed by the Department of State. It is a part of the International Boundaries Theme created by the Federal Geographic Data Committee. Dataset Source Details Sources for these data include treaties, relevant maps, and data from boundary commissions, as well as national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process includes analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground. Cartographic Visualization The LSIB is a geospatial dataset that, when used for cartographic purposes, requires additional styling. The LSIB download package contains example style files for commonly used software applications. The attribute table also contains embedded information to guide the cartographic representation. Additional discussion of these considerations can be found in the Use of Core Attributes in Cartographic Visualization section below. Additional cartographic information pertaining to the depiction and description of international boundaries or areas of special sovereignty can be found in Guidance Bulletins published by the Office of the Geographer and Global Issues: https://data.geodata.state.gov/guidance/index.html Contact Direct inquiries to internationalboundaries@state.gov. Direct download: https://data.geodata.state.gov/LSIB.zip Attribute Structure The dataset uses the following attributes divided into two categories: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | Core CC1_GENC3 | Extension CC1_WPID | Extension COUNTRY1 | Core CC2 | Core CC2_GENC3 | Extension CC2_WPID | Extension COUNTRY2 | Core RANK | Core LABEL | Core STATUS | Core NOTES | Core LSIB_ID | Extension ANTECIDS | Extension PREVIDS | Extension PARENTID | Extension PARENTSEG | Extension These attributes have external data sources that update separately from the LSIB: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | GENC CC1_GENC3 | GENC CC1_WPID | World Polygons COUNTRY1 | DoS Lists CC2 | GENC CC2_GENC3 | GENC CC2_WPID | World Polygons COUNTRY2 | DoS Lists LSIB_ID | BASE ANTECIDS | BASE PREVIDS | BASE PARENTID | BASE PARENTSEG | BASE The core attributes listed above describe the boundary lines contained within the LSIB dataset. Removal of core attributes from the dataset will change the meaning of the lines. An attribute status of “Extension” represents a field containing data interoperability information. Other attributes not listed above include “FID”, “Shape_length” and “Shape.” These are components of the shapefile format and do not form an intrinsic part of the LSIB. Core Attributes The eight core attributes listed above contain unique information which, when combined with the line geometry, comprise the LSIB dataset. These Core Attributes are further divided into Country Code and Name Fields and Descriptive Fields. County Code and Country Name Fields “CC1” and “CC2” fields are machine readable fields that contain political entity codes. These are two-character codes derived from the Geopolitical Entities, Names, and Codes Standard (GENC), Edition 3 Update 18. “CC1_GENC3” and “CC2_GENC3” fields contain the corresponding three-character GENC codes and are extension attributes discussed below. The codes “Q2” or “QX2” denote a line in the LSIB representing a boundary associated with areas not contained within the GENC standard. The “COUNTRY1” and “COUNTRY2” fields contain the names of corresponding political entities. These fields contain names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the ‘"Independent States in the World" and "Dependencies and Areas of Special Sovereignty" lists maintained by the Department of State. To ensure maximum compatibility, names are presented without diacritics and certain names are rendered using common cartographic abbreviations. Names for lines associated with the code "Q2" are descriptive and not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS denote independent states. Names rendered in normal text represent dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user. Descriptive Fields The following text fields are a part of the core attributes of the LSIB dataset and do not update from external sources. They provide additional information about each of the lines and are as follows: ATTRIBUTE NAME | CONTAINS NULLS RANK | No STATUS | No LABEL | Yes NOTES | Yes Neither the "RANK" nor "STATUS" fields contain null values; the "LABEL" and "NOTES" fields do. The "RANK" field is a numeric expression of the "STATUS" field. Combined with the line geometry, these fields encode the views of the United States Government on the political status of the boundary line. ATTRIBUTE NAME | | VALUE | RANK | 1 | 2 | 3 STATUS | International Boundary | Other Line of International Separation | Special Line A value of “1” in the “RANK” field corresponds to an "International Boundary" value in the “STATUS” field. Values of ”2” and “3” correspond to “Other Line of International Separation” and “Special Line,” respectively. The “LABEL” field contains required text to describe the line segment on all finished cartographic products, including but not limited to print and interactive maps. The “NOTES” field contains an explanation of special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, limitations regarding the purpose of the lines, or the original source of the line. Use of Core Attributes in Cartographic Visualization Several of the Core Attributes provide information required for the proper cartographic representation of the LSIB dataset. The cartographic usage of the LSIB requires a visual differentiation between the three categories of boundary lines. Specifically, this differentiation must be between: International Boundaries (Rank 1); Other Lines of International Separation (Rank 2); and Special Lines (Rank 3). Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary. Please consult the style files in the download package for examples of this depiction. The requirement to incorporate the contents of the "LABEL" field on cartographic products is scale dependent. If a label is legible at the scale of a given static product, a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field contains the preferred description for the three LSIB line types when they are incorporated into a map legend but is otherwise not to be used for labeling. Use of the “CC1,” “CC1_GENC3,” “CC2,” “CC2_GENC3,” “RANK,” or “NOTES” fields for cartographic labeling purposes is prohibited. Extension Attributes Certain elements of the attributes within the LSIB dataset extend data functionality to make the data more interoperable or to provide clearer linkages to other datasets. The fields “CC1_GENC3” and “CC2_GENC” contain the corresponding three-character GENC code to the “CC1” and “CC2” attributes. The code “QX2” is the three-character counterpart of the code “Q2,” which denotes a line in the LSIB representing a boundary associated with a geographic area not contained within the GENC standard. To allow for linkage between individual lines in the LSIB and World Polygons dataset, the “CC1_WPID” and “CC2_WPID” fields contain a Universally Unique Identifier (UUID), version 4, which provides a stable description of each geographic entity in a boundary pair relationship. Each UUID corresponds to a geographic entity listed in the World Polygons dataset. These fields allow for linkage between individual lines in the LSIB and the overall World Polygons dataset. Five additional fields in the LSIB expand on the UUID concept and either describe features that have changed across space and time or indicate relationships between previous versions of the feature. The “LSIB_ID” attribute is a UUID value that defines a specific instance of a feature. Any change to the feature in a lineset requires a new “LSIB_ID.” The “ANTECIDS,” or antecedent ID, is a UUID that references line geometries from which a given line is descended in time. It is used when there is a feature that is entirely new, not when there is a new version of a previous feature. This is generally used to reference countries that have dissolved. The “PREVIDS,” or Previous ID, is a UUID field that contains old versions of a line. This is an additive field, that houses all Previous IDs. A new version of a feature is defined by any change to the

Thank you for your your interest in downloading the PADDDtracker.org Data Release Version 2.0. This dataset includes validated data on Protected Area Downgrading, Downsizing, and Degazettement (PADDD). It updates prior versions of PADDDtracker data (Versions 1.0 and 1.1), prepared by the World Wildlife Fund and Conservation International.

PADDDtracker.org Data Release Version 2.0 contains a total of 4597 PADDD events, including updated PADDD events from previous data releases (1.0 and 1.1), and new records from around the world (North America, Australia, Latin America and the Caribbean, Africa, Asia, Europe).

Please note that this is not a full list of PADDD events occurring in these regions during this time period, but only those that have been validated following peer review. Please see PADDDtracker.org for more information.

In the folder PADDDtracker_DataReleaseV2_May2019, you will find:

1. PADDDtracker_DataReleaseV2_May2019.xlsx: this excel file contains data on all validated PADDD events, including numerical and categorical data. This includes data on location, dates, areas, IUCN categories, and causes associated with PADDD events.

• Readme tab: summary of data

• Field definitions: contains definitions for all fields (attributes) in the database

• PADDDevents tab: information about location, dates, causes, etc. on PADDD events

• SupportingDetails&References tab contains supporting details and references for PADDD events. Note that the field “PADDDtrackerID” is a unique identifier for each PADDD event and can be used to join the two tables. (PADDDtrackerID_old is the field used in Version 1.1 and 1.0). The Supporting Details and References are omitted from the shapefile, as the text exceeds the character limit.

2. PADDDtracker.org_DataReleaseV2.0_May2019_Pts.shp: This shapefile contains point data for all validated PADDD events as in Golden Kroner et al. (2019).

• Please note that events for which exact locations are unknown are represented as points on the capital city of the country. If use this data for spatially explicit analyses for which location of PADDDed areas is necessary, please use the field “Location Known?” as a filter.

3. PADDDtracker.org_DataReleaseV2.0_May2019_Poly.shp: This shapefile contains validated polygon data for PADDD events as in Golden Kroner et al. (2019).

• Please note that events for which exact extent are unknown are represented as circular buffers with the PADDDed area. Use “Location Known?” column to identify the records.

4. FieldDefinitions_for_PADDD_Data: contains definitions for fields used in dataset

5. PADDDtracker Technical guide: contains an additional information about PADDD data collection methodology.

6. README file, containing terms of agreement and technical notes

If you have any questions about the dataset, please contact admin@padddtracker.org

How to Attribute

Please use the following attribution when using or referencing this data:

Conservation International and World Wildlife Fund. 2019. PADDDtracker.org Data Release Version 2.0 (May 2019). Arlington, VA: Conservation International. Washington, DC: World Wildlife Fund.

Terms of Use

Terms of Use

Thank you for your interest in using the PADDDtracker.org Data Release Version 2.0 (May 2019)

The dataset is offered for download without charge, as a service to the public. By choosing to download or use the dataset, you agree to the following terms and conditions.

You may use the dataset only for noncommercial purposes that are scientific, charitable, or educational. You may create new works based upon the dataset for your own use for these purposes; however, you may not publish, distribute, sell, rent, lease, sublicense, lend, assign, or transfer, in whole or in part, or provide unlicensed third parties access to the data without our express written permission.

You agree to provide the following attribution, reasonable to the medium or means you are using, with any use you make of the dataset:

• Conservation International and World Wildlife Fund. 2019. PADDDtracker.org Data Release Version 2.0 (May 2019). Arlington, VA: Conservation International. Washington, DC: World Wildlife Fund. DOI: 10.5281/zenodo.3371733

In addition:

• You acknowledge and agree that World Wildlife Fund, Inc. (“WWF”) and Conservation International (“CI”) are the creators and owners of the data; that it is protected by copyright and other law; and that this permission grants you no rights to the data other than the limited permission expressly provided here.

• You agree that the data is provided “as is,” without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, noninterference, system integration, and non-infringement. You shall bear the entire risk of use of the data and expressly acknowledge that the data may contain some nonconformities, defects, and errors.

• You acknowledge that WWF and CI are nonprofit, charitable organizations not engaged in a commercial business, industry, or trade, and AGREE THAT THE LIABILITY OF WWF AND CI AND THEIR OFFICERS, DIRECTORS, OR EMPLOYEES TO YOU, UNDER ANY THEORY OF LIABILITY, SHALL NOT EXCEED THE ROYALTY, IF ANY, PAID TO WWF AND CI FOR ACCESS TO THE DATA, AND SHALL NOT INCLUDE ANY GENERAL, INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, LOSS OF BUSINESS, LOSS OR USE OR OF DATA, OR INTERRUPTION OF BUSINESS), EVEN IF WWF AND CI OR THEIR OFFICERS, DIRECTORS, OR EMPLOYEES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Finally, we request users to provide copes, reasonable to the medium you are using, of any products arising from your use of the dataset. This includes, but is not limited to, peer reviewed publications reports, informational communications, posters, or electronic media.

This file provides duplicate information from: https://www.padddtracker.org/download-data-1

This data is published in: Golden Kroner, R.E., Qin, S., Cook, C., Pack, S., Krithivasan, R., Bonilla, O.D., Cort-Kansinally, K.A., Coutinho, B., Feng, M., Martinez Garcia, M.I., He, Y., Kennedy, C., Lebreton, C., Ledezma, J.C., Lovejoy, T.E., Luther, D., Parmanand, Y., Ruíz-Agudelo, C., Yerena, E., Zambrano, V.M., and Mascia, M.B. 2019. The uncertain future of protected lands and waters. Science. https://science.sciencemag.org/content/364/6443/881

The database contains native and alien species records for National Park islands in the southern Great Barrier Reef. Attributes for each record include information on abundance, life history traits, habitat requirements, limitations of source, and relevant species information from government bodies including EPBC and NCA listings. Basic interaction information among species (alien vs. native) is also recorded. This dataset also has basic information about the islands such as area, location, and regional ecosystem types present on the island. One shapefile, Island Threats, contains information on the presence and absence of a number of animals and plant threats on islands in the Southern Great Barrier Reef as elicited from experts. Each spatially explicit point represents data for a given species on a specific island. Another shapefile, Regional Ecosystems, contains information on the various Queensland Herbarium regional ecosystem (RE) types extracted for National Park Islands in the Southern Great Barrier Reef. Individual polygons represent an area of a specific RE type. The last shapefile, Features on Islands, contains information on the abundance of a number of native animals on islands in the Southern Great Barrier Reef as elicited from experts. Each spatially explicit point represents data for a given species on a specific island. This database was created as a basis for the decision support tool being developed for NERP 9.3. The database is the most complete dataset for the islands in the Southern Great Barrier Reef at the time of release. Method: Database: A comprehensive literature review was conducted for all published and ‘grey’ source material containing biological records for National Park islands in the southern Great Barrier Reef (GBR). Unpublished species records were also compiled from sources such as WildNet, the Queensland Herbarium, and personal communications. For a given source, each species on each island received a unique record. Records were structured within the database so that each record remained associated with its source, allowing revisitation in order to review records within their original context. Attributes relevant to each record were extracted from source, including information on habitat requirements, life history traits, abundance, and source limitations e.g. incomplete sampling of island area. Additional attributes for each record were extracted from the Australian and Queensland government websites, including information on EBPC and CNA listings, and endemicity. Island Threats: Experts who frequent the islands were consulted as to whether they believed a given threat was present or absent on the islands. These data were input into the associated access database Island_database.accbd, and then transformed into the point based shapefile. The following is the list of threats considered in this dataset. * African Big Headed Ant * Black Rat * Brushtail Possum * Cane toad * Climbing Asparagus * Cobblers Peg * Red Junglefowl * Dwarf Poinsettia * Eastern Grey Kangaroo * Feral Cat * Feral Cattle * Feral Goat * Feral Horse * Feral Pig * Fox * Green Panic * Groundsel * Guinea Grass * Hog Deer * House Mouse * House Sparrow * Lantana * Morning Glory * Mother of Millions * Nightshade * Noogoora Burr * Periwinkle * Rubbervine * Singapore Daisy * Sisal Hemp * Soft Scale * Yellow Guava * Molasses Grass * Mossman River Grass * Mother-in-Law Tongue * Pink Periwinkle * Prickly Pear Regional Ecosystems: Shape files of regional ecosystem (RE) types and National Park Islands in the Southern GBR were obtained from Queensland Herbarium (in 2014). These data were rearranged and merged to create a single shape file. eAtlas editor note: It was noticed when mapping this shapefile that many of the polygon regions had multiple overlapping features, sometimes consisting of duplicates, and sometimes containing multiple RE codes. The cause of this in the dataset is unknown. A map of these overlaps was made by rendering them as black transparent polygons. This map is available in the download section of this metadata record. Features on Islands: Experts who frequent the islands were consulted as to the maximum and minimum number of individuals/pairs of native species on the islands. On each island there are multiple estimates for each species, one from each expert. The following is the set of species that are included in this dataset. * Anous minutus (Black noddy) * Anous stolidus (Brown noddy) * Burhinus grallarius (Bush stone-curlew) * Calyptorhynchus lathami (Glossy black cockatoo) * Caretta caretta (Loggerhead sea turtle) * Charadrius ruficapillus (Red-capped plover) * Chelonia mydas (Green sea turtle) * Chroicocephalus novaehollandiae (Silver gull) * Egretta sacra (Pacific reef heron) * Epthianura crocea (Yellow chat) * Esacus magnirostris (Beach stone-curlew) * Falco peregrinus (Peregrine falcon) * Fregata ariel (Lesser frigatebird) * Fregata minor (Great frigatebird) * Gallirallus philippensis (Buff-banded rail) * Haematopus fuliginosus (Sooty oystercatcher) * Haematopus longirostris (Pied oystercatcher) * Haliaeetus leucogaster (White-bellied sea eagle) * Haliastur indus (Brahminy kite) * Hydroprogne caspia (Caspian tern) * Megapodius reinwardt (Orange-footed scrubfowl) * Natator depressus (Flatback sea turtle) * Onychoprion anaethetus (Bridled tern) * Onychoprion fuscata (Sooty tern) * Pandion cristatus (Osprey) * Phaethon rubricauda (Red-tailed tropicbird) * Phalacrocorax varius (Australian pied cormorant) * Phascolarctos cinereus (Koala) * Pluvialis squatarola (Grey plover) * Ptilinopus regina (Rose-crowned fruit dove) * Sterna dougallii (Roseate tern) * Sterna sumatrana (Black-naped tern) * Sternula albifrons (Little tern) * Sula dactylatra (Masked booby) * Sula leucogaster (Brown booby) * Thalasseus bengalensis (Lesser crested tern) * Thalasseus bergii (Greater crested tern) * Tringa brevipes (Grey-tailed tattler) * Xeromys myoides (False Water Rat) * Zosterops lateralis (Silvereye) Further information on the methodology can be found in the final report for this project: Pressey, R., Wenger, A. (2015) Prioritising Management Actions for Great Barrier Reef Islands. http://www.nerptropical.edu.au/sites/default/files/publications/files/NERP9.3_final_report-FINAL-Complete.pdf Limitations of the data: Database: Abundance data varies over different units of time. For example in the ‘Total’ column, 100 might indicate 100 individuals observed in a single survey, or over repeated visits to an island. The units of observation are maintained in the ‘Abundance’ column, e.g. 100/birds January 2000. Values in the ‘Total’ column should be interpreted in conjunction with the ‘Abundance’ column. We have removed any data for which we have data sharing agreements. Therefore, the database used for this project is much more comprehensive than we are able to submit.
Island Threats: The shapefile is limited to presence or absences only for a focal number of threats on targeted islands in the Southern Great Barrier Reef. There is no data on the number of individuals or the extent of the species on the islands. The presence or absence of a species is based on general consensus by experts. If there is no point for a given island/threat pair then the presence of absence of the species on that island is unknown. Regional Ecosystems: The shapefile is limited to National Park Islands in the Southern Great Barrier Reef. Information on RE types on other islands exists but was not the focus of this work. In some cases multiple polygons of the same shape and size exist for the same region of an island. Here a number of RE types were recorded within the polygon/area but the exact spatial extent of the RE is unknown, only the percentage of the polygon/area that the RE covers. Features on Islands: The shapefile is limited to best guess estimates of the maximum and minimum number of individuals/pairs of a select number of native species on an island. The extent of the species on the island and how the population has changed over time are not known. Format: Island_database.accbd Format: Access database. This database contains a number of tables which are categorised according to their name: 1 "Records:…" are record tables where each row is a specific record relating to the focus of the table. 2 "Attributes:…" are attribute tables which have information specific to each category (e.g. islands, native animals, regional ecosystems. Attribute tables typically list the primary keys for each category which link to the records tables. 3 "Stats:…" are tables that contain basic statistics on records tables. These have been created using queries and will have queries with associated query names. 4 "Queries:…" are tables that have been created from queries (other than specific statistics queries) run on records/attributes tables and will have queries with associated query names. This database also contains a number of queries which are based on the records/attributes tables, a most of which are linked to stats or queries tables of an associated name. See the ‘Design View’ of any of the tables for more information, in particular for column/field descriptions. Island Threats: Threats_on_Islands.*, GIS shape file Projected Coordinate System: GDA_1994_MGA_Zone_55 Projection: Transverse_Mercator Data dictionary:

Isl_name: name of the island where the record occurs LONG: x co-ordinate location of the island (descimal degrees) LAT: y co-ordinate location of the island (descimal degrees) Threat: Common name of the threat Interactio: Whether the threat species is present (1) or absent (0) on the island

Regional Ecosystems: RE_on_NP_Islands.*, GIS shape file Projected Coordinate System: GDA_1994_MGA_Zone_55 Projection: Transverse_Mercator Data dictionary:

RE_type: Code for the regional ecosystem type, see associated access database Island_database.accbd for RE type descriptions PC_of_Poly: percentage of

This data set is part of an ongoing project to consolidate interagency fire perimeter data. Currently only certified perimeters and new perimeters captured starting in 2021 are included. A process for loading additional perimeters is being evaluated.The Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service includes perimeters for wildland fire incidents that meet the following criteria:Categorized in the IRWIN (Integrated Reporting of Wildland Fire Information) integration service as a Wildfire (WF) or Prescribed Fire (RX)Is Valid and not "quarantined" in IRWIN due to potential conflicts with other recordsAttribution of the source polygon is set to a Feature Access of Public, a Feature Status of Approved, and an Is Visible setting of YesPerimeters are not available for every incident. This data set is an ongoing project with the end goal of providing a national interagency fire history feature service of best-available perimeters.No "fall-off" rules are applied to this service. The date range for this service will extend from present day back indefinitely. Data prior to 2021 will be incomplete and incorporated as an ongoing project.Criteria were determined by an NWCG Geospatial Subcommittee task group. Data are refreshed every 5 minutes. Changes in the perimeter source may take up to 15 minutes to display.Perimeters are pulled from multiple sources with rules in place to ensure the most current or most authoritative shape is used.Warning: Please refrain from repeatedly querying the service using a relative date range. This includes using the “(not) in the last” operators in a Web Map filter and any reference to CURRENT_TIMESTAMP. This type of query puts undue load on the service and may render it temporarily unavailable.Attributes and their definitions can be found below. More detail about the NWCG Wildland Fire Event Polygon standard can be found here.Attributes:poly_SourceOIDThe OBJECTID value of the source record in the source dataset providing the polygon.poly_IncidentNameThe incident name as stored in the polygon source record.poly_MapMethodThe mapping method with which the polygon was derived.poly_GISAcresThe acreage of the polygon as stored in the polygon source record.poly_CreateDateSystem generated date for the date time the source polygon record was created (stored in UTC).poly_DateCurrentSystem generated date for the date time the source polygon record was last edited (stored in UTC).poly_PolygonDateTimeRepresents the date time that the polygon data was captured.poly_IRWINIDIRWIN ID stored in the polygon record.poly_FORIDFORID stored in the polygon record.poly_Acres_AutoCalcSystem calculated acreage of the polygon (geodesic WGS84 acres).poly_SourceGlobalIDThe GlobalID value of the source record in the source dataset providing the polygon.poly_SourceThe source dataset providing the polygon.attr_SourceOIDThe OBJECTID value of the source record in the source dataset providing the attribution.attr_ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency initial attack fire suppression expenditures. for A, B, C & D size class fires on FS lands.attr_ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.attr_ContainmentDateTimeThe date and time a wildfire was declared contained. attr_ControlDateTimeThe date and time a wildfire was declared under control.attr_CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.attr_IncidentSizeReported for a fire. The minimum size is 0.1.attr_DiscoveryAcresAn estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.attr_DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.attr_EstimatedCostToDateThe total estimated cost of the incident to date.attr_FinalAcresReported final acreage of incident.attr_FFReportApprovedByTitleThe title of the person that approved the final fire report for the incident.attr_FFReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.attr_FFReportApprovedDateThe date that the final fire report was approved for the incident.attr_FireBehaviorGeneralA general category describing the manner in which the fire is currently reacting to the influences of fuel, weather, and topography. attr_FireBehaviorGeneral1A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral2A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral3A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireCauseBroad classification of the reason the fire occurred identified as human, natural or unknown. attr_FireCauseGeneralAgency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. attr_FireCauseSpecificA further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. attr_FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. attr_FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.attr_FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.attr_FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. attr_FireOutDateTimeThe date and time when a fire is declared out. attr_FireStrategyConfinePercentIndicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.attr_FireStrategyFullSuppPrcntIndicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.attr_FireStrategyMonitorPercentIndicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.attr_FireStrategyPointZonePrcntIndicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.attr_FSJobCodeA code use to indicate the Forest Service job accounting code for the incident. This is specific to the Forest Service. Usually displayed as 2 char prefix on FireCode.attr_FSOverrideCodeA code used to indicate the Forest Service override code for the incident. This is specific to the Forest Service. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.attr_GACCA code that identifies one of the wildland fire geographic area coordination center at the point of origin for the incident.A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.attr_ICS209ReportDateTimeThe date and time of the latest approved ICS-209 report.attr_ICS209RptForTimePeriodFromThe date and time of the beginning of the time period for the current ICS-209 submission.attr_ICS209RptForTimePeriodToThe date and time of the end of the time period for the current ICS-209 submission. attr_ICS209ReportStatusThe version of the ICS-209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates, and even multiple finals (as determined by business rules).attr_IncidentManagementOrgThe incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.attr_IncidentNameThe name assigned to an incident.attr_IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. attr_IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category further breaks down the Event Kind into more specific event categories.attr_IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.attr_InitialLatitudeThe latitude location of the initial reported point of origin specified in decimal degrees.attr_InitialLongitudeThe longitude location of the initial reported point of origin specified in decimal degrees.attr_InitialResponseAcresAn estimate of acres burning at the time of initial response. More specifically when the IC arrives and performs initial size up. The

The Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service includes perimeters for wildland fire incidents that meet the following criteria:Categorized in the IRWIN (Integrated Reporting of Wildland Fire Information) integration service as a Wildfire (WF) or Prescribed Fire (RX) recordFire Discovery Date is in the year 2025Is Valid and not "quarantined" in IRWIN due to potential conflicts with other recordsAttribution of the source polygon is set to a Feature Access of Public, a Feature Status of Approved, and an Is Visible setting of YesPerimeters are not available for every incident. For a complete set of features that meet the same IRWIN criteria, see the 2025 Wildland Fire Incident Locations to Date service.No "fall-off" rules are applied to this service. Criteria were determined by an NWCG Geospatial Subcommittee task group. Data are refreshed every 5 minutes. Changes in the perimeter source may take up to 15 minutes to display.Perimeters are pulled from multiple sources with rules in place to ensure the most current or most authoritative shape is used.Attributes and their definitions can be found below. More detail about the NWCG Wildland Fire Event Polygon standard can be found here.Attributes:poly_SourceOIDThe OBJECTID value of the source record in the source dataset providing the polygon.poly_IncidentNameThe incident name as stored in the polygon source record.poly_MapMethodThe mapping method with which the polygon was derived.poly_GISAcresThe acreage of the polygon as stored in the polygon source record.poly_CreateDateSystem generated date for the date time the source polygon record was created (stored in UTC).poly_DateCurrentSystem generated date for the date time the source polygon record was last edited (stored in UTC).poly_PolygonDateTimeRepresents the date time that the polygon data was captured.poly_IRWINIDIRWIN ID stored in the polygon record.poly_FORIDFORID stored in the polygon record.poly_Acres_AutoCalcSystem calculated acreage of the polygon (geodesic WGS84 acres).poly_SourceGlobalIDThe GlobalID value of the source record in the source dataset providing the polygon.poly_SourceThe source dataset providing the polygon.attr_SourceOIDThe OBJECTID value of the source record in the source dataset providing the attribution.attr_ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency initial attack fire suppression expenditures. for A, B, C & D size class fires on FS lands.attr_ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.attr_ContainmentDateTimeThe date and time a wildfire was declared contained. attr_ControlDateTimeThe date and time a wildfire was declared under control.attr_CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.attr_IncidentSizeReported for a fire. The minimum size is 0.1.attr_DiscoveryAcresAn estimate of acres burning upon the discovery of the fire. More specifically when the fire is first reported by the first person that calls in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.attr_DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.attr_EstimatedCostToDateThe total estimated cost of the incident to date.attr_FinalAcresReported final acreage of incident.attr_FFReportApprovedByTitleThe title of the person that approved the final fire report for the incident.attr_FFReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.attr_FFReportApprovedDateThe date that the final fire report was approved for the incident.attr_FireBehaviorGeneralA general category describing the manner in which the fire is currently reacting to the influences of fuel, weather, and topography. attr_FireBehaviorGeneral1A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral2A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireBehaviorGeneral3A more specific category further describing the general fire behavior (manner in which the fire is currently reacting to the influences of fuel, weather, and topography). attr_FireCauseBroad classification of the reason the fire occurred identified as human, natural or unknown. attr_FireCauseGeneralAgency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. attr_FireCauseSpecificA further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. attr_FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. attr_FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.attr_FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.attr_FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. attr_FireOutDateTimeThe date and time when a fire is declared out. attr_FireStrategyConfinePercentIndicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.attr_FireStrategyFullSuppPrcntIndicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.attr_FireStrategyMonitorPercentIndicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.attr_FireStrategyPointZonePrcntIndicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.attr_FSJobCodeA code use to indicate the Forest Service job accounting code for the incident. This is specific to the Forest Service. Usually displayed as 2 char prefix on FireCode.attr_FSOverrideCodeA code used to indicate the Forest Service override code for the incident. This is specific to the Forest Service. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.attr_GACCA code that identifies one of the wildland fire geographic area coordination center at the point of origin for the incident.A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.attr_ICS209ReportDateTimeThe date and time of the latest approved ICS-209 report.attr_ICS209RptForTimePeriodFromThe date and time of the beginning of the time period for the current ICS-209 submission.attr_ICS209RptForTimePeriodToThe date and time of the end of the time period for the current ICS-209 submission. attr_ICS209ReportStatusThe version of the ICS-209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates, and even multiple finals (as determined by business rules).attr_IncidentManagementOrgThe incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.attr_IncidentNameThe name assigned to an incident.attr_IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. attr_IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category further breaks down the Event Kind into more specific event categories.attr_IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.attr_InitialLatitudeThe latitude location of the initial reported point of origin specified in decimal degrees.attr_InitialLongitudeThe longitude location of the initial reported point of origin specified in decimal degrees.attr_InitialResponseAcresAn estimate of acres burning at the time of initial response. More specifically when the IC arrives and performs initial size up. The minimum size must be 0.1. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.attr_InitialResponseDateTimeThe date/time of the initial response to the incident. More specifically when the IC arrives and performs initial size up. attr_IrwinIDUnique identifier assigned to each incident record in IRWIN.attr_IsFireCauseInvestigatedIndicates if an investigation is underway or was completed to determine the cause of a fire.attr_IsFSAssistedIndicates if the Forest Service provided assistance on an incident outside their jurisdiction.attr_IsMultiJurisdictionalIndicates if the