Supported data formats #290
Replies: 2 comments 2 replies
-
It turns out I've answered my own question - downloading 'S1A_IW_GRDH_1SDV_20151021T063752_20151021T063817_008247_00B9CD_097D.SAFE' rather than 'S1A_IW_GRDH_1SDV_20151021T063752_20151021T063817_008247_00B9CD_2770_COG.SAFE', i.e., not using the COG, pyroSAR opens the dataset fine. |
Beta Was this translation helpful? Give feedback.
-
Hi @davedavemckay. For my better understanding...what do you mean by ESA OData? As far as I know OData is just a web interface protocol and I don't know of any ESA-hosted data service. Are you referring to the new Copernicus Data Space Ecosystem (CDSE)? In this case I think the data comes from creoDIAS operated by CloudFerro. I am not sure about the reasoning behind the format conversion but could ask around. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I'm trying to run geocode on some unzipped Sentinel-1 GRD scenes. So this might be a quick one! I'm running the example pyrosar.identify() code and get "data format not supported". I suspect this is either due to the datasets being cloud-optimized geoTIFF, or simply because they're ingested into the system I'm using as .SAFE folders, not zip files.
My source is ESA OData. I can download the original data, not the COG versions, if that's the issue, or zip downloaded datasets.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions