Hosted Feature ServiceThe heart of the Idaho Trails Experience web app is the geographic data served by the Idaho Recreation Trails collection of Hosted Feature Layers. The Hosted service can be updated more frequently and on-the-fly than the previous technology used to maintain Idaho Trails-- changes now appear on the App and through the Feature Service in real time. The newest web presentation technology under AGOL, Experience Builder, served by this dataset, will make possible several extended features to come in future updates to the App.Under the hood Linear routes, closure routes and areas, and boundary area data are ported through a Web Map from the underlying Hosted Feature Layers. In addition to view settings for attributes popups set in the Web Map, additional visibility option not managed directly in the Hosted Feature data or controllable in the Web Map will be further processed in the Experience App presentation.Underlaying Classes in the Dataset: One single linear class "Idaho Routes" contains all road and trail features (59,000+ route segment features): Routes characterized as recreational in nature include "High Clearance" (previously "Jeep" treated as a road type, now as a full-width "trail" type): High-clearance, Special Vehicle Designation (mostly OHVs >50"), OHVs 50" and under, and single-track (each width class separated by seasonal and not); E-Bike; and, non-motorized and non-mechanized.Routes where vehicles either must be highway-legal (OHVs prohibited; typically paved roads), or routes requiring Restricted plate for legal OHV travel (mostly JURISDICTION = County); combined from previously-separate Layers: Highway-legal, Automobile, Other Roads (each with subcategories for seasonal access restrictions). (Note: Different route types are no longer kept in separate layers as with the legacy Map Service dataset. Route symbology, and selectable visibility will be filtered based on the value in the SYMBOL attribute from the above linear class within the Web Map and Experience-based App. If dynamically consuming the Feature Service, provisions will need to be made to filter to select visibility by road and trail types based on the value in the SYMBOL field.)"Points of Interest" (point type data) is comprised of a layer previously titled "Trailheads" and now includes the flexibility of other types of lat/lon point-based information such as links to external maps and "attractions" information such as site seeing destinations not previously included in IDPR's map presentation. "Emergency Route Closures" contains linear route Closures (overlays any route where a Closure Order applies in web map)"Area Restrictions" is added for areas such as defined by human exclusion Orders (polygon; usually planned annual human or vehicle exclusion areas, but can be emergency closure as well)Multiple "Boundary" polygon classes contain boundary outlines and attributes information for IDPR Regions (3), Counties (44), Wildernesses (42), National Forests and Ranger Districts (39), and BLM District and Field Offices (12), and BLM land units (700+). These separate classes reduce the data footprint of the Routes data and are joined in App popups by geographic Intersection logic. Bonus Material:Added to the web app are several optional, dynamic layers via publicly-available REST services selectable for visibility:NIFC Current and Historic Fire primetersIdaho Department of Lands- Lands Available for Recreational Use (visible by-default)Idaho Department of Fish & Game Hunting Units boundaries and numbers BLM Surface Management Agency layer for all local, state, and federal agencies which manage public lands (accessible, and not) US Forest Service Motor Vehicle Use Map, National Dataset (mirrors local MVUM paper and GeoPDF maps, where data available, lags local data when changes are made)National Park Service (NPS) Parks and Monuments areas and boundariesNOHRSC Snow Depth Other REST Services to be added based on utility in researching recreational accessThis dataset is published for the use of the individuals who fund this Program. Organizations wishing to consume this Feature Service into their own application should inquire to IDPR to obtain a use agreement and schema information to aid in development.AGOL Experience App here: https://experience.arcgis.com/experience/97a42a2a73c944ba918042faf518c689 Inquire to maps@idpr.idaho.gov

An ArcGIS Experience Builder app used by emergency management staff view dashboards for Individual and Public Assistance damage reports.

This National Shore Mark map aims to provide public access to fishing mark information through a map centric visualisation tool (ArcGIS Experience Builder) based on recreational fishing mark locations previously collated by IFI.Shore marks data are being collected on an ongoing basis. The original source of name, location and description is taken from an IFI internal department with all other data being taken from the IMREC project. Supplementary layers included in this map are provided by INFOMAR. Contains Irish Public Sector Data (Geological Survey Ireland & Marine Institute) licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. .hidden { display: none }

2023 Updates to the National Incident Feature Service and Event Geodatabase For 2023, there are no schema updates and no major changes to GeoOps or the GISS Workflow! This is a conscious choice and is intended to provide a needed break for both users and administrators. Over the last 5 years, nearly every aspect of the GISS position has seen a major overhaul and while the advancements have been overwhelmingly positive, many of us are experiencing change fatigue. This is not to say there is no room for improvement. Many great suggestions were received throughout the season and in the GISS Survey, and they will be considered for inclusion in 2024. That there are no critical updates necessary also indicates that we have reached a level of maturity with the current state, and that is good news for everyone. Please continue to submit your ideas; they are appreciated and valuable insight, even if the change is not implemented. For information on 2023 AGOL updates please see the NWCG page. There are three smaller changes worth noting this year: Standard Symbology is now the default on the NIFS For most workflows, the update will be seamless. All the Event Standard symbols are now supported in Field Maps and Map Viewer. Most users will now see the same symbols in all print and digital products. However, in AGOL some web apps do not support the complex line symbols. The simplified lines will still be present in the official Editing Apps (Operations, SITL, and GISS), and any custom apps built with the Web App Builder (WAB) interface. Experience Builder can be used for any new app creation. If you must use WAB or another app that cannot display the complex line symbology in the NIFS, please contact wildfireresponse@firenet.gov for guidance. Event Line now has Preconfigured Labels Labels on Event Line have historically been uncommon, but to speed their implementation when necessary, color-coded labels classes have been added to the NIFS and the lyrx files provided in the GIS Folder Structure. They can be disabled or modified as needed, should they interfere with any of your workflows. “Restricted” Folder added to GeoOps Folder Structure At the base level within the 2023_Template, a ‘restricted’ folder is now included. This folder should be used for all data and products that contain sensitive, restricted, or controlled-unclassified information. This will aid the DOCL and any future FOIA liaisons in protecting this information. When using OneDrive, this folder can optionally be password protected. Reminder: Sensitive Data is not allowed to be hosted within the NIFC Org.

Use this app to explore and visualise native title data, supporting the Native Title Act 1993 (Cth). About the data in this appCustodial geospatial data held by the National Native Title Tribunal (NNTT) consists of those datasets necessary to contribute to the statutory functions associated with Registers and other information, in support of the Native Title Act 1993 (Cth).Whilst these datasets do not form part of the statutory registers, they enable the visualisation and ability to search on these matters.For more information, see Native Title.Key featuresInteractive map: Zoom and pan in the interactive map to explore native title data. Layer control: Toggle between various map layers to customise your viewing experience. Add data: Add data to create your own custom map. Export: Export map views and native title data in various formats for your research. CurrencyModification frequency: As needed, refer to the Native Title dataset for details.ContactDigital Atlas of AustraliaChangelog Version 1.1.0 (2025-06-19)

Minor content changes Retitled app. Previous title: Native title

Version 1.0.0 (2024-08-23) ArcGIS Experience Builder app configured with the following: Native Title mapLocation search and other location toolsMap creation tools, such as map base map, add data and map layersLegendDrawing and measure toolsAnalysis tools, such as table and selectPrintHelp

This is the complete list of Adopt-A-Spot sites for CCS's Keep Dallas Beautiful program. This layer is used by the CCS/KDB team to edit and update the information displayed on the public-facing app. It allows staff to efficiently manage and track adopted sites across the city, ensuring that the public app reflects the most current and accurate data.Through this layer, the team can make real-time updates to area statuses and improve the program’s accessibility and functionality for community members. This tool is crucial for maintaining an up-to-date database, supporting the ongoing success of the Adopt-A-Spot program, and fostering community involvement in keeping Dallas clean and beautiful. Used in this Experience Builder App where it is updated by this Survey123 surveyAppears on this web map Updated (8/20/2025)

This data supports the identification of Virginia’s environmental justice communities with additional layers available on the Virginia EJScreen+ Experience Builder for community outreach purposes such as public meetings. It is intended for use by DEQ staff, partner agencies, environmental justice and community leaders, the regulated community, and the public.Click Here to view Data Fact Sheet