Latest Contributions by TorstenLange

Ok, thank you, George! I think for the time beeing I have what I need. Regarding the registering I followed the documentation. I'll figure it out later. ... View more

Thank you for your answers! It took a bit, but as far as I can see, I got it right now. First issue was 4 unexpected double matches in the data view. Fixing, however, it didn't solve the problem. Then I created an extra table to hold unique OBJECTIDs for all objects from the queried tables, which also didn't solve the problem in the beginning. After a while I got the impression it may be related to the data type of the OBJECTID, which was bigint. Changing the type to int finally made it successful. Is type bigint an issue with ArcGIS? Also, trying to register the view in the geodatabase wasn't possible. Although, I read that registering is only required for doing certain things with the data in ArcGIS Pro and it could made reading a bit faster. However, the errors from the python command arcpy.RegisterWithGeodatabase_management("DATABASE.dbo.vw_boreholes", "OBJECTID","geom","POINT") were: ERROR 001050: Registrierung in der Geodatabase ist bereits erfolgt, oder das Dataset kann nicht geöffnet werden.                              -> Data set is already registered in the geodatabase or it can't be opend ERROR 000308: Ungültiger Feldtyp                              -> Invalid field typ ERROR 001050: I couldn't find any hint where in the database I could check if the view was already registered. How can it be done? Another issue could be related rigths on the database side. The connection is OS based, so, theoretically, everything should be fine? ERROR 000308: Not sure, what that means - could it be my geometry column? That's how it is created:        geometry:: STGeomFromText('POINT(' +                                                         CAST(CAST(bores.XCOORD AS decimal(14, 6)) AS varchar) +                                                         ' ' +                                                         CAST(CAST(bores.YCOORD AS decimal(14, 6)) AS varchar) +                                                         ')', 25832                                                        ) as geom ... View more

Yes, all queried tables are within the same database and the view is the only one. The point geometry column is added on the fly from X, Y coordinates. As you suggested, I created a simple view from only one table, which works perfectly. I guess, the problem is connected to the oid, that ArcGIS tries to create. By pulling the view from the catalog to the map, the simple view is opened with a dialog requesting the primary key columns, but the complex view is just loaded without any dialog. If I try to apply a definition query in the properties dialog of the dataset the ESRI_oid shows just values of 1 to 3 and the query cannot be applied (error message). To force assigning primary key columns I tried to use 'add data' -> 'query layer' which allows me to select the relevant key columns, but it doesn't change the behavior at all. The complex view covers 9 tables including subqueries and serveral unions. Could there be limitations regarding query complexity of views? ... View more

The SQL Server version is 14.0.1000.169. Unfortunately, our IT department doesn't update the ArcGIS Pro version quite often. ... View more

I have some more screen shots now. I tried to use smoothing factors between 0 and 1, which doesn't work at all. Neither I can code the smoothing factor by floating point nor by string (0.9, "0.9"). The function actually takes for cell size and smoothing factor either values as strings or as number. But any smoothing factor between 0 and 1 crashes the process when it comes to smoothing, not matter if I give the value as floating point number or string: Fuer Zellgroesse 50 m...  ( == this run is for 50 grid) java version "1.6.0_43" Java(TM) SE Runtime Environment (build 1.6.0_43-b01) Java HotSpot(TM) Client VM (build 20.14-b01, mixed mode) ERROR: 'Spline mit Barrieren' fehlgeschlagen    ( == failed) ERROR: Traceback (most recent call last):   File "contourgridder.py", line 189, in <module>     outSplineBarriers = SplineWithBarriers(tmp_points, o.Z_field, tmp_stoerungen, cell_size, o.r_glaettung) File "C:\Program Files (x86)\ArcGIS\Desktop10.2\arcpy\arcpy\sa\Functions.py", line 7079, in SplineWithBarriers     Smoothing_Factor)   File "C:\Program Files (x86)\ArcGIS\Desktop10.2\arcpy\arcpy\sa\Utils.py", line 47, in swapper     result = wrapper(*args, **kwargs)   File "C:\Program Files (x86)\ArcGIS\Desktop10.2\arcpy\arcpy\sa\Functions.py", line 7072, in Wrapper     Smoothing_Factor)   File "C:\Program Files (x86)\ArcGIS\Desktop10.2\arcpy\arcpy\geoprocessing\_base.py", line 498, in <lambda>     return lambda *args: val(*gp_fixargs(args, True)) arcgisscripting.ExecuteError: 'Spline mit Barrieren' fehlgeschlagen Fehler beim Ausführen von (SplineWithBarriers).  ( == Error during execution of SplineWithBarriers) Below are the new screen shots. See the huge difference between external script and sript in the ArcGIS python client. Actually, it looks to me now, that the smoothing factor indeed works, but maybe only as True or False (1 or 0) and that there is a difference in how smoothing is applied...? Screen shot 1: 50 m grid with smoothing factors 1 (blue) and 0 (yellow), isolines in red. Screen shot 2: 10 m grid with smoothing factors 1 (blue) and 0 (yellow), isolines in red. Screen shot 3: 10 m grid from within ArcGIS smoothing factor 1 (blue), isolines in red. ... View more

Ok, that's how it looks. I got two screen shots, actually from our 3D geometrical modeling software to have a better view on the data. The grid cells are represented by the points now. What one can clearly see ist the difference between running from inside ArcGIS (graphical dialog or python client) and the from external script. Screen shot 1: inside Arcgis Screen shot 2: Result from external script ... View more

Sorry, I wrote mistakable - its not like that. The isolines are every 10 m - like 250, 260, 270 etc. 'Guess, contour level was the appropriate term. Distances between 10 m isolines of less than 10 m don't exist. It's about a rather gentle morphology of geological layers - no steep gradients. I could provide some screen shots on monday... ... View more

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. ... View more

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...? ... View more