Dear all, just wanted to let you know that I found a solution for this problem.
As mentioned, we are using Oracle Spatial for storing the granule index. In the indexer.properties file for the ImageMosaic the time parameter was defined as "time" and upon creation of the index table in Oracle this was automatically capitalized into "TIME". While this was no problem with normal requests by time parameter without sorting enabled, this wasn't the case with sorting enabled (as described in my earlier posts). So, to fix this issue I altered the indexer.properties entries for "time" to "TIME" and it is working fine now. The store does not necessarily need to be recreated for fixing this. It is sufficient to replace every occurence of the column name "time" with "TIME" in the following files after the ImageMosaic was created: - indexer.properties - <ImageMosaicName>.properties - .mosaic/<ImageMosaicName>.properties After having set the sorting parameter for the layer to "TIME D" or "TIME A" respectively and having reloaded the configuration and catalog, the sorting should work as expected. Regards, Max -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Possible-Image-Mosaic-time-bug-tp5089638p5151167.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
