nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SplineWithBarrier (Spacial Analyst): Different results between Modelbuilder and external PythonScript

TorstenLange

Hi,

I'm puzzled by different results I get from application of SplineWithBarrier (Spacial Analyst) using Modelbuilder and by external Python scripting:

import arcpy

points_shp = "pointShape.shp"

faults_shp = "faultsShape.shp"

outGrid = "r_out"

arcpy.gp.SplineWithBarriers_sa(points_shp, "id", faults_shp, "10", outGrid, "1")

This is the code I got from the model builder. While results there are as expected (smooth surface with discontinuities) I used it in an external script. The resulting surface derived from the external script, however, shows, that smoothing was skipped. Before I tried the version from model builder I followed the example from the ArcGIS help. Same result - the grid is created, but again smoothing step is skipped. My first code was:

import arcpy

points_shp = "pointShape.shp"

faults_shp = "faultsShape.shp"

outGrid = "r_out"

arcpy.CheckOutExtension("Spatial")

outSplineBarriers = SplineWithBarriers(points_shp, "id", faults_shp, 10, 1)

outSplineBarriers.save(outGrid)

That's the syntax from the help:

SplineWithBarriers (Input_point_features, Z_value_field, {Input_barrier_features}, {Output_cell_size}, {Smoothing_Factor})

Why is smoothing not activated? Where is my fault?

Thanks for any hint!

Torsten

Find more posts tagged with

Accepted answers

TorstenLange

Thanks for your thoughts, Dan! Luck was on my side It turned out to be as tricky as simple. A member of staff of our local ArcGIS support asked me to perform some testings with very simple paths, as some raster functions seem to be sensitive here. He also suggested to change our system decimal delimiter, even though I was using strictly "." in my python scripts (German delimiter is ",").

The last suggestion made the difference. I can now apply the range between 0 and 1 to the smoothing factor - no matter - as string or floating point.

All comments

TorstenLange

Thanks, Dan, I try your suggestion as soon as I'm at the desk again. I'm very on the edge , as I lost almost a day. Unfortunately (...or good) I don't have ArcGIS at home.

Indeed, we actually running the splinewithbarrier() for two cell sizes, 50 m and 10 m and combine those in a later step with having 10 m density close to our faults or barriers, and 50 m elsewhere. So, the 50 m grid is smooth, but the 10 m grid has an ugly stepping, which is about 1 m between the steps. The original isoline distance is 10 m. I mean, for our purpose it's not completely bad, but it makes people uncertain. And that has to be improved. But, when thinking about, and scale effects are in play, than I wonder why from within the arcgis python client smoothing seems to be better. This would mean that internally some scale depend corrections to the smoothing factor are applied without notice in the help.

DanPatterson_Retired

{ } simply means an optional parameter... on a lark...try a factor of 0.9 instead of 1 since there is some suggestion that the smoothing factor shouldn't be randomly chosen see this link near the bottom

TorstenLange

Actually, as I wrote, I tried both, the version from the model builder and the version proposed in the ArcGIS-help. Both versions run without any error, but no smoothing. I can, however, easily adjust cell size or the field of the Z values in both versions. I'm aware of the inconsistency refereing to the different application of the cell size and smoothing parameters (string vs "numbers"). But these two versions are coming from ArcGIS itself.

I have the problem, that running the exported model builder code inside the ArcGIS python client works perfect. If I run exactly the same code from the console smoothing doesn't happen. In the ArcGIS help, the smoothing factor is not applied in the examples.

I'm also confused about the small difference in the function parameters:

model builder: arcpy.gp.SplineWithBarriers_sa(points_shp, "id", faults_shp, "10", outGrid, "1")

ArcGIS help: outSplineBarriers = SplineWithBarriers(points_shp, "id", faults_shp, 10,{1})

Seems, there happens some wrapping around some other code (e.g. the Java code that is used behind).

So actually, it would be helpful to have a code snippet that is supposed to work including smoothing from an external script. Just to see if there are problems with the environment or with different python versions etc. There was a suggestion from a colleage that ArcGIS uses two Python versions (32 and 64 bit).

Hmm...?

DanPatterson_Retired

modelbuilder used "10" and "1" in double quotes

your script used numbers 10 and 1

they are not the same

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.