Landsat8 WFS request problem | Planet Community

Hello

I’m trying to get image history from WFS service. It works fine for Sentinel 2 with TYPENAMES=S2.TILE (http://services.sentinel-hub.com/ogc/wfs/INSTANCE_ID?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TIME=2019-09-01/2020-01-01/P1D&OUTPUTFORMAT=application/json&TYPENAMES=S2.TILE&SRSNAME=EPSG:4326&BBOX=51.8888774436112,39.0887805772598,51.9004602040773,39.1014729230514).

But when I’m trying to get same data for Landsat8 with TYPENAMES=L8.TILE or DSS6 service responses “TYPENAME=L8.TILE not found!”.

What am I missing for Landsat 8?

Thanks

Page 1 / 1

Landsat is located on another deployment so you need to change the end-point.

Instead of services.sentinel-hub.com you have to use the us-west one:
https://docs.sentinel-hub.com/api/latest/#/data/Landsat-8?id=endpoint-locations

For

http://services-uswest2.sentinel-hub.com/ogc/wfs/INSTANCE_ID?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TIME=2019-09-01/2020-01-01/P1D&OUTPUTFORMAT=application/json&TYPENAMES=L8.TILE&SRSNAME=EPSG:4326&BBOX=51.8888774436112,39.0887805772598,51.9004602040773,39.1014729230514

response is still the same - TYPENAME=L8.TILE not found!

WFS service documentation doesn’t mention any special enpoint for Landsat - https://www.sentinel-hub.com/develop/api/ogc/standard-parameters/wfs/

Are you sure that you have at least one Landsat layer in the configuration (instance ID) that you are using?

WFS works under layers in the configuration.

If it is a bit confusing, sorry about that… specifics of OGC…

We will soon publish a catalogue API, which will hopefully address all these issues. (WFS will still work)

Yes, you are right, was missing Landsat layer in configuration. Thanks for pointing that out!

The Catalogue API I was mentioning:
https://docs.sentinel-hub.com/api/latest/#/Catalog/README