Latest Contributions by JoshuaBixby

As Russell Brennan‌ points out, this isn't currently possible with ArcPy.  ArcGIS 10.3 adds 9 tools to the Geodatabase Administration toolset, but sadly, this still won't be possible natively through ArcPy or any Geoprocessing Tools with the new release. This is yet another reason retiring the SDE command line tools is premature.  The use cases just keep piling up in the forums (sorry, GeoNet) where SDE command line tools work and nothing else is available, but Esri is doing their best David Farragut impersonation with this one.  Unfortunately for those customers needing to script advanced geodatabase administration tasks, this isn't Mobile Bay and the mines will go off and cause damage. The sdelayer command should work for what you need, at least for the short while it will be around: sdelayer -o {grant | revoke} -l <table,column> -U <user> -A <SELECT,UPDATE,INSERT,DELETE> [-s <server_name>] [-i {<service> | <port#> | <direct connection>}] [-D <database_name>] -u <DB_user_name> [-p <DB_user_password>] [-I] [-q] Starting with ArcGIS 10.1, Esri decided to stop publishing the reference documentation for the tools online.  If you install the tools, the reference documentation is there.  Since the tools haven't changed much over the years, I usually just look up information in the ArcGIS 10.0 ArcSDE Administration Command Reference. ... View more

I don't think using the list or tuple function in the way described here will yield the desired result.  In the original code snippet, I understand MyAttribute to be a single field/attribute, and that the goal is to populate that attribute with "ALL" or some other multi-character string.  Since a multi-character string is iterable, passing MyValue to the tuple function will result in a tuple with multiple single-character items instead of a tuple with a single multi-character items, as demonstrated. The suggestion by Dallas Shearer‌ works since it passes the update cursor a single item multi-character tuple, which is what I think the OP is after. ... View more

The recent release of the ArcGIS 10.2.2 for (Desktop, Engine, Server) Geodatabase and Feature Service Sync Optimization Patch demonstrates how much this enhancement is needed.  The patch addressed the follow bug/enhancement: NIM100697 - Change the "_VW" suffix to "_EVW" when versioned views are created, in order to be consistent the EVW naming convention when we create MV views. Since the patch doesn't go back and actually rename any existing views, we now have a situation where there is a system-set standard that isn't configurable and yet varies depending on when the data was versioned. I would say this attempt to be "consistent" has made things much less consistent in the short term, and once the SDE command line tools are gone, there is no simple way to address the inconsistency with _VW and _EVW views. ... View more

The recent release of the ArcGIS 10.2.2 for (Desktop, Engine, Server) Geodatabase and Feature Service Sync Optimization Patch demonstrates how much this enhancement is needed.  The patch addressed the follow bug/enhancement: NIM100697 - Change the "_VW" suffix to "_EVW" when versioned views are created, in order to be consistent the EVW naming convention when we create MV views. Since the patch doesn't go back and actually rename any existing views, we now have a situation where there is a system-set standard that isn't configurable and yet varies depending on when the data was versioned. I would say this attempt to be "consistent" has made things much less consistent in the short term, and once the SDE command line tools are gone, there is no simple way to address the inconsistency with _VW and _EVW views. ... View more

This topic gets even more convoluted with the recent ArcGIS 10.2.2 for (Desktop, Engine, Server) Geodatabase and Feature Service Sync Optimization Patch, which addresses the following bug/enhancement: NIM100697 - Change the "_VW" suffix to "_EVW" when versioned views are created, in order to be consistent the EVW naming convention when we create MV views. EVW?  Esri View?  Ecclesiastical Volkswagen?  Anyhow, assuming applying the patch doesn't automagically go back and rename all the existing views in an enterprise geodatabase, now we have a system-defined standard that isn't configurable and yet varies depending on when the data was versioned.  Great. ... View more

Melissa Jarman‌, no disrespect to you personally, but this is another example of why I get on soapboxes about how poor Esri's documentation is on technical limitations and implementations.  To me, personally, it is a pretty sad state of affairs when a single note in 4-version old documentation (I am counting the new incremental releases as full versions because Esri's accountants do) is used to call functionality that has worked for many years a loophole and therefore it won't be addressed in the new software.  One could argue that since the note doesn't exist in 10.2.x documentation, which is the current documentation, that it no longer applies, and therefore there is no loophole. If Esri isn't going to support Nate Arnold‌'s workflow in 10.3, Esri needs to just own it and don't try to rationalize it or blame the user. ... View more

Sadly, I ended up having to install Portal 10.3 on a workstation just to access the documentation on licensing Pro through Portal!  Seems ridiculous, but I have yet to find another place where the information is readily available. ... View more

We already have 10.2 Portal running with named users, will hopefully have 10.3 up and running in test environment shortly. Thanks for the pointer about Pro licensing information, I will take a look.  Will this same information be available on ArcGIS Resources so users don't have to download and extract files to look at higher level information like licensing? ... View more

If my memory serves me, SDC files are not supported in Pro, that may be your problem. ... View more

Single vs. multiple exit points can be one of those discussions that turns into a holy war of sorts.  I do use multiple exit points at times in specific situations, but for this small block of code I liked the single exit point.  That said, others might like the way it reads with multiple exit points. ... View more

If I understand what you are saying correctly, the code could be updated to:  (Not sure if 0.2 is float or if you have '0.2 PCT' as text, I went with float) def CalcField(zone):       risk = ''       if zone in ('A', 'AE', 'AH', 'AO'):         risk = 'High'       elif zone in ('Whatever', 'Whatever2'):         risk = 'Moderate'       elif zone in ('X', 0.2):         risk = 'Low'       else:         risk = 'somedefaultvalue'       return risk ... View more

You may be able to achieve what you want just using raster extents and not getting into cursors at all.  Does the following code work for you? def rasterDim(raster, EPSG=None):     ras = arcpy.Raster(raster)     extent = arcpy.Describe(ras).Extent     if EPSG is not None:         sr = arcpy.SpatialReference(EPSG)         extent = extent.projectAs(sr)     return extent.width, extent.height Pass the function above the text path to the raster and an optional EPSG code if you want to get the width and height based on a different projection than the raster's spatial reference. ... View more

A fairly broad question.  What specifically have you tried already?  Do you have specific code that is generating errors?  If so, what are the parts of the code generating errors and what are the errors? Not to answer a question with a question, but it is easier to get specific and quicker feedback when more details are given, especially samples of code that aren't working for you. ... View more

Read the original post a bit too quickly, I now see we are talking about lines.  I guess I don't completely understand the intent or goal of the original code.  Are featX and featY different features or the X and Y component of the same feature? ... View more

The reason for the "row does not support indexing" error is tied to the data type of row.  The code you posted is returning an arcpy Polygon object, and that object doesn't support indexing.  Since I don't know whether you are working with points, lines, or polygons, I will assume polygons and use the centroids in the code snippet below: for row in rows:     lenX = row.getValue(shapeName).centroid.X     lenY = row.getValue(shapeName).centroid.Y And I agree with Greg Keith‌, the Data Access (arcpy.da) cursors are much more robust than the older/original arcpy cursors. ... View more