Latest Contributions by ShaunWalbridge

Hello Jake, Glad you found something that works for you. The other way of doing this is running arc.select on the input after opening it: > # Read in example shapefile from package > ozone.path <- system.file("extdata", "ca_ozone_pts.shp", +                           package="arcgisbinding") > ozone.arc.dataset <- arc.open(ozone.path > ozone.obs <- arc.select(ozone.arc.dataset)       This two-step process is intentional, to give you a step to filter the data before it is imported during the arc.select step. If you only want certain columns or otherwise to filter the data, you can select just the features you want – minimizing the amount of memory used in R with the resulting dataset. Cheers, Shaun ... View more

Hello Jake, I can't reproduce this issue with polygon data I have on hand. For the variable that stores the arc.open output, could you paste what it displays when just typing the variable name. For example, here's a simple layer I was using to test: > d <- arc.open("c:/workspace/basic_catalog.gdb/example_with_nulls_buff_50km") > d dataset_type : FeatureClass path : c:/workspace/basic_catalog.gdb/example_with_nulls_buff_50km fields : OBJECTID, Shape, ID, Data, BUFF_DIST, ORIG_FID, Shape_Length, Shape_Area extent : xmin=-85.45471, ymin=-9.452023, xmax=-75.55085, ymax=0.4521846 geometry type : Polygon WKT : GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984"... WKID : 4326 ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ What does your data source display? Can you share a sample of the input GDB you're using? Thanks, Shaun ... View more

Hello Joshua, Was Orhun's answer enough to get you going with this? If you need to configure the R connection for each Pro instance, when you select the desired installation of R from the Geoprocessing options pane, internally all that is happening is creating a new text file, located at %LOCALAPPDATA%\Esri\RIntegration.conf. This file is a text file containing a single line: R_HOME=<Path to selected R installation> For example, with R 3.6.0 installed, it might be set to: R_HOME=c:\Program Files\R\R-3.6.0 Cheers, Shaun ... View more

If you're just performing an aspatial join (based on a shared column), you can use the default `merge` method from R to join, see for example this post. Since you have ArcGIS available, you may also want to perform this beforehand, you can use Join Field, including via ArcPy. ... View more

Can you provide a code sample? I'm not able to reproduce this, as.Date and POSIX date objects are being converted to a Date field in an output geodatabase in my tests. Here's an example: library(arcgisbinding) arc.check_product() Sys.setenv(TZ="UTC") df <- data.frame( a = c(0, 1, NA, -Inf, Inf), b = c("a", "b", NA, "c", ""), c = c(as.Date("2001-01-01"), NA, -99, 0, 1), d = c(as.POSIXct("2001-01-01"), NA, -99, 0, 1), arc.write("date.gdb/with_date") ‍‍‍‍‍‍‍‍‍‍‍‍‍ With that, I get two date columns, "c" and "d", which contain values I would expect. ... View more

If you start the Python Command Prompt, is arcgispro-py3-clone your default environment? If not, can you type `activate arcgispro-py3-clone`, then run: conda list‍ That should list all installed packages in the environment. It looks like the version of lxml installed isn't the correct version for Python. You can also run this: import lxml lxml.__path__‍‍ To confirm that the lxml version being used is the one in your conda environment. ... View more

Hi Milen, If you visit the Python backstage, you should be able to select "arcgispro-py3" as the environment. Alternatively, you can run the Python Command Prompt, then type proswap arcgispro-py3 to set the default environment as the one the application is using. Cheers, Shaun ... View more

Are you in the default environment? Does it crash when you start a Python session for Pro then type `import arcpy`? ... View more

As of Pro 2.3, you can make environments in any location -- just click the Clone button adjacent to the environment you'd like to copy, then change the path to your desired location:   Using Python with ArcGIS - YouTube  It should then work -- Pro will see it, and you can use it as your default for Pro if you'd like. Conda should also see it (via its inclusion into the environments.txt file that conda shares across installs). ... View more

Hello Anne, Sorry to hear of the trouble you're having with your environments. There shouldn't be any issues doing patch upgrades (e.g. 2.3 to 2.3.1), but we do know that upgrading from new versions (2.2 to 2.3) currently makes them incompatible with Pro, since the environment contains ArcPy binaries versioned for the specific version of Pro we ship with. From the above, it looks like you're trying to install into the default `arcgispro-py3` environment. We generally try to keep that environment free of changes, because it is modified by the installer at installation, and means there is always a fallback environment users can use independent of what we lay down. If you run `conda env list` do you see any additional environments? By default, user environments are written to %LOCALAPPDATA%\Esri\conda\envs. If you only need a few packages, the simplest thing to do is to create a new environment, then populate it with anything you do need. There are complete instructions in this thread: https://community.esri.com/message/830134-re-upgraded-to-23-and-i-cannot-use-my-previously-cloned-conda-environment?comm…  but for a couple of packages, I'd just create a new one then ask for the packages you do need. For your case, you'll want the `opencv` package. I confirmed that it does install locally for me in a cloned environment, both from within Pro and the command line, with the package name of just "opencv" (It is currently pulling in version 3.4.2). If that doesn't work for you, let us know and we can dig further. Cheers, Shaun ... View more

Thanks Jay, it'd be great to confirm it works for you. The fix to PYTHONPATH should prevent Pro from ever crashing, though it will still crash a standalone python.exe session since it loads the DLLs prior to us being able to modify the environment. ... View more

Scott Davis‌ Adam Thomas This issue has been resolved in Pro 2.3. Thanks for bringing it up, and if you see something similar once you have Pro 2.3, let me know. Cheers, Shaun CC Kory Kramer‌ ... View more

Great! Glad we figured it out. ... View more

Yes, I'm happy to see this fix go in too! One thing I should note -- it actually retains the PYTHONPATH value, but makes them a lower priority than the DLLs for the environment that is driving Pro. This ensures that Pro will work correctly, but will still allow someone who relied on PYTHONPATH for sharing e.g. a Python module to show up in Pro. The PYTHONPATH fix won't help on the command line, because that's a setting built into the python.exe. For posterity, if anyone hits this on the command line, you can start Python with `python -E` to ignore Python environment variables, or better yet unset PYTHONPATH. If you do need to inject additional locations for Python to find modules, add a .pth file which includes the path into Lib\site-packages. ... View more