HydroCoupleOgc  0.1.0
OGC web service clients (WMS, WMTS, WCS, WFS) over Qt Network (0.1.0)
Loading...
Searching...
No Matches
wcscapabilities.h File Reference

What a WCS server offers, and what one of its coverages is. More...

#include "hydrocoupleogc/export.h"
#include <QByteArray>
#include <QList>
#include <QRectF>
#include <QString>
#include <QStringList>
Include dependency graph for wcscapabilities.h:
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes

struct  HydroCouple::Ogc::WcsCoverageSummary
 One coverage as the capabilities document lists it. More...
 
struct  HydroCouple::Ogc::WcsRangeField
 One band, or field, of a coverage's range. More...
 
struct  HydroCouple::Ogc::WcsCoverageDescription
 What DescribeCoverage says one coverage actually is. More...
 
struct  HydroCouple::Ogc::WcsCapabilities
 What a WCS server said about itself. More...
 

Namespaces

namespace  HydroCouple
 
namespace  HydroCouple::Ogc
 

Functions

HYDROCOUPLEOGC_EXPORT WcsCapabilities HydroCouple::Ogc::parseWcsCapabilities (const QByteArray &xml)
 Reads a WCS GetCapabilities response.
 
HYDROCOUPLEOGC_EXPORT WcsCoverageDescription HydroCouple::Ogc::parseWcsCoverageDescription (const QByteArray &xml)
 Reads a WCS 2.0 DescribeCoverage response.
 
HYDROCOUPLEOGC_EXPORT QString HydroCouple::Ogc::wcsExceptionText (const QByteArray &body)
 What an OGC exception report says, if that is what this is.
 

Detailed Description

What a WCS server offers, and what one of its coverages is.

Author
Caleb Buahin

A WCS answers with values rather than with a picture of them, which is what makes it the service that can put elevations on mesh vertices instead of merely a hillshade behind them.

It is also the one service here where the capabilities document is not enough. WMS, WMTS and WFS all publish, per layer, where it is and what it can be asked for in. A WCS 2.0 CoverageSummary is permitted to carry nothing but an identifier, and real ones do: PDOK's national elevation service publishes exactly <CoverageId> and <CoverageSubtype> per coverage and not one word about extent, system or bands. Everything a request needs comes from DescribeCoverage.

So there are two documents here, not one, and the second is not optional.