Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I am working with ArcToolBox's tools and their python supports. I found there is some restriction on file size of shape files/feature classes etc. It makes me interested to know about is there any restriction with file size on these tools/python methods also? As an example, suppose I am using "Con" method of "Spatial Analyst Tools". Does this method has any size restriction? I read "tool help" document. But I found nothing about file size here.

share|improve this question
1  
What problem are you trying to solve? What questions are you being asked? What tools or methods are you using? What type of databases or files are you working with? Have you tried searching? –  blah238 Jan 3 '13 at 5:08
    
@blah238 Actually these are not what actually I am searching for. I want to know about the ArcToolBox's tools and their python supports. Such as "Con" method of "Spatial Analyst Tools". Does this method has any size restriction? I read "tool help" document. But I found nothing like that. But as there is some restriction on file size of shape files, feature classes etc., so I thought if there any restriction in those methods also. –  Emi Jan 3 '13 at 5:28
1  
Spatial Analyst implies raster. What type of raster data are you working with? –  blah238 Jan 3 '13 at 5:47
    
@blah238 Now I am working with "file system raster". But I actually want to know the common behavior of these tools. Because I am going to make some add-in that I can use in future. So, its important for me to know does it create problem for any raster/ feature class –  Emi Jan 3 '13 at 6:01

1 Answer 1

up vote 8 down vote accepted

This help topic discusses some of the raster format limitations for Spatial Analyst: Data formats supported by Spatial Analyst

While it is focused mainly on vector overlay operations, this blog post has many suggestions, including improvements made at 10.1 and 10.1 SP1. In particular, if you are working with very large datasets, then using 64-bit geoprocessing at 10.1 SP1 is recommended. Also notable is ESRI's stance (see comments section) on not providing specific numbers regarding internal limitations as there are (allegedly) far too many variables involved.

Beyond that, there is very little that you as a developer can do to ensure that your customers will not have problems processing very large datasets, just as they would without using your custom tool, especially if, as you say, you have to support ANY dataset in ANY format. All bets are off.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.