FGDC Metadata

Project level metadata for each deliverable product must be created. Metadata must be delivered that fully comply with FGDC metadata format standard in eXtensible Markup Language (XML) format. Metadata must contain the following information:

(1) Collection Report detailing mission planning and flight logs

(2) Survey Report detailing the collection of ground control and reference points used for both data calibration and QA/QC accuracy assessments.

(3) Processing Report detailing LiDAR calibration, LiDAR classification, and product generation procedures including methodology used for breakline collection and hydro-flattening.

(4) QA/QC Reports detailing the analysis, accuracy assessment and validation of the point data (absolute, within swath, and between swath); the bare-earth surface (absolute); and other optional deliverables as appropriate

(5) Control and Calibration points: All control and reference points used to calibrate, control, process and validate the LiDAR point data or any derivative products will be delivered.

(6) Geo-referenced, digital spatial representation of the precise extents of each delivereddataset. This should reflect the extents of the actual LiDAR source or derived product data, exclusive of Triangular Irregular Network (TIN) artifacts or raster NODATA areas. A union of tile boundaries or minimum bounding rectangle is not acceptable. ESRI Polygon shapefile is usually preferred.

(7) All metadata files must contain sufficient content to fully detail all procedures used fordata processing, QAQC, and finalization.