Define Query responses - requires YAML knowledge

rggibb commented 3 years ago

responses are:

 Distance: real + uom.asString .. uom can just be a string, but ifa OGC compliant uom has been defined then lets use it

  Boolean: True|False

  RelativePosition: enum,eration with possible values of:
  {Before, After, Meets, MetBy, Overlaps, OverlappedBy, Starts, StartedBy, 
       During, Contains, Finishes, FinishedBy, Equals, In, Disjoint}

rggibb commented 3 years ago

Boolean and relativePosition defined as schemas and used in response definitions and in parameter defenitions, with thx for contributions from @allixender & @doublebyte1

rggibb commented 3 years ago

Distance: actually a tad more complex. Since we are supporting up to 4D DGGS, so Distance can be spatial, temporal or spatio-temporal, so it needs to be an array of a [spatialDist,temporalDist] and each of spatialDist and temporalDist need to be comrpised of both a number and a uom, where uom is selected from a spatial uom enumerated list and a temporal uom enumerated list. To be a valid list at least one of spatialDist and temporalDist must be present, otherwise it is a null distance

At present the schema:distance is an array of 1 or 2 strings. So this needs a bit more work to determine best the YAML structure, and to locate spatial and temporal enum lists of uom, and see if they are already implemented somewhere or where they should be defined.

I suggest we stick to non-Gregorian calendar temporal distances, ie restrict the input to decimal fractional s, m, h, d, y etc.

opengeospatial / ogcapi-discrete-global-grid-systems

Define Query responses - requires YAML knowledge #23