Context Navigation

Changes between Version 10 and Version 11 of PetascopeSubsets

-              v10
+              v11
 This section will focus on how the topology of a grid coverage is stored in the metadata database and how ''Petascope'' interprets it.
+For point-clouds (multipoint coverages, in the GML realm), the subject is straightforward: each point is a 0D element (please not that bbox description of point-clouds are currently not implemented: see #571).
+For point-clouds (multipoint coverages, in the GML realm), the subject is straightforward: each point is a 0D element.
+(The solutions described here have been selected in order to achieve a coherent behavior, while custom coverage-point footprints are yet to be solved: refer to #680).
 When it comes to the so-called ''domainSet'' of a coverage (hereby also called domain, topology or geometry), the metadata database (`petascopedb`) follows pretty much the GML model for rectified grids: the grid origin and one offset vector per grid axis are enough to deduce the full ''domainSet'' of such (regular) grids. When it comes to referenceable grids, the ''domainSet'' still is kept in a compact vectorial form by adding weighting coefficients to one or more offset vectors. For more on coefficients refer to the [PetascopeUserGuide user guide].