Latest Contributions by ClintonDow1

Are you just missing the 'rows.updateRow(row)' in your for loop in the last snippet? ... View more

I haven't used ArcREST for Portal Administration personally, but I am fairly sure the usage is as follows: Once you have your SecurityHandler, you can use it to connect to your Portal Administration using the arcrest.manageportal.administration module  arcrest.manageportal package — ArcREST 3.5.4 documentation  From here you can access the PortalAdministration.security property which should give you access to the security functionality of your portal, assuming the username/password has the necessary permissions on your install.  This follows a similar pattern to the sample on the github page: GitHub - Esri/ArcREST: python package for REST API (AGS, AGOL, webmap JSON, etc..)   ... View more

In this case it is probably easier to use the result from the Clip rather than ListFeatureClasses() to find the input dataset for ExportCAD. For example: result = arcpy.Clip_analysis('input_fc', 'roads', 'output_fc') result_cad = arcpy.ExportCAD_conversion(result, 'DWG_R2010', 'result_cad.dwg') result_cad <Result 'C:\\Users\\user\\Documents\\ArcGIS\\Projects\\MyProject4\\result_cad.dwg'>‍‍‍‍‍‍‍‍ In your case if the workspace and location of outFeatureClass are different then it will not find the result from Clip_analysis() when using ListFeatureClasses() ... View more

Thanks for the follow up, very glad that its working now. Its good to know that interop may be related, I'll relay the info to the relevant teams. ... View more

Hello Cyrus, Sorry to hear that didn't work for you. Perhaps instead of the Python environment it could be an issue with your geoprocessing tool cache. In C:\Users\<username>\AppData\Local\ESRI\Local Caches - delete the files g0.* and g1.* - these are the geoprocessing tool cache. It may have been corrupted somewhere along the way and doesn't necessarily get removed when you reinstall. Once they've been deleted open a brand new project and the GP pane to regenerate the caches and see if your tools will work as expected.  ... View more

This looks okay to me for a fresh install. Very odd that you're still having issues after a full reinstall. Perhaps try running "%Pro Install Location%\bin\Python\Scripts\proswap.bat arcgispro-py3" to ensure that your registry keys needed by Pro didn't somehow get changed? ... View more

Hello Cyrus Blankinship‌ sorry to hear you're having issues. I tried to reproduce your situation by installing Pro 1.3.1 and immediately installing the arcgis package following the same instructions. However in my case Pro still works fine. Did you happen to install other packages prior to updating to 1.3.1? They may remain in the env upon update, unless manually deleted due to limitations of the installer.   Can you open the Python Command Prompt (Start>Programs>ArcGIS>ArcGIS Pro>Python Command Prompt) and type 'conda list' then paste the result here? It sounds like something got updated that shouldn't have.  ... View more

Just for a follow up, since the TableToDBASE tool can take one or many input tables the result returns the folder path where all of the converted tables would end up - this is the correct behavior so I was mistaken, however the suggested fix should still work for your script. In the TableToTable tool which Joshua mentioned, you can only use a single input at a time and therefore the result will be the path to the single converted table and may in fact be the simpler fix to implement in your case.  ... View more

Currently, the Table to dBASE tool's result returns the same output folder path, rather than the name of the created table. r = arcpy.TableToDBASE_conversion('roads',"C:\\Projects\\MyProject") r # <Result 'C:\\Projects\\MyProject'>‍‍‍ This seems erroneous, I'll check with the tool author to see if it should be the path to the dBASE table which is returned. This is why in your error message output, the folder path is listed three times as the input datasets for your merge.  In the meantime, you'll have to manually concatenate the outputFolder path, the original table name (ie: Green_Parks) and the expected extension (.dbf) for each table that you're converting, then use those strings in your tablesMergeInput list. Once its the three paths to your datasets that you're passing, the merge tool should work as expected and your script should complete successfully.  ... View more

In PyCharm there are two settings dialogs, Settings and Default Settings - go into Default Settings>Project Interpreter (make sure it says 'For default Project' at the top of the dialog) and set the interpreter there. Then all subsequent new projects should use it. Existing projects you'll have to set it per-project as far as I can see.  ... View more

It should be okay as long as the version is within 4.0.* - Updating to a newer version than that may cause issues with the Python Backstage UI. ... View more

Hello Júlio, You are correct that the spatial join tool doesn't have this functionality built in. I think an approach like you have in your first possible solution would work. Get the angle of a line using the function below: import numpy as np def angle_between(p1, p2):     ang1 = np.arctan2(*p1[::-1])     ang2 = np.arctan2(*p2[::-1])     return np.rad2deg((ang1 - ang2) % (2 * np.pi))‍‍‍‍‍‍‍ Create a list of other lines which satisfy the spatial join. Then do a loop through the second list and use the above function to compare the angles of the lines.  ... View more

Hi Andy, You can deactivate your current environment, change directories into the <Pro Install Path>\bin\Python\Scripts folder, then just run 'activate' with no env name and you will be in the root environment, denoted by [Python] before the prompt. That said, its possible to break Python and thus your Pro installation by doing so. As functionality around Conda matures we will no longer be bound to specific Python/numpy/scipy versions per ArcGIS Pro release. However as it stands we have to be overly protective of accidental updates of certain packages.  For this specific issue with spyder and qt, try the following without updating conda, within your environment: conda remove qt -y conda install qt=4.8.7=vc_10_4 -y Please give it a try and let us know if it helps. ... View more

You could look into installing Background Geoprocessing (64-bit)—Help | ArcGIS for Desktop which will allow you to use more of your system memory. Also you may have more success running the script in ArcGIS Pro which natively supports 64 bit.  ... View more

Unfortunately I don't think this will work like you're expecting. ArcPy relies on a large portion of the underlying ArcGIS application to execute the breadth of its functionality. If you're attempting to package a script that imports arcpy it would have to include the majority of ArcGIS within that package to be functional. Even in that case I'm not sure it would work since ArcGIS also relies on registry keys etc which are set during it's install.  I would suggest looking into creating a Python Package instead of creating an executable - How To Package Your Python Code — Python Packaging Tutorial  - this is a widely used method of sharing arcpy scripts.  ... View more