= Procedures =

These pages document established procedures for processing, data delivery, archiving, etc. Please be aware that these pages may be written in technical language as they are mainly used for documenting internal processing.

== Project processing procedure ==

This page contains links to detailed step-by-step instructions on how to deal with data from arrival to dispatch to the user. Please keep updated. A simplified overview of the procedures can be seen in the flow chart, with the more detailed, technical descriptions below.

[[Image(simple_overview.jpeg, align=center, margin=20, 800px)]]

=== Procedure ===

 1. [wiki:Procedures/NewDataArrival Unpacking data]
 1. [wiki:Procedures/ProcessingChainInstructions/NavigationProcessing Processing nav data]
 1. Processing
   1. [wiki:Procedures/EagleHawkProcessing Processing Eagle/Hawk data]
   1. [wiki:Processing/LeicaProcedure Processing LiDAR data]
   1. [wiki:Procedures/RCDPhotoProcessing Processing Leica's RCD digital camera data]
 1. [wiki:Procedures/DeliveryCreation Creating a delivery]
   1. [wiki:Procedures/EagleHawkProcessing#Makingadelivery Hyperspectral data]
   1. [wiki:Procedures/DeliveryCreation/LIDAR LIDAR data]
   1. [wiki:Procedures/RCDPhotoProcessing#DeliveryScript Photography data]
 1. Once the delivery has been created, it needs to be [wiki:Procedures/DeliveryChecking delivery checked]
 1. [wiki:Procedures/EndUserDelivery Dispatching to PI]
 1. Tidy the project. Get rid of any unnecessary files and make sure the directory and file names conform to the current standard (use proj_tidy.sh)
 1. (2010 and earlier) [wiki:Procedures/DeliveryCreation/rsync r-syncing from the workspace to the repository]
 1. [wiki:Procedures/NEODCDelivery Archiving at NEODC]

== Other procedures ==
 * [wiki:Procedures/NewAzgcorr How to update azgcorr and who to notify]
 * [wiki:Procedures/NewSeason What needs to be done prior to starting a new season]
 * [wiki:Procedures/UserSupport User support]