Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-03 Thread Darell van der Voort
Hello Daniele, Thank you for the update, however I do not seem to get it to work. Please let me know if i'm missing something. I start with the following initial folder structure: /geoserver/data/workspace//*.tiffs /geoserver/data/workspace//datastore.properties

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-02 Thread Daniele Romagnoli
Hi Darell, On Mon, Oct 2, 2017 at 11:30 AM, Darell van der Voort wrote: > Hello Daniele, > > Thank you for your input! I now use a schema per workspace, but creating a > schema per imagepyramid would indeed solve the problem of duplicate table > names. So do I understand

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-02 Thread Darell van der Voort
Hello Daniele, Thank you for your input! I now use a schema per workspace, but creating a schema per imagepyramid would indeed solve the problem of duplicate table names. So do I understand correctly that there is no possibility to change the table names? For example to: schema.imagepyramid0,

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-02 Thread Daniele Romagnoli
Hi Darell, as you said, the imagePyramid is basically a set of imageMosaics: an ImageMosaic for each pyramid level. Therefore, each level should have its own indexer and, optionally, a datastore.properties if you want to catalog the granules into a DB instead of default shapefile. When using DB

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-02 Thread Darell van der Voort
Hi Peter, Thank you for the examples, very helpful! Using a indexer.xml indeed seems like a better set-up. Have you ever tried this in combination with the imagepyramid plugin? I know that the imagepyramid are basically just imagemoasics per folder level. However as the folder structure is

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-09-29 Thread Darell van der Voort
Hi Peter, This is my indexer.properties configuration: Caching=false TimeAttribute=ingestion Schema=*the_geom:Polygon,location:String,ingestion:java.util.Date:Double PropertyCollectors=TimestampFileNameExtractorSPI[timeregex](ingestion) And this is my 0.properties which is automatically

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-09-29 Thread Peter Kovac
I usually configure ImageMosaic for time-series plain GeoTIFF granules so my advice might not be 100% accurate but I hope it helps anyway. Firstly, your schema seems wrong to me: you have two types specified for ingestion - java.util.Date and a Double after that. Perhaps another attribute of

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-09-29 Thread Peter Kovac
Hi Darell, can you post your indexer.xml configuration for the imagemosaic? Regards, Peter Kovac On 28. 9. 2017 9:59, Darell van der Voort wrote: Hello everybody, I'm running Geoserver 2.11.2 on Java 1.8.0_144 32 bits on Amazon Linux together with Tomcat 9. The plugins I have installed

[Geoserver-users] ImagePyramid using Postgresql for granules

2017-09-28 Thread Darell van der Voort
Hello everybody, I'm running Geoserver 2.11.2 on Java 1.8.0_144 32 bits on Amazon Linux together with Tomcat 9. The plugins I have installed are imagemosaic, imagepyramid, GeowebCache (internal) and Geofence. When using the imagemosaic plugin I am able to use a Postgresql DB for storing the