Overview: This document is a reference guide for users of the SAR Field Data Collection Form User Guide. The purpose is to provide a better understanding of how to use the form in the field.
The underlying technology used with this form is likely to evolve and change over time, therefore technical user guides will be provided as appendices to this document.
Background: The SAR Field Data Collection Form was created by an interdisciplinary group of first responders, decision-makers and technology specialists from across Federal, State, and Local Urban Search and Rescue Teams – the NAPSG Foundation SAR Working Group. If you have any questions or concerns regarding this document and associated materials, please send a note to comments@publicsafetygis.org.
Purpose: The SAR Field Data Collection Form is intended to provide a standardized approach to the collection of information during disaster response alongside resource management and tracking of assets.The primary goal of this approach is to obtain situational awareness (where, when, what) for SAR Teams in the field across four relevant themes: Victims that may need assistance or have already been helped. Hazards that must be avoided or mitigated. Damage that have been rapidly assessed for damage, when time and the mission permits. Other mission critical intelligence that vary based on mission type. The secondary goal of this approach is to provide essential elements of information to those not currently on-scene of the disaster. Using the themes above, information and maps can be shared based on “need to know”. If you are a technology specialist looking to deploy this application on your own see the Deployment Kit.
Location of topographic low confidence areas.
This table is used for tracking areas of low confidence in topographic data, whether it be LiDAR, photogrammetry or IFSAR, as a required in the Data Capture Standards Technical Reference. The spatial entities representing topographic low confidence areas are polygons. The spatial information contains the bounding polygon for each topographic low confidence area, matching the full extents of the corresponding S_Submittal_Info terrain submittal record.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
The Prince of Wales Existing Vegetation mapping project encompasses over 4.2 million acres of Southeastern Alaska—2.3 million of which are terrestrial. This map was designed to be consistent with the standards established in the Existing Vegetation Classification and Technical Guide (Nelson et al. 2015), and to provide baseline information to support project planning and inform land management of the Prince of Wales and surrounding islands. The final map comprises seven distinct, integrated feature layers: 1) vegetation type; 2) tree canopy cover; 3) trees per acre (TPA) for trees ≥ 1’ tall; 4) trees per acre for trees ≥ 6” diameter at breast height (dbh); 5) quadratic mean diameter (QMD) for trees ≥ 2” dbh; 6) quadratic mean diameter for trees ≥ 9” dbh; and 7) thematic tree size. The dominance type map consists of 18 classes, including 15 vegetation classes and 3 other land cover types. Continuous tree canopy cover, TPA, QMD, and thematic tree size was developed for areas classified as forest on the final vegetation type map layer. Geospatial data, including remotely sensed imagery, topographic data, and climate information, were assembled to classify vegetation and produce the maps. A semi-automated image segmentation process was used to develop the modeling units (mapping polygons), which delineate homogeneous areas of land cover. Field plots containing thematic vegetation type and tree size information were used as reference for random forest prediction models. Important model drivers included 30 cm orthoimagery collected during the height of the 2019 growing season, in addition to Sentinel 2 and Landsat 8 satellite imagery, for vegetation type prediction. Additionally, detailed tree inventory data were collected at precise field locations to develop forest metrics for Quality Level 1 (QL1) Light Detection and Ranging (LiDAR) data. LiDAR information was acquired across approximately 80% of the project’s land area. Continuous tree canopy cover and 2nd order forest metrics (TPA and QMD) were modeled across the LiDAR coverage area, and subsequently, extrapolated to the full project extent using Interferometric Synthetic Aperture Radar (IfSAR) as the primary topographic data source.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Overview: This document is a reference guide for users of the SAR Field Data Collection Form User Guide. The purpose is to provide a better understanding of how to use the form in the field.
The underlying technology used with this form is likely to evolve and change over time, therefore technical user guides will be provided as appendices to this document.
Background: The SAR Field Data Collection Form was created by an interdisciplinary group of first responders, decision-makers and technology specialists from across Federal, State, and Local Urban Search and Rescue Teams – the NAPSG Foundation SAR Working Group. If you have any questions or concerns regarding this document and associated materials, please send a note to comments@publicsafetygis.org.
Purpose: The SAR Field Data Collection Form is intended to provide a standardized approach to the collection of information during disaster response alongside resource management and tracking of assets.The primary goal of this approach is to obtain situational awareness (where, when, what) for SAR Teams in the field across four relevant themes: Victims that may need assistance or have already been helped. Hazards that must be avoided or mitigated. Damage that have been rapidly assessed for damage, when time and the mission permits. Other mission critical intelligence that vary based on mission type. The secondary goal of this approach is to provide essential elements of information to those not currently on-scene of the disaster. Using the themes above, information and maps can be shared based on “need to know”. If you are a technology specialist looking to deploy this application on your own see the Deployment Kit.