Latest Contributions by RichardHughes3

My current task is developing a python addin toolbar to help with my data production.  It works great most of the time, but there are closed state issues that I need to seriously address at some point.  Anyway, I've read into the 'headless' user technique for restricting what operations can be performed on the database during scripting.  I've been absorbing the previous replies and seem to understand them as a need for user tiers with groups and permissions.  Is this an accurate assessment? ... View more

Table names are case-insensitive.  All comparisons should be done with an insensitive operator or by first upcasing both strings. Best practice is to reserve the SDE user for geodatabase administration.  Instead of creating spatial data as SDE you really ought to create user(s) (with same-named schemas) to own spatial tables, and user(s) to access it (without the possibility of removing the tables accidentally, or as a result of a DOS attack). - V Vince, I created a new version under my user and connected to it using database connections.  Is that more or less what you were referring to?  The owner of my editing version is now richard instead of sde. Thanks, Richard ... View more

Table names are case-insensitive.  All comparisons should be done with an insensitive operator or by first upcasing both strings. Best practice is to reserve the SDE user for geodatabase administration.  Instead of creating spatial data as SDE you really ought to create user(s) (with same-named schemas) to own spatial tables, and user(s) to access it (without the possibility of removing the tables accidentally, or as a result of a DOS attack). - V Setting all upper case did solve the issue.  It will just remain a mystery.  I will have to do some additional research into your second paragraph.  We operate by using versions, but alas I am not at that stearing wheel. ... View more

I have noticed depending on how and where layers are created in SDE the software changes the capitalization regardless of what I entered as the creation or output name.  What problem is it causing you?  If trying to set a layer by the source name then I would suggest to uppercase all layer name variables when looking for them, so they will match.  Would that help with this situation? Thanks, Sol Using .upper() at the end of the dataSource fixed the problem and my python set() condensed the layer's dataSources down to a single source.  This is just something I has to be included in all scripts with dataSources.  Thank you for your input. ... View more

                          try:                                         ID_check = entry[0]                                         print entry[0]                                         intable = "in_memory\ID_Check"                                         counter = 0                                         with da.SearchCursor(intable,["ID"]) as cursor:                                             for row in cursor:                                                 if row[0] == ID_check:                                                     counter += 1                                                                                             if counter >= 1:                                             pythonaddins.MessageBox("This Feature's ID is a duplicate.  Solve thi                                                                                s error before continuing!","Error",0)                                             raise Exception()                                                                                 elif counter == 0:                                             print "All is good, this ID is not a duplicate."                                             cursor = arcpy.da.InsertCursor(intable,["ID"])                                             cursor.insertRow([ID_check])                                             del cursor                                             edit = da.Editor(workspace)                                             edit.startEditing(False,True)                                             edit.startOperation()                                                                                         with da.UpdateCursor(targetlayer,fields) as cursor:                                                 for row in cursor:                                                     row = entry                                                     print "row: {}".format(row)                                                     cursor.updateRow(row)                                                                                                 del cursor                                             del row                                             edit.stopOperation()                                             #edit.stopEditing(True)                                                                                                                             except Exception as e:                                         print e.message                                         print arcpy.GetMessages()                                                                             arcpy.RefreshActiveView()                                     print "Complete"                                 When using "print edit.isEditing" after each edit method they are all true.  When I uncomment the line edit.stopEditing(True) an exception is thrown before the print statement saying Start Edit Session.  This happens in a versioned sde environment.  When using the same code in a personal geodatabase the exception message states something like "unable to perform within an edit session." So my solution for sde is to comment out the stop editing method.  This works however if I create a feature then save edits.  If I later change the attributes or geometry of that feature the state of the geodatabase changes and the edits cannot be saved.  "Attempting to perform action on a closed state.  Unable to save edits." ... View more

I too am unable to view WMS 1.1.0 or 1.3.0 inside of ArcMap 10.2.  Both my GetMap and GetCapabilities work in a browser and I can view the the images inside of MapServer for Windows.  They are being served by Apache so my situation is a little different.  The problem is the same though, that the images are not being displayed inside ArcMap. A GetCapabilities request is being sent to MapServer successfully from ArcMap.  There is not record in the logs of a GetMap request being sent at all. Richard ... View more

True about the color balancing.  From what I can gather, the various color balancing techniques are very different from one another, and in some cases one will work while the others cannot.  When multiple rasters (over 5) are involved, I would recommend setting them into groups by attribute in the footprint.  There is a block setting in the color balancing menu that will treat all rasters in a group as a single raster and not balance them individually.   This should allow smaller groups to be balanced to larger groups.    Right now I have all of the Landsat 8 scenes that cover South Carolina.  Since each row was shot hours apart, there are drastic differences between the images.  I realize that Landsat data is WYSIWYG, but the analysis process of the entire states seems difficult when the histograms are shifted. I have had color balancing crash ArMap ( I don't know why), and I have gotten white blotches (I don't know why).  So far my best case scenario with color balancing is with 3rd Order Dodging on 8 bit unsigned NAIP Imagery.  The 16 bit unsigned Landsat imagery does not play well with color balancing for me.  I did read in a python script this morning where an Esri employee used the color grid balance on a Landsat 8 mosaic dataset.  I will be going with that next time.  Looking through Esri python scripts for mosaic datasets seems to be the best place to find the answers for this stuff.  After spending time learning the theory, process, and what does not work, I just need to know what works so I can move on to the analysis .... ... View more

Update: I went into the Results window and the Append tool shows the hour glass.  I right clicked Output Features and chose to Add To Display.  The new waterbodies feature class was added to the display.  However, the background process is still running.  The lock on my geodatabase is still there. ... View more