Latest Contributions by ShaunWalbridge

How much memory is installed on the machine you're using for this analysis? Does it work with smaller inputs? Setting the stack size on Windows requires editing the executable file (its a compile-time option), which requires Visual Studio. Do you know where it gets in the execution prior to the stack size limit being hit? Thanks, Shaun ... View more

Mike, You're probably long past this question, I missed it when you posted it (over a year ago!). It sounds like you're trying to access a database engine which stores its geometries in a GEOGRAPHY type. In this case, you'll need to pass in a layer that references the underlying database connection -- the bridge doesn't have the ability to directly specify a query to a database. Hope that helps, Shaun ... View more

Looks good! Note that the random seed might be something you want to expose as a parameter as well, if you want each iteration to be randomized. As is (hard-coded seed), this will always produce the same output for the same input. ... View more

Jean Christophe, Sorry for the long delay answering your question -- I missed this earlier. When you send data types containing multiple values to R, you should get back a vector of the values, with the most native data type mapped for each (for example, for files, full strings of the paths for each). You can then loop through these in R as you would with any other vector. Hope that helps, Shaun ... View more

Giacomo, Thank you for the report. The leaflet.esri package isn't something we wrote in house, it lives here on Github: GitHub - bhaskarvk/leaflet.esri: ESRI Plugin for Leaflet R Package  You may be able to adapt the Esri Leaflet basic examples for authentication, for example following this example: ArcGIS Server username/password | Esri Leaflet  We're also examining what handling authenticated services via the R-ArcGIS bridge package might look like for a future release. Cheers, Shaun ... View more

There are a few issues that can come up with Server. If you haven't seen it already, I'd review the instructions here: Deploying R for ArcGIS Server—Documentation | ArcGIS Enterprise  A few things I'd check:  - The `arcgisbinding` package is installed into the Program Files\R\<version>\library folder. If you install it as your user, it won't be accessible to the ArcGIS Server user (which has a separate %userprofile%).  - Your testing is against the x64 version of R -- ArcMap works by default against the 32-bit version of R, so testing it in this environment won't replicate what Server is using. If you follow the guide above, and check those steps and still no dice, let us know. It is possible that there is some more nuanced complication, I'm not sure we have many users who have deployed on Server with Desktop on the same machine, so potentially an issue with that. Cheers, Shaun ... View more

Jacob, Just before that step, what does the contents of your `shape_info` object look like? It should be defined on the line: shape_info <- list(type="Polygon", WKT=arc.shapeinfo(data_shp)$WKT) One option would be to try this instead: shape_info <- list(type="Polygon", WKID=arc.shapeinfo(data_shp)$WKID) I don't see anything in the lesson that is obviously wrong with that command, let us know if the above helps. Cheers, Shaun ... View more

Daniel, Have you built the corresponding Geoprocessing tool already? That's the first step -- select the data types and variables for each of the inputs and outputs you'd like to use in the tool. This process is the same as it would be with a Python script tool. In those parameters, you can define the workspace, n and m values, and the output shapefile. If you are restricting this tool to just use Shapefiles, you can just pass around a reference to the Shapefile input, the .dbf and .prj files are part of the format. So I'd pass in just the Shapefile name, then if you need for example, the path to the DBF, you can run something like: shape.root <- tools::file_path_sans_ext(input.shapefile) # extract name without .shp shape.dbf <- paste(shape.root, '.dbf', sep='') shape.prj <- paste(shape.root, '.prj', sep='') That way, your tool will have less inputs required. Once you've created your GP script with the necessary inputs and outputs, you can pass them directly to R as shown in this vignette Using the R-ArcGIS Bridge: the arcgisbinding Package, under the "Wrapping R Tool Functionality" section. Assign each one to a parameter, and the bridge will convert it to an appropriate type -- you only really have two things from the R side, paths as strings (shape and working directory) and integers. If you need further examples of how to build something like this, I recommend looking at the sample tools provided here:   GitHub - R-ArcGIS/r-sample-tools: Sample tools illustrating R usage in geoprocessing scripts  If you examine those tools, you'll see the parameters they set up, and how they are pulled in on the R side in the R scripts. As is the case with Python scripts, building fully generic tools from scripts does take a little bit of work, but I think its a worthwhile investment in your skillset. Cheers, Shaun ... View more

Thank you for reporting this issue. We're tracking this internally as a bug, and will update this issue once it's resolved. Cheers, Shaun ... View more

Michael, Sorry to hear the R-ArcGIS integration is crashing for you. Did you submit the related crash dump? Can you successfully run R code using the bridge from an R session, or does it crash there as well? For the script you're running, can you see if it contains a line reading ` arc.progress_label `? If so, can you see if commenting out that line has any effect? Thanks, Shaun ... View more

Hello Dani, Patrick Hammons‌ clued me into this issue, thanks for posting on GeoNet. As Dan mentions, your script has a lot going on which can make debugging complicated. The raster intermediary layers will be typically saved out to their own temporary files, though you're just referencing them as variables in Python. One approach would be to create explicitly new GDB files for each bin step. Check that these results are as expected, and copy the final output you're interested in into another GDB. If that approach is working, then you can just delete this GDB, which will clear out all of the files used by it, assuming no locks are preventing its deletion. For the SA outputs, I would recommend explicitly binding these to rasters you want by using `raster.save` on them, and storing those in the output GDB. The other more in-depth approach is to do what Dan suggested -- start adding debugging information, and dig into why it is failing in the second iteration as-is. You can start by just sprinkling print statements after each step, and making sure that it is executing the way you're expecting. There are more complicated debugging solutions, like pdb, but I'd start simple and see if that's enough to figure out the issue. Cheers, Shaun ... View more

Zhitao, Are you still having the issue with the R session crashing? Could you see if it reproduces from a plain R session as well? Thanks! Shaun ... View more

Bill, Thanks for the report. Can you open a standalone R session (x64) and confirm that you observe the same behavior there? Could you also let us know what type of license you're using for Pro (named user with ArcGIS Online, named user with Portal, single use, concurrent use license). Could you also see if a sample Geoprocessing tool which uses R works from the Pro side? There is a collection of sample tools here:   GitHub - R-ArcGIS/r-sample-tools: Sample tools illustrating R usage in geoprocessing scripts  Thanks, Shaun ... View more