Skip to main content

Hi Team,


We are successfully using the OGC API FIS on a daily basis but we have seen an error today. An example here returns no data against the ESA World Cover (BYOC):


https://services.sentinel-hub.com/ogc/fis/<instance_id>?LAYER=GLOBAL-COVERAGE&GEOMETRY=POLYGON((118.238039647324%20-30.28121676774709,%20118.233989797872%20-30.28473436180334,%20118.2339289542329%20-30.28468161923464,%20118.2338681106591%20-30.2846288766354,%20118.2379179603978%20-30.28111128628904,%20118.2379788038283%20-30.28116402703333,%20118.238039647324%20-30.28121676774709))&CRS=EPSG:4326&RESOLUTION=10m&bins=10


Can you help us resolve why this is occuring.

Steve

Hi @steven.williams2,


if I am not mistaken, the issue is in order of coordinates - when using FIS with EPSG:4326, it should be lat/lon (in line with WCS 1.1.1).


See this FAQ and FIS docs.


This is the most common error, but also most difficult to find. I often wonder, if guys at OGC know, how much chaos they created with these inconsistencies.


If you change the order, and increase resolution to 100m (your area is pretty large, I believe), you get a result:


https://services.sentinel-hub.com/ogc/fis/<INSTANCE_ID>?LAYER=GLOBAL-COVERAGE&GEOMETRY=POLYGON((-30.292274851024242%20118.11950683593749,-30.51494904517772%20118.19641113281249,-30.35865642078877%20118.45458984375,-30.197366063272245%20118.37219238281249,-30.292274851024242%20118.11950683593749))&CRS=EPSG:4326&RESOLUTION=100m&bins=10


I hope this works for you?


Reply