![]() ![]() A Raster Catalog is essentially a group layer. The other option that I would recommend, based on your comment about wanting to have the zones separated would be to create a Raster Catalog. It also lets you perform raster operations such as Hillshade. This dataset will allow you to not only treat all of the individual tiles as a single seamless image, but it also maintains metadata about the individual tiles contained within. As mentioned in the comments above, there is the option to create a Mosaic Dataset. There may be 2 or 3 or more of these before the finalĭataset is even written, so it is conceivable to use up all your Many of the raster operations create temp files in your "workspace" directory The other issue is likely to be hard disk space.That is enough to crash the process right there. You don't haveĥ50GB of RAM, meaning there will be read/write from virtual memory. Ideally, that entire file would be held in memory. In order to mosaicĭata, you are merging everything into a single file, which means The first is going to be in your RAM buffer.To break it down, there are probably two places where you are running out of space. A simple guess would say there is not a desktop out there that could handle the amount of data you would have to process in order to mosaic all of those tiles. I will have to 2nd suggestions of using some other method of data access than creating a single mosaiced image. Would even 100 tiles process? -i.e should we look at breaking the zones up further? I have 1.5TB+ free space on my drive but the process crashes with a 9999 error. Where tifList should be read in from a csv file but this didn't work in python so I am running the above in a model instead. # The following inputs are layers or table views: "test2"Īrcpy.CopyRaster_management(OutputFile,RootOutput+"Tile1b.tif","#","256","256","NONE","NONE","16_BIT_UNSIGNED") # Replace a layer/table view name with a path to a dataset (which can be a layer file) or create the layer/table view within the script arcpy.MosaicToNewRaster_management(tifList+" " +mask,RootOutput,"Tile1.tif","PROJCS],PRIMEM,UNIT],PROJECTION,PARAMETER,PARAMETER,PARAMETER,PARAMETER,PARAMETER,UNIT]","16_BIT_UNSIGNED","0.5","3","MAXIMUM","#") In arcgis the code is as follows (this is run as a model and not in python as I can't get it to take the tifList input). ![]() So having the colored areas as 5 zones will minimize the no data areas in the larger AOI. Global Mapper/ERDAS are fine but it's not correct in arcgis. Sorry should add that we can't use a mosaic dataset (or equivalent in other software) as we need to create zones with defined no-data areas as ecw's so that they can be opened in any GIS software and combined with lower resolution/older data when new data doesn't exist seamlessly.Īn example of how some mosaiced files look in different sofware. Any other options or opensource software to try? I am looking into using Grass (never have before) but i.image.mosaic only seems to only handle 4 files.some of mine have 600 tiles. Mullti-core (4 total), Hyper-threaded (8 total) machine. I have used the latest versions of ERDAS (Imagine and Mapper), ArcINFO and Global Mapper on a 3.30 gigahertz Intel Xeon E31245, DELL, 16GB RAM, 64-bit Win 7 Professional. The area has been split into zones so that the smallest has approx 200 tiles. Leave the defaults and click OK.I need to mosaic about 550Gb of tif imagery together and the software I have tried keeps failing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |