Hi Daniele,
I created a JIRA issue:
http://jira.codehaus.org/browse/GEOS-6564[1]
I also created a unit test, which mimicks my setup, and exposes the issue:
https://github.com/geoserver/geoserver/pull/639[2]
It took my a bit of time, but I hope I can reuse this unit test setup in the
future to illustrate other issues. In fact it also a nice demonstration of a
complex multi dimensional setup.
best regards,
Jeroen
On Wednesday 02 July 2014 16:42:57 Daniele Romagnoli wrote:
> Hi Jeroen,
> If you also have a small sample mosaic (configuration and data) and a
> request to replicate it, to be attached to JIRA, they would be very helpful
> for debugging and fixing it.
>
> Cheers,
> Daniele
>
>
>
>
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/NWWaa2 for more information.
> ==
>
> Ing. Daniele Romagnoli
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> On Wed, Jul 2, 2014 at 4:38 PM, Jeroen Dries <jeroen.dr...@vito.be>
wrote:
> > Hi all,
> >
> > I'm seeing some strange behaviour in WCSDimensionsSubsetHelper in
> > combination
> > with a multi-dimensional mosaic:
> >
> > ->In the splitRequest method, all of the granules are queried for a
given
> > bounding box, and set of dimensions. In the case of a mosaic, a
granule
> > exists
> > for each tile in the mosaic, and for each dimension.
> >
> > So for example if my bounding box covers 2 tiles, and my dimension
range
> > also
> > intersects with 2 discrete values, I get 4 granules in total.
> >
> > -> Next the weird thing happens, for all of the 4 granules, a new
> >
> > subrequest
> > is made. The bounding box remains the original bounding box, but the
value
> > for
> > the dimension is correctly extracted from the granule.
> >
> > The result is that in the final output, I now have 2 identical pairs of
> > coverages, which seems wrong.
> >
> > I hope that this description is a bit clear, if no one objects, I'll log
> > this
> > in Jira.
> >
> > Not sure what the right solution is, perhaps the subRequests can be
stored
> > in
> > a Set, so that only unique requests are retained...
> >
> > best regards,
> > Jeroen
> >
> >
> > --------------------------------------------------------------------------
> > ---- Open source business process management suite built on Java and
> > Eclipse Turn processes into business applications with Bonita BPM
> > Community Edition Quickly connect people, data, and systems into
> > organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner
awards
> > http://p.sf.net/sfu/Bonitasoft
> > _______________________________________________
> > GeoTools-Devel mailing list
> > GeoTools-Devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geotools-devel
--------
[1] http://jira.codehaus.org/browse/GEOS-6564
[2] https://github.com/geoserver/geoserver/pull/639
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
