Latest Contributions by ShaunWalbridge

‎07-11-2016

Hi Dan Patterson, My understanding is that the standard installation locations are recommended in part because of how the Windows security model is set up – for example, Python at 3.5 similarly installs itself into Program Files as addressed in this bug. That said, I'm not aware of any specific limitations you would hit by installing into another location, and have used and tested ArcGIS Pro 1.3 in other top-level locations for a global install. Hope that helps, Shaun

‎07-09-2016

Could you describe what you're trying to do? In most contexts, it should be possible to use Python directly to invoke the related Python script instead of needing the batch file middleman.

‎04-13-2016

Yes, the issue was resolved in 10.4.0. It isn't identified as a candidate for service packs, so won't make it into 10.2.1. That said, there is a workaround -- write to a FGDB data source instead of a Shapefile.

‎03-17-2016

Conda will ship with ArcGIS Pro 1.3 -- the mismatch in the talk description is my mistake that we didn't catch till after it went to press. If you'd like to learn more about Conda and how it relates to ArcGIS, I've published the presentation we gave on it at DevSummit here: https://4326.us/esri/conda In terms of the SciPy stack, some of its history of integration is discussed in last years' talk on SciPy, but I've revised and expanded the content to include current status as of 10.4 / Pro 1.2 in this years' talk on taking advantage of the SciPy stack with ArcGIS: https://4326.us/esri/scipy If you have any specific questions or issues, I'm happy to help and will work to address them. Cheers, Shaun

‎12-09-2015

I'd start by trying a version of IronPython matched against CPython 2.6: IronPython - Download: 2.6.2

‎09-09-2015

Great! Glad to hear it. The 10.4 release will include the same packages currently included in Pro, so you should be able to write code that will work equally well in both ArcMap and Pro at that point. Let us know if you have any further issues, and look forward to hear more about your work with raster object detection. Cheers, Shaun

‎09-08-2015

Scott and Ed: This issue will be resolved in the next release of ArcGIS.

‎09-08-2015

Can you post a screenshot of what you're seeing when trying to modify the documentation of a tool?

‎09-08-2015

You're probably best trying this question elsewhere, since this is a support forum for Python in the context of ArcGIS. That said, if you need the exact implemention that ArcGIS provides, you could set up a server instance that does the conversion. If you're not afraid of the command line, you can also try your luck with ogr2ogr, which has a somewhat limited DXF AutoCAD 2000 driver: ogr2ogr -f "DXF" destination.dxf source.kml Both formats are complicated and have non-overlapping featuresets, so expect this to be a lossy translation.

‎09-08-2015

The reason that the pipe character is special, is on UNIX based operating systems, it's used to denote steps in a pipeline, and is handled specially. In your case this isn't what you want, I'd recommend using the subprocess module instead of os.system: import subprocess subprocess.call([r'C:\Program Files (x86)\AquaInfo\AI-Viewer.exe', r'SystemMDW=C:\Program Files (x86)\AquaInfo\Aqua.mdw|UserMDB=C:\Program Files (x86)\AquaInfo\System\AI_mbn.mdb|DataBaseName=C:\Users\ps\Desktop\atest\Test.mdb|UserId=99999998|ObjIdsList=7297|SelObjId=7297|ObjType= 0|']) I don't have the AquaInfo software to test against, but in an example script, that passed the arguments correctly. Cheers, Shaun

‎09-08-2015

As of ArcGIS 10.3, this issue is fixed and you can directly use the latitudeOfOrigin property: >>> sr = arcpy.SpatialReference("NAD 1983 Contiguous USA Albers") >>> sr.latitudeOfOrigin 23.0 I'd use that over the solution I'd originally posted above for any newer release.

‎09-08-2015

Sure, just embed '\' separators between the toolsets. Here's an example where the two "Export" tools will be in separate toolsets, nested underneath the parent (also on GitHub😞 import arcpy class Toolbox(object): def __init__(self): self.label = u'Example_Toolbox' self.alias = '' self.tools = [FirstTool, SecondTool, ThirdTool] class FirstTool(object): def __init__(self): self.label = u'First Tool' self.description = u'' self.canRunInBackground = False self.category = "Import" def getParameterInfo(self): return def execute(self, parameters, messages): pass class SecondTool(object): def __init__(self): self.label = u'Second Tool' self.description = u'' self.canRunInBackground = False self.category = "Export\\GeoJSON" def getParameterInfo(self): return def execute(self, parameters, messages): pass class ThirdTool(object): def __init__(self): self.label = u'Third Tool' self.description = u'' self.canRunInBackground = False self.category = "Export\\TopoJSON" def getParameterInfo(self): return def execute(self, parameters, messages): pass

‎07-29-2015

Note that this issue is now solved at ArcGIS 10.3 or later, and in ArcGIS Pro.

‎07-17-2015

Yeah, that's what I'd expect out of the box with Conda -- the version of NumPy that is on your sys.path is 1.7.1, and the version in Conda is 1.9.1 -- NumPy is not ABI compatible between major releases. If you want to stick to ArcMap, you can try making a environment with NumPy 1.7.1 and a related SciPy release, e.g.: conda install numpy=1.7.1 conda install scipy=0.13.2 And see if it works linked against that conda environment. Good luck!

‎07-16-2015

Hello Tobias Litherland (and thanks for the heads-up Xander Bakker): If you have Pro installed, that's the easiest route -- it ships with SciPy, and is usable today. Further improvements are coming soon to our other products, but that doesn't help you for solving your immediate needs. For that, you can try using Python path files (.pth) to bridge between the environments. WARNING: This approach is risky, and can potentially break your Python installation, so be careful, and this isn't a directly supported method. Because you're using different versions of packages like NumPy under the hood, strange things can happen, and sometimes introduce crashes. 1. Find the site packages path for your Anaconda install. On my machine, it was C:\Miniconda\envs\default\Lib\site-packages . Copy that path into a file called anaconda.pth . 2. Copy anaconda.pth into C:\Python27\ArcGIS10.3\Lib\site-packages (or the correct location if you used a different installation path). 3. Open Python, type: import sys print(sys.path) If it worked correctly, you should see a new entry for the Anaconda environment from within the ArcGIS installed version of Python, and import scipy should work. Again, note that this may cause other problems, and if anything is breaking, delete the pth file to return your setup to a stock install. Cheers, Shaun

Online Status	Offline
Date Last Visited	36 seconds ago

My Ideas

Latest Contributions by ShaunWalbridge

Re: Python and ArcGIS Pro 1.3 : Conda

Re: While using ArcGis Python toolbox I have a subprocess.popen.. how to stop command prompt screen from appearing while it runs?

Re: arcpy.da.UpdateCursor SHAPE@ error when updating M-values

Re: Conda Comes to ArcGIS Pro

Re: IronPython in ArcObjects 10.0

Re: SciPy.ndimage and ArcGIS Tools

Re: arcpy.da.UpdateCursor "SHAPE@" error when updating M-values

Re: Create a Help file for a new geoprocessing tool

Re: Python Script: Convert KML to AutoCAD(DWG\DXF)

Re: Run external program

Re: Getting the Latitude of Origin for a spatial reference

Re: Python Toolbox Toolset

Re: Generate Spatial Weights Matrix error in ArcGIS 10.2

Re: SciPy.ndimage and ArcGIS Tools

Re: SciPy.ndimage and ArcGIS Tools

Re: Table of Python Versions for Each Pro Release?

Re: ArcGIS Pro 3.0 "Failed to create notebook serv...

Re: Running python using server

Re: ArcGIS 2.8.0 GeoPandas Error - rtree problem

Re: "Failed to load notebook" when using custom en...

R-ArcGIS

Esri Forestry Group (EFG)