Latest Contributions by ShaunWalbridge

Thanks for the suggestion @curtvprice. At this point, Pro has diverged significantly from ArcMap and ArcMap is in mature support, so we are unable to add new features to it. Hopefully Pro is doing what you need in your current workflows, and if not, please let us know so we can address any remaining gaps. Cheers, Shaun ... View more

Thank you for your suggestion. Most Geoprocessing tools operate on individual layers, and applying a geoprocessing tool to multiple inputs can be accommodated in Python by iterating over the list, e.g. for layer in arcpy.ListFeatureClasses("input/path"):     arcpy.Buffer(layer, ...) Excepting for a subset of tools where working on multiple inputs is common, this is the default pattern used in Python to work against multiple inputs. Cheers, Shaun ... View more

Thanks for your submission. This makes good sense and we'll look into the discrepancy. ... View more

This is valid, and thanks for bringing it to our attention. In the future, for issues of this nature (significant performance regression when asking for less data) are bugs and should be submitted via support requests. However given this has a number of Kudos and a clear story, keeping this idea open to track its progress.  Cheers, Shaun ... View more

Working with NetCDF can be challenging and require investing in either tooling or data manipulation skills to get what you want, especially if you are working with specific models that store their data in ways less aligned with the more traditional data representations. The Pro Python distribution includes both netcdf4 and xarray which can work with NetCDF files directly, see for example this user who shifted values with netcdf4.  The xarray package has a number of reshaping operations including "roll" functions which can be used to shift the data as well. I would recommend you start small with a specific dataset, in practice it will take some learning before you can easily manipulate arbitrary NetCDF files if they differ in structure. Cheers, Shaun ... View more

Sounds like a possible bug. Might look at if the behavior is reproducible outside the application in a standalone script, and whether it is the same in standalone Jupyter notebook. If it reproduces in those environments, it is something fairly deep and not related to the particular application state of Pro. ... View more

What driver are you using? The correct way to access the resource will be dependent on the driver, for example the Postgres driver supports a number of different formats for authentication. you may be best served first confirming you can access the data with the command line tools, then switching to using the Python bindings afterward.  ... View more

Please try moving the toolbox to a local drive and see if it has any impact. When you have remote resources for things like toolboxes, you are beholden to the network latency and bandwidth for basic operations, which can get easily into a situation where the application hangs, because it is waiting on I/O operations it expects to be fast (reading some text or data from local disk) but in reality it has to wait for a high latency connection to respond. Not specific for toolboxes, but we currently don't support cloud data storage for Pro resources for similar reasons. If the hangs are reproducible with local files, then you've eliminated one class of issues. If it reproduces with local on disk tools, I would log a support request and we can dig into it further through a support case. Thanks! Shaun ... View more

One approach to determining the appropriate properties for cases like this is to change the data you'd like to change from Python, save the result as a new project, then extract the two APRX files and compare the related JSON CIM representations, and compare them with a diff tool. The documentation as recommended by @alfredman is the better approach, but sometimes seeing what the code actually changed can also be useful. ... View more

It doesn't look like Apache Airflow has support for Windows currently, but they do have an issue for tracking its availability here:  https://github.com/apache/airflow/issues/10388 Without that, you could set up WSL2 to use Airflow via Linux on Windows, but that requires an extra set of skills and technology to use and may not fit into the model you're trying to work with. There are Linux based environments like Server that potentially could work, depending on what you're trying to accomplish. Cheers, Shaun ... View more

This issue is addressed in Pro 3.1.3, which was released today. Let us know if you run into anything else. Cheers, Shaun ... View more

Powershell support was added with Pro 3.1 as @Luke_Pinner mentioned. It can be used by first configuring it with conda init, see this blog post for further details: https://www.esri.com/arcgis-blog/products/arcgis-pro/developers/conda-init-and-arcgis-pro/ If there's something else that you'd like to see on this front, feel free to add a comment and we can work to understand how it'd fit in. Cheers, Shaun ... View more

There should be a patch coming out later this month which addresses this issue for Pro 3.1 by disabling the add-in data sources from Python code and will work again without needing to delete anything. This issue has an associated bug, at BUG-000157823 that also can be tracked. Best of luck! Shaun ... View more

The issue has been addressed, and will be fixed in the upcoming Pro release. ... View more

OK, yes the goal with arcpy-base is to strip out all non-critical packages, and move those which are normally included but not critical into arcpy. You can evaluate the versions we include by looking at the arcpy file information for the version you're installing, e.g. we ship scipy >=1.5.2 for Pro 3.1. I think including only the minimal set of things is the right way to break this up since different users will need different sets of things beyond the arcpy-base set, and if they need 1:1 mapping with Pro, they can use the full ArcPy package. ... View more