Hello,
no objection, but maybe we should start a processing module to separate
api/implementation from futur processes, like resampling, merge, band
selection,etc...
Johann
On 03/06/2019 16:56, Martin Desruisseaux wrote:
SIS currently has the following modules:
* "sis-feature", released in SIS 0.8.
* "sis-raster", never released yet.
I propose to move "sis-raster" classes into the "sis-feature" module.
The reason is that those modules are unlikely to be used independently.
The next module in the dependency chain is "sis-storage", and that
module needs those two modules anyway because many storages (netCDF
files, Geopackage, PostGIS database…) can contain both kind of data
(features and rasters). The module name "sis-feature" would still be
appropriate even for raster data if we take the Open Geospatial
Consortium (OGC) point of view, which considers "grid coverage" as a
kind of "feature" even if the API differ.
The package names would be the same. Since "sis-raster" has never been
released yet, no application using SIS releases would be impacted.
Is there any comment or objection?
Martin
