|
POST
|
Try removing the toolbox alias.
arcpy.ImportToolbox(r"C:\Documents and Settings\Derek\FRAME\FORTEST.tbx")
...
arcpy.TEST()
Also try recreating the toolbox and model in 10.0 and not touching it with 10.1. Can you run the model from ArcMap 10.0?
... View more
02-26-2014
05:50 AM
|
0
|
0
|
1908
|
|
POST
|
If the toolbox was created in 10.1 then 10.0 cannot read from it.
... View more
02-26-2014
04:49 AM
|
0
|
0
|
1908
|
|
POST
|
For the second the da cursors have a different parameter format. Review the ArcGIS documentation of cursors. http://resources.arcgis.com/en/help/main/10.2/index.html#//018w00000011000000
... View more
02-25-2014
07:41 AM
|
0
|
0
|
2293
|
|
POST
|
You can make a reference dictionary with the alias name as the key. dict = {f.aliasName: f.name for f in arcpy.ListFields(layer)}
... View more
02-24-2014
01:16 PM
|
0
|
0
|
960
|
|
POST
|
Can you post an example of the table your are selecting from?
... View more
02-05-2014
05:16 AM
|
0
|
0
|
1738
|
|
POST
|
What happened when you tried to make your selection code in one query and then switch selection?
... View more
02-03-2014
06:16 AM
|
0
|
0
|
1738
|
|
POST
|
Easiest way is to open IDLE that installed with your version of ArcGIS. At the top it will say whether the default is 32 or 64 bit. As 10.0 and 10.1 use different versions of Python you almost definitely have the 32 bit version, so would have this tag. ...[MSC v.1500 32 bit (Intel)]... 64 bit would have this. ...[MSC v.1500 64 bit (AMD64)]... Using 64 bit geoprocessing should solve this issue for you so I would look into getting that.
... View more
01-30-2014
05:26 AM
|
0
|
0
|
2560
|
|
POST
|
Most likely cause is the local user isn't authorized to access the database using their OS credentials.
... View more
01-30-2014
04:56 AM
|
0
|
0
|
1733
|
|
POST
|
Does your SDE connection use OS authentication or database authentication? And is the path in your script the actual path to the SDE connection file? Not something like "Database Connections\SDE_admin.sde"?
... View more
01-29-2014
01:29 PM
|
0
|
0
|
1733
|
|
POST
|
What are the specs of the machine you are running this on? You may be running in to memory issues, do you have the 64-bit background geoprocessing module installed?
... View more
01-29-2014
01:27 PM
|
0
|
0
|
2560
|
|
POST
|
I would first try moving it out of a GRID to a geodatabase raster or ascii. How big is your dataset? Have you tried breaking it up unto smaller sections? If performance is also something you want to gain you can look at multiprocessing. Esri has a blog entry on performing analysis on a large dataset using multithreading that you may find interesting. http://blogs.esri.com/esri/arcgis/2011/08/29/multiprocessing/
... View more
01-29-2014
09:33 AM
|
0
|
0
|
2560
|
|
POST
|
It seems like something is wrong with your source data. What format is it in? Have you run this from ArcGIS with the same data source without issues?
... View more
01-29-2014
09:01 AM
|
0
|
0
|
2560
|
|
POST
|
The best option I know of is using trace. It will can create a file of the code executed. Here is an example. http://pymotw.com/2/trace/ Profile also has some good options. http://docs.python.org/2/library/profile.html
... View more
01-27-2014
11:46 AM
|
0
|
0
|
3823
|
|
POST
|
Dissolve has some memory management issues, especially with 64-bit geoprocessing where it becomes very unstable with large datasets. With the 32-bit standard geoprocessing it just skips features that would consume too much memory to dissolve as opposed to outright crashing. That has been my experience anyways.
... View more
01-27-2014
04:08 AM
|
1
|
0
|
5388
|
|
POST
|
I'd recommend contacting the vendor's customer support.
... View more
01-21-2014
01:50 PM
|
0
|
0
|
1301
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 05-17-2011 10:36 AM | |
| 1 | 08-16-2012 10:48 AM | |
| 1 | 10-31-2012 08:39 AM | |
| 1 | 07-16-2012 01:52 PM | |
| 1 | 03-15-2012 10:57 AM |
| Online Status |
Offline
|
| Date Last Visited |
08-22-2024
11:12 PM
|