Imagery - Discrete layers BL

[ssharon-rnd]

• The system shall ingest discrete layers from external systems.

• The system shall create a discrete layer entity from the ingested metadata. -- For each image uploaded as part of the discrete layer the system shall build a pyramid tiif

• The system shall expose: -- 1. API for layer upload -- 2. API for tile streaming -- 3. API for CRUD operation for metadata -- 4. Query API for searching imagery data by Metadata fields -- 5. API to send discrete layers to best process (fusion api wrappers) -- 6. API to Export layers. Export shall support standard GDAL formats. -- 7. API to Export as Geo package. see epic

• The system shall

• • Validate metadata
• • Support S3 storage and file system
• • Support permissions, authentication and auditing

• The system shall have a UI to control all the server side APIs.

Layer metadata

• id string [guid] Mandatory
  • creationTime [dateTime] Mandatory
• imagingTime [dataTime] Mandatory
• resolution [double] Mandatory
• footprint [geoJson] Mandatory
• imageSection [string] Mandatory for example north/south/etc
• imageUri [string] Mandatory
• height [int] Mandatory
• width [int] Mandatory
• sensorType [Enum] Mandatory values VIS/RGB/Pan_Sharpen
• imageColorType [Enum] Mandatory values Color/BW
• imageBitPerPixel [int]
• imageFormat [string] values j2k/jpg/tiff
• isBitSigned [bool]
• imageSource [string] layer’s creator
• cloudCoverPrecentage [int] [%]
• additionalFilesUri [string] array of file locations
• geographicReferenceSystem

TBDs:

support storing Additional files ??

[ssharon-rnd]

@shaziri look at the metadata taken from Mazit

[ssharon-rnd]

@alebinson look here is the meatadata

[ssharon-rnd]

@asafMasa @CL-SHLOMIKONCHA please look at the ingest flow added