Latest Contributions by RichardFairhurst

‎11-17-2011

On my first topic I have found several interfaces that need to be checked to determine if an Edit Session can be safely started on SDE data. When dealing with SDE, you need to check if the feature class can be updated, deleted or inserted. For that you can use the ISQLPrivilege interface: Dim workspace As ESRI.ArcGIS.Geodatabase.IWorkspace = pDataset.Workspace ' Assume pDataset is assigned a Dataset If workspace.Type = esriWorkspaceType.esriRemoteDatabaseWorkspace Then Dim pFCName As IFeatureClassName = pDataset.FullName Dim pSQLPriv As ISQLPrivilege = pFCName If pSQLPriv.SQLPrivileges And esriSQLPrivilege.esriUpdatePrivilege <> esriSQLPrivilege.esriUpdatePrivilege Then ' Bitwise check for Update Privileges MsgBox("You do not have priveleges to update this feature class!") End If End If The Bitwise check can combine multiple states. For example to see if all edit priveleges are granted use: If pSQLPriv.SQLPrivileges And (esriSQLPrivilege.esriUpdatePrivilege Or esriSQLPrivilege.esriDeletePrivilege Or esriSQLPrivilege.esriInsertPrivilege) <> (esriSQLPrivilege.esriUpdatePrivilege Or esriSQLPrivilege.esriDeletePrivilege Or esriSQLPrivilege.esriInsertPrivilege) Then ' Bitwise check for All Edit Privileges Assuming the user has the approrpiate edit privileges you also need to check the current state of the Editor Options setting to permit versioned and non-versioned editing and compare it to the version status of the Dataset you want to edit. The IEditProperties3 interface tells whether the Editor Options are set to allow versioned or non-versioned editing while the IVersionedObject3 can determine if an SDE dataset object is versioned or non-versioned. The settings of the Editor and the Feature Class target must match to allow the Editor to be started: Dim pVO3 As IVersionedObject3 = pDataset ' Assume a valid SDE Dataset is assigned to this variable Dim pEP3 As IEditProperties3 = m_Editor ' assumes this variable is assigned with an instance of IEditor Dim MESM As esriMultiuserEditSessionMode = pEP3.MultiuserEditSessionMode If MESM = esriMultiuserEditSessionMode.esriMESMVersioned And Not pVO3.IsRegisteredAsVersioned Then ' Do something when the Edit Mode in set to versioned editing but the Dataset is non-versioned ElseIf MESM = esriMultiuserEditSessionMode.esriMESMNonVersioned And pVO3.IsRegisteredAsVersioned Then ' Do something when the Edit Mode in set to non-versioned editing but the Dataset is versioned End If The MultiuserEditSessionMode setting can used to notify the user that there is a mismatch or it can actually change the Editor Option setting to match the dataset. If the Editor Option is changed it should be reset back before the user can regain control or else the user should be allowed to determine if the tool should proceed and be notified of the change, since if the code does not change the setting back if will affect the user's ability to start or stop an edit session on versioned or non-versioned data. I hope this helps someone.

‎11-16-2011

A few observations in my testing of a new set of routines based on the help I found. The help encourages the use of the Editor interfaces (IEditor, IEditor2 or IEditor3) for managing edit sessions rather than the Geodatabase interfaces (IWorkspaceEdit and IMultiuserWorkspaceEdit). This appears to relate to the locking behavior I mentioned in my second question and to my third question about refreshing the Desktop editing tools like the Sketch Properties window. The Editor interfaces are the only ones that affect what the user sees in Desktop. The Geodatabases interfaces do not. So if I use the Editor interfaces to start an edit session and an edit operation the Desktop responds by enabling the Editor menu and blanks out the Sketch Properties window. When the edit operation complete it does not leave a lock that prevents user actions with editor in Desktop. The operation can also be undone by the user through the normal undo interface if the edit session is left active and the edits are not saved. But if I use the Geodatabase interfaces the Desktop does not respond at all and any failure to complete the edit session with that interface when the user had not started an edit session will interfere with the user trying to start an edit session in Desktop if the program edit session did not complete. There also is no way for the user to undo the operation through the normal Desktop interface and only the program can manange any undo. So to the extent that the Geodatabase interfaces are used the edit session those interfaces manage has to be completely self contained and must complete all operations and edit sessions begun by those interfaces in the code. It appears to me that the Geodatabase interfaces are better suited to ArcCatalog operations rather than Desktop operations, given that these interfaces interfere with the Desktop edit session but do not give the user access through the normal interfaces to resolve any conflicts the program may have created and failed to resolve. In Desktop the Geodatabase interfaces can be used to test for certain edit states that are not available with the Editor interfaces, but only the Editor interfaces should be used to actually start or stop the editor or the edit operations in Desktop code.

‎11-14-2011

I completed a Model that overlays several polygon layers, clips out a specified section, dissolves according to certain attributes and sums the acreage. What I want to do is add another Calculate Field entry into my Model, but I can't get the Field Calculation correct. The Fields I want to select from are [CAUVLCType] and [MUSYM]. The fields are coded-value domains and descriptions. What I've tried is similar to Label expressions: Function if ([CAUVLCType] = 'CROP' AND [MUSYM] = 'NpA') then [Soil_Acreage] * 460 elseif ([CAUVLCType] = 'WOOD' AND [MUSYM] = 'NpA') then [Soil_Acreage] * 100 End if End Function Can someone provide me a couple lines of code that will work on a copy/paste basis which I can repeat and enter different field descriptions as needed?! Thanks, Jeff Drop the Function brackets. They are not used in the Field Calculator. Also, if you are using VB Script, use double quotes not single quotes for literal strings. Finally you have to return a variable value to the expression in order to output your calculated values. Try these settings (use the expression builder in the Field Calculator tool): Parser: VB Script Code Block: Dim Output If ([CAUVLCType] = "CROP" AND [MUSYM] = "NpA") then Output = [Soil_Acreage] * 460 elseif ([CAUVLCType] = "WOOD" AND [MUSYM] = "NpA") then Output = [Soil_Acreage] * 100 End if Expression: Output

‎11-14-2011

Thanks for that-very complicated methods to do a simple task and clunky too-thanks, I'm investigating but may be easier just to do it in MapInfo cheers You're welcome. Post a picture if you can get beyond your attitude. This "simple task" is not well described.

‎11-14-2011

After searching the forums a little more I came across a few help topics that seem to deal with many of my questions. The most useful topics are Editing with the geodatabase API, Updating Features, Managing edit sessions and edit operations, IWorkspaceEdit Interface and IMultiuserWorkspaceEdit Interface It looks like I will need to revise my code substantially to properly implement the recommended practices for editing with ArcObjects. If I come up with a good workflow for properly checking the current state of the Editor relative to the layer I want to edit, determining appropriate editing options for a layer based on its data type, selecting the best method that enhances performance without compromising data, etc... I will post it here.

‎11-14-2011

All the Python examples to work with geometry are for point features. Would someone please tell me how I can get the measure (not length) from a route feature class? Your help is greatly appreciated. Fardosht If all you want is the beginning or ending measure value of a line the code in the Field Calculator that works using Python (if you have 9.3 or up) is one of the following: !Shape.FirstPoint.M! !Shape.LastPoint.M! If you are wanting the measure at any point along the line I am not really sure if Python has an interface that replicates the ArcObjects IRouteLocator and IRouteLocation functionality.

‎11-13-2011

Actually, now that I think about it the Drop Elevations would be useful in conjunction with the other tools to set up a reinterpolation of a portion of the line and would avoid having to switch to the Sketch Properties Window to do it with the Z button. The Set Direction as Z also would be useful to make the line orient to the overall Elevation increase or decrease as specified by the user (however, this option could not apply to polygon boundaries).

‎11-13-2011

For editing lines with Z values and possibly polygon boundaries with Z values in ArcMap, ArcScene and ArcGlobe, provide editing capabilities similar to those found on the Route Editing Toolbar and Route Measure Editng Context Menu options available for Linear Referencing. The Route Editing Toolbar allows the editor to Define a Line portion between verticies, which would be useful for lines and polygon boundaries. The context menu works on the entire feature of on the defined line portion. The Route Measure Editing options that seem applicable to Elevation Editing include: Insert Vertex at Z... - Enter an elevation value and have a vertex inserted at that elevation along the line (multiple verticies could be created if the line goes up and down above and below that elevation, but if the line holds constant at that elevation or already has a vertex at that elevation for a given portion of the line no new vertex would be inserted). This could be very useful in defining vertical snapping planes between existing features that new features could follow. Apply Factor - Apply a unit conversion factor to the entire feature or just a portion of the feature. While this most obviously allows for conversions between different unit types, used creatively with the opther options listed here this could allow for the creation of vertical bowing or curving (power line sags or overpass vertical curves) by manipulating only 3 or 4 points. Offset - Add a set unit value to a feature or portion of a feature - This would maintain the existing elevation profile but raise or lower it by a specified amount. Interpolate Value - While Z does not have NaN values like M, it does default to an elevation 0 for new features or the user may have set a constant elevation where they really want values to be reintepolated between other known elevations. This option would allow a user to enter an elevation value (typically 0) and have those values on the feature or portion of the feaure interpolated to fall between the elevations with other values on either side of those vertices. Set From/To - This tool reports the elevation at the ends of the feature or the portion of feature selected and allows the user to reset the ends and cause interpolation to occur on all vertices between. Two interpolation options exist with this menu choice. The default does not preserve the existing elevation schema and interpolates a straight line elevation between the two end points (based on 2D segment lengths). The other option preserves the elevation schema and maintains relative elevation increases and decreases between the two ends, but adjusts them by the differential factor to stay proportionate between the two new end elevations. I do not think that the Set as Distance, Drop Measures and Set Direction as M options are transferrable to Elevation editing, but if someone thinks that they are I am willing to be corrected. Polygon boundaries would have to enforce rules to ensure closure if they could be edited in this way, but I believe it is possible to apply these editing tools to their boundaries as well. See the help here for illustrations of how the ideas above apply to editing Measure values: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//00390000002s000000.htm An illustration of what I would like is below:

‎11-13-2011

Esri has confirmed the behavior I observed and has logged a bug report under NIM075261 - ICurve3D.Length3D property returns incorrect value if Z units differ from XY units. This affects the Geometry calculator for 3D Lengths and any ArcObjects code using this interface when Z units are not the same as XY units.

‎11-12-2011

I have a fairly simple application where I want to create a measure system of miles for a subset of our roads. The route is created correctly with measure units in meters, but when I attempt to use miles, the issue I have is as follows. I did a test with only one street. The street and route feature class are in a feature dataset with a state plane projection, units in meters. I used the default M resolution for the output feature dataset of 0.0001 (also tried 0.00001). The street is 0.6 miles long. Using the Create Routes tool I applied a measure factor of 0.000621371192 (conversion from meters to miles). The route created has vertices with zero measures where the steet is less than 0.5 miles in length, then vertices with measure values of 1 for vertices where the street is above .5 miles in length. (see attached image). I also tried to add a miles field to the street and reference this when creating the route with the same effect. How can I keep the measure from being rounded to the nearest integer? Did you set the Environment Settings of the Create Route tool to match the settings you wanted for the output and double check that the output actually maintained the input M Tolerance, Resolution and Domain? I find that it is important to set that up in the Environment Settings even if your input has everything correct. A related item is to set up the XY Domain, Resolution and especially Extent in the Environment Settings since a subselection sometimes overrides the input domain and extent and reduces the accuracy of the length units output or shifts points, which affects the Create Route tool accuracy. I recommend not relying on the Same As Input environmental setting for cases like this. Also, you may want to try setting the min resolution Environmental Setting with something like -10000.0001 to force decimal places into the domain. It took me some experimentation to get the Environmental Settings the way I wanted and I had to play around with both the XY and the M settings to get it to work. Here are the settings I use in my model to get the output I want: # Set the Geoprocessing environment... #gp.XYTolerance = "0.003280833333333 Feet" #gp.XYResolution = "0.000328083333333 Feet" #gp.XYDomain = "-118608900 -91259500 2954993346592.94 2955020695992.94" #gp.outputCoordinateSystem = "PROJCS['NAD_1983_StatePlane_California_VI_FIPS_0406_Feet',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Lambert_Conformal_Conic'],PARAMETER['False_Easting',6561666.666666666],PARAMETER['False_Northing',1640416.666666667],PARAMETER['Central_Meridian',-116.25],PARAMETER['Standard_Parallel_1',32.78333333333333],PARAMETER['Standard_Parallel_2',33.88333333333333],PARAMETER['Latitude_Of_Origin',32.16666666666666],UNIT['Foot_US',0.3048006096012192]]" #gp.extent = "6129957.88366199 2098700.9515318 7097398.14694032 2341052.42516121" gp.MTolerance = "0.001" gp.MResolution = "0.0001" #gp.MDomain = "-100000 900719825474.099" Of course the Extent is specific to my data, but I found all of these work together to get accuracy to 4 decimal places for my M values, which are in Feet. Leaving the values as Same As Input did not work and caused similar effects to what you are describing. In my case I also needed the Extent to stay constant othewise I could not append output files together (I build my routes in groups and then append them together to improve performance of the Create Routes tool).

‎11-11-2011

I tried to run a watershed delimitation on a small piece of 10m DEM in Central Washington State. I was getting some strange results and when I examined the accumulation grid, I found that a seam in the DEM was causing all the flow from an adjacent drainage to get captured by my drainage. I set about trying to correct this DEM. I figured I'd just go Raster to Multipoint, create a point FC with Z values to act like little dams and channels in the surface, create a new terrain from the multipoints and the new point feature class, then terrain to raster, and rerun the watershed. But editing the point feature class has become my problem. When I created the points layer, I created it to contain Z-values, and I added an attribute called VALUES, and when editing, I stuck the desired corrected elevation into the VALUES attribute. The only way I could figure out to get the corrected elevation into the Z-values while editing was by editing the vertices under Sketch Properties, and I could only do one at a time. I thought I would just "Populate Zs from attributes". But after I got this far, it seems that "Populate Zs from attributes" is only available from Production Z Management and Production Editing, but I think Production Editing is only available in the Nautical or Aeronautical extensions which I don't have. Searching support I found VBA solutions to updating Z values from attributes, but that seems to be only applicable to 9.x. I'm trying to figure out how to do this in 10.0, SP3. Based on the ArcGIS 10 Field Calculator help you can adjust the coordinates of a point by using the field calculator on the Shape field of your point class. Here is the example given: "For a point feature class, shift the x coordinate of each point by 100. Parser: Python Expression: shiftXCoordinate(!SHAPE!) Code Block: def shiftXCoordinate(shape): shiftValue = 100 point = shape.getPart(0) point.X += shiftValue return point " Adapting this to what you need it should be something like this (where the !VALUES! field should match the name of the attribute field containing the Z values you want to assign to your points and no values of that field should be Null): Parser: Python Expression: assignZCoordinate(!SHAPE!, !VALUES!) Code Block: def assignZCoordinate(shape, z_Value): point = shape.getPart(0) point.Z = z_Value return point I hope this helps.

‎11-11-2011

I got the same Reshape error working in ArcGIS 10 personal geodatabase. I saved the mxd in 9.3 to troubleshoot the problem and didn't get the error. After couple of hour of struggle, I exported the file from personal geodatabase to Shapefile format and tried Reshaping again in ArcGIS 10, that seem to work. I am having wierd issues with ArcGIS 10, hope these issues will get resolved in next version (or service pack). By exporting to Shapefile format the non-linear geometry (circular, ellipse, bezier) was densified and converted to linear geometry (the curve is broken into short segments that are straight lines). This is because Shapefiles are incapable of supporting non-linear geometry, while a geodatabase can. If your objective was to get the process to preserve your non-linear geometry you did not succeed. Possibly the reason edges do not match as reported in other parts of this thread is that densification may be occurring in other geoprocessing steps and it will always occur if the output is to a Shapefile.

‎11-10-2011

Three questions: 1) I am trying to create an add-in for distribution that edits features both inside and outside of an edit session while Desktop is open. If I was designing this just for my own use I would know the way the add-in behaved and would generally know not to try to edit a workspace I do not have write access to, but I do not want to assume that about my users. What is the best way to test that a workspace can be edited by a user? 2) SDE seems to always need an Edit session started for any of the editing code I have ever gotten to work, but geoprocessing tools work on SDE data without an edit session being started by the user. I have tried using the IWorkSpaceEdit to determine if an edit session already exists and if it does not I begin an edit session in the code and wrap the actual edits in a StartOperation and StopOperation pair. I do not seem to see this behavior with non-SDE feature classes (which do not use a edit session and just update the feature directly). Below is my code. It completes fine, but the Editor in ArcMap does not actually start an Edit session and if after it completes I try to manually start an Edit Session on an affected SDE feature class it says it is not editable until I click on the map somewhere. So it seems that somehow I am not releasing the lock on the feature class. I am using an Update cursor, which I know does not fire events like the store method on a search cursor, and I notice that I cannot flush the cursor within the Edit Operation without triggering an error. But I would like to use the Update Cursor for speed. Any ideas on what I can do to get the edits to complete in a way that allows the user to begin an edit session? ' Assume I have a valid Feature Class assigned to the pFC variable Try Dim pFCursor As ESRI.ArcGIS.Geodatabase.IFeatureCursor = Nothing pFCursor = pFC.Update(Nothing, False) ' Create an UpdateCursor on FeatureClass Dim pFeat As ESRI.ArcGIS.Geodatabase.IFeature pFeat = pFCursor.NextFeature ' Get First Feature If pFeat Is Nothing Then MsgBox("No Route Features Selected!") Return End If Dim pDataset As ESRI.ArcGIS.Geodatabase.IDataset = pFC Dim IsVersion As Boolean = False If TypeOf pDataset Is ESRI.ArcGIS.Geodatabase.IVersionedObject Then IsVersion = True End If Dim workspace As ESRI.ArcGIS.Geodatabase.IWorkspace = pDataset.Workspace ' use IWorkspaceEdit Dim pWorkspaceEdit As ESRI.ArcGIS.Geodatabase.IWorkspaceEdit = workspace If IsVersion Then If Not pWorkspaceEdit.IsBeingEdited Then pWorkspaceEdit.StartEditing(True) If Not pWorkspaceEdit.IsBeingEdited Then MsgBox("Cannot start editing SDE Workspace") Return Else pWorkspaceEdit.StartEditOperation() End If Else pWorkspaceEdit.StartEditOperation() End If End If Dim i as Long = 0 ' Initialize a feature counter Do While Not pFeat Is Nothing ' do some kind of edit of the feature here pFCursor.UpdateFeature(pFeat) ' Update the cursor pFeat = pFCursor.NextFeature i = i + 1 ' Counter for features processed If i Mod 1000 = 0 Then ' flush edits after every 1,000 features If Not IsVersion Then pFCursor.Flush() End If End If Loop If Not IsVersion Then pFCursor.Flush() ' Final Flush of edits Else pWorkspaceEdit.StopEditOperation() End If Catch ex As Exception MsgBox(ex.ToString) End Try 3) If an Edit session is started on the workspace, I want to be able to update the Editor dialogs, such as the feature coordinate dialog that can be accessed when a single feature is selected and its vertices are being edited. I know that the Update cursor won't do this as it is processing the features. Is there a way to get the Editor to see the updates when the edits are finished? Do I have to use a SearchCursor and the feature's store method to make that happen? Thanks for any help.

‎11-09-2011

Thanks Neil. Exactly what I was looking for. I was unaware of those interfaces and properties. All help searches I did hate specifying a single letter like Z or M as a search criteria (it either removed the letter from the criteria returned or any text with a Z or an M in it anywhere seems to come back). HasZ would have worked, but it didn't occur to me that is what it would be named (quite a logical name though now that I know about it). Thanks again.

‎11-09-2011

Yes, you are right the 2048 is the default value for the number of rows that ESRI returns at first so as not to overwhelm you when you have a half a million rows in a table like I do in some other tables. I have pressed the end of the table arrow and only get the 2048 - I want to know where the rest of the 20K are. Thanks Given that then the suspect becomes the way that fetch limit is interacting with the way you defined your view. This could be something very specific to your SDE set up. I have never found a fix for this behavior with normal table connection outside of SDE other than the one I mentioned, so I would contact technical support now that you have told me that does not work. If you cannot replicate it on any other table, then you will need to retrace how you set that specific view up to get any real help from Esri. (I am not an SDE expert, so I cannot help you there, I just know what tech support looks for to help with this kind of problem).

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by RichardFairhurst

Re: .Net Update Cursors SDE Editing and Updating Editor

Re: .Net Update Cursors SDE Editing and Updating Editor

Re: 'If...Then' Code for Field Calculator

Re: Polygon Vertex labels

Re: .Net Update Cursors SDE Editing and Updating Editor

Re: How to get the route measure?

Re: Provide Z Tools similar to Route Editing tools

Provide Z Tools similar to Route Editing tools

Re: I3DCurve apparently does not account for Z units

Re: Linear referencing - measure in miles - measure rounded to nearest integer

Re: Correcting a DEM, editing Z-values, Z-values from attributes

Re: Reshaping a feature gives an internal error with the geometry system

.Net Update Cursors SDE Editing and Updating Editor

Re: .Net Is Feature Class Z and M Enabled?

Re: X,Y event layer and not all rows

Add Dynamic, Epoch-Aware Spatial Reference Support

Add a Bearing WKID System Parallel to Spatial Refe...

What Does ArcGIS Pro 4.0 Really Need To Be For Dev...

Re: Turbo Charging Data Manipulation with Python C...

Re: Turbo Charging Data Manipulation with Python C...

Addressing