Configuration

The package contains a configuration file config.json. After the package is installed you can check the initial configuration parameters in command line:

$ sentinelhub.config --show

Sentinel Hub Capabilities

The instance_id parameter will be empty. In case you would like to use any capabilities of the package that interact with Sentinel Hub services you can set your Sentinel Hub instance ID with:

$ sentinelhub.config --instance_id <your instance id>

By doing so the package will use this instance ID to interact with Sentinel Hub unless you purposely specify a different one in the code.

Amazon S3 Capabilities

The package enables download of Sentinel-2 L1C and L2A data from Amazon S3 storage buckets. The data is contained in Requester Pays buckets therefore AWS credentials are required in order to use these capabilities. The credentials can be set in package’s configuration file with parameters aws_access_key_id and aws_secret_access_key. This can be configured from command line:

$ sentinelhub.config --aws_access_key_id <your access key> --aws_secret_access_key <your secret access key>

In case these credentials are not set the package will instead automatically try to use locally stored AWS credentials if they were configured according to AWS configuration instructions. Any other configuration parameters (e.g. region) will also be collected the same way.

Important: Because satellite data at S3 is contained in Requester Pays buckets Amazon will charge users for download according to Amazon S3 Pricing. In this case users are charged for amount of data downloaded and the number of requests. The sentinelhub package will make at most one GET request for each file downloaded. Files metadata.xml, tileInfo.json and productInfo.json will be obtained without any charge from Sentinel Hub public repository.

Other

For more configuration options check:

$ sentinelhub.config --help