Deliverable Packaging, Metadata, and Professional Reporting

Why Deliverable Packaging Matters

A photogrammetric project is only as valuable as the package you hand to the client. Raw point clouds and unorganized image folders sitting on a hard drive serve no one. Professional deliverable packaging means every file is named correctly, every dataset carries complete metadata, and the client receives a written report they can read, archive, and defend in court or before a regulator. Employers in GIS, surveying, and drone operations judge competence in part by how well a technician organizes and documents work products. Sloppy packaging signals sloppy fieldwork, even when the data itself is sound.

Metadata: What It Is and Why You Must Include It

Metadata is structured information that describes a dataset—who made it, when, how, in what coordinate system, and how accurate it is. Without metadata, a raster or shapefile is an orphan: no one can evaluate whether it is fit for a given purpose.

Two widely used standards govern spatial metadata in the United States:

• FGDC Content Standard for Digital Geospatial Metadata (CSDGM): Developed by the Federal Geographic Data Committee, this standard defines required and optional elements for describing geospatial datasets. Federal agencies are required to follow it for publicly distributed data, and many state and local agencies adopt it as well.
• ISO 19115: An international standard for geographic information metadata. It is more modular than FGDC CSDGM and is increasingly used in enterprise GIS environments. Esri ArcGIS Pro supports ISO 19115 metadata authoring natively.

Key metadata fields you must populate for every photogrammetric deliverable:

| Field | What Goes There |

|---|---|

| Title | Short descriptive name of the dataset |

| Abstract | What the data represents, area covered, date |

| Lineage | How the data was collected and processed (sensor, software, GCP strategy) |

| Positional Accuracy | Horizontal and vertical RMSE from your accuracy assessment |

| Coordinate Reference System | Full CRS name plus EPSG code |

| Scale / Resolution | GSD for rasters; point spacing for point clouds |

| Contact Information | Organization, person, address, email |

| Date | Collection date and publication date |

Lineage is especially important in photogrammetry. It must describe the drone platform, camera, flight altitude, overlap percentages, number of GCPs and their collection method, processing software and version, and any filtering or editing steps applied to the output.

The Deliverable Package: Standard Components

A complete photogrammetric project deliverable typically includes:

1. Orthomosaic – GeoTIFF or similar, at the agreed GSD, in the project CRS.

2. Digital Elevation Model (DEM) or Digital Surface Model (DSM) – single-band raster, same CRS.

3. Contour file – vector (shapefile or GeoPackage), with interval matching contract requirements.

4. Point cloud – LAS or LAZ format, classified if required.

5. Accuracy report – tabular comparison of check points: known coordinates vs. derived coordinates, with computed RMSE values.

6. Metadata records – one per deliverable file, or a project-level record if accepted by the client.

7. Project summary report – written document described below.

File naming must follow whatever convention the contract specifies. When no convention is given, use a consistent scheme such as `ProjectName_YYYYMMDD_Product_CRS.ext` (e.g., `Riverside_20250410_Ortho_EPSG6432.tif`). Avoid spaces, special characters, and vague names like `final2` or `ortho_REAL`.

Folder structure should be logical: one parent folder per project, with subfolders for raw imagery, GCP files, processing outputs, deliverables, and reports. Version control matters: never overwrite a file without keeping the previous version in an archive subfolder.

The Professional Project Summary Report

The project summary report is a two-page client-facing document written in plain language. It must contain five sections:

1. Project Overview – location, purpose, survey dates, client name, and contract reference.

2. Equipment and Methods – drone make/model, camera specifications, flight parameters (altitude, overlap, GSD), GCP collection equipment and method, processing software.

3. Accuracy Results – horizontal and vertical RMSE from check points, number of check points used, whether results meet the contracted accuracy standard.

4. Deliverable Index – a table listing every file delivered, its format, coordinate system, and a one-line description.

5. Limitations and Recommendations – any conditions that affected data quality (weather, vegetation occlusion, moving objects), areas of reduced accuracy, and suggestions for future surveys.

Write for a technically informed but non-specialist audience. Avoid jargon without definition. State accuracy numbers clearly: "Horizontal RMSE: 0.03 m" is more useful than "the data looks accurate."

Professional and Safety Considerations

Deliverable packaging is a professional responsibility with legal implications. Survey data may be used for construction, legal boundary determination, or environmental compliance. Errors in metadata—especially wrong coordinate systems or falsified accuracy values—can cause physical harm or financial loss. Never populate an accuracy field with a value you did not actually compute from check points.

Data security is also a consideration. Client data should be stored on encrypted drives or secure servers, not left on personal devices or uploaded to unvetted cloud services without client approval. When delivering files electronically, use secure transfer methods.

For field-collected reference data that feeds into the deliverable (GCP measurements, control loops), ensure all field safety protocols followed during collection are noted in the lineage section—this creates a complete audit trail.