Latest Contributions by LucasDanzinger

‎01-30-2014

You could make a table view first, and filter the fields, similar to Example 2 in the help.

‎01-28-2014

This is kind of a shot in the dark, but do you have ArcGIS Server installed on that server? If so, my guess is that the file association when you open through PythonWin points you towards the ArcGIS Desktop install of Python, which can access this tool from any license level. If you are running a scheduled task, and not using a .bat file to explicitly set what version of Python you want to run the script with, it is possible it is trying to run the script with the ArcGIS Server Python install (there will be a 32 bit and 64 bit install of Python if you have both products installed). As this functionality matrix points out, the basic license level of Server does not include geoprocessing, so you would want to run these scripts using the Desktop (32-bit) version of Python. My suggestion would be to make a .bat file that calls the 32 bit version of Python to ensure you are using your desktop license. If this is all the case, this blog will help further explain this.

‎10-18-2013

I'm not sure if this will be helpful if you aren't familiar with Python, but in this case, you would probably want to use a Search Cursor. Since you aren't familiar with Python, a better route might be to use a nested model by creating a second model/iterator, and adding that model to your original model.

‎10-03-2013

If you type import sys, then print sys.version below that, are you running in 64-bit? If so, your issue might be that the tools in the metadata toolset do not run in 64-bit.

‎07-29-2013

Since ArcGIS for Server 10.1 was released, the ArcPy library has been accessible through a 64-bit platform. In addition, the 64-bit Background Geoprocessing patch was released at 10.1 Service Pack 1, which allows ArcGIS for Desktop users to utilize geoprocessing in 64-bit. This means that if you have ArcGIS for Desktop and either ArcGIS for Server or the Background 64-bit Geoprocessing Patch installed, you have two different installs of Python 2.7. The default paths for those are: C:\Python27\ArcGIS10.1 - (32-bit) C:\Python27\ArcGISx6410.1 - (64-bit) This ArcGIS Resource Center blog post explains how to go about utilizing 64-bit geoprocessing in Python, and the ArcGIS Desktop Help has a very informative article on what the advantages are of running geoprocessing operations in 64-bit, as well as some of the limitations. Very briefly, one major advantage is that with 64-bit Background Geoprocessing, you are able to utilize larger amounts of RAM for large geoprocessing jobs that may have failed in 32-bit. However, some limitations that should be noted include processing with certain data types (such as personal geodatabase, Excel tables, and OLEDB) and using certain tools (Metadata conversion tools, geodatabase administration tools, to name a few). The implications of this are that you must be aware of the 64-bit limitations when determining what version of Python you want to use. When running geoprocessing tools in ArcGIS for Desktop, the application knows that if you have the 64-bit patch installed and are using Background Geoprocessing on a tool or data type that does not support it, to just run in 32-bit instead. However, running a standalone script in 64-bit that calls for unsupported data types or tools results in an error. Here are a few different scenarios to be aware of that may cause you some confusion with the two versions of Python, especially if you are executing the script against the 64-bit version unknowingly. If the most recent version of Python that was installed was 64-bit, then the file association of the .py file will be with that 64-bit version. This means that if you double-click a Python script, or call a script from the command line/scheduled task without specifying which version of Python to use, it will run in 64-bit. This is due to how Windows assigns file associations. However, if the script uses any unsupported data types or tools, it will fail. Esri Knowledge Base Article 40838 explains this scenario, along with how to change the file association or explicitly call the version of Python that you want to use. I recommend that if you are going to set up your scripts to run as scheduled tasks, you first review the help documentation to determine if you should utilize the 32-bit or 64-bit version of Python, then create a Windows batch file to call whichever version of Python you wish to use. The scheduled task can then point to the .bat file instead of the Python script to avoid any confusion. This is explained in the above referenced KB article. If running a Python script from an IDE, make sure to check what version of Python it (or its shortcut) is pointing to. For example, the 32-bit version of IDLE can be found at: C:\Python27\ArcGIS10.1\Lib\idlelib\idle.bat, and the 64-bit version can be found here: C:\Python27\ArcGISx6410.1\Lib\idlelib\idle.bat. Other IDEs such as PythonWin or PyScripter have different downloads for the 32-bit and 64-bit version, so be aware of the version of Python that the IDE you are working from uses. Just as mentioned in the above scenario, using the 64-bit version of Python on unsupported data or tools will result in an error. The version of Python can be checked by using the following command: import sys print(sys.version) In some cases, uninstalling ArcGIS for Server or 64-bit Background Processing could result in the Python files (.py) not being associated with Python. If you do not specify to run your scripts with the 32-bit Python executable through the command line or a schedule task, there could be issues successfully running that script. Esri Knowledge Base Article 41185 discusses this scenario, along with how to resolve it. There are undoubtedly more scenarios that could cause confusion with the 32-bit vs. 64-bit versions of Python. However, one thing to remember is that if your script works in ArcMap or ArcCatalog, but fails with an error in an IDE or as a schedule task, make sure to check the version of Python to be sure you are not using an unsupported data type or geoprocessing tool with 64-bit Python.Lucas D. - Desktop Support Analyst

‎07-05-2013

Hi Jose, Just a thought, but do you have any other versions of Python installed? I'm wondering if ArcMap is pointing to the correct version and perhaps the IDEs that you are using are pointing to a different version? -Luke

‎07-03-2013

Every IDE is different, but as an example, when you click to run a script in PythonWin, there is a section to add parameters. You can just specify your parameters here. Please see the attached screenshot as an example.

‎07-03-2013

It's kind of hard to tell what the issue is with the way the code is formatted above, but are you trying to save a copy inside of a loop? If you are, then perhaps it is trying to save a new copy with the same name every time you replace a layer's data source, which I could see causing locking issues. I suggest you first move the save a copy outside of the loop if it is in a loop, and if it is not, re-post your code with the code tags so it is easier to read. If you are trying to save a copy several times, this could add to the slower performance as well.

‎07-03-2013

I'm guessing you can repro this through the UI and outside of Python. Are your data registered with the data store? If not, I would start with that. Otherwise, I have seen this happen with a corrupt MXD, so you could try adding the layers to a new map and trying to publish that MXD.

‎07-03-2013

Yes, please see the help doc for specifics.

‎06-27-2013

The help might get you on the right track, but I'm pretty sure the biggest key is going to be creating the Desktop10.1.pth file, which is discussed in the above article. This is a pointer from python27 to the ArcGIS Install location, so you'll definitely need that if you haven't done so already. For me, the Desktop10.1.pth file is located here: C:\Python27\ArcGIS10.1\Lib\site-packages. It's basically a text file called "Desktop10.1" with the file extension of ".pth" and has a few paths in it: C:\Program Files (x86)\ArcGIS\Desktop10.1\bin C:\Program Files (x86)\ArcGIS\Desktop10.1\arcpy C:\Program Files (x86)\ArcGIS\Desktop10.1\ArcToolbox\Scripts Not positive this will completely take care of it for you, but it's a good place to start if you haven't done this already.

‎06-26-2013

1. Add a new variable (perhaps a Long or a String) from the Insert menu and right click > make model parameter. 2. Use If-Then_Else logic as described in this help page to determine where to go depending on the input value for the variable created in step #1.

‎06-24-2013

You would need to describe the source feature class: import arcpy desc = arcpy.Describe("pathToFeatureClass") descExtent = desc.extent #returns an extent object arcpy.env.extent = descExtent #extent object can be used to set arcpy.env.extent print arcpy.env.extent

‎06-21-2013

Not sure if this answers your question, but you can reset the arcpy.env.extent however many times you want throughout the script... import arcpy from arcpy import env env.extent = "-107.0 38.0 -104.0 40.0" arcpy.Clip_analysis(r"C:\temp\indata",r"C:\temp\clipFeatures",r"C:\temp\outFeatures") env.extent = "-108.0 39.0 -105.0 50.0" arcpy.Clip_analysis(r"C:\temp\indata1",r"C:\temp\clipFeatures1",r"C:\temp\outFeatures1")

‎06-18-2013

Double click the .lpk file in Windows Explorer to extract the data. The package will by default be extracted to %userprofile%\Documents\ArcGIS\Packages.

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by LucasDanzinger

Re: Troubles Importing XTools Pro Tools In Python

Re: The tool is not licensed

Re: How to add iteration loops to model builder python export.

Re: XSLTransform_conversion works on Windows 7 PC but not on Windows 2008 Server

64-bit vs. 32-bit Python explained

Re: ArcPy 10.1 StageService fails

Re: Python Parameter Prompting in IDLE

Re: Problemas con saveACopy y replaceDataSource

Re: ArcPy 10.1 StageService fails

Re: Is ArcGIS 10.1 Compatible with the SQL Server 2012 or SQL Server Express 2012

Re: Change where Arc looks for Python

Re: Modelbuilder - run tool dependent on user input

Re: Set multiple output extent in python scripting.

Re: Set multiple output extent in python scripting.

Re: .lpk file to .shp or a feature class

Re: Possible memory leak with Dictionary Renderer ...

Logging into the future: Introducing the Next Gene...

Re: Ubuntu 24.04 Qt Version 6.4.2 is not compatibl...

Re: Windows Deployment

Re: Converting image into .tpk format