Is it by convention that each image loaded into Geoserver by way of the
REST API be required to be in its own coverage store?
Or, is it possible to have multiple coverages inside of the same store?
Ronak
Patel, Ronak Avinash (US SSA) ha scritto:
Is it by convention that each image loaded into Geoserver by way of the
REST API be required to be in its own coverage store?Or, is it possible to have multiple coverages inside of the same store?
It is not convention but a technical limitation. At the moment there
is no real software concept of a store, it's just there for naming
uniformity. What we have is Format, a class that can read one file
containing coverages, most of the time one coverage only.
There is work underway in GeoTools land to propose a real CoverageStore
api so that we can treat a filesystem directory, a Oracle database,
a SDE server, a remote WCS server as single sources of many coverages.
Simone is leading the effort, atm there is a prototype in some branch,
not sure when this is going to hit mainline thought, that depends
on people available resources (without explicit funding time tend
to be long as effort is allocated when nothing else "paying the bills"
is on the plate).
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.