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.

The geoprocessor programming model was an excellent tool for python scripting using ArcGIS 9.3. There is still no equivalent diagram for ArcGIS 10 - although there is a request on the ArcGIS ideas site.

A previous question on this site asked if the 9.3 diagram is good to use for ArcGIS 10. The answer was that some of it is relevant and it is best not to use it. However, I really like the diagram and would like to reference it when scripting ArcGIS 10. Therefore my specific question is:

What parts of the ArcGIS 9.3 diagram are not relevant to ArcGIS 10? Correct me if I'm wrong, but from what I understand, if an equivalent diagram was made for ArcGIS 10, there would be new functions added to the diagram; the diagram would only get bigger.

share|improve this question
    
Have you looked at the following? I came across an updated version here - forums.arcgis.com/threads/… .. (scroll all the way down to the last post) –  kolor Nov 21 '11 at 0:44
add comment

2 Answers

up vote 3 down vote accepted

The main differences between arcgisscripting and arcpy, are instantiation and a more rigid adherence to a naming convention, i.e. [tool_name]_[category](*args, **kwargs)

Apart from that the answer from Dan Patterson is correct, you'll have to look at each tool to determine if the functionality or parameters have changed for each tool.

ESRI being ESRI, are great at repackaging the same functionality in a different wrapper and calling it a new product. ArcPy is an elaborate stub for COM objects, and therefore the lag in performance.

update

The last sentence wasn't intended to sound like a stab at ESRI. It was more of an indicator to potential performance lags. Using a COM library from python has the added overhead of translating python data types to c/c++ data types. And often requires some complex conversions. Being aware of this, and having an understanding of COM will help you squeeze performance out of your scripts where necessary.

share|improve this answer
    
+1 Putting that in very blunt but true terms; with 10.1 being 64bit on the server side; hopefully the COM issue for much of the engine will be gone. –  D.E.Wright Nov 22 '11 at 18:05
    
Thanks for expanding on Dan's answer a bit OptimizePrime. Do you know of any webpages/resources that give actual examples? Perhaps side-by-side 9.3 vs 10.0 python script? I do not yet have ArcGIS 10, so it's difficult for me make my own example. –  GIStack Nov 24 '11 at 2:58
    
@GIStack I haven't really found many that are comprehensive. I suggest looking at this or looking at the ArcPy help documents to get a feel for the changes. Start by looking at the common tools you use in existing scripts. –  OptimizePrime Nov 24 '11 at 20:29
add comment

You will have to compare specific differences between version 10 and version 9.3 on the online help files. Creating the geoprocessor is different, however, you can invoke 9.3 functionality within the arcpy module by importing arcgisscripting from within arcpy. This maintain some backward compatability issues, but you will need to compare each geoprocessing tool to determine what, if any, changes have been made.

share|improve this answer
add comment

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.