A 2017-11-23 release of Sentinel Hub services is bringing some changes in the use of APIs, which will make it possible to continue with future improvements. You might want to read a public announcement about it here.
We've put a lot of effort into making the changes backward compatible and the majority of users should not feel a difference. However, as our services are being used in the most innovative ways, it might be that some actions will be needed on the side of our users.
Note: for users, who use our services solely through EO Browser, there are no significant changes.
These are the changes:
- The configuration utility (formerly called WMS Configurator) is available at the new location. It is also getting simplified (many users complained about the complexity of the old one). Almost all options are still configurable but we have hidden the rarely used ones behind an "Advanced" button.
- The service end-point is changing from https://services.sentinel-hub.com/v1/* to https://services.sentinel-hub.com/ogc/*. The old end-point will be redirected (after the transition period ends) to the new one so there is no immediate need to change this. However, we would still recommend you do this as soon as possible. Note: this is only for request URLs, there is no need to change any URLs in the configurator!
- Hard-coded EO products are gone as our users asked for more transparency on the path from the original reflectance/sensor values to the output from our services. We replaced these with "EO Products", essentially custom script product templates (we have learned that our users love custom scripts), which can be used directly exactly like before, or further adjusted in line with a user's expectations.
- We are getting rid of "STYLES" as people found it confusing. Each layer therefore has only one output option. For existing layers created prior to these changes STYLES will continue to be supported, however any modifications to these layers will require its multiple styles to be removed. All previous visualization options (RGB, grayscale, Red-blue, etc.) will continue to be available, each under a different EO Product template. Check this FAQ entry for more information.
- Each service call can only accept one layer. It did not make sense to query for "TRUE_COLOR,NDVI" even before, but some users were querying our API with a combination of raw band layers, e.g. "LAYERS=B04,B03,B02,B08". This can still be done now by configuring a layer with a custom script: "return [B04,B03,B02,B08];". One can also use this custom script as a part of a URL request, see the EVALSCRIPT parameter. If you want to get an image composite similar to the one in the old version, try adding gain factor 2.5 to each of the bands, e.g. "return [2.5*B04,2.5*B03,2.5*B02];" For raw data (or reflectance), there should not be any multiplication.
- An exception to the rule above is, for now, combinations containing the meta-data layer "DATE", e.g. "TRUE_COLOR,DATE", which will show true color imagery and imagery dates of the scene. This feature will remain to assure backward compatibility as we have noticed that quite a few of our users use this.
- There are no "default" or preset layers available to be used in the API. Each instance needs its own configuration of layers. E.g. if one used to query for B08 (NIR sensor in Sentinel-2), one needs to configure this layer in the Configuration utility. Similarly one cannot query only for "DATE" meta-data. For those who would like to only get DATE information, you can create a layer returning white (e.g. "return [1,1,1];") and append the "DATE" layer in your request.
- GAIN, GAMMA and OFFSET parameters will be deprecated as they did not act consistently in the past. They should now be included in custom script.
- Maximum area, a very rarely used feature for limiting the extent at which layer is visualized, can now be set only on the instance level. For those who need different extent limits, you can always create several differnet instances. Or better yet, use the "GEOMETRY" parameter when calling the service to clip the image.
- The channel placeholder names in FIS API have changed. It now returns enumerated keys C0, C1, C2,... for described channels, when it returned named keys like RED, GREEN, BLUE in the previous version.
- WCS specific
- WCS service now supports version 1.0 only (support for 1.1 and 1.2 was poor beforehand anyway). We have decided to put more focus into implementing our own API for data provision than to support OGC in the case of WCS.
- Parameters LAYERS (for WMS) and COVERAGE (for WCS) are now mandatory. For those, working with EVALSCRIPT parameter in a dynamic fashion, you can simply create a default layer in Configuration utility (e.g. you create one with Custom Script and define "return [1,0,0];" in it).
- WFS specific
- Datasource speification became mandatory as there are more datasources coming in. E.g. if one used "TYPENAMES=TILE", it should be changed to "TYPENAMES=S2.TILE".
- FIS specific:
- "NDVI" element was changed to "C0" as we rolled out FIS in a more generic fashion, e.g. supporting any index, not just NDVI.
- Custom script specific:
- eval() function was renamed to evaluatePixel()
- Mosaic Generator is getting deprecated and replaced with EO Browser.
- TILE, FILL and OUTLINE default layers were deprecated.
The roll-out of the new version on various infrastructures:
- The core infrastructure, where Sentinel-2 is available (services.sentinel-hub.com) will be migrated in the week commencing the 20th of November 2017. There will be a temporary period of one month during which both the old and new version will operate.
- US West infrastructure, where we serve Landsat, MODIS and DEM data (services.aws-uswest2.sentinel-hub.com) was migrated on 8th of February 2018. here will be a temporary period of one month during which both the old and new version will operate.
- EO Cloud infrastructure, where we serve Sentinel-1, Sentinel-3, etc., will be migrated in Q2 2018.
NOTE: This post will be updated through time so come back.
Watch Quick tutorial on Sentinel Hub.