Latest Contributions by MichaelBranscomb

Hi, You could also try applying a mask e.g. async Task AddRasterAndSetBackgroundColorValue() { try { // Create a raster dataset from a local file raster. Raster raster = new Raster(@"..\FileRaster.tif"); // Await the Load to catch any errors. await raster.LoadAsync(); // Create a raster function from the JSON string using the static/Shared method called: RasterFunction.FromJson(json as String) RasterFunction rasterFunction = RasterFunction.FromJson(jsonFunction); // Get the raster function arguments RasterFunctionArguments rasterFunctionArguments = rasterFunction.Arguments; // Get the list of raster names from the raster function arguments. IReadOnlyList<string> rasterNames = rasterFunctionArguments.GetRasterNames(); // Set the local file raster as a raster name argument. rasterFunctionArguments.SetRaster(rasterNames[0], raster); // Create a new raster based on the raster function. Raster rasterWithFunction = new Raster(rasterFunction); // Create a new raster layer from the raster with function applied. RasterLayer rasterLayer = new RasterLayer(rasterWithFunction); // Add RasterLayer with function to Map OperationalLayers collection. Map.OperationalLayers.Add(rasterLayer); } catch (Exception ex) { } } string jsonFunction = @"{ ""raster_function"":{""type"":""Mask_function""}, ""raster_function_arguments"": { ""nodata_values"":{""double_array"":[0],""type"":""Raster_function_variable""}, ""nodata_interpretation"":{""nodata_interpretation"":""all"",""type"":""Raster_function_variable""}, ""raster"":{""name"":""raster"",""is_raster"":true,""type"":""Raster_function_variable""}, ""type"":""Raster_function_arguments"" }, ""type"":""Raster_function_template"" }";‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Mike ... View more

Hi, Unfortunately that means your output folder path length is still exceeds 260 characters once the destination path of these LocalServer files is appended. You have two options: 1. Shorten your output path  Consider using relative paths in your project to define a shorter output location (either via the Project > Properties dialog > Build tab or directly in the .csproj file e.g. `<OutputPath>..\..\..\..\bin\</OutputPath>`. 2. Disable the automatic deployment of Local Server and use the Deployment Builder GUI - Open the file `ArcGISLocalServer_100.9.AGSDeployment` in your Project folder - Set the top-level ArcGIS Pro node to false `<Package id="Pro" name="ArcGIS Pro Compatible Server" enabled="false">`. - Ensure the top-level ArcMap node is also false `<Package id="ArcMap" name="ArcMap Compatible Server" enabled="false">`. - Note at this point you're now setup for the API to use the SDK installation (in Program Files (x86)) : this can actually be a good approach for everyday development because everything will work and avoids file copies *but* when you're ready to start thinking about building setups/deployments then you definitely want to switch back to using a deployment and you must ensure everything works with the deployment options you have chosen. Read on to use the Deployment Builder GUI... - Open the Deployment Builder GUI (search in Start Menu or go to `C:\Program Files (x86)\ArcGIS SDKs\LocalServer100.9\Tools\DeploymentBuilder.exe`). - Use the GUI to choose your deployment options and create a deployment. - Deployments are typically created in `C:\Users\<username>\Documents\ArcGIS\Runtime Deployments\<deployment_name>`. - Copy the `localserver100.9` folder created by the deployment builder GUI to the same folder as your application exe (for testing/debug).  We'll review the approach we're taking and see if there are any opportunities to reduce folder depth / file name length and avoid these path length issues.  Thanks Mike ... View more