Tag Info

New answers tagged

6

The most important thing 9.x users need to know is that ArcSDE no longer exists. There had been no fundamental changes to the ArcSDE API since 9.0, when XML, INT64, UUID, CLOB, NSTRING and NCLOB types were added. Since then, the only changes have been Projection Engine mods to support newer projections and vertical datums. The API itself is now deprecated ...


0

If I understand your question correctly, the following workflow could be an alternative. Create sets of non-overlapping polygon either by code (see this discussion) or manually (run 'zonal statistics as table', identify the zones that have not been calculated and separate them into a new layer. Repeat with the separated layer to find more potential ...


1

You should not need to write the temporary rasters on disks. arcpy optimization is quite obscure to me, but not writing the feature class should help. In fact, you should be able to use geometry object directly for the clip for row in rows: # Execute ExtractByMask outExtractByMask = ExtractByMask(inRaster, row.getValue(shapefieldname)) ...


1

I think you are approaching the problem the wrong way. You can't load a gigantic dataset and expect fast interactivity. If you've already simplified as much as you want, and it's not fast enough. Try a different technology. If you're not happy with TileJSON, use CartoDB or MapBox to to it for you, or use WMS for viewing and WFS for interactivity. Or load ...


1

I recommend that you review the Help page entitled Managing the performance of ArcGIS map services. In particular I think you should look at the dot point from that page below: Precompute information results when you can do so. For example, you can precompute the maps that are delivered with ArcGIS for Server and use cached map services or basemap ...


0

In its current form I think your question is too broad for our focussed Q&A format because in essence it is asking for a list of ways that we can think of to speed up your code. However, to get about a ten-fold increase in one aspect I think that you should start by replacing your arcpy.SearchCursor syntax with arcpy.da.SearchCursor. From there I would ...


1

Interrupting a rendering process is not possible in Leaflet since it is performed in a single atomic JS job (AFAIK). The only way to make your app more responsive to user interactions might be to boost the rendering process so that it completes faster. Simplifying the geometries (or using topojson) is an excellent first solution for that. Another one could ...


5

Turn off snapping (Snapping toolbar, uncheck "Use Snapping"). I've had this problem before when there are many vector layers in a project, the cursor is getting bogged down looking for a vertex (or edge, or whatever) to snap to. You could also try copying the image to be georeferenced to a new, empty ArcGIS project along with the bare minimum of vector ...


2

The only way you are going to know for sure is to do it by yourself. The answer is not definitive and is dependent on your system... how many cores, what else the OS is doing at the time etc.. Yes, ArcGis and QGIS are that close that it sometimes makes little difference which one you use. The bigger question is why buy ArcGis when QGIS is free?, the answer ...


16

One of the developers of arcpy.da here. We got the performance where it is because performance was our primary concern: the main gripe with the old cursors were that they were slow, not that they lacked any particular functionality. The code uses the same underlying ArcObjects available in ArcGIS since 8.x (the CPython implementation of the search cursor, ...


3

Performance related Cursor only iterates through set list of fields by default (not the entire database) Other not directly related to performance, but nice enhancements: Ability to use tokens (e.g. SHAPE@LENGTH, SHAPE@XY) for accessing feature geometry Ability to walk through databases (using arcpy.da.Walk method)



Top 50 recent answers are included