Clark County Political Boundaries: Cities, Urban Boundary, Zip Codes, Townships, Ward, Senate, Place, MCD, Indian Reservations, Assembly, Commission District, Congressional District, Commission District, CD Boundary

This layer is stored as two datasets (point and polygon)in the Geographical Information System (GIS). Points represent landing areas, mammal, flying bird and penguin data. Polygons represent the horizontal flight limits of helicopters and areas set aside for specific management purposes.

Basemap of Sherburne County, Minnesota.

This is shapefile of data collected through the U.S. Fish and Wildlife Service Monarch Conservation Database (MCD) summarized at the county-level. The spatial extent of the data is the continental United States. Summary data includes the number of completed, implemented, or planned conservation efforts in each county, the number of acres of conservation effort, and an estimate of the number of milkweed stems added to the landscape as a result of conservation efforts. All of the data was provided on a voluntary basis by registered users of the MCD. This data was used in the monarch species status assessment to evaluate the current level of conservation effort, and project future levels of conservation effort.

A coastline of Heard Island and McDonald Islands, created in the AMBIS (Australian Maritime Boundaries Information System) by Geoscience Australia (previously AUSLIG).

This layer is stored as three datasets (polygon, line and point) in the Geographical Information System (GIS). Polygon data represents lakes and reefs. Line data represents reef boundaries. Point …Show full descriptionThis layer is stored as three datasets (polygon, line and point) in the Geographical Information System (GIS). Polygon data represents lakes and reefs. Line data represents reef boundaries. Point data represents spotheights, volcanic cones, refuges and a grave. All the data in this dataset was sourced from the Heard Island 1:50 000 map, edition 3, published in 1985. The data conforms to the Australian Antarctic Spatial Data Model which includes Data Quality Indicators.

Coastline, ridgelines and areas of bare rock of McDonald Islands were digitised from Quickbird satellite imagery acquired 9 April 2003.

Polygon boundary files for the incorporated townships and cities within Sherburne County MN.

The 2020 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any other place. The generalized boundaries of the consolidated cities in this file are based on those as of January 1, 2020, as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

2020 Census Tract to MCD lookup table

Bathymetry around Heard and McDonald Islands and the Kerguelen Plateau.

This layer is stored as two datasets (line and polygon) in the Geographical Information System (GIS).

The line data were interpolated from soundings made on ANARE voyages and soundings provided by the Royal Australian Navy Hydrographic Service.

The line data were polygonised to create the polygon data.

The data were produced for a 1:1 million scale bathymetric map (refer to link).

Geospatial data about Columbiana County, Ohio Census mcd. Export to CAD, GIS, PDF, CSV and access via API.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

The Heard Island management zones are a polygon and line dataset stored in the Geographical Information System (GIS). These areas were developed inline with the Heard Island and McDonald Islands Marine Reserve Management Plan, published in 2005.

Heard Island and McDonald Islands, vegetation layer. This is a polygon dataset stored in the Geographical Information System (GIS). The data represents approximately the areas of vegetation cover on these islands.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2019, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally- recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2019, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs, delineated in 20 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

American Community Survey 5-year Estimates 2016-2020. Includes Age, Disability, Education, Female Population, LEP, Low Income, Place of Birth (Foreign Born), Race (Minority) and Zero Vehicle Households for MCDs.

1. PUBLICATION CORRESPONDING TO THESE DATA

Sloan, Sean*; Locatelli, Bruno; Andela, Niels; Cattau, Megan E.; Gaveau, David; Tacconi, Luca. 2022 'Declining Severe Fire Activity on Managed Lands in Equatorial Asia'. Communications Earth & Environment. DOI: 10.1038/s43247-022-00522-6.

*Corresponding author email: sean.sloan@viu.ca

2. ABSTRACT OF THE DATA

The GIS data and corresponding attribute data described here pertain to discrete fire events, their severity, and their ignitions, as derived on the basis of daily MODIS Collection 6 MCD14ML active-fire detections (AFDs). Data on fire events and their ignitions are provided separately, as two data files. These data files on fire events and ignitions may however be linked to each other by the data user. Fire-event severity is quantified per fire event and reported in the data file for fire events.

A fire event is a cluster of MODIS Collection 6 MCD14ML active-fire detections (AFDs) wherein each AFD has a spatial (<=1-km) and temporal (<=4-day) proximity to another AFD in the same fire event, inferring thus a relational co-occurrence amongst AFDs in time and space. In other words, a fire event is considered a likely occasion of burning wherein all constituent AFDs are related to each other in time and space, either directly (as for proximate AFDs) or indirectly (as in the case of a large area of fire activity that spread progressively over time and space from an initial source).

Each fire event has a designated ignition AFD, being the AFD of the fire event with the earliest detection date. A given fire event can have more than one ignition AFD if the ignitions all share same earliest detection date. The ignition AFD(s) is the nominal initial source of the burning described by the corresponding fire event. All other, non-ignition AFDs of a fire event are deemed its 'propagation' AFDs, since these AFDs follow from the ignitions, temporally and spatially.

See Figure 4 in the publication by Sloan et al. for an illustration of the geography of fire events and their ignition AFDs.

Fire events and their ignitions were derived from standard science-quality MODIS Collection 6 MCD 14ML AFD data, commonly referred to as fire 'hotspot' data. Data were detected by both the Terra and Aqua satellite sensors daily for Indonesia between July 2002 and December 2019. Information on these input data are provide by the two citations below. The publication of Sloan et al. provides methodological details on how the MODIS Collection 6 MCD 14ML AFD data were processed into discrete fire events and ignitions.

EarthData. MODIS Collection 6 Active-Fire Detections standard scientific data (MCD14ML), NASA EarthData, https://earthdata.nasa.gov/firms (2019).

Giglio, L., Schroeder, W. & Justice, C. O. The Collection 6 MODIS active fire detection algorithm and fire products. Remote Sensing of Environment 178, 31-41, (2016).

3. DATA FILES

Two data files are distributed here – one for discrete fire events, and another for the ignition AFDs of each fire event. The data files are provided in a GIS-compatible format, and also as a generic text format, as described below.

3.1 GIS VERSION

Data files in GIS-compatible format are provided as 'feature classes' within an ArcGIS file geodatabase 'Sloan_MODIS_FireEvents_Ignitions_2002_2019.gdb'. These data files can be viewed and manipulated using either ArcGIS Desktop or ArcGIS Pro software. There is one feature class for fire events, and another file for ignitions.

Sloan_MODIS_FireEvents_Ignitions_2002_2019.gdb fire4_all_spatial_fire_2002_2019_joins_sp_LC

This file pertains to fire events. All AFDs of a given fire event are included, without differentiation as to whether the AFDs are ignition AFDs or other (propagation) AFDs. Fire events are assigned unique ID values and basic attribute data.

Sloan_MODIS_FireEvents_Ignitions_2002_2019.gdb fire4_all_spatial_fire_2002_2019_igs_sp_LC

This file pertains to ignitions. Only ignition AFDs are included for a given fire event. Fire events corresponding to the ignitions are assigned unique ID values and basic attribute data.

3.2 CSV TEXT VERSION

Both data files are also supplied as comma-separated value (CSV) text files for viewing and manipulation in non-GIS software, such as Excel, text editors, or any statistical software. The text files can also be read into various GIS software. CSV-formatted files have the same file name and attribute fields as the corresponding GIS-formatted data files. These CSV-formatted data files (as well as the GIS-formatted data files) include attribute data on the latitude and the longitude of each AFD.

Attribute field names are included as the first row of values in a CSV file.

No 'text qualifiers' like quotations (" ") or inverted commas ('') are used to designate text/string values within the CSV file. Text values appear directly between commas in the CSV data file, e.g., …,Kalimantan_Southern,… .

Note two points of caution for working with these CSV data:

i) Microsoft Excel may be used for a partial view of the data file nfire4_all_spatial_fire_2002_2019_joins_sp_LC.csv, but it is not recommended for working with this data file. This is because the number of records/rows in this csv file slightly exceeds that maximum that may be read by Excel, which is just over 1 million. This limitation does not apply to the other csv file, however.

ii) The GIS-formatted data files employ 'null values' in their attribute tables, and so the corresponding 'values' in the CSV-formatted data files are similarly null. For null values, no value whatsoever is ascribed, not even 0. In the syntax of a CSV file (apparent upon opening the file in any text editor like Microsoft Notepad), a null value is denoted by two consecutive commas without any value, text, or space between them. If a CSV file were opened in Excel, a cell assigned a null value would be blank, not 0 or otherwise. This denotes the correct transcription of the GIS-formatted data. This feature will not impede the correct reading of these CSV data by whatever software. Users are made aware of this feature merely to ensure the proper input of these data into whatever software.

4. DATA STRUCTURE / GEOGRAPHY

The GIS-formatted data files are 'point data', i.e., they map the geography of AFDs as individual 'points', in keeping with how these MODIS MCD14ML AFD data were originally structured. For the GIS-formatted data files, each record/row in its corresponding attribute tables corresponds geographically to single AFD 'point', regardless of whether that AFD belongs to a fire event comprised of many AFDs. In the parlance of GIS files, the files depict 'single-part' point features. The unique ID field [nfireID2] serves to denote the fire event to which a given AFD belongs.

Similarly, for the CSV-formatted data files, each record/row of values corresponds to a single AFD.

There are 1,232,377 records for the data file 'nfire4_all_spatial_fire_2002_2019_joins_sp_LC'.

There are 720795 records for the data file 'nfire4_all_spatial_fire_2002_2019_igs_sp_LC'.

5. ATTRIBUTE FIELDS

In the data files, while some attribute fields pertain to the individual AFD as the unit of observation (e.g., the land-cover class coincident with the AFD), other attribute fields correspond to the larger 'fire event' to which the individual AFD belongs (e.g., the total duration of fire activity for the fire event). Accordingly, for certain attribute fields pertaining to the fire event as a whole, their values will appear 'duplicated' in the data file amongst those individual AFDs (records) that constitute the fire event in question. Whether a given attribute field pertains to the individual AFD or to its constituent fire event is denoted below for each field.

Each AFD is assigned a unique ID field denoting its constituent fire event, [nfireID2]. This field is consistent between both data files, so that attribute data for a given fire event may be 'matched' to attribute data for its corresponding ignition AFD(s), and vice versa, on the basis of the common value of the field [nfireID2].

Note that many attributes below are as originally defined/measured by the input MCD 14ML data, or are derived directly thereof.

5.1 DATASET nfire4_all_spatial_fire_2002_2019_joins_sp_LC

| Field Name | Geography of Attribute Value | Definition | | OID | AFD | Object ID value. Unique values for each AFD (record) in the GIS-formatted data file when viewed in ArcGIS. Field values are -1 in the CSV-formatted data file. | | Peat | AFD | Denotes whether the AFD occurs on peatlands (value=1) as defined in Sloan et al. | | MIN_CONFIDE | Fire Event | The minimum detection confidence of all AFDs in the fire event, where confidence ranges from 1-100%. | | MAX_CONFIDE | Fire Event | The maximum detection confidence of all AFDs in the fire event, where confidence ranges from 1-100%. | | MEAN_CONFIDE | Fire Event | The mean detection confidence of all AFDs in the fire event, where confidence ranges from 1-100%. | | STD_CONFIDE | Fire Event | The standard deviation of detection confidence of all AFDs in the fire event, where confidence ranges from 1-100%. | | SUM_FRP | Fire Event | The sum total of all fire-radiative power (FRP) measures for all AFDs in the fire event. Units are megawatts. | | MEAN_FRP | Fire Event | The mean of all fire-radiative power (FRP) measures for all AFDs in the fire event. Units are megawatts. | | MIN_FRP | Fire Event | The minimum of all fire-radiative power (FRP) measures for all AFDs in the fire event. Units are megawatts. | | MAX_FRP | Fire Event | The