Interface DataSet

All Superinterfaces:
All Known Subinterfaces:
Feature­Set, Grid­Coverage­Resource, Writable­Feature­Set, Writable­Grid­Coverage­Resource
All Known Implementing Classes:
Abstract­Feature­Set, Abstract­Grid­Coverage­Resource, Concatenated­Feature­Set, Join­Feature­Set

public interface DataSet extends Resource
Collection of features that share a common set of attributes or properties. Features may be organized in coverages, but not necessarily. The common set of properties is described by feature types, grid geometries or sample dimensions, depending on the Data­Set subtype. The actual values are provided by methods defined in Data­Set subtypes.
Example: the features contained in a Data­Set could be all bridges in a city. A Data­Set can be associated to one Feature­Type which specifies that all bridges shall have "construction date" and "height" attributes, and an arbitrary number of Feature instances which contains the actual values for all bridges in the dataset.


Datasets should have metadata / metadata­Scope / resource­Scope sets to Scope­Code​.DATASET. If this datasets is part of a series or an Aggregate, the aggregate name should be declared as the parent metadata. That parent metadata is often the same instance than Data­Store​.get­Metadata().

Defined in the sis-storage module

  • Method Details

    • getEnvelope

      Optional<Envelope> getEnvelope() throws DataStoreException
      Returns the spatiotemporal extent of this resource in its most natural coordinate reference system. The following relationship to Resource.getMetadata() should hold (departures may exist):
      • The envelope should be contained in the union of all geographic, vertical or temporal extents described by metadata / identification­Info / extent.
      • The coordinate reference system should be one of the instances returned by reference­System­Info.
      The envelope should use the coordinate reference system (CRS) that most closely matches the geometry of the resource storage. It is often a projected CRS, but other types like engineering CRS are also allowed. If this resource uses many different CRS with none of them covering all data, then the envelope should use a global system (typically a geographic CRS).

      Estimated envelopes

      The returned envelope is not necessarily the smallest bounding box encompassing all data. If the smallest envelope is too costly to compute, this method may conservatively return a larger envelope. The converse (returning a smaller envelope) should be avoided, but is not strictly forbidden because some resources may compute the envelope using only a subset of all the resource data.
      the spatiotemporal resource extent. May be absent if none or too costly to compute.
      Data­Store­Exception - if an error occurred while reading or computing the envelope.