Hi folks,
I will soon have a large pile of GeoTIFFs that tile a metropolitan area, perhaps 100-200GB in all. I'm looking for a WMS server that will serve this data as described below, and I'm posting here to see if GeoServer can be that WMS server (we have some additional WMS tasks that GeoServer seems ideal for, and it'd be great if it could do both).
The client needs to be able to make a WMS request to the server without knowing which particular tile the data will come from. The server would (a) gather together the image data from multiple GeoTIFF files and (b) reproject the image data into the client's SRS before sending it along. Can GeoServer do this? Version 1.5beta is fine given its expected finalization timeline.
Furthermore, the following would be nice but is not essential. There are actually two sets of tiles, one of which is better than the other, and I'd like the WMS server to serve the better of the two but automagically fall back to the not-so-good one if the better one is not available in the requested area.
Let me know if you need any clarification.
Please CC me as I'm not subscribed to the list, and apologies for any errors or misassumptions above (I'm relatively new at this).
Thanks for any help or suggestions,
Reid
Reid Priedhorsky ha scritto:
Hi folks,
I will soon have a large pile of GeoTIFFs that tile a metropolitan area, perhaps 100-200GB in all. I'm looking for a WMS server that will serve this data as described below, and I'm posting here to see if GeoServer can be that WMS server (we have some additional WMS tasks that GeoServer seems ideal for, and it'd be great if it could do both).
The client needs to be able to make a WMS request to the server without knowing which particular tile the data will come from. The server would (a) gather together the image data from multiple GeoTIFF files and (b) reproject the image data into the client's SRS before sending it along. Can GeoServer do this? Version 1.5beta is fine given its expected finalization timeline.
What you're describing is the mosaic plugin afaik.
Some instructions on how to setup data in order to use it is here:
http://docs.codehaus.org/display/GEOSDEV/Using+the+ImageMosaic+plugin
Furthermore, the following would be nice but is not essential. There are actually two sets of tiles, one of which is better than the other, and I'd like the WMS server to serve the better of the two but automagically fall back to the not-so-good one if the better one is not available in the requested area.
Looks slightly like pyramid plugin, but it's not it. So, it's not something we can provide at the moment, but it's definitely something
that can be implemented working against the shapefiles the mosaic plugin
uses (which contains the extent of each component of the mosaic) and doing some image composition. More or less, gather the area covered by
the good images in the rendering bounds, if not complete, gather the
tiles of the not very good mosaic that fill the hole, draw them, and then overwrite with the good ones.
Cheers
Andrea
Furthermore, the following would be nice but is not essential. There are actually two sets of tiles, one of which is better than the other, and I'd like the WMS server to serve the better of the two but automagically fall back to the not-so-good one if the better one is not available in the requested area.
Looks slightly like pyramid plugin, but it's not it. So, it's not something we can provide at the moment, but it's definitely something
that can be implemented working against the shapefiles the mosaic plugin
uses (which contains the extent of each component of the mosaic) and doing some image composition. More or less, gather the area covered by
the good images in the rendering bounds, if not complete, gather the
tiles of the not very good mosaic that fill the hole, draw them, and then overwrite with the good ones.
Or, in the (near?) future when SLD RasterSymbolizer has been implemented and nodata values can be rendered as transparent, you could simply stack the 2 mosaics on top of each other with the better one on top (thus requesting both mosaic layers in one WMS request) and geoserver would render the lower quality mosaic where the higher quality one is transparent (nodata). Performance-wise probably a bit worse than a pyramid-like plugin, but easier imho.
I've planned to do some renewed trials with mosaic/pyramid this week, maybe mosaics already support nodata as transparent rendering...?
Cheers,
Vincent.
Cheers
Andrea
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Vincent Schut wrote:
Furthermore, the following would be nice but is not essential. There are actually two sets of tiles, one of which is better than the other, and I'd like the WMS server to serve the better of the two but automagically fall back to the not-so-good one if the better one is not available in the requested area.
Looks slightly like pyramid plugin, but it's not it. So, it's not something we can provide at the moment, but it's definitely something
that can be implemented working against the shapefiles the mosaic plugin
uses (which contains the extent of each component of the mosaic) and doing some image composition. More or less, gather the area covered by
the good images in the rendering bounds, if not complete, gather the
tiles of the not very good mosaic that fill the hole, draw them, and then overwrite with the good ones.
Or, in the (near?) future when SLD RasterSymbolizer has been implemented and nodata values can be rendered as transparent, you could simply stack the 2 mosaics on top of each other with the better one on top (thus requesting both mosaic layers in one WMS request) and geoserver would render the lower quality mosaic where the higher quality one is transparent (nodata). Performance-wise probably a bit worse than a pyramid-like plugin, but easier imho.
I've planned to do some renewed trials with mosaic/pyramid this week, maybe mosaics already support nodata as transparent rendering...?
Hi folks,
Thanks for the pointers -- sounds great. Looks like I probably could have found the info with enough searching, but you guys have saved me a lot of time. Your help is very much appreciated!
Reid