You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although undesirable, there may be rare cases where the DigitalGlobe archive has already been enhanced before it enters the inference process. In fact, there is a optional parameter when ordering to apply a Dynamic Range Adjustment to the product. From my observations, applying our own in-house enhancement to this type of source greatly affects the quality of the image, making it unusable (see figure)
A suggested solution would be to omit the enhancement step when it is already done by the supplier. Although the approach applied is probably a bit different from ours, I would expect better extractions than for a "double enhanced" image.
Here's how to find that information:
In the METADATA asset of the STAC Item, see the tag <RADIOMETRICENHANCEMENT>DRA/ACOMP</RADIOMETRICENHANCEMENT> as opposed to expected <RADIOMETRICENHANCEMENT>ACOMP</RADIOMETRICENHANCEMENT>
The text was updated successfully, but these errors were encountered:
Although undesirable, there may be rare cases where the DigitalGlobe archive has already been enhanced before it enters the inference process. In fact, there is a optional parameter when ordering to apply a Dynamic Range Adjustment to the product. From my observations, applying our own in-house enhancement to this type of source greatly affects the quality of the image, making it unusable (see figure)
A suggested solution would be to omit the enhancement step when it is already done by the supplier. Although the approach applied is probably a bit different from ours, I would expect better extractions than for a "double enhanced" image.
Here's how to find that information:
In the METADATA asset of the STAC Item, see the tag
<RADIOMETRICENHANCEMENT>DRA/ACOMP</RADIOMETRICENHANCEMENT>
as opposed to expected<RADIOMETRICENHANCEMENT>ACOMP</RADIOMETRICENHANCEMENT>
The text was updated successfully, but these errors were encountered: