Skip to content
English
Solution Suite
  • There are no suggestions because the search field is empty.

(HRI/CRI) File Specification

Each release contains the same set of files and each file follows the same naming conventions, which indicate the event ID, release, name and release number.

Naming Convention

< ICEYE_WIND > < #### > < STORM TYPE > < STORM NAME > < DELIVERABLE TYPE > < R# > . < FILETYPE >

US example (Hurricane Otis):

  • Building Damage Classification: ICEYE_WIND-0000_hurricane_otis_building_damage_R4.gpkg
  • Raster Damage Heatmap: ICEYE_WIND-0000_hurricane_otis_damage_raster_R4.tif
  • Vector Hexgrid Damage Heatmap: ICEYE_WIND-0000_hurricane_otis_damage_vector_hexgrid_R4.gpkg
  • Release notes: ICEYE_WIND-0000_hurricane_otis_release_notes_R4.gpkg
  • Metadata: ICEYE_WIND-0000_hurricane_otis_metadata_R4.json

Australia example (Tropical Cyclone Alfred):

  • Building Classification Layer: ICEYE_WIND-2812_tropical_cyclone_alfred_building_damage_R4.gpkg
  • Raster Damage Heatmap: ICEYE_WIND-2812_tropical_cyclone_alfred_damage_raster_R4.tif
  • Vector Hexgrid Damage Heatmap: ICEYE_WIND-2812_tropical_cyclone_alfred_damage_vector_hexgrid_R4.gpkg
  • Release notes: ICEYE_WIND-2812_tropical_cyclone_alfred_release_notes_R4.gpkg
  • Metadata: ICEYE_WIND-2812_tropical_cyclone_alfred_metadata_R4.json

Note: For ease of future updates ICEYE advises not to hardcode naming conventions in delivery integrations.

Files in this release (links to child articles below):