Assess Hierarchical Collections for OGC API - 3D GeoVolumes

[jeffharrison]

The OGC API – 3D GeoVolumes organizes access to a variety of 3D content according to a hierarchy of 3D geospatial volumes (GeoVolumes).

The key focus of the API is on indexing 3D content according hierarchies of 3D geospatial volumes, and it may be useful to assess the role of new approaches to 'Hierarchical Collections'

Best Regards,
Jeff

[jerstlouis]

Outcome of discussion at session in 127th members meeting in Singapore:

The children property related not to the relationship between BVH nodes, but to relationship between different collections as per hierarchical collections discussed in #5 as well as opengeospatial/ogcapi-common#11 and opengeospatial/ogcapi-common#298 . Since we agreed that we can resolve this in common (likely with a parent property specifying the parent {collectionId}), we can get rid of children here.

Hierarchical collections should be confused with the Bounding Volume Hierarchy of nodes, which are internal to the 3D Tiles or i3s BVH representation of one collection.

Hierarchical collections allow to organize separate collections in an arbitrary hierarchy.