···
On Thu, Feb 25, 2016 at 5:09 PM, Padhrig Mccarthy <paddy@anonymised.com> 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 file per time step.
I think the main answer to my question comes from Danielle – the mosaic dir needs to be under the GeoServer data dir,
Well, I didn’t said that.
Let me give you an example:
The mosaic dir can be as an instance /path/to/mosaicconfig, containing indexer.xml datastore.properties and _auxiliary.xml file.
The same folder may also contain netcdf datasets. However, in case the rasters are into a different location, as an instance on /path/to/netcdfdatasets, just make sure to add the IndexingDirectories parameter to indexer.xml, referring to /path/to/netcdfdatasets.
and contain the necessary properties files to identify it as a mosaic. I take it that GeoServer will ‘discover’ that directory and use said properties files to find the raster files, if their location is different from the location of the mosaic dir? Does that sound correct? There is no place in GeoServer where it’s necessary to specify the path to my mosaic dir containing the properties files?
You just need to configure an ImageMosaic coverageStore by indicating /path/to/mosaicconfig as URL parameter.
http://docs.geoserver.org/latest/en/user/_images/imagemosaicconfigure1.png
GeoServer will create an ImageMosaic on top of that folder, checking the configuration available in the related configuration files so it will also parse the IndexingDirectories parameter (if specified), resulting into looking for raster files somewhere else.
In case you need additional clarifications, you could consider checking this tutorial too which provides some more details about multidimensional mosaics:
http://geoserver.geo-solutions.it/multidim/en/index.html
Hope this clarifies a bit the topic.
Please, let us know if you still have issues.
Cheers,
Daniele
I’ll go about trying to debug what I’ve mis-configured that’s prevented my mosaic dir from being ‘discovered!’
Thank you so much for your help.
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
On Thu, Feb 25, 2016 at 6:11 AM, Daniele Romagnoli <daniele.romagnoli@anonymised.com.> wrote:
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 to specify multiple schema, coverages, domains.
If you are instead serving single variable time series, indexer.properties should be enough.
Please, see also my notes below:
On Wed, Feb 24, 2016 at 5:10 PM, Padhrig Mccarthy <paddy@anonymised.com> wrote:
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 on information in that tutorial, it seems MOSAIC_DIR can be anywhere on our system. However, when I go to create the ImageMosaic data store in GeoServer,
all of the configuration seems to use relative paths from MOSAIC_DIR.
What do you mean?
How do I tell GeoServer where my MOSAIC_DIR is? Or do I need to place MOSAIC_DIR in some location where GeoServer expects it? Alternatively, do I need to define MOSAIC_DIR env var for the user running the tomcat container? I have tried this last option, yet still have no joy.
The MOSAIC_DIR referred in that tutorial is simply a placemark, a reference name to identify a place where the mosaic configuration will be setup (as an instance /data/mymosaic) as well as the folder to be used when configuring the ImageMosaic coverage store (the URL connection parameter).
That folder should contain properties files as reported in the tutorial.
Usually that folder also contain granules (raster files) to be mosaicked.
However, there is also support for separate locations for the raster data.
Suppose you have a read only folder with huge amount of data that you won’t copy somewhere else, as an instance /mnt/storage/myrasterdata.
So, you can configure the Mosaic on your MOSAIC_DIR (again, as an instance: /data/mymosaic) and instruct the mosaic to look for raster files on a different location by adding
an “IndexingDirectories” parameter to your indexer file specifying /mnt/storage/myrasterdata as value.
Does it helps?
Please, let us know.
Cheers,
Daniele
Thank you in advance for any hints.
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
Ing. Daniele Romagnoli
Senior Software Engineer
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
Ing. Daniele Romagnoli
Senior Software Engineer
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.
