If you have updates of individual photos, I would not create a  
geotiff. The best would be to find a solution without transforming  
your photos.

Cheers

Zitat von Robert Buckley <[email protected]>:

> Hi,
>
> I like your approach. Although one problem from my end  is how to   
> manage the datasets when we get new photos. I guess the whole   
> process will have to be done again from step one!
>
>
> If I keep the photos as single files, I would then be able to just   
> replace the old photos and recreate the new image mosaic.
>
> OR
>
> create a number of imagemosaic e.g for each Region (we have 5) and   
> then serve the 5 regions together in a grouped layer.
>
>
> It´s hard to tell which is easier....Orthophoto management is a real pain!
>
> yours,
>
> Robert
>
>
>
> ________________________________
>  Von: "[email protected]" <[email protected]>
> An: Robert Buckley <[email protected]>
> Cc: "[email protected]"   
> <[email protected]>
> Gesendet: 11:18 Montag, 30.Januar 2012
> Betreff: Re: [Geoserver-users] How to best serve Orthophotos with geoserver?
>
> Hi Robert, answers inside
>
> Zitat von Robert Buckley <[email protected]>:
>
>> Hi,
>>
>> I would like to serve all by Orthophotos with geoserver and then    
>> cache them with GeoWebCache.
>>
>> Each Photo is a 3 band 8 bit raster with a 40cm resolution at   
>> around  74mb each.
>>
>> - Is there any benefit to reducing the bands from 3 to 1? ( the   
>> size  of the raster remains the same)
>
> The pixel dimensions remain the same, but  one pixel is represented   
> by one byte instead of three bytes. The answers is definitely YES.
>
>>
>>  - Is there any way I can reduce the size from 75mb? I have around   
>>  1300 Photos and it would be nice to lower the upload time...
>
>
>
> I have the same problem here and thinking about the following solution.
> use gdal_merge.py or gdalwarp to create one big picture having 3 bands
> use rgb2pct.py to create a big picture having one band.
> use gdal_translate to create a geotiff (using inner tiles and LZW   
> compression).
> use gdaladdo to create the the overviews you need
>
> The result should be one geotiff file (Probably a bigtiff if the   
> size is bigger than 4GB).
>
> Geoserver supports geotiff out of the box. Geoserver 2.2.x supports   
> bigtiff, Geoserver 2.1.x supports it recently.
> http://jira.codehaus.org/browse/GEOT-3931
> If you are on 2.1.x and you need bigtiff support, you have to test   
> with a nightly build.
>
>
> Hope this helps
> Christian
>
>>
>> thanks for your suggestions,
>>
>> Rob
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to