nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Converting scripts to arcpy for use in ags 10

KevinGooss

Is anyone else out there undergoing a conversion project to get python scripts written for 9.3 to work in 10?
I'm wondering if there is a guide to the common things that need to be changed? If it is absolutely necessary to upgrade to arcpy and what kinds of experiences people have had doing this?
I am trying to convert about 30 scripts and it's a big job. Besides the find and replace with gp to arcpy I'm finding alot of case sensitive issues like SearchCursors next() method which cannot be Next() like it used to.
Right now I'm stuck on

result1 = arcpy.GetCount_management("TempSelection")
    affectedFeatures = int(result1.GetOutput(0))

the GetOutput call produces an error and I'm trying to work around it.
Any suggestions?

Vind meer berichten getagd met

Accepted answers

All comments

curtvprice

So far, I have also needed to change the path to any toolboxes I've loaded. For example...
from:
gp.AddToolbox("C:/Program Files/ArcGIS/ArcToolbox/Toolboxes/Data Management Tools.tbx")
to:
gp.AddToolbox("C:\Program Files\ArcGIS\Desktop10.0\ArcToolbox\Toolboxes\Data Management Tools.tbx")

Am I doing something I don't need to? This was originally a script back at 9.1 or 9.2 that imported win32com.client. Do we no longer need to call out a specific toolbox?
Thanks, Gavin

If youre still using GP:

import os
ARCHOME = gp.ArcInstallInfo("Desktop")["InstallDir"] # replaces os.environ["ARCHOME"] at 9.3
gp.AddToolbox(os.path.join(ARCHOME,"ArcToolbox/Toolboxes/Data Management Tools.tbx")

The above code will work for 9.x or 10.x

But, note that system toolboxes do NOT need to be added, a new gp automatically has them all available, even though an export from modelbuilder includes the AddToolbox call.

RDHarles

Hmm. Odd. I assume that must have come out of model builder at some point as that is how we originally started our scripting. I've always assumed it was needed. I'll test without thanks.
G

You're not alone. I see it all the time in people's scripts, output from Model Builder and even in ESRI's documention (before 9.3/10.0).

GavinMcGhie

Hmm. Odd. I assume that must have come out of model builder at some point as that is how we originally started our scripting. I've always assumed it was needed. I'll test without thanks.
G

RDHarles

To my knowledge, you never needed to add the "AddToolbox" line to a script as long as you included the toolbox name after the tool name [e.g. gp.Clip_analysis()]. Before Arc10, adding the toolbox to the tool name was optional, now it's required.

GavinMcGhie

So far, I have also needed to change the path to any toolboxes I've loaded. For example...
from:
gp.AddToolbox("C:/Program Files/ArcGIS/ArcToolbox/Toolboxes/Data Management Tools.tbx")
to:
gp.AddToolbox("C:\Program Files\ArcGIS\Desktop10.0\ArcToolbox\Toolboxes\Data Management Tools.tbx")

Am I doing something I don't need to? This was originally a script back at 9.1 or 9.2 that imported win32com.client. Do we no longer need to call out a specific toolbox?
Thanks, Gavin

DanPatterson_Retired

Kevin, perhaps the transfer from 9.2 to 10 is causing more of a problem (aka the switch from enumerations to python lists etc). The only thing that I can think of off hand is that 9.3 had an ARCGISHOME environment variable which no longer exists in 10. i used it frequently to import toolboxes that may reside there along with the system toolboxes, however, unless an alias was established, the method in V10 is a little more circuitous...

...code before
  sub_folder = "ArcToolbox/Toolboxes/"
  install_dir = arcpy.GetInstallInfo()['InstallDir'].replace("\\","/")
  tbx_home = os.path.join(install_dir, sub_folder)
...code after

unless I have missed something obvious

KevinHibma

I don't think that is entirely true. There have been lots of my models and scripts that seem to have trouble.

Could you post something from a previous version which doesn't work in 10?

JasonScheirer

You do not need to do anything to make your scripts work in 10.0, all previous functionality with the geoprocessor object will continue to work unmodified.

KimOllivier

Don't need next() ?
Yes you do, in anything but a SearchCursor because you need access to a row object.

How would you do cur.insert(row) and cur.update(row) ?

If your 9.3 script is working, why bother rewriting it?

The arcgisscripting module is still there and it works just fine.
Maybe write new scripts using arcpy, and leave the rest alone.

ChrisMathers

In arcpy you dont need to use next() in your cursors. Using next() was to force the cursor to advance to the next row in the table when using a while loop. Now that you can use a for loop next is not needed as for has better built in iterator functions.

for row in arcpy.SearchCursor(featureclass):
do some stuff and automatically go to the next row

KevinGooss

The very latest issue i have been dealing with is converting a script that handled some shapefile exports using the fieldMap and fieldMappings objects in arcpy.
Once again the issue was with case sensitivity. The aliasName, outputField, and name methods have to begin with lowercase as they are listed in the docs.
No errors are thrown if you have the incorrect case making it tough to track down these kinds of bugs.
My best advice is to go through the docs for each method you call and see if you have the case correctly spelled.
the next() method is used on cursors so i would check that you have the exact spelling and case syntax when creating the cursor and using it.

KevinGooss

increased sensitivity to overwriting in-memory datasets
before you may have been able to get away with it but now you need to make sure you have:

arcpy.env.overwriteOutput = True

ChrisMathers

Two reasons why you should switch to arcpy:
1. You can use a for loop to iterate cursors in arcpy which is better than while loops.
2. arcpy.mapping lets you edit mxds programatically.

Case sensitivity is irritating though. getValue() not getvalue() or GetValue()

KevinGooss

That is helpful, thanks for that link.
For others running into this same conversion process it would be great if esri had a white paper or guide to the conversion process. But we can start one here:

1. replace 'import arcgisscripting' with 'import arcpy'
2. remove gp = arcgisscripting.create(9.3)
3. find and replace all 'gp.' with 'arcpy.'
4. modify environment vars like 'gp.extent' to read 'arcpy.env.extent'
5. check your case sensitivity for method calls like next() on a SearchCursor (not Next())

and more to follow.......

DanPatterson_Retired

check the online help, specifically
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//002z0000000n000000.htm
case-sensitive
you can import arcpy and do a help(arcpy) or dir(arcpy) to get further information or import its submodules and get further info there.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.