Hi,
I have been following these guidelines -
http://elogeo.nottingham.ac.uk/xmlui/bitstream/handle/url/226/gs_steroids_sgiannec_foss4g2013_01.03.pdf?sequence=1
<http://elogeo.nottingham.ac.uk/xmlui/bitstream/handle/url/226/gs_steroids_sgiannec_foss4g2013_01.03.pdf?sequence=1>
So I have ended up with a test directory (1.3TB) that includes the tiles
in folders and sub-folders.
I used the geoserver web interface to create a new image pyramid
coverage and itv ran for over 30 hours. It has created shapefiles for
every level and pyramid prj and property files. When tested in layer
preview, it loads up a black tile in wrong coordinates.
is this time consuming behaviour normal?
Any ideas why the pyramid turned out to be a black image with wrong coords?
My total data set size is over 5TB. So does that mean that I will have
to make the 1.3TB super fast in order for the total data to be served
fast enough?
My geo-server version is 2.4.1 and the hardware meets suggested
requirements as well.
Any advice would be greatly appreciated if you have experience in
similar size data sets.
All the best,
Antony
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
