Latest Contributions by ShaunWalbridge

‎10-06-2022

With Pro 2.9, ArcGIS Pro was updated to GDAL 3.3.0, and Pro 3.0 ships with GDAL 3.4.0. We can't easily allow free-floating upgrades of GDAL because of its significant use elsewhere in the software, but we continue to upgrade it and make the version Pro includes close to the latest available upstream. Thanks for your idea!

‎09-26-2022

‎09-26-2022

Hello @RPGIS and @BillHagerman thanks for your suggestion. We've discussed this with our team and a couple of related teams, and at this time are not planning to add FloPy directly to our distribution because we don't have allied use of CFD based solutions in any core software. That said, you can install FloPy by following its installation instructions: https://github.com/modflowpy/flopy#installation If you start a Python Command Prompt session in a custom environment, you can run conda install conda-forge::flopy or the install command they used above. You can also install it through pip. We continually evaluate the package set, but typically the packages that end up directly in the core software are either (a) used by the tools that we develop themselves or (b) show a broad and general pattern of utility for a large number of customers. Thanks for your time, Shaun

‎09-26-2022

@MichaelRaasch could you log a case with support on this issue? We don't yet have a reproducible case for this issue and working through technical support will allow us to ensure we have the same workflow locally and understand any potential configuration issues that may be present. If we identify a specific issue with SSMS, it may be on our side, on Microsoft's side, or a configuration setting that can be handled.

‎09-23-2022

Thanks for providing the additional context. It looks like the particular service you're using has a couple of empty geometries in the input, and sf doesn't like this input. I'm not sure if there is a simple way to filter these from the sf side, you might want to check in their documentation. As a quick workaround, sp will drop these geometries on import, and sf can read sp objects. This worked for me locally: library(arcgisbinding) arc.check_product() arc.open(path='https://services9.arcgis.com/RHVPKKiFTONKtxq3/arcgis/rest/services/NWS_Watches_Warnings_v1/FeatureServer/5') wes <- arc.select(wec) wes.sp <- arc.data2sp(wes) # sp reports: "removed missing geometry:393 451" # convert the resulting sp object back to sf wes.sf <- sf::st_as_sf(wes.sp) If you discover a filter on sf that does the trick, potentially we could add that to our documentation, or otherwise find a way to make the need to have non-null geometries when working with sf clearer. Cheers, Shaun

‎09-21-2022

Thanks for your report of this fix. We've uploaded a new build of the ArcPy package for 3.0 which reflects this change and should work for any new environments, or after doing conda upgrade arcpy in an affected environment. Cheers, Shaun

‎09-21-2022

Hello Explorador, How would you like to use the data? If you want the shape in an R native format, you can use arc.shape2sp or arc.shape2sf to export into the sp and sf formats which would be easier to work with elsewhere in R. You can also use arc.shape to pull out the native Esri geometry, but typically you'll want to be working with something that understands the complexities of the polygon format. Cheers, Shaun

‎09-16-2022

Thanks for posting these details. We've logged an internal issue on this, I don't think it is related to the build that is hosted on anaconda.org, but something more subtle. Issues of this class aren't trivial to debug because they are removed from our stack and introduce a number of VSCode specific elements that are difficult to isolate. The VSCode help documentation is along the lines of "something is wrong with your environment" if this is the case, but that is not a useful diagnostic to separate out a cause. We do test that VSCode works with the out of the box environment, and are creating an environment where we can reproduce this issue with Pro 3.0.

‎09-09-2022

My first guess is some issue with the pathing or quoting in the `inputs` list, subprocess can be persnickety about this particularly on Windows. Perhaps try a simpler `inputs` to start to isolate what's causing the issue, or disable the no_window and see if there is are any details the process call shows. Just try launching the python_path and a script that returns a value. I would also check that the path being sent as `in_df_csv` is properly normalized.

‎09-09-2022

The current system requirements for Pro 3.0 GPGPU workflows is for 6GB+ of GPU memory, and in the past this was set at a minimum of 4GB. We unfortunately can't support smaller memory cards because of the size of the underlying models we are building. That said, producing more useful errors in this case is something we intend on doing in future releases, and there are other GPGPU workflows like the SA tools that will work with less memory.

‎09-08-2022

@EricEagle thanks for your idea on this. I believe that the solution proposed by @Luke_Pinner is a good one, and relies on existing components we provide in our stack without Esri trying to maintain something that we don't directly use nor expect to deliver to customers at this time. If certificate handling becomes part of the product, exposing this through Python would definitely be a valuable addition. Cheers, Shaun

‎08-30-2022

Hello Anonymous, I don't think that is possible today with the current dashboard design, but there are some approaches that could allow you to accomplish this. Probably the simpler is to generate static images for each of your locations / observations in R, then reference those static images using the embedded content element of dashboards. Then the images will be precomputed in R, but available quickly from the dynamic web app. It technically would be possible to use the R bridge and a geoprocessing service to dynamically generate the images on the fly with R, but would require a server environment to host the GP service and would add additional latency to the application as the R service was executed dynamically. I hope that helps, Shaun

‎08-30-2022

If you have an Esri desktop product like ArcMap or ArcGIS Pro installed already, once you install R you can run the command: install.packages("arcgisbinding", repos="https://r.esri.com", type="win.binary") From an R session to install the arcgisbinding package. If you have ArcGIS Pro, you can also visit Options > Geoprocessing and configure the bridge through the support provided here.

‎08-30-2022

Hello Vratika, R 4.2 no longer provides a 32-bit version of the software, and only ships a 64-bit version. Because of this, R 4.2 and later won't work with ArcMap except through background geoprocessing. ArcGIS Pro is a 64-bit application and will work without additional steps for R 4.2, or as you did continue using R 4.1 which still provides a 32-bit version in the installation. Cheers, Shaun

‎08-29-2022

Can you provide the support request this is logged under? I believe what is happening is that for some legacy authentication systems, the md4 hashing algorithm is still in use. Pro 3.0 ships with OpenSSL 3.0 which disables these hashing algorithms by default. It is possible to reenable them though with some tradeoffs to do so. Cheers, Shaun

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by ShaunWalbridge

Re: Upgrade default build in gdal library to 3.3.2 - Status changed to: Implemented

Re: Possibility of including the FloPy module for future releases of ArcGIS Pro. - Status changed to: Closed

Re: Possibility of including the FloPy module for future releases of ArcGIS Pro. - Status changed to: Needs Clarification

Re: arcpy, Licensing

Re: Using ESRI Living Atlas in R Environment

Re: Standalone ArcPy Anaconda Distribution for ArcGIS Pro 3.0 crashes Jupyter Notebook Kernel in VSCode

Re: Using ESRI Living Atlas in R Environment

Re: Standalone ArcPy Anaconda Distribution for ArcGIS Pro 3.0 crashes Jupyter Notebook Kernel in VSCode

Re: Issue calling a subprocess from ArcGIS Pro Toolbox

Re: deep learning error

Re: Fetch client certificate from Windows cert store using arcpy - Status changed to: Closed

Re: Connect R to dashboard

Re: install error with R 4.0

Re: install error with R 4.0

Re: unsupported hash type md4

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)