Hi Padhrig,
On Thu, Feb 25, 2016 at 5:09 PM, Padhrig Mccarthy wrote:
> Dear Danielle and Peter-
>
> Thank you for the helpful tips! The lead on the XML indexer is going to be
> critical, because we have NetCDF files with several atmospheric variables
> (RAP model output) encapsulated in a single
Dear Danielle and Peter-
Thank you for the helpful tips! The lead on the XML indexer is going to be
critical, because we have NetCDF files with several atmospheric variables
(RAP model output) encapsulated in a single file per time step.
I think the main answer to my question comes from Danielle
Hi Padhrig,
which type of data are you serving? (GeoTiffs, NetCDF, ...?)
If you are serving different geophysical parameters / variables from the
same store (as an instance, temperature, pressure, humidity,...) , the
indexer.xml approach suggested by Peter may better fit your needs since it
allows
Hi Padhrig,
I recommend using XML indexer, not .properties file for configuring
image mosaics:
http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_indexer.html
Then provide appropriate parameters in your indexer.xml and you can
store granules anywhere on your filesystem:
Hi-
I am a novice GeoServer user, and I am tasked with setting up multiple
timeseries ImageMosaics for our project. I have a MOSAIC_DIR set up and
configured according to the tutorial at
http://docs.geoserver.org/latest/en/user/tutorials/imagemosaic_timeseries/imagemosaic_timeseries.html
.
Based