[Geoserver-users] Geoserver-users Digest, Vol 88, Issue 40

Rick,
I'm not a GeoServer dev, but perhaps I can offer some help as I'm doing something similar.

I briefly looked into PostGIS Raster, but after discussions with Christian Mueller I came to the realization that it would not work for us as ImageMosaic-JDBC does not support temporal (time) queries.

1) GeoServer can indeed handle a large number of files via the ImageMosaic store because it only "looks" on disk for the filename specified in the DB column. Our use case is for Radar imagery that we receive every 5 minutes and even with an extended backlog it keeps up quite nicely. The only trick for us was having to manage two separate purge tasks (DB and FileSystem), but it sounds like you never delete so that's even easier.

2) Assuming I understand your question, that is correct. After creating a layer via the ImageMosaic store, adding a new entry to the referenced DB table and placing the appropriately named file on disk causes the new data to automatically become available.

3) I believe the author was talking about adding a feature layer in GeoServer from the same dataset as the coverages are generated. So, once your ImageMosaic coverage is setup, you can create another layer from the DB table which only displays the feature which in this case would be the bounding box that shows the area the image would cover. In our case this was useful because it allowed us to query additional columns (metadata) in the table via getFeatureInfo requests. GetFeatureInfo requests against coverages currently only return raster band data (rgb or grayscale values).

Hopefully I was able to help and didn't just make things more confusing for you. Good luck with your application.

Kevin M. Weiss
Software Engineer
HARRIS IT Services

1408 Fort Crook Road South
Bellevue, NE 68005
kevin.weiss@anonymised.com

-----Original Message-----

Date: Fri, 13 Sep 2013 11:59:40 -0500
From: Rick Wayne <fewayne@anonymised.com>
Subject: [Geoserver-users] Rasters and time...again
To: geoserver-users@lists.sourceforge.net
Message-ID: <1386845A-1D26-4652-8EAD-A09F70670BF0@anonymised.com>
Content-Type: text/plain; charset="us-ascii"

Hi all,

I've been browsing the archives looking for pointers on getting some time-series raster data published. And as usual, I'm left with noob questions :-).

Background: I'm looking to publish results of various weather-derived models. The outputs are at 15-kilometer resolution, and cover about 800 by 1000 kilometers. The models run every day and we have data going back 15 years. So by the time I retire we're talking 10,000 rasters of that size. (Or more; the National Weather Service is contemplating 4K resolution!)

I had assumed that I'd be using PostGIS rasters for this. It seemed improbable that GeoServer would nimbly handle 10,000 files for each model (we have about 8 of them). First question: Is that correct, or will it be happy managing all those files? (Obviously I'd have to use the REST API to manage them!) Since the ImageMosaicJDBC plugin doesn't handle timesteps, that might not work at all for me.

Second question: the image mosaic time series tutorial publishes a fixed set of TIFs. Just to be clear: as TIFs with new timestamps are added to the store, do they automatically become available?

Thirdly, said tutorial ends with "Create and publish a Layer from mosaic indexes". I'm not getting the intent there -- a combination of my thickness and the tutorial written by someone for whom English is not their first language. Don't get me wrong, it's overall very clear and I'm grateful to the author! (I'm sure my competence in their native language is laughable at best.) But I'm baffled by what this particular step does -- what are the "footprints of the images", and why would the user want to get them? This has to do only with spatial indexing, and nothing to do with the time dimension, correct?

Finally, there's one possible optimization: Although we need to keep the data going back for basically ever, and need to be able to do various calculations on it and map the results by hand, if push comes to shove, we only have to present the most recent visualizations automatically on the Web. So for example, perhaps I can use the IMJDBC plugin if I add a timestamp column to the raster table, create a "most recent" table, and point IMJDBC at a view that does something like "...where raster_table.timestamp = most_recent.timestamp". Does anybody know if that will work? The alternative would be to just use a file-based raster for the current day, and keep overwriting it.

Thanks, yet again, for your help. And just so you know, GeoServer enables a couple of applications that have pretty high political visibility and are making me look quite brilliant to my stakeholders* -- so thanks to the GeoServer team!

rw

--------------------------
*Only you folks know the truth! Shhhhh! >;-}
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7351 bytes
Desc: not available

------------------------------

------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk

------------------------------

_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

End of Geoserver-users Digest, Vol 88, Issue 40
***********************************************