Registration of profile definitions for OGC API - DGGS

[jerstlouis]

For the purpose of negotiating specific profiles of DGGS zone data and DGGS zone list representations all using the same media type, a number of profiles are defined by OGC API - DGGS. A particular profile can be selected using the profile query parameter, following the decisions regarding JSON-FG in opengeospatial/ogc-feat-geo-json#129. These profiles would need to be registered on the definition server within the https://www.opengis.net/def/profile/ogc/0/ namespace.

They are:

For both zone data and zone lists in GeoJSON (application/geo+json):

• rfc7946: return standard GeoJSON without using any extension
• jsonfg: return JSON-FG representation
• jsonfg-plus: return JSON-FG representation with GeoJSON compatibility

For zone data in GeoJSON (application/geo+json):

• jsonfg-dggs: return DGGS-JSON-FG representation, using dggsPlace to encode geometry points quantized to sub-zone, represented as local indices from 1 to the number of sub-zones corresponding to the DGGRS deterministic sub-zone order, with a special value of 0 representing an artificial node
• jsonfg-dggs-plus: return DGGS-JSON-FG representation, with GeoJSON compatibility geometry
• jsonfg-dggs-zoneids: return DGGS-JSON-FG representation, using dggsPlace to encode geometry points as textual global zone identifiers, with a special value of null representing an artificial node
• jsonfg-dggs-zoneids-plus: return DGGS-JSON-FG representation, encoding geometry points as global zone IDs, with GeoJSON compatibility geometry

For zone data in netCDF (application/x-netcdf):

• netcdf3: return NetCDF classic and 64-bit offset format (not quantized to DGGH)
• netcdf3-dggs: return NetCDF classic and 64-bit offset format where one axis corresponds to local sub-zone indices
• netcdf3-dggs-zoneids: return NetCDF classic and 64-bit offset format where one axis corresponds to the global identifiers of sub-zones (textual or 64-bit integer)
• netcdf4: return HFG5-based NetCDF 4 format (not quantized to DGGH)
• netcdf4-dggs: return HDF5-based NetCDF 4 format where one axis corresponds to local sub-zone indices
• netcdf4-dggs-zoneids: return HDF5-based NetCDF 4 format where one axis corresponds to the global identifiers of sub-zones (textual or 64-bit integer)

For zone data in zipped Zarr 2.0 (application/zarr+zip):

• zarr2: return zipped Zarr 2.0 (not quantized to DGGH)
• zarr2-dggs: return zipped Zarr 2.0 where one axis corresponds to local sub-zone indices
• zarr2-dggs-zoneids: return zipped Zarr 2.0 where one axis corresponds to the global identifiers of sub-zones (textual or 64-bit integer)

For zone data in CoverageJSON (application/prs.coverage+json):

• covjson: return CoverageJSON (not quantized to DGGH)
• covjson-dggs: return CoverageJSON where one axis corresponds to local sub-zone indices
• covjson-dggs-zoneids: return CoverageJSON where one axis corresponds to the global identifiers of sub-zones (textual or 64-bit integer)

See also openapi/parameters/dggs-core/profile.yaml.

cc. @ghobona @rob-metalinkage

[ghobona]

Noting that the namespace has been used in a number of other places. I think the use and semantics are consistent.

https://github.com/search?q=repo%3Aopengeospatial%2FNamingAuthority+http%3A%2F%2Fwww.opengis.net%2Fdef%2Fprofile&type=code

https://github.com/search?q=repo%3Aopengeospatial%2FNamingAuthority%20https%3A%2F%2Fwww.opengis.net%2Fdef%2Fprofile&type=code

[ghobona]

@jerstlouis @geofizzydrink Thanks for briefing the OGC-NA session yesterday. We'll prepare the definitions for registration soon after the Member Meeting.