> For the complete documentation index, see [llms.txt](https://ess-dive.gitbook.io/uas-reporting-format/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ess-dive.gitbook.io/uas-reporting-format/overview.md). # Overview ## About the reporting format This reporting format provides metadata requirements and format guidelines for uploading data from small (≤ 25 kg) Unoccupied Aerial Systems (UASs) to the ESS-DIVE archive. This includes basic recording of core flight data (e.g. telemetry), when available, and primary flight metadata (e.g. flight location, flight paths, altitude, date, start/end time), basic UAS payload and instrumentation information (e.g. camera make and model), and the general data product and file metadata needed for interpreting and accessing derived UAS datasets (e.g. pixel resolution, spatial reference system). Templates are provided to enable rapid compilation of metadata. Data products are classfied into processing levels, and recommendations are given for file naming. ## Instructions See the [Instructions](/uas-reporting-format/instructions.md) for how to use the format.\ Parts 1-4 provide guidance and templates for metadata associated with the campaign, platform, flights and sensors. Part 5 describes examples of UAS data products classified as product Levels depending on the degree of processing. ## Updates in v1.0.1 In March 2025, a patch version of the UAS reporting format was made to improve the overall experience with the associated reporting format documentation. ## How to contribute Comments, questions and suggestions for improvement of this reporting format and documentation may be made by opening an [Issue](https://github.com/ess-dive-workspace/essdive-uas/issues). We also encourage contributors to make use of the [Discussions](https://github.com/ess-dive-workspace/essdive-uas/discussions). ## Recommended citation Ely KS; Yang D; Serbin SP (2023). ESS-DIVE Unoccupied Aerial Systems (UAS) Reporting Format v1. Environmental Systems Science Data Infrastructure for a Virtual Ecosystem (ESS-DIVE), ESS-DIVE repository. Dataset. doi:10.15485/2204420 ## Published examples Data packages using development versions of this reporting format are available for public access. Shawn Serbin, Dedi Yang, Andrew McMahon. 2021. Landscape-scale Characterization of Arctic Tundra Vegetation Composition, Structure, and Function with a Multi-sensor Unoccupied Aerial System: Supporting Data. Next Generation Ecosystem Experiments Arctic Data Collection, Oak Ridge National Laboratory, U.S. Department of Energy, Oak Ridge, Tennessee, USA. . Dedi Yang, Wouter Hanston, Daniel Hayes, Shawn Serbin. 2022. UAS remote sensing (DJI Phantom 4 RTK platform): RGB orthomosaic, digital surface and canopy height models, plant functional type map, Seward Peninsula, Alaska, 2019. Next Generation Ecosystem Experiments Arctic Data Collection, Oak Ridge National Laboratory, U.S. Department of Energy, Oak Ridge, Tennessee, USA. . ## Liscensing information This repository content is license for use under the [CC BY 4.0 license](https://creativecommons.org/licenses/by/4.0/) ## Funding and acknowledgments Funding for the development of the ESS-DIVE Unoccupied Aerial Systems (UAS) Reporting Format was provided by the U.S. Department of Energy, Office of Science, Office of Biological and Environmental Research, Climate and Environmental Science Division, Data Management program under contract number DE-AC02-05CH11231. We would like to acknowledge the following people for their contributions to the content and structure of this reporting format: Christian G. Andresen, Yose Angel, Adam Collins, Brett Feddersen, Sean Freeman, Peng Fu, Brian Greene, Wouter Hanston, Mark J. Lara, David LeBauer, Trina Merrick, Emily Robles, Alexey Shiklomanov, Matthias Siewert, Charaluka Varadharajan and Jin Wu. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://ess-dive.gitbook.io/uas-reporting-format/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.