HydroCoupleOgc  0.1.0
OGC web service clients (WMS, WMTS, WCS, WFS) over Qt Network (0.1.0)
Loading...
Searching...
No Matches
HydroCouple::Ogc::WcsCoverageDescription Struct Reference

What DescribeCoverage says one coverage actually is. More...

#include <wcscapabilities.h>

Collaboration diagram for HydroCouple::Ogc::WcsCoverageDescription:

Public Member Functions

bool isTwoDimensional () const
 Whether this coverage has exactly the two spatial axes this library can request.
 
QRectF boundsAsRect () const
 The envelope as a rectangle, x horizontal.
 
int horizontalAxisIndex () const
 Which of axisLabels is the easting/longitude one.
 
int verticalAxisIndex () const
 Which of axisLabels is the northing/latitude one, or -1.
 

Public Attributes

bool ok = false
 
QString message
 
QString identifier
 
QString envelopeCrs
 The system the envelope below is written in, as the server spells it.
 
QStringList axisLabels
 What the coverage's axes are called, in the envelope's own order.
 
QList< double > lowerCorner
 The envelope's corners, in the same axis order as axisLabels.
 
QList< double > upperCorner
 
QList< WcsRangeField > rangeFields
 

Detailed Description

What DescribeCoverage says one coverage actually is.

The load-bearing document. Three things live only here, and a request built without them is a guess:

  • the envelope, and the system it is written in;
  • the axis labels, which WCS 2.0 subsets by name;
  • the range fields, which is the list this library's caller must choose a band from.

Member Function Documentation

◆ boundsAsRect()

QRectF HydroCouple::Ogc::WcsCoverageDescription::boundsAsRect ( ) const
nodiscard

The envelope as a rectangle, x horizontal.

Ordered by what the axes are, not by where they sit: a coverage whose axes read "Lat Lon" has its northing first, and returning that as a QRectF's x would put the map on its side.

Here is the call graph for this function:

◆ horizontalAxisIndex()

int HydroCouple::Ogc::WcsCoverageDescription::horizontalAxisIndex ( ) const
nodiscard

Which of axisLabels is the easting/longitude one.

Returns
Its index, or -1 when the axes cannot be told apart.
Here is the caller graph for this function:

◆ isTwoDimensional()

bool HydroCouple::Ogc::WcsCoverageDescription::isTwoDimensional ( ) const
nodiscard

Whether this coverage has exactly the two spatial axes this library can request.

A coverage over time or depth needs those axes pinned too, which is a question for the caller and not something to guess.

◆ verticalAxisIndex()

int HydroCouple::Ogc::WcsCoverageDescription::verticalAxisIndex ( ) const
nodiscard

Which of axisLabels is the northing/latitude one, or -1.

Here is the caller graph for this function:

Member Data Documentation

◆ axisLabels

QStringList HydroCouple::Ogc::WcsCoverageDescription::axisLabels

What the coverage's axes are called, in the envelope's own order.

Not decoration. WCS 2.0 subsets an axis by name, and a name that is not the coverage's own is refused: rasdaman answers InvalidAxisLabel with HTTP 404. The names vary by coverage, not by protocol – "x y" for a projected national grid, "Lat Lon" for a geographic one, "ansi Lat Lon" when a time axis leads.

◆ envelopeCrs

QString HydroCouple::Ogc::WcsCoverageDescription::envelopeCrs

The system the envelope below is written in, as the server spells it.

Often the long URI form, "http://www.opengis.net/def/crs/EPSG/0/28992".

◆ identifier

QString HydroCouple::Ogc::WcsCoverageDescription::identifier

◆ lowerCorner

QList<double> HydroCouple::Ogc::WcsCoverageDescription::lowerCorner

The envelope's corners, in the same axis order as axisLabels.

◆ message

QString HydroCouple::Ogc::WcsCoverageDescription::message

◆ ok

bool HydroCouple::Ogc::WcsCoverageDescription::ok = false

◆ rangeFields

QList<WcsRangeField> HydroCouple::Ogc::WcsCoverageDescription::rangeFields

◆ upperCorner

QList<double> HydroCouple::Ogc::WcsCoverageDescription::upperCorner

The documentation for this struct was generated from the following files: