Skip to main content

Full Strip Delivery

When Vantor optionally delivers a full EO image strip, the data is placed in S3 in addition to the standard detection results and image chips. This can occur for tip-based collections (when deliverFullStrip is set to true in a tip's exploitation section) as well as for watchbox-triggered collections where full-strip delivery has been configured.

Availability of a full strip is announced by a Full_Strip_Available callback, whose details.deliveryManifestUrl points to a delivery manifest listing every file in the delivery.

What a full-strip delivery contains​

A full strip is not delivered as a single image. Because a collected strip can be very large, it is split into a grid of square GeoTIFF tiles that together cover the full strip footprint. Each delivery is written to a single full_strip_<uuid>/ S3 folder and contains two types of files:

  • strip.geojson (purpose: strip_metadata)

    • A single GeoJSON metadata file describing the overall strip
    • Includes the strip's footprint geometry, collection vehicle, datetime, cloud cover, and GSD
    • See Payload of strip.geojson file for the full schema

  • granule_<inventory_id>_R<row_index>_C<column_index>.tif (purpose: eo_full_strip_tile)

    • One GeoTIFF file per grid tile of the image
    • There is one such file per occupied tile in the row/column grid
Full strips are S3-only

Full-strip deliveries do not appear in the Maritime Sentry Application (MSA); they exist only in S3. For the exact S3 bucket and path conventions for both standard and custom-bucket delivery, see Data Delivery.

Tile naming and the grid​

Tiles are gridded by row and column. The filename pattern is:

granule_<inventory_id>_R<row_index>_C<column_index>.tif

For example, the first tile of inventory 1050010038B31700 is:

granule_1050010038B31700_R1_C1.tif

The complete set of tiles forms a regular grid, so a client can reconstruct the full image (or locate a specific region of interest) from the row/column indices. All tiles for a delivery are placed under a single full_strip_<uuid>/ folder; see Data Delivery for the full S3 path for both standard and custom-bucket deliveries.

Example: delivery manifest for a full strip​

The delivery manifest enumerates the metadata file and each tile, with a downloadUrl and fileSizeBytes for each. An abbreviated example:

{
  "deliveryDetails": {
    "manifestId": "20240202T122809_abcd-1234",
    "manifestGenerationDatetime": "2024-02-02T12:28:09Z",
    "customer": "vantor-customer",
    "mission": "vantor-customer",
    "tipIdentifier": "abcd-1234",
    "inventoryIdentifier": "1050010038B31700"
  },
  "files": [
    {
      "purpose": "strip_metadata",
      "filename": "strip.geojson",
      "downloadUrl": "https://d1234567890.cloudfront.net/1050010038B31700/full_strip_abcd-1234/strip.geojson",
      "fileSizeBytes": 1372
    },
    {
      "purpose": "eo_full_strip_tile",
      "filename": "granule_1050010038B31700_R1_C1.tif",
      "downloadUrl": "https://d1234567890.cloudfront.net/1050010038B31700/full_strip_abcd-1234/granule_1050010038B31700_R1_C1.tif",
      "fileSizeBytes": 20448384
    }
  ]
}

See Payload of a delivery manifest file for the full manifest schema and the complete list of file purpose values.