Dear all,

I'm trying to configure an imagemosaic based on a postgis table:

> create table scene
> (
>    id serial primary key,
>    product_name varchar not null,
>    timestamp timestamp not null,
>    location varchar not null,
>    footprint geometry(Polygon,3857) not null
> );
>
> I would like to keep a single table, but configure different mosaics
(stores or layers) based on the column product_name. Each mosaic may have
different Levels and characteristics, e.g., geostationary, LEO.
It is possible to specify a default CQL filter in layer's "Coverage
Parameters" section, however, it can be overriden by a user specified
filter. Moreover, I believe layer's bbox and possibly other quantities are
then calculated using all records from the table, regardless of the
product_name value.

There is an SQL View layer type, which is capable of such filtering but
from what I have found its is not compatible with imagemosaic if I'm not
mistaken.

I'm currently looking at extending ImageMosaic store properties, so that
one could specify such filter. Is it the right approach or maybe it could
be solved differently, using existing components?

Thanks,
Jakub
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to