Add validation rules for input rasters

[soaressgabriel]

Checklist

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Added tests for changed code.
• Updated documentation for changed code.

Description

• Added the following rules in RasterDataRules enum:

  • FORBID_NO_DATA: Ensure no parts of the raster contain NO_DATA values;
  • FORBID_ALL_ZEROES: Ensure the raster does not consist entirely of zero values;
  • FORBID_ALL_ONES: Ensure the raster does not consist entirely of one values;
  • FORBID_OUT_OF_RANGE: Ensure the raster pixels must be within the specified valid range.

• Implemented a validation mechanism based on Chain of Responsibility pattern that checks each raster dataset against the above rules (RasterMapValidator);

• The validation is performed automatically as part of the model simulation configuration processing pipeline (ModelConfiguration), flagging any datasets that violate their respective rules for further investigation or correction;

• Configures use of GitHub Actions for CI to run related tests on each push and pull request.

Related Issue

• Resolve Add validation rules for input rasters #109.

Motivation and context

• See Add validation rules for input rasters #109.

How has this been tested

• Manually;
• The specific unit test suite must pass without any exception.

Screenshots

• N/A

[LINAMARIAOSORIO]

Tested with known database with problmes

[LINAMARIAOSORIO]

Tested with known database with problems

The merge-base changed after approval.

[LINAMARIAOSORIO]

LGTM

[LINAMARIAOSORIO]

No Conflicts