Latest Contributions by GhislainPrince

Hi Vidar,  could you try to modify your code to have `ProcessStartInfo` with `UseShellExecute=True` . Just curious if that has positive impact. ... View more

Thanks for clarification James. Just in case others post links to more recent versions of the topic you mention. I'd say the "Calculate Geometry Attributes" gp tool and methods on SHAPE.getArea quite recent additions, so they many not feature on those docs, but they probably should eventually. Cheers ... View more

Hi James,  The recommended ways of yore which you link is good: project the data into a coordinate system that is appropriate for areal or distance calculation based on your data's extent, then use a calculation like SHAPE.AREA. It's old like you say, maybe there's something more current somewhere. I will say though that WebMercator is pretty much never a good choice for area or distance calculations as it is highly distorted and areal values derived from it will be poor.  See https://www.youtube.com/watch?v=UksOGfKrxXk  A newer way you have access to in Pro is through the shape object.  I'd say you'd want to look into this :  `SHAPE.getArea(method="PRESERVE_SHAPE", units="AcresInt")` .  This you can run on most coordinate systems, as the "PRESERVE_SHAPE" method will unproject the data, drape to geometry over the associated ellipsoid and perform the areal calculation of the shape. It's a bit slower , but removes common mistakes with bad coordinate systems, bad units, etc...  Finally i always recommend to use explicit qualified units : eg "AcresInt" (for international) or "AcresUS" (for US unit) , not the unqualified "Acres", for clarity. Lastly , we have a gp tool called "Calculate Geometry Attributes" which does this PRESERVE_SHAPE pattern for calculating area, you can use that a bit more easily than writing python code (if you want).  See https://pro.arcgis.com/en/pro-app/3.0/tool-reference/data-management/calculate-geometry-attributes.htm Cheers Ghislain Prince, Geoprocessing team ... View more

Hi Alfred,  community ideas are good way to go for that catalog pane "add file type" feature, also getting attached to ENH requests with tech support. We have arcpy.da.Walk to get data we know about, for the data formats Pro doesn't know about the approach of os.walk seems right to me.   Your approach of a white and/or black list for your org's other data seems right. Finally we've worked on arcpy.da.Walk in recent releases, there's improvements to the online doc, as well as improved results for KML, .geodatabase, .atbx, parcel fabrics in the Pro 3.x releases. Cheers ... View more

Hi Alfred, arcpy.da.Walk only returns object types recognized by the arcgis Pro application. Probably best analog is that walk will return data you see in Pro's catalog pane. Pro doesn't support Personal GDBs, so we don't see/find them in the catalog pane, nor in arcpy.da.Walk. For objects which happen to be a file on disk (eg: .zip, .pdf, ...) it's totally valid and good to use os.walk to find those. ... View more

by command line i mean the "Python Command Prompt" application you can launch from the windows start menu. The multiple NumPy installation sounds like a meaningful error.  If you've managed to get 2 of them installed into your arcgispro-py3 environment then that environment is in an unusable state. It may be easiest at this point to call tech support and get them to help you to get this machine back to functional/known state.  The way will be through uninstall of pro, rename the leftover folder, and do new install (maybe some more things they're aware of). ... View more

Joe,  if you're having trouble at 2.2.1 .. do read over both these issue Problem: After upgrading to ArcGIS Pro 2.2, geoprocessing tools fail to load and Python window returns "Failed to Initia…  Problem: Unable to create environments or install packages after upgrading to ArcGIS Pro 2.2   "Is not having an active env selected problematic." yes, you need an active environment for various functionality in pro (python window, many gp tools, pyt, options on certain tools - like calculateField, etc). The fix is as you describe it: go to python backstage and activated arcgispro-py3 in the `Manage Environments` dialog.  You can also this at the command line : proswap arcgispro-py3 .  At that point you should not get a blank `Python Package Manager` page. Once the active environment is fixed, you may see the `env's does not exist` once. But not afterwards. Hope this helps. ... View more

you can keep the bz2, or delete them (they'll get pulled down again). James when you click `New` , do make sure you wait for the blue spinning status bar to complete before you click `Activate`. If that still doesn't work can you tell me what you see at the bottom of %LocalAppData%\esri\conda\conda_debug.log ? ... View more

James, did you look at this already? https://support.esri.com/en/technical-article/000018813 ... View more

Hi Malcolm,  that's the error you'd get if you forgot to import arcpy. Try this instead pls...  1. windows start button , select "Python Interactive Terminal" 2. import arcpy 3. print(arcpy.GetInstallInfo()) ... View more

Hi Abhijeet, can you look in conda_log.txt for the call that creates pyenv. It'll be this  DEBUG:__main__:conda.cli.main called with ('C:\\Program Files\\ArcGIS\\Pro\\bin\\Python\\Scripts\\conda.exe', 'create', '--clone', 'arcgispro-py3', '-p', 'C:\\Users\\YourUserName\\AppData\\Local\\ESRI\\conda\\envs\\pyenv', '--no-shortcuts', '--pinned', '--json')‍ can you paste here the next 5-10 lines of messages. thanks ... View more

Hi Håkon,  thanks for reply.  I noticed that late yesterday too.  We've been trying to figure out a way to make conda work with this situation, we don't have it yet.  We'll keep researching that. In the meantime this works if you're willing: browse to C:\Program Files\ArcGIS\Pro\bin\Python\pkgs .  Do NOT delete the cache folder, and no need to delete the *.bz2, but delete the rest of the packages folders (asn1crypto-0.24.0-py36_0, attrs-18.1.0-py36_0, backcall-0.1.0-py36_0...) then clone & pro's python backstage worked for me. These folders will get created from the *.bz2 files next time you need them (ie. next time you clone). If you delete the *.bz2 files it's no big deal they'll get downloaded again (they're 80MB total). ... View more

@Hakon, i got by your problem by using `conda clean`.  We're finding that some machines upgraded from 2.1 require this step. Also, your use of `conda create` will create an environment without modules such as numpy, matplotlib, and arcgis (to name a few) which parts of arcpy needs.  To create an environment that'll work with arcpy (and that you can use with ArcGIS Pro you should clone arcgispro-py3 like so conda create --clone arcgispro-py3 --name %LocalAppData%\ESRI\conda\envs\my_env --verbose Fixing the "CondaError: Cannot link a source that does not exist." error. (arcgispro-py3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>conda create --name prodebug2 python=3.6 WARNING: A space was detected in your requested environment path 'C:\Program Files\ArcGIS\Pro\bin\Python\envs\prodebug2' Spaces in paths can sometimes be problematic. Fetching package metadata ............... Solving package specifications: . Package plan for installation in environment C:\Program Files\ArcGIS\Pro\bin\Python\envs\prodebug2: The following NEW packages will be INSTALLED:     certifi:        2018.4.16-py36_0     pip:            10.0.1-py36_0     python:         3.6.6-hea74fb7_0     setuptools:     39.2.0-py36_0     vc:             14-h0510ff6_3     vs2015_runtime: 14.0.25420-0       esri     wheel:          0.31.1-py36_0     wincertstore:   0.2-py36h7fe50ca_0 Proceed ( /n)? y ERROR conda.core.link:_execute_actions(337): An error occurred while installing package 'defaults::python-3.6.6-hea74fb7_0'. CondaError: Cannot link a source that does not exist. C:\Program Files\ArcGIS\Pro\bin\Python\pkgs\python-3.6.6-hea74fb7_0\Lib\__pycache__\__future__.cpython-36.pyc Attempting to roll back. CondaError: Cannot link a source that does not exist. C:\Program Files\ArcGIS\Pro\bin\Python\pkgs\python-3.6.6-hea74fb7_0\Lib\__pycache__\__future__.cpython-36.pyc (arcgispro-py3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>conda clean --all Cache location: C:\Program Files\ArcGIS\Pro\bin\Python\pkgs Will remove the following tarballs: C:\Program Files\ArcGIS\Pro\bin\Python\pkgs ------------------------------------------- --- SNIPPED OUT LONG LIST OF PACKAGES AND PROMPTS --- (arcgispro-py3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>conda create --name prodebug3 python=3.6 WARNING: A space was detected in your requested environment path 'C:\Program Files\ArcGIS\Pro\bin\Python\envs\prodebug3' Spaces in paths can sometimes be problematic. Fetching package metadata ............... Solving package specifications: . Package plan for installation in environment C:\Program Files\ArcGIS\Pro\bin\Python\envs\prodebug3: The following NEW packages will be INSTALLED:     certifi:        2018.4.16-py36_0     pip:            10.0.1-py36_0     python:         3.6.6-hea74fb7_0     setuptools:     39.2.0-py36_0     vc:             14-h0510ff6_3     vs2015_runtime: 14.0.25420-0       esri     wheel:          0.31.1-py36_0     wincertstore:   0.2-py36h7fe50ca_0 Proceed ( /n)? y vs2015_runtime 100% |###############################| Time: 0:00:00   2.38 MB/s vc-14-h0510ff6 100% |###############################| Time: 0:00:00   0.00  B/s python-3.6.6-h 100% |###############################| Time: 0:00:02   9.62 MB/s certifi-2018.4 100% |###############################| Time: 0:00:00   0.00  B/s wincertstore-0 100% |###############################| Time: 0:00:00 881.16 kB/s setuptools-39. 100% |###############################| Time: 0:00:00   4.67 MB/s wheel-0.31.1-p 100% |###############################| Time: 0:00:00   5.26 MB/s pip-10.0.1-py3 100% |###############################| Time: 0:00:00   6.07 MB/s # # To activate this environment, use: # > activate prodebug3 # # To deactivate an active environment, use: # > deactivate # # * for power-users using bash, you must source # (arcgispro-py3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>activate prodebug3 (prodebug3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more