On Thu, Jun 2, 2016 at 3:28 AM, Ben Caradoc-Davies wrote:
> On 01/06/16 20:12, Daniele Romagnoli wrote:
>
>> On Tue, May 31, 2016 at 11:06 PM, Ben Caradoc-Davies
>>
>>> - When using a custom dimension like sigma, should it be specified in the
>>> indexer.xml?
>>>
>> Yes. each domain/dimension in
On 01/06/16 20:12, Daniele Romagnoli wrote:
> On Tue, May 31, 2016 at 11:06 PM, Ben Caradoc-Davies
>> - When using a custom dimension like sigma, should it be specified in the
>> indexer.xml?
> Yes. each domain/dimension involved in your mosaic should be declared.
>> - If an indexer dimension for
On Tue, May 31, 2016 at 11:06 PM, Ben Caradoc-Davies
wrote:
> On 01/06/16 00:26, Daniele Romagnoli wrote:
>
>> On Tue, May 31, 2016 at 4:25 AM, Ben Caradoc-Davies
>> wrote:
>>
>>> In a nutshell: should elevation variables that are *internal* to each
>>> granule be indexed? Is this supported? If
On 01/06/16 00:26, Daniele Romagnoli wrote:
> On Tue, May 31, 2016 at 4:25 AM, Ben Caradoc-Davies
> 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 nee
Hi Ben,
On Tue, May 31, 2016 at 4:25 AM, Ben Caradoc-Davies
wrote:
> Daniele,
>
> these dimensions are in effect a Z dimension. The data is sourced from
> GRIB2 but by the time it is ingested by ImageMosaic, it is equivalent to
> NetCDF (CDM API). Below I have included a small but self-consisten
Daniele,
these dimensions are in effect a Z dimension. The data is sourced from
GRIB2 but by the time it is ingested by ImageMosaic, it is equivalent to
NetCDF (CDM API). Below I have included a small but self-consistent
subset from the CDL generated with NetCDF-Java ToolsUI (current master
4.
Hi all
I have a similar (I think) issue I’d like to solve. Like Ben, I have netCDF
files with bands, and in each band are timeslices. Here’s an openDAP look
inside a sample file:
http://dapds01.nci.org.au/thredds/dodsC/uc0/rs0_dev/alberscube/LANDSAT_5_TM_NBAR_ALB_15_-41_1990-03-02T23-11-39.
I Ben.
I'm not sure to have fully understood your problem/question.
Can you give us an example of a ncdump output (a shorter form of the
interesting part) for 2 involved files?
As far as I remember, the current NetCDF low level readers only deal with
inner dimension referencing to times and elevat
I have several NetCDF files that comprise an ImageMosaic time series.
This works fine for variables with only spatial dimensions, and I can
get NetCDF output from WCS:
foo(y, x) --ImageMosaic-NetCDF-out--> foo(t, y, x)
However, when there is an extra dimension in the source NetCDF files
(sam
