This is a training dataset for the ArcGIS Collector application. This training will be held August 24, 2017.

This database was designed in response to the Director Memorandum - "Effective January 1, 2019 all structure greater than 120 square feet in the State Responsibility Area (SRA) damaged by wildfire will be inspected and documented in the DINS Collector App."To document and structure damaged or destroyed by the Oak wildland fire open the associated Field Map app.NOTE - this feature service is configured to not allow record deletion. If a record needs to be deleted contact the program manager below.This is the schema developed and used by the CAL FIRE Office of State Fire Marshal to assess and record structure damage on wildland fire incidents. The schema is designed to be configured in the Esri Collector/Field Maps app for data collection during or after an incident.

This database was designed in response to the Director Memorandum - "Effective January 1, 2019 all structure greater than 120 square feet in the State Responsibility Area (SRA) damaged by wildfire will be inspected and documented in the DINS Collector App."To document structures damaged or destroyed by the 2023 Pineapple Express flooding in Monterey County open the associated Field Map app.NOTE - this feature service is configured to not allow record deletion. If a record needs to be deleted contact the program manager below.This is the schema developed and used by the CAL FIRE Office of State Fire Marshal to assess and record structure damage on flooding incidents. The schema is designed to be configured in the Esri Collector/Field Maps app for data collection during or after an incident.

This database was designed in response to the Director Memorandum - "Effective January 1, 2019 all structure greater than 120 square feet in the State Responsibility Area (SRA) damaged by wildfire will be inspected and documented in the DINS Collector App."To document and structure damaged or destroyed by the Mosquito wildland fire open the associated Field Map app.NOTE - this feature service is configured to not allow record deletion. If a record needs to be deleted contact the program manager below.This is the schema developed and used by the CAL FIRE Office of State Fire Marshal to assess and record structure damage on wildland fire incidents. The schema is designed to be configured in the Esri Collector/Field Maps app for data collection during or after an incident.

This database was designed in response to the Director Memorandum - "Effective January 1, 2019 all structure greater than 120 square feet in the State Responsibility Area (SRA) damaged by wildfire will be inspected and documented in the DINS Collector App."To document and structure damaged or destroyed by the 2023 Tulare Flooding Incident open the associated Field Map app.NOTE - this feature service is configured to not allow record deletion. If a record needs to be deleted contact the program manager below.This is the schema developed and used by the CAL FIRE Office of State Fire Marshal to assess and record structure damage on flooding incidents. The schema is designed to be configured in the Esri Collector/Field Maps app for data collection during or after an incident.

This database was designed in response to the Director Memorandum - "Effective January 1, 2019 all structure greater than 120 square feet in the State Responsibility Area (SRA) damaged by wildfire will be inspected and documented in the DINS Collector App."To document and structure damaged or destroyed by the Mill wildland fire open the associated Field Map app.NOTE - this feature service is configured to not allow record deletion. If a record needs to be deleted contact the program manager below.This is the schema developed and used by the CAL FIRE Office of State Fire Marshal to assess and record structure damage on wildland fire incidents. The schema is designed to be configured in the Esri Collector/Field Maps app for data collection during or after an incident.

This database was designed in response to the Director Memorandum - "Effective January 1, 2019 all structure greater than 120 square feet in the State Responsibility Area (SRA) damaged by wildfire will be inspected and documented in the DINS Collector App."To document and structure damaged or destroyed by the McKinney wildland fire open the associated Field Map app.NOTE - this feature service is configured to not allow record deletion. If a record needs to be deleted contact the program manager below.This is the schema developed and used by the CAL FIRE Office of State Fire Marshal to assess and record structure damage on wildland fire incidents. The schema is designed to be configured in the Esri Collector/Field Maps app for data collection during or after an incident.

This is a dataset of location and photo data for the debris flow deposits measured in the Tadpole Wildfire. The data were collected using the ArcGIS Collector application by multiple individuals. The original data are stored in a geodatabase here, and the geodatabase has the following fields: Latitude (decimal degrees), Longitude (decimal degrees), Elevation (meters), GlobalID (a unique ID), CreationDate, Creator, EditDate, Editor, and Notes. Each point in the geodatabase represents an observation (either a debris flow deposit or a wood measurement), and most points also include associated photos of the deposit/wood. An opensource version of the geodatabase is provided as a shapefile, containing the same fields mentioned above. The photos associated with each point are in a separate folder in this data release, and the file called photo_table.csv contains the GlobalIDs and photo names that correspond to each location in the shapefile.

This database was designed in response to the Director Memorandum - "Effective January 1, 2019 all structure greater than 120 square feet in the State Responsibility Area (SRA) damaged by wildfire will be inspected and documented in the DINS Collector App."To document and structure damaged or destroyed by the Mosquito wildland fire open the associated Field Map app.NOTE - this feature service is configured to not allow record deletion. If a record needs to be deleted contact the program manager below.This is the schema developed and used by the CAL FIRE Office of State Fire Marshal to assess and record structure damage on wildland fire incidents. The schema is designed to be configured in the Esri Collector/Field Maps app for data collection during or after an incident.

Additional fields such as Category and Structure Type are based off of fields needed in the Incident Status Summary (ICS 209).

This data set contains the trails data that is published for public consumption. It includes hiking, biking, and multi-use trails in Lake County, plus several connecting trails in surrounding counties. Data identifies the location of the trails, the trail name, surface type, trail use, its status within the county's Trails Master Plan, and other details.Local Lake County data is collected in the field using the Collector app. Data from other sources - including FWC, and other counties - was received from those sources with no additional checking. Data is updated as needed and new trails are added as acquired.Contact Lake County Office of Parks and Trails for additional details.

Bird surveys are completed once a month by Cheadle Center staff and associates. Each survey starts 45 minutes after sunrise and lasts about 2 hours. The survey has at least 4 experienced birders- 2 that survey the eastern side and 2 that survey the western route (exact routes can be found on ArcGIS online). Surveyors use a combination of binoculars, scopes, and listening for calls to identify species. A point is placed on the map to the best accuracy possible using the ArcGIS app field maps or collector. The survey is also set up to record the surveyors' location every 30 seconds as a way to track the survey route. When there are large groups of birds, 10 or more, an approximate number is decided between the two surveyors. If a bird is seen multiple times along the route, it is labeled a repeat. The two groups met up after the survey and discussed what was seen. Any birds that are expected to be a repeat were changed to note that they were a repeat within the dataset. Environmental data..., Each survey starts 45 minutes after sunrise, and lasts about 2 hours. The survey has at least 4 experienced birders- 2 that survey the eastern side and 2 that survey the western route (exact routes can be found on ArcGIS online). Surveyors use a combination of binoculars, scopes and listening for calls to identify species. A point is placed on the map to the best accuracy possible using the ArcGIS app field maps or collector. The survey is also set up to record the surveyors location every 30 seconds as a way to track the survey route. When there are large groups of birds 10 or more an approximate number is decided between the two surveyors. If a bird is seen multiple times along the route it is labeled as a repeat., , # North Campus Open Space (NCOS) Monthly Bird Survey Data (2017-2023)

https://doi.org/10.5061/dryad.bvq83bkhz

A thorough data description can be found at https://escholarship.org/uc/ccber_data_descriptions

Description of the data and file structure

The data consists of only one .csv file. The following describes each column of data

1. Observation.Date: Date at which the survey was completed.
2. Year: Calendar year that the survey was completed.
3. Species: Species identification common name
4. General.Type:Â Classification of bird type including the following types: 'Comorants', 'Gulls & Terns', 'Herons, Egrets, Ibis', 'Hummingbirds', 'Insectivores- Aerial', 'Insectivores- Terrestrial', 'Kingfisher', 'Omnivores', 'Seed & Fruit Eaters', 'Shorebirds', 'Wardblers', 'Waterfowl & Friends'
5. eBird.Group: More detailed classification of bird types including the following type...

Public Trash Cans Map was created to have a inventory of the trash cans in the City of Harrisburg. The Public Trash Cans Hosted Feature layer is the primary dataset in this map. Data was collected using ArcGIS Collector Field Application on an Iphone. Photos were taken of each public trash can and are visible as a link in the item pop-up. Questions regarding this dataset can be forwarded to the GIS Administrator (Evan Rubin), John Rarig or Chris Nafe. Data does not include:Temporary trash barrels primarily located in the City Parks.Trash containers at bus stops or parking garagesTrash containers in the Capitol Park Complex Map Created by Evan Rubin - Aug 26th 2021Uses: Public Trash Cans Hosted Feature Layer

This layer represents DCR playgrounds and playground equipment. Both layers work together to provide an inventory of the current DCR playgrounds that are open to public use. Conditions can change rapidly so this is just a snapshot in time.This dataset has 2 nested sets of features: Data A: Playgrounds- Each point represents the approximate center of a DCR playground. - Attributes describe the playground as a whole, including access, fencing, parking, amenities etc. - Picture attachments visualize each playground. Attributes:AssocDCRfac: DCR facility with which this Playground is associated. PG_name: Name of Playground.Town: Town or City this Playground is in. SqFootage: approximate area of Playground (square feet).BikeRack: Availability of a bike rack.FacilityLighting: If the playground is illuminated for the dark.PredomMat: Predominant surface material of the ground covered by the Playground.PathSurf: Surface of any paths between equipment on this Playground.ADAparking: Availability of Accessivle parking.FenceType: Type of fence (if any).FenceHtEst: Height of fence (in feet).TablesNumber: Count of tables.TablesPredMat: Material of tables.BenchesNumber: Count of benches.BenchesPredMat: Predominant material of benches.ShadeNatural: Availability of Natural shade.ShadeBuilt: Availability of Built shade.TrashRecNum: Count of trash receptacles.TrashRecType: Type of trash receptacles.RecyclingNum: Count of Recycling receptacles (if any).InspDate: Date when the data was last updated.Address: The nearest address, for navigation.Data B: equipment - Each point represents an individual play equipment in the playground point in Data A (above). So each Data A point must have at least one point in Data B. Most playgrounds have many play structures and thus, multiple Data B points. - Attributes describe the play equipment according to it's component pieces. - Picture attachments visualize each piece of equipment. The Visit_date field for each record/playground indicates when the dataset was last updated and thus, is an indicator of the currentness of this data. The actual condition of the playground can change fast and render observations outdated.Attributes:PG_name: Name of PlaygroundEquipNum: An ID number for the Equipment that is unique to this playground.PredomMat: Predominant material of equipment.PlayAgeGrp: Intended age group for play.SurfaceMat: Material of surface under each equipment.Seesaw: Count of this kind of equipment in this structure. Oscillate: Same as above.Climber: Same as above.HorizOverhd: Same as above.BalanceFeat: Same as above.SandFeat: Same as above.SpringCoil: Same as above.Deck: Same as above.Swing: Same as above.Roof: Same as above.InteractPanel: Same as above.Bridge: Same as above.AcousElem: Same as above.OpenSlide: Same as above.TubeSlide: Same as above.CrawlTunnel: Same as above.Other: Count of any playground component not listed.InspDate: Date when the data was last updated.The 2 datasets are linked by the field: pg_name Item type:This public, non-editable View is based on the Hosted Feature layer, DCR Playgrounds(editable).Source:Ongoing updates: DCR Playgrounds manager. Created: from fieldwork conducted by Warner Larson Landscape Architects in 2016. A professional playground inspector was part of the team. Commissioned by DCR to be used for management and planning. Field data collection with the ESRI Collector app on smart tablets (iPad minis) using web-maps created by DCR GIS. Please note:This layer contains data that changes frequently and may need to be updated.

PLEASE NOTE: This data product is not available in Shapefile format or KML at https://naturalengland-defra.opendata.arcgis.com/datasets/Defra::living-england-habitat-map-phase-4/about, as the data exceeds the limits of these formats. Please select an alternative download format.This data product is also available for download in multiple formats via the Defra Data Services Platform at https://environment.data.gov.uk/explore/4aa716ce-f6af-454c-8ba2-833ebc1bde96?download=true.The Living England project, led by Natural England, is a multi-year programme delivering a satellite-derived national habitat layer in support of the Environmental Land Management (ELM) System and the Natural Capital and Ecosystem Assessment (NCEA) Pilot. The project uses a machine learning approach to image classification, developed under the Defra Living Maps project (SD1705 – Kilcoyne et al., 2017). The method first clusters homogeneous areas of habitat into segments, then assigns each segment to a defined list of habitat classes using Random Forest (a machine learning algorithm). The habitat probability map displays modelled likely broad habitat classifications, trained on field surveys and earth observation data from 2021 as well as historic data layers. This map is an output from Phase IV of the Living England project, with future work in Phase V (2022-23) intending to standardise the methodology and Phase VI (2023-24) to implement the agreed standardised methods.The Living England habitat probability map will provide high-accuracy, spatially consistent data for a range of Defra policy delivery needs (e.g. 25YEP indicators and Environment Bill target reporting Natural capital accounting, Nature Strategy, ELM) as well as external users. As a probability map, it allows the extrapolation of data to areas that we do not have data. These data will also support better local and national decision making, policy development and evaluation, especially in areas where other forms of evidence are unavailable. Process Description: A number of data layers are used to inform the model to provide a habitat probability map of England. The main sources layers are Sentinel-2 and Sentinel-1 satellite data from the ESA Copericus programme. Additional datasets were incorporated into the model (as detailed below) to aid the segmentation and classification of specific habitat classes. Datasets used:Agri-Environment Higher Level Stewardship (HLS) Monitoring, British Geological Survey Bedrock Mapping 1:50k, Coastal Dune Geomatics Mapping Ground Truthing, Crop Map of England (RPA), Dark Peak Bog State Survey, Desktop Validation and Manual Points, EA Integrated Height Model 10m, EA Saltmarsh Zonation and Extent, Field Unit NEFU, Living England Collector App NEFU/EES, Long Term Monitoring Network (LTMN), Lowland Heathland Survey, National Forest Inventory (NFI), National Grassland Survey, National Plant Monitoring Scheme, NEFU Surveys, Northumberland Border Mires, OS Vector Map District , Priority Habitats Inventory (PHI) B Button, European Space Agency (ESA) Sentinel-1 and Sentinel-2 , Space2 Eye Lens: Ainsdale NNR, Space2 Eye Lens: State of the Bog Bowland Survey, Space2 Eye Lens: State of the Bog Dark Peak Condition Survey, Space2 Eye Lens: State of the Bog (MMU) Mountain Hare Habitat Survey Dark Peak, Uplands Inventory, West Pennines Designation NVC Survey, Wetland Inventories, WorldClim - Global Climate DataFull metadata can be viewed on data.gov.uk.

Points features of river access locations (kayak and canoe paddling trail inputs and take-outs) along SARA Mission Reach project. Data created and field-verified (using ESRI Collector App) October 2014.

Points features of pavilion locations at SARA Mission Reach project.Data interpreted from 2014 Google 6" orthoimagery (received through Bexar Metro 9-1-1 Network District acquisition). Data created and field-verified (using ESRI Collector App) October 2014.

This application provides an overview of the CUSEC Safety Assessment templates available, including the Safety Assessment Collector and Geoform apps for field reporting, and the Ops Dashboard view for visualizing the safety assessments from the field.For more information, contact cusec@cusec.org.

This data set contains the trails data that is published for public consumption. It includes hiking, biking, and multi-use trails in Lake County, plus several connecting trails in surrounding counties. Data identifies the location of the trails, the trail name, surface type, trail use, its status within the county's Trails Master Plan, and other details.Local Lake County data is collected in the field using the Collector app. Data from other sources - including FWC, and other counties - was received from those sources with no additional checking. Data is updated as needed and new trails are added as acquired.Contact Lake County Office of Parks and Trails for additional details.

This dataset represents the location of mile markers along trails in Lake County. The data was collected using GPS units and the Collector app. Latitude/Longitude coordinates are in decimal degrees.Currently markers only exist along the South Lake Trail. Others will be added as they become available.Contact Lake County Office of Parks and Trails for additional details.