Latest Contributions by KoenVolleberg

‎12-06-2013

Hi all, I come up with the same issue. Anyone found a solution yet? The last suggestion jamesfreddyc did works for point features, not for polyline features. Cheers, Koen

‎07-21-2011

Hi Fred, just tried it, but without success. It's a very strange bug. Thanks for the suggestion. Cheers, Koen

‎07-18-2011

I use Data Driven Pages (ArcGis 10) to create some 1000 maps. In these maps, I've got an elevation raster dataset of which the streched symbology is recalculated for each display extent. When scrolling through the pages in the DDP-toolbar, I see the symbology scaling as expected. So far, so good. When I add a legend showing the raster symbology, things start to get buggy. Although the data is updated in every page, the legend is not. Also, in the TOC, I don't see the new min-max values. I tried to solve this with ArcPy (adding, removing, updating the layer etc), but without success. Of course, I want to have a legend that corresponds with the view, and not with the first page out of 1000. I posted this bug to Esri Netherlands. They were able to reprooduce the bug, and forwarded it to Esri Inc. This was 4 weeks ago, and Esri NL and myself are still waiting for a solution or workaround from Esri Inc. No response from the USA yet. Anyone the same problem and a solution? Esri Inc: when you read this: it would be nice to respond and (at least try to) solve things when your customers find out problems. Looking at this forum, I conclude that the people that pay huge amounts of money for your licenses are pretty negative about your software. It surely would pay off to improve customer service. Koen

‎03-29-2011

Hi Chris, thanks for the suggestion. I implemented it (indeed I had to modify a bit), but without success. I'm going to try if it has to do with arcgisscripting instead of arcpy in ArcGIS 10. If I find a solution, I'll post it here. EDIT: arcpy does not work either. Seems like something in FeaturetoRaster coversion. Maybe ESRI has a solution?

‎03-28-2011

I've got an ArcGIS 9.3 script that is also to be used in ArcGIS 10 (but not exclusively). Under ArcGIS 9.3, this script runs quite fast (<1min per raster), but in ArcGIS 10, running time is dramatically longer (>10min per raster). This is, obviously, not acceptable. The resulting raster has 7349 columns and 6110 rows. Can anyone tell the reason behind this huge differnce in processing-time (is it because I'm using arcgisscriping instead of arcpy?). import os, sys, arcgisscripting gp = arcgisscripting.create(9.3) inShape = gp.GetParameterAsText(0) outRas = gp.GetParameterAsText(1) field = gp.GetParameterAsText(2) cellSize = gp.GetParameterAsText(3) snapRaster = gp.getParameter(4) #Storing old snapping parameter oldSnap = gp.snapRaster #Define snap raster #define extent gp.SnapRaster = snapRaster oldExt = gp.extent rasDesc = gp.Describe(snapRaster) newExt = rasDesc.extent gp.extent = newExt #Conversion gp.FeatureToRaster_conversion(inShape, field, outRas, cellSize) gp.snapRaster = oldSnap gp.extent = oldExt del oldSnap, oldExt

‎09-02-2010

Hi all, as Richard also stated, my LR-event layers are definately slowing down the process. Thanks for the sugegstion! I performed the calculations directly on the tables, instead of the event-layers, which dramatically improved performance. This opened my eyes for the performance-issues (but not big ones) for other scripts which process LR-event layers. Cheers, Koen

‎09-02-2010

Hi Richard, Chris and others, sorry about my somewhat negative posts, but I was kind of frustrated that things did not work as they should be. I hope with all your suggestions, the problem may be solved. I'm running an XP-machine (2core 2*2.8, 2GB mem, XP SP3, ArcGIS 9.3 SP1), with my FGDM stored on my local disk, so network-problems do not occur. In my FGDB are stored 7 FD's, all containing around 5 FC's (structure must be maintained). In one of the FD's are routes stored, with the route-eventtables directly in the FGDB root. My script converts these event-tables to event-layers (MakeRouteEventLayers), before the part that I have shown does it's job on the EventLayer. Could this cause the slow-down? I tried to find out which tool causes the slowdown: it's the set of CalculateField-commands, and not the AddField-commands, which do their job (almost) instantly. Hope someone has some more suggestions. In the meanwhile, I'll fiddle around with other options. If I got something that solves it, I'll post the solution here. Thanks, Koen

‎09-01-2010

Found out that it's also related to the fact that the data on which CalculateField is performed, is stored in a File Geodatabase. The File Geodatabase seems to be extremely slow. I copied the data into an in_mem dataset before calculating, which improved performance from 1min to 2sec! Only problem is that by copying the features, the ID's are messed up, since I need these to make notifications with. (saw 5 reasons to go for FGDB, but one of the reasons not to is the terrible performance). Koen

‎09-01-2010

Hi all, I've got a Python-script (sample below) which appends all points from a list of Route Event Layers into one in_memory feature class. Before the append, I need to calculate some field, using CalculateField. However, CalculateField is extremely slow (say 5min for 5000 records). I also tried the UpdateCursor, but same lack of performance. Anyone a suggestion how to speed up my process in ArcGIS 9.3? Thanks, Koen allPoints = "in_memory/allPoints" gp.CreateFeatureClass("in_memory","allPoints","POINT") gp.AddField(allPoints,"ORIGID","LONG") gp.AddField(allPoints,"ALLELEV","DOUBLE",15,6) gp.AddField(allPoints,"ORIGFC","TEXT",50) i = 1 for item in elevationPointList: desc = gp.Describe(item) oidFieldName = desc.OidFieldName flds = gp.ListFields(item) origIDExist = False allHExist = False origFcExist = False for fld in flds: if fld.Name == "ORIGID": origIDExist = True if fld.Name == "ALLELEV": allHExist = True if fld.Name == "ORIGFC": origFcExist = True if origIDExist == False: gp.AddField(item,"ORIGID","LONG") if allHExist == False: gp.AddField(item,"ALLELEV","DOUBLE",15,6) if origFcExist == False: gp.AddField(item,"ORIGFC","TEXT",50) writeLog(item + "0 " + dt.now().ctime()) gp.CalculateField(item,"ORIGID",'[' + oidFieldName + ']') if item.count("_events") > 0: gp.CalculateField(item,"ORIGFC",'\"' + item.replace("lyr_","") + '\"') gp.CalculateField(item,"ALLELEV",'[TOPELEV]') else: gp.CalculateField(item,"ORIGFC",'\"' + getBaseName(item) + '\"') gp.CalculateField(item,"ALLELEV",'[ELEV]') writeLog(item + " " + dt.now().ctime()) gp.Append_Management(item,allPoints,"NO_TEST") gp.DeleteField_Management(item,"%s;%s;%s" %("ORIGID","ALLELEV","ORIGFC"))

‎05-19-2010

I believe it is possible. Just write a Python script as if it were run from within ArcGIS. Run it from within a dos-prompt: <name_script.py> <param1> <param2>... Works for me, so I think it should work for you as well. But only just as long you have ArcGIS installed. Cheers, Koen

‎05-19-2010

Hi all, I want to extract elevation data from a terrain to a point feature class, like in the Surface Spot tool. However, in ArcGIS 9.3, Surface Spot won't accept terrains as surface input (what is the difference between a terrain and a surface?). Any suggestions that do not involve converting the terrain to a raster or tin? How are we supposed to use terrains instead of tins when such analysis-tools are not working with terrains? Cheers, Koen

‎05-18-2010

Hi all, I've got a tool which calls the Locate Features along Route tool: gp.LocateFeaturesAlongRoutes_lr(in_points, in_routes, "number", tolerance, out_events, "rid POINT MEASURE ", "ALL", "DISTANCE" ) For a dataset with 225 lines/routes (with an attribute index for "number") and on these lines 7912 points to be converted to events, it takes some 45seconds to complete the process. However, I've got some pretty large datasets (several 1.000s lines and >50.000 points), it takes quite long. Where can I look for speeding up this process, or is LocateFeatures... a very slow tool whatever you do. Thanks in advance! Cheers, Koen

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by KoenVolleberg

Re: Creating Polylines with Z-values very slow

Re: Data Driven Pages fail to update legend

Data Driven Pages fail to update legend

Re: Feature to raster Python very slow in ArcGIS 10

Feature to raster Python very slow in ArcGIS 10

Re: CalculateField extremely slow

Re: CalculateField extremely slow

Update: CalculateField extremely slow >> in a File Geodatabase

CalculateField extremely slow

Re: Dumb question - can I write standalone python script to run without arcgis?

3D Analyst - Surface Spot for terrains

Locate Features along Route slow - how to speed up things