Currently in bignbit when we submit a Harmony job in the submit_harmony_job.py lambda, the outputCrs option is purposefully excluded from the query parameters https://github.com/podaac/bignbit/blob/develop/bignbit/submit_harmony_job.py#L114-L122:
# Workaround to prevent sending harmony requests that are
# equirectangular projection through the reproject service.
# Avoids unnecessary processing and errors for some collections
# that do not support reprojection.
if output_crs.upper() != 'EPSG:4326':
kwargs['crs'] = output_crs
# Use the scaleExtent either from datasetConfig or use the
# default values from GIBS
if output_crs.upper() == "EPSG:3413" or output_crs.upper() == "EPSG:3031":
kwargs['scale_extent'] = big_config['config'].get(
'scaleExtentPolar',
[-4194303, -4194303, 419303, 419303]
)Imagenator-L2 and Imagenator-L3 do not support reprojection (although L3 should), so this was originally done as a workaround for that limitation. There is a big caveat though in the sense that the inputCrs is assumed to be EPSG:4326 if the outputCrs is ESPG:4326.
With NISAR processing, this is not always the case. Any L2 GCOV above or below +/- 80 degrees latitude or so is in polar projection by default. GIBS does not plan to support polar projection for the L2 GCOV layer, so we need to reproject this data to EPSG:4326 in HyBIG. This is perfectly doable if the Harmony config is correct, but the submit_harmony_job lambda needs to be updated to know when the outputCrs parameter should be sent and when it shouldn't.
Currently in bignbit when we submit a Harmony job in the submit_harmony_job.py lambda, the outputCrs option is purposefully excluded from the query parameters https://github.com/podaac/bignbit/blob/develop/bignbit/submit_harmony_job.py#L114-L122:
Imagenator-L2 and Imagenator-L3 do not support reprojection (although L3 should), so this was originally done as a workaround for that limitation. There is a big caveat though in the sense that the inputCrs is assumed to be EPSG:4326 if the outputCrs is ESPG:4326.
With NISAR processing, this is not always the case. Any L2 GCOV above or below +/- 80 degrees latitude or so is in polar projection by default. GIBS does not plan to support polar projection for the L2 GCOV layer, so we need to reproject this data to EPSG:4326 in HyBIG. This is perfectly doable if the Harmony config is correct, but the submit_harmony_job lambda needs to be updated to know when the outputCrs parameter should be sent and when it shouldn't.