Closed joemcglinchy closed 6 years ago
Let me dig into this a little bit and I'll let you know what can be done. Currently Radarsat is not accessible via gbdxtools, but i think the general attitude at DG is that it should be. However, there is one little hurdle and thats that the bucketname and prefix to the data living in S3 are encrypted and need to be decrypted in order to fetch the pixels. I've decrypted them with a key in the past but i'm pretty sure the thinking is that the key shouldn't become publicly accessible.
I'll figure out if we can get support decrypting them on the server, and if so I can add Radarsat to gbdxtools.
Got some info back on this and unfortunately we're not going to have support for Radarsat for some time still. There are a number of blockers that prevent us from efficiently providing any sort of meaningful access to the Radarsat archive. As those barriers are removed i'll work on getting what ever support we can provide into gbdxtools.
Hello, I was wondering if it is possible to access RADARSAT-2 data from the gbdxtools API? I see it can be returned from the search API using Postman. I checked out one of the entries (below) and tried both the 'Identifier' and 'CatalogID' as arguments to CatalogImage. I get the following errors:
CatalogImage('PDS_05854100')
Exception: Could not find a catalog entry for the given id: PDS_05854100
CatalogImage('556282')
UnsupportedImageType: Unsupported image type: [u'GBDXCatalogRecord', u'RADARSAT2', u'SGFProduct', u'MDAProduct']
Does this mean RADARSAT-2 data can't yet be accessed with CatalogImage or something similar, and is limited to task-workflow execution only?