[mapserver-users] Re: Raster dataset recommendations
Hello Jean, You can use the gdal_retile.py script to generate the tiles and the zoom levels, than use the minscale and maxscale for showing and hiding the appropriate level. The raster data are not suggested to have them in a database or in your case in postgis. If they are file system it is faster, it is easier to maintain, to update tiles ect. You can see also other posts that give suggestion about file system vs database for raster data. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Raster-dataset-recommendations-tp6064491p6183710.html Sent from the Mapserver - User mailing list archive at Nabble.com. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] Re: Raster dataset recommendations
Since it as less than 4gb, if you have the image in different tiles just merge them together. The image format should be tif. 1- Fisrt enable internal tiling with the command gdal_translate -co TILED=YES original.tif tiled.tif 2-than add overviews gdaladdo -r average 2 4 8 16 32 64 128 3-create a tileindex gdaltindex myindex.shp *.tif 4-than create a spatial index shptree myindex.shp and finally add the layer to the map LAYER NAME myorthos TYPE RASTER DUMP TRUE STATUS ON TILEINDEX ../data/myindex TILEITEM Location -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Raster-dataset-recommendations-tp6064491p6064777.html Sent from the Mapserver - User mailing list archive at Nabble.com. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Re: Raster dataset recommendations
If you are merging tiles together to create 1 large tif, why would you need to create an index to it? I would think you would just directly reference the tif. so, rather than TILEINDEX ../data/myindex skip the index building steps just DATA ../data/big.tif On Fri, Feb 25, 2011 at 9:08 AM, Edi.Karadumi edikarad...@gmail.com wrote: Since it as less than 4gb, if you have the image in different tiles just merge them together. The image format should be tif. 1- Fisrt enable internal tiling with the command gdal_translate -co TILED=YES original.tif tiled.tif 2-than add overviews gdaladdo -r average 2 4 8 16 32 64 128 3-create a tileindex gdaltindex myindex.shp *.tif 4-than create a spatial index shptree myindex.shp and finally add the layer to the map LAYER NAME myorthos TYPE RASTER DUMP TRUE STATUS ON TILEINDEX ../data/myindex TILEITEM Location -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Raster-dataset-recommendations-tp6064491p6064777.html Sent from the Mapserver - User mailing list archive at Nabble.com. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] Re: Raster dataset recommendations
I would agree with Edi and recommend TIFF. It's easy to move around and deal with, and is the fastest of the raster formats. (unless something new has come up?) I would also agree with Mark: a tileindex is for mosaicing many TIFFs, and if your result is 1 single TIFF the tileindex is unnecessary. Edi's recommendation about a internal tile is VERY important. It costs slightly more disk space, but makes a tremendous improvement in the random access within the TIFF's extent. The overviews accomplish a similar performance gain, but for views in which the TIFF's extent is only a subset of what's showing on the map. -- HostGIS, Open Source solutions for the global GIS community Greg Allensworth - SysAdmin, Programmer, GIS Person, Security Network+ Server+ A+ Security+ Linux+ PHP PostgreSQL MySQL DHTML/JavaScript/AJAX No one cares if you can back up — only if you can recover. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
[mapserver-users] Re: Raster dataset recommendations
Jean, thats my problem too. I haven't resolved it yet the perfect way, but i have created mosaics of the data with lowered resolution, and a lower number of tiles . The number of tiles that are requested to see the map increases when you zoom out, so it needs to seek and read the tiles. Having them in different HD will make the displaying of the map faster because you will have more than one hd that does the seek/read process. The idea is that in your zoom levels you dont need more than four tiles to display the image. So youll have to calculate the mapserver resolution, image resolution and map control size. I have more than 3 terabytes of data in 15000 tiles and i created another mosaic with 1.5 terabytes and ~ 4000 tiles. And so on. My main problem is determining the scale when to switch from one mosaic to the other and i resolved it with testing the speed of the response. Maybe this time someone will have an idea to this post. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Raster-dataset-recommendations-tp6064491p6066256.html Sent from the Mapserver - User mailing list archive at Nabble.com. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
