On 01/06/16 00:26, Daniele Romagnoli wrote: > On Tue, May 31, 2016 at 4:25 AM, Ben Caradoc-Davies <[email protected]> > wrote: >> In a nutshell: should elevation variables that are *internal* to each >> granule be indexed? Is this supported? If so, is indexer configuration >> required? Why would the granule index need to know? > I would say yes. In the past we have worked with NetCDF containing sigma > levels, exposing them as sigma dimension, similarly to what you did. > If my memory serves me right, when having issues with custom dimensions the > problem was related to the axisType not being declared but I should double > check. > Would this help?
Yes, please. - When using a custom dimension like sigma, should it be specified in the indexer.xml? - If an indexer dimension for sigma is required, what form should it take? - Does sigma need an entry in the granule schema in indexer.xml? - How did you overcome sigma not having a recognised axisType? Kind regards, -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
