Currently no geographical footprint is associated with the product metadata (at least not in the generic data model, there are mission-specific additions for that). This also means that products cannot be selected by geographical constraints.
A representation for the geographical footprint shall be added as an optional element to the Product entity. The representation shall take into account the features provided by Hibernate and the representations for polygons in applicable standards, e. g. the OGC GML and OGC EO-GeoJSON formats. ("Take into account" means that a conversion to and from such formats shall be reasonably straightforward.)
Currently no geographical footprint is associated with the product metadata (at least not in the generic data model, there are mission-specific additions for that). This also means that products cannot be selected by geographical constraints.
A representation for the geographical footprint shall be added as an optional element to the Product entity. The representation shall take into account the features provided by Hibernate and the representations for polygons in applicable standards, e. g. the OGC GML and OGC EO-GeoJSON formats. ("Take into account" means that a conversion to and from such formats shall be reasonably straightforward.)