This guide will show the process of adding data to a group in ArcGIS Online. If you don't have a group set up click here to learn how to create a group and add members.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
Author: Titus, Maxwell (mtitus@esri.com)Last Updated: 3/4/2025Intended Environment: ArcGIS Notebooks on ArcGIS Online, ArcGIS Portal, or ArcGIS Pro.Purpose: This Notebook can batch share content from one group to another within ArcGIS Online Organization or an ArcGIS Portal. This does not require admin privileges to do this script and does not impact the original group having content moved.Requirements: Whoever runs the Notebook must have:They have access to both groups; where they share content from (i.e., the origin group) and (i.e., the target group).Can share content with the targeted group.
(1) Sign in to ArcGIS Online and open the "Group" tab.(2) Click "Create Group"(3) Enter a name for your new group
ArcGIS Tapestry is the third generation of Esri’s geodemographic segmentation system, designed to classify almost 240,000 U.S. neighborhoods at the census block group level. These neighborhoods are grouped into 12 summary, or LifeMode, groups, which are then further classified into 60 distinct segments to create a model of lifestyle and life stage classifications.ArcGIS Tapestry data can be used to understand a community's complexity. Each segment provides insight into patterns at the neighborhood and community level and can be used to compare study areas. Typically, communities are composed of multiple segments and the diversity of an area's segments is relevant to understanding each community's unique socioeconomic and demographic dynamics.Timmons Group conducted an analysis of three geographies showcased in this service. Enriched with 2020 population, 2025 population, and 2025 Dominate Tapestry Segment values are States, Counties, and 25 square mile transverse hex bins. ArcGIS Tapestry by Timmons Group v1 published on August 7, 2025. Contact brian.kingery@timmons.com for more information.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
U.S. Census Block GroupsThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), displays Census block groups in the 50 states, the District of Columbia, and Puerto Rico. Per the USCB, "Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same decennial census. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas".Block Group 2 - Census Tract 010400 (Santa Fe, NM area)Data version: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Census Block Groups) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 70 (Series Information for Block Group State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (U.S. Census Block Groups - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: What are census blocks?For feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets
This guide will show the process of adding data to a group in ArcGIS Online.If you don't have a group set up click here to learn how to create a group and add members.Click here to see how to add content to your group before creating the gallery app.
The map data and summary statistics data are sourced from Johns Hopkins University and Esri’s Living Atlas. The charts are being sourced from a database created by Timmons Group GIS that leverages the temporal data provided by JHU on github.
Why did we do this?
How did we do this?
The raw data from JHU does not support the temporal charting at the State level or County level, so we created a data pipeline to leverage JHU’s source data files and transforms their raw data into our data model
Key features:
Check out our other ArcGIS Dashboard powered by the new ArcGIS Experience Builder to explore the COVID-19 curves at the country level around the world - Explore the COVID-19 Curve
For additional information, please contact:
ArcGIS Tapestry is the third generation of Esri’s geodemographic segmentation system, designed to classify almost 240,000 U.S. neighborhoods at the census block group level. These neighborhoods are grouped into 12 summary, or LifeMode, groups, which are then further classified into 60 distinct segments to create a model of lifestyle and life stage classifications.ArcGIS Tapestry data can be used to understand a community's complexity. Each segment provides insight into patterns at the neighborhood and community level and can be used to compare study areas. Typically, communities are composed of multiple segments and the diversity of an area's segments is relevant to understanding each community's unique socioeconomic and demographic dynamics.Timmons Group conducted an analysis of three geographies showcased in this service. Enriched with 2020 population, 2025 population, and 2025 Dominate Tapestry Segment values are States, Counties, and 25 square mile transverse hex bins. ArcGIS Tapestry by Timmons Group v1 published on August 7, 2025. Contact brian.kingery@timmons.com for more information.
Crowdsource Manager is a configurable group app template that can be used for triaging crowd sourced data across multiple layers and maps as it is collected using applications such as Crowdsource Reporter or Collector. Using Crowdsource Manager, these reports can be reviewed and attributes such as assignment and status can be updated. Attachments and comments associated with each report are also accessible.Use CasesCrowdsource Manager can be configured for reviewing any crowd sourced information, including data collected through Crowdsource Reporter configurations such as these:citizen service requestshealth and safety reportscitizen science reportsdrone imagery reviewreviewing real estate property listingsConfigurable OptionsConfigure Crowdsource Manager to present a group of maps with editable layers, and personalize the app by modifying the following options: Display a custom title and logo in the application headerChoose a color schemeUse the map pop-up settings to specify which fields should be visible and which should be editableSupported DevicesThis application is responsively designed to support use in browsers on desktops and tablets..Data RequirementsCrowdsource Manager requires an ArcGIS Online group that contains at least one map with at least one editable feature layer.This web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a group and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.Learn MoreFor release notes and more information on configuring this app, see the Crowdsource Manager documentation.
This layer shows disability status by sex and age group. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the percentage of elderly (65+) with a disability. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B18101Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.
Maps and Apps Gallery is a configurable group app template that can be used for displaying a collection of maps, applications, documents, and layers. Gallery contents are searchable and can be filtered using item tags. Private gallery content can be accessed by signing in to the app using your ArcGIS credentials.Use Casesbuilding a common operational picture organizing a series of maps & apps for a community eventConfigurable OptionsConfigure Maps and Apps Gallery to present content from any group in your organization and personalize the app by modifying the following options: Display a custom title and logo in the application headerUse a custom color schemeChoose between grid- and list-style layoutsEnable or disable the tag cloud which can be used to filter the items displayed in the galleryChoose to open maps and layers in ArcGIS Online, or to preview them in the app's viewerSupported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsMaps and Apps Gallery will display all item types supported by ArcGIS Online and Portal, although sharing maps is preferable to sharing stand-alone layers.Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a group and choose to create a web appOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.Learn MoreFor release notes and more information on configuring this app, see the Maps and Apps Gallery documentation.
The establishment of a BES Multi-User Geodatabase (BES-MUG) allows for the storage, management, and distribution of geospatial data associated with the Baltimore Ecosystem Study. At present, BES data is distributed over the internet via the BES website. While having geospatial data available for download is a vast improvement over having the data housed at individual research institutions, it still suffers from some limitations. BES-MUG overcomes these limitations; improving the quality of the geospatial data available to BES researches, thereby leading to more informed decision-making.
BES-MUG builds on Environmental Systems Research Institute's (ESRI) ArcGIS and ArcSDE technology. ESRI was selected because its geospatial software offers robust capabilities. ArcGIS is implemented agency-wide within the USDA and is the predominant geospatial software package used by collaborating institutions.
Commercially available enterprise database packages (DB2, Oracle, SQL) provide an efficient means to store, manage, and share large datasets. However, standard database capabilities are limited with respect to geographic datasets because they lack the ability to deal with complex spatial relationships. By using ESRI's ArcSDE (Spatial Database Engine) in conjunction with database software, geospatial data can be handled much more effectively through the implementation of the Geodatabase model. Through ArcSDE and the Geodatabase model the database's capabilities are expanded, allowing for multiuser editing, intelligent feature types, and the establishment of rules and relationships. ArcSDE also allows users to connect to the database using ArcGIS software without being burdened by the intricacies of the database itself.
For an example of how BES-MUG will help improve the quality and timeless of BES geospatial data consider a census block group layer that is in need of updating. Rather than the researcher downloading the dataset, editing it, and resubmitting to through ORS, access rules will allow the authorized user to edit the dataset over the network. Established rules will ensure that the attribute and topological integrity is maintained, so that key fields are not left blank and that the block group boundaries stay within tract boundaries. Metadata will automatically be updated showing who edited the dataset and when they did in the event any questions arise.
Currently, a functioning prototype Multi-User Database has been developed for BES at the University of Vermont Spatial Analysis Lab, using Arc SDE and IBM's DB2 Enterprise Database as a back end architecture. This database, which is currently only accessible to those on the UVM campus network, will shortly be migrated to a Linux server where it will be accessible for database connections over the Internet. Passwords can then be handed out to all interested researchers on the project, who will be able to make a database connection through the Geographic Information Systems software interface on their desktop computer.
This database will include a very large number of thematic layers. Those layers are currently divided into biophysical, socio-economic and imagery categories. Biophysical includes data on topography, soils, forest cover, habitat areas, hydrology and toxics. Socio-economics includes political and administrative boundaries, transportation and infrastructure networks, property data, census data, household survey data, parks, protected areas, land use/land cover, zoning, public health and historic land use change. Imagery includes a variety of aerial and satellite imagery.
See the readme: http://96.56.36.108/geodatabase_SAL/readme.txt
See the file listing: http://96.56.36.108/geodatabase_SAL/diroutput.txt
Link to landing page referenced by identifier. Service Protocol: Link to landing page referenced by identifier. Link Function: information-- dc:identifier.
Youtube Channel that has various Videos using ArcGIS to teach Geography.
This layer was deprecated on 12/31The layer will still be publicly available, but no longer update. Information and links on how to access the new updated feature service in ArcGIS Marketplace will be posted here soonSafeGraph is just a data company. That's all we do.Social Distancing MetricsDue to the COVID-19 pandemic, people are currently engaging in social distancing. In order to understand what is actually occurring at a census block group level, SafeGraph is offering a temporary Social Distancing Metrics product. This product is delivered daily (3 days delayed from actual).The data was generated using a panel of GPS pings from anonymous mobile devices. We determine the common nighttime location of each mobile device over a 6 week period to a Geohash-7 granularity (~153m x ~153m). For ease of reference, we call this common nighttime location, the device's "home". We then aggregate the devices by home census block group and provide the metrics set out below for each census block group.To preserve privacy, we apply differential privacy to all of the device count metrics other than the device_count.SchemaColumn NameDescriptionTypeExampleorigin_census_block_groupThe unique 12-digit FIPS code for the Census Block Group. Please note that some CBGs have leading zeros.String131000000000date_range_startStart time for measurement period in ISO 8601 format of YYYY-MM-DDTHH:mm:SS±hh:mm (local time with offset from GMT). The start time will be 12 a.m. of any day.String2020-03-01T00:00:00-06:00date_range_endEnd time for measurement period in ISO 8601 format of YYYY-MM-DDTHH:mm:SS±hh:mm (local time with offset from GMT). The end time will be the following 12 a.m.String2020-03-02T00:00:00-06:00device_countNumber of devices seen in our panel during the date range whose home is in this census_block_group. Home is defined as the common nighttime location for the device over a 6 week period where nighttime is 6 pm - 7 am. Note that we do not include any census_block_groups where the count <5.Integer100distance_traveled_from_homeMedian distance traveled from the geohash-7 of the home by the devices included in the device_count during the time period (excluding any distances of 0). We first find the median for each device and then find the median for all of the devices.Integer200completely_home_device_countOut of the device_count, the number of devices which did not leave the geohash-7 in which their home is located during the time period.Integer40median_home_dwell_timeMedian dwell time at home geohash-7 ("home") in minutes for all devices in the device_count during the time period. For each device, we summed the observed minutes at home across the day (whether or not these were contiguous) to get the total minutes for each device. Then we calculate the median of all these devices.Integer1200part_time_work_behavior_devicesOut of the device_count, the number of devices that spent one period of between 3 and 6 hours at one location other than their geohash-7 home during the period of 8 am - 6 pm in local time. This does not include any device that spent 6 or more hours at a location other than home.Integer10full_time_work_behavior_devicesOut of the device_count, the number of devices that spent greater than 6 hours at a location other than their home geohash-7 during the period of 8 am - 6 pm in local time.Integer0For data definitions and complete documentation visit SafeGraph Developer and Data Scientist Docs.For statistics on the dataset, see SafeGraph Summary Statistics.Data is available as a hosted Feature Service to easily integrate with all ESRI products in the ArcGIS ecosystem.Want More? Want this POI data for use outside of ArcGIS Online? Want POI data for Canada? Want POI building footprints (Geometry)?Want more detailed category information (Core Places)?Want phone numbers or operating hours (Core Places)?Want POI visitor insights & foot-traffic data (Places Patterns)?To see more, preview & download all SafeGraph Places, Patterns, & Geometry data from SafeGraph’s Data Bar.Or drop us a line! Your data needs are our data delights. Contact: support-esri@safegraph.comView Terms of Use
This layer shows health insurance coverage by type and by age group. This is shown by tract, county, and state centroids. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the count and percent uninsured. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B27010 (Not all lines of this ACS table are available in this feature layer.)Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.
Learn, Reconnect, and Discover the latest advances in Geographic Information Systems (GIS) technology when the New Zealand Esri User Conference returns in-person. Join hundreds of users from around the New Zealand and the South Pacific to discover how they’re leveraging GIS capabilities to solve problems, create shared understanding, and map common ground.This year's 3-day event includes not-to-be-missed opportunities for training, networking and sharing your own stories and experiences.A 2-day option is available for those short on time, while a 4-day option includes discounted instructor-led training for migrating to ArcGIS Pro.
Crowdsource Reporter is a configurable group app template that can be used for submitting a variety of issues or observations in a single application. Reports can be submitted anonymously, by ArcGIS named users or Twitter users. The app can also be configured to support voting for and commenting on reports submitted by others.Use CasesCrowdsource Reporter can be configured to collect information for a wide variety of topics including:citizen service requestscommunity health and safety reportscitizen science reportsreporting damaged utility assetscollecting real estate property listingsConfigurable OptionsConfigure Crowdsource Reporter to present a group of maps with editable layers, and personalize the app by modifying the following options: Customize the splash screen with a background image, title, subtitle, and options for signing in to the appSet a theme color, icon, and app messaging that suit your organizationChoose to allow users to vote and/or comment on reportsSupported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsCrowdsource Reporter requires an ArcGIS Online group that contains at least one map with at least one editable feature layer. In addition, the following requirements must be met to expose full app functionality:To enable votes, this layer must have a numeric field for storing the number of votes on each featureTo collect comments, the feature layer must have a related tableTo allow authenticated users to track reports they have submitted, the layer must have a text field for storing a GUID associated with their accountTo allow users to submit supporting documents with the reports, the layer must support attachmentsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a group and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.Learn MoreFor release notes and more information on configuring this app, see the Crowdsource Reporter documentation.
SourceOID | The OBJECTID value of the source record in the source dataset providing the attribution. |
ABCDMisc | A FireCode used by USDA FS to track and compile cost information for emergency IA fire suppression on A, B, C & D size class fires on FS lands. |
ADSPermissionState | Indicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation. |
ContainmentDateTime | The date and time a wildfire was declared contained. |
ControlDateTime | The date and time a wildfire was declared under control. |
CreatedBySystem | ArcGIS Server Username of system that created the IRWIN Incident record. |
IncidentSize | Reported for a fire. The minimum size is 0.1. |
DiscoveryAcres | An estimate of acres burning when the fire is first reported by the first person to call in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands. |
DispatchCenterID | A unique identifier for a dispatch center responsible for supporting the incident. |
EstimatedCostToDate | The total estimated cost of the incident to date. |
FinalAcres | Reported final acreage of incident. |
FinalFireReportApprovedByTitle | The title of the person that approved the final fire report for the incident. |
FinalFireReportApprovedByUnit | NWCG Unit ID associated with the individual who approved the final report for the incident. |
FinalFireReportApprovedDate | The date that the final fire report was approved for the incident. |
FireBehaviorGeneral | A general category describing how the fire is currently reacting to the influences of fuel, weather, and topography. |
FireBehaviorGeneral1 | A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography). |
FireBehaviorGeneral2 | A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography). |
FireBehaviorGeneral3 | A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography). |
FireCause | Broad classification of the reason the fire occurred identified as human, natural or unknown. |
FireCauseGeneral | Agency 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. |
FireCauseSpecific | A 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. |
FireCode | A code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. |
FireDepartmentID | The 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. |
FireDiscoveryDateTime | The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes. |
FireMgmtComplexity | The highest management level utilized to manage a wildland fire event. |
FireOutDateTime | The date and time when a fire is declared out. |
FireStrategyConfinePercent | Indicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented. |
FireStrategyFullSuppPercent | Indicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented. |
FireStrategyMonitorPercent | Indicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented. |
FireStrategyPointZonePercent | Indicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented. |
FSJobCode | Specific to the Forest Service, code use to indicate the FS job accounting code for the incident. Usually displayed as 2 char prefix on FireCode. |
FSOverrideCode | Specific to the Forest Service, code used to indicate the FS override code for the incident. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used. |
GACC | "A code that identifies the wildland fire geographic area coordination center (GACC) at the point of origin for the incident. A GACC is a facility used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic area." |
ICS209ReportDateTime | The date and time of the latest approved ICS-209 report. |
ICS209ReportForTimePeriodFrom | The date and time of the beginning of the time period for the current ICS-209 submission. |
ICS209ReportForTimePeriodTo | The date and time of the end of the time period for the current ICS-209 submission. |
ICS209ReportStatus | The 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 multiple finals (as determined by business rules). |
IncidentManagementOrganization | The 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. |
IncidentName | The name assigned to an incident. |
IncidentShortDescription | General descriptive location of the incident such as the number of miles from an identifiable town. |
IncidentTypeCategory | The Event Category is a sub-group of the Event Kind code and description. The Event Category breaks down the Event Kind into more specific event categories. |
IncidentTypeKind | A general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community |
This guide will show the process of adding data to a group in ArcGIS Online. If you don't have a group set up click here to learn how to create a group and add members.