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
jamesfwood
changed the title
If can't find lat lon, it returns an empty subset file. It should fail instead
If can't find lat lon, it returns successful with an empty subset file. It should fail instead and not return an empty file
Dec 12, 2024
Yeah we should return empty in most situations. @sliu008 please investigate why it's failing because of the lat and lon. Also, we pass in the granule that should be within that bbox too, so we need to figure out why this is returning empty. Maybe it shouldn't fail but we need to understand what's going on here.
jamesfwood
changed the title
If can't find lat lon, it returns successful with an empty subset file. It should fail instead and not return an empty file
If can't find lat lon, it returns successful with an empty subset file. Why does it return empty?
Dec 19, 2024
Collection SMAP_RSS_L2_SSS_V5.3 in OPS
autotest request:
https://harmony.earthdata.nasa.gov/C2936721448-POCLOUD/ogc-api-coverages/1.0.0/collections/parameter_vars/coverage/rangeset?forceAsync=true&subset=lat(-82.29044999999999%3A82.08044999999998)&subset=lon(4.51755%3A175.50045)&granuleId=G3062447313-POCLOUD&variable=all
What is wrong with the lat lon for this collection? And why is the file returned empty? It should be within the bounding box.
The text was updated successfully, but these errors were encountered: