Web Coverage Service 2.0 MetOcean extension

The Web Coverage Service 2.0 exposes the data in the form of coverages that can be described as "the digital representation of some spatio-temporal phenomenon". In the context of the meteorological web services, these are usually values of the requested forecast parameter(s) from the specified NWP model.

Supported WCS 2.0 requests:

GET/KVP HTTP Binding for GetCoverage and GetCorridorCoverage

https://swim.iblsoft.com/request-examples/OGC-WCS2.0-GetCoverage-GET-KVP-HTTP-Binding.html

https://swim.iblsoft.com/request-examples/OGC-WCS2.0-GetCorridorCoverage-GET-KVP-HTTP-Binding.html

Example GetCoverage and GetCorridorCoverage Requests

GetCoverage Request Example - Rectangular Area - Sampled Levels and Times

A dataset is required that is homogeneous i.e. all data are regularly spaced either in space. In the example the data is required for every degree (irrespective of the model grid) and at every 50hPa and at hourly intervals. The sampling of the model is done in 4 dimensions.

https://swim.iblsoft.com/wxcube?REQUEST=GetCoverage&

VERSION=2.0.0&

COVERAGEID=LOWW_2014-08-14T06.00.00Z_ISBL&

SUBSET=long,CRS:84(16.35,16.8)&

SUBSET=lat,CRS:84(48,48.25)&

SUBSET=t,http://www.opengis.net/def/trs/ISO-8601/0/Gregorian+UTC("2014-08-14T06:00:00Z","2014-08-14T15:00:00Z")&

SUBSET=z,http://codes.wmo.int/grib2/codeflag/4.5/100(1000,250)&

RANGESUBSET=temperature,relative-humidity,wind-u,wind-v&

FORMAT=NetCDF3&

SIZE=long(11)&

SIZE=lat(11)&

SIZE=z(16)&

SIZE=t(10)&

INTERPOLATION=long(cubic)&

INTERPOLATION=lat(cubic)&

INTERPOLATION=z(barycentric)&

INTERPOLATION=t(linear)

https://swim.iblsoft.com/request-examples/GetCoverageRequest-Area-SampledLevelsAndTimes.xml

GetCorridorCoverage Request Example - 2D Corridor - Constant Level and Time

This example illustrates how a simple 2D corridor may be described e.g. a road. The road will have a width (in this case lateral extent of 5km) and a centreline. In this example the corridor is divided into 500 segments of equal length from start to finish. The centre line is defined by the output feature with the way points being a set of latitudes and longitudes. The two axes are defined with one axis as being along the corridor path and the other perpendicular to it. All values are taken for a fixed time 2014-06-23T12:00:00Z.

https://swim.iblsoft.com/wxcube?SERVICE=WCS&

REQUEST=GetCorridorCoverage&

VERSION=2.0.0&

COVERAGEID=KWBC_Latest_Atmosphere&

OUTPUTFEATURE=CRS:84[-2.5;50.0] CRS:84[-2.0;51.0] CRS:84[-1.1;51.2] CRS:84[-0.5;51.6] CRS:84[1.5;52.5] CRS:84[2.5;52.9] CRS:84[3.5;53.6]&

SUBSET=Corridor_Width(-2.5,2.5)&

SUBSET=t,http://www.opengis.net/def/trs/ISO-8601/0/Gregorian+UTC("2014-06-23T12:00:00Z")&

RANGESUBSET=horizontal-extent-of-cumulonimbus&

FORMAT=NetCDF3&

SIZE=Corridor_Length(500)&

SIZE=Corridor_Width(5)

https://swim.iblsoft.com/request-examples/GetCorridorCoverageRequest-2D-ConstantLevelAndTime.xml

GetCorridorCoverage Request Example - 2D + Time Corridor - Constant Level

This example illustrates how a 3D (2D + time) corridor may be described. The corridor will have a width (in this case lateral extent of 5km) and a centreline. In this example the corridor is divided into 50 segments of equal time from start to finish. The centre line is defined by the output feature with the way points being a set of latitudes, longitudes and times. The two axes are defined with one axis along the corridor path and the other perpendicular to it. The corridor lies at the constant 300hPa level.

https://swim.iblsoft.com/wxcube?SERVICE=WCS&

REQUEST=GetCorridorCoverage&

VERSION=2.0.0&

COVERAGEID=KWBC_Latest_ISBL&

OUTPUTFEATURE=CRS:84%5B2;49%5D@2014-06-24T12:00:00Z%20CRS:84%5B-74;40%5D@2014-06-25T00:00:00Z&

SUBSET=Corridor_Width(-2.5,2.5)&

SUBSET=z,http://codes.wmo.int/grib2/codeflag/4.5/100(300)&

RANGESUBSET=temperature,wind-u,wind-v,icing-mean,icing-max,clear-air-turbulence-mean,clear-air-turbulence-max,in-cloud-turbulence-mean,in-cloud-turbulence-max&

FORMAT=NetCDF3&

SIZE=Corridor_Time(51)&

SIZE=Corridor_Width(11)&

INTERPOLATION=Corridor_Time(linear)

GetCorridorCoverage Request Example - 3D + Time Corridor

This example illustrates how a 4D (3D + time) corridor may be described. The corridor will have a width (in this case lateral extent of 5km), height (in this case vertical extent of 2km) and a centreline. In this example the corridor is divided into 50 segments of equal time from start to finish. The centre line is defined by the output feature with the way points being a set of latitudes, longitudes, heights and times. The three axes are defined with one axis along the corridor path and the other perpendicular to it. The third, i.e. the verical axis is defined as the corridor height and is perpendicular to the corridor path.

https://swim.iblsoft.com/wxcube?SERVICE=WCS&

REQUEST=GetCorridorCoverage&

VERSION=2.0.0&

COVERAGEID=LOWW_Latest_ISBL&

OUTPUTFEATURE=CRS:84[-2.5;50.0]^0m@2014-06-23T12:00:00Z CRS:84[1.5;52.5]^3000m@2014-06-23T18:00:00Z CRS:84[3.8;53.8]^0m@2014-06-24T00:00:00Z&

SUBSET=Corridor_Width(-2.5,2.5)&

SUBSET=Corridor_Height(-1,1)&

RANGESUBSET=temperature,relative-humidity,wind-u,wind-v&

FORMAT=NetCDF3&

SIZE=Corridor_Time(51)&

SIZE=Corridor_Width(11)&

SIZE=Corridor_Height(5)&

INTERPOLATION=Corridor_Time(linear)&

INTERPOLATION=Corridor_Height(linear)

https://swim.iblsoft.com/request-examples/GetCorridorCoverageRequest-3D%2bTime.xml