Latest Contributions by RichardFairhurst

Using row or r is fine.  I think the problem is that the comparison continues after the row has been deleted.  Once deleted, row would be undefined for the comparison to the next r[0] value.  You would need to break out of the for loop once the del(row) operation takes place. That also raises the question about the comparison logic.  If you do not query the table for any specific records, than I would expect many records to not match your row values, and the row would virtually always be deleted.  A dictionary would help with this, since doing a if not row[0] in dict: compares to all the of dictionary keys you previously loaded from the entire table at once, not to just one row at a time in the comparison table. ... View more

row is use in many part of your code.  Which specific line is throwing the error? Also, do not use nested cursors.  They are horribly inefficient and in my opinion should never be used.  Instead first use a cursor to load the entire source you want to match into a dictionary and then run an updatecursor on the data that needs to match it using the dictionary to compare the values.  See my blog on the subject here for some ideas of how this can be set up. ... View more

Use Attribute Assistant to do the auto numbering.  It comes as part of the Local Government Information Model (LGIM) templates like the Address Data Management template (you don't need to the the LGIM).  To create an auto increment number use the Attribute Assistant toolbar, the GenerateID table and DynamicValue table.  Press the download button to get to the link to download it. After extracting the files double click the esriAddin files for Attribute Assistant and Address Management to install them while ArcMap is closed.  In the GenerateID table you add a row with the feature class name, the current number of the sequence in your table.  Use 0 if you are starting with nothing numbered, but this only works for blank feature classes/tables.  Use the last existing number of an existing sequenced field if it already has records (see the autoincrement calculation to initialize an existing long field). OBJECTID * Sequence Name Sequence Counter Interval Value Comments 20 WHYDRANT 44448 1 <Null> Then in the DynamicValue table you enter the feature class/table name holding the feature class name (WHYDRANT), the field to be incremented (FACILITYID), the Value Method (GENERATE_ID), a Value string (WHYDRANT|0|[seq] - meaning increment a normal number with no leading zeros stored in the WHYDRANT feature class), and make On Create True and all other options false. OBJECTID * Table Name Field Name Value Method Value Info On Create On Change (Attribute) On Change (Geometry) Manual Only Rule Weight Comments 147 wHydrant FACILITYID GENERATE_ID WHYDRANT|0|[seq] True False False False <Null> <Null> Add both of these tables to your map from the directory you extracted it to in the \AddressDataManagementLG\MapsandGeodatabase\LocalGovernment.gdb.  Also add the feature class (like wHydrant under the WaterDistribution dataset).  Now add the Attribute Assistant toolbar (right click toolbar area and choose Attribute Assistant) and make sure that the first button is active (the red exclamation mark in the icon disappears).  Add a new feature and notice the next number in the series for your field was added. ... View more

Are they two columns on the same page aligned in rows already?  If so, then I do not understand the problem, since you could just concatenate the two columns together on the same row. If they are on separate pages or in separate spreadsheets then you would first need to break apart the address from each component first and do a match on the address that is common in both using ZLookup. I have attached a spreadsheet that shows how to parse the two columns if they were on separate spreadsheet pages and then do a match using VLookup.  After matching, just concatenate as needed. ... View more

I am not clear what I am looking at.  Are these two separate spreadsheets, two separate columns, two separate pages?  Are the values in each set in a single field each (set1 and set2) or are the sets made up of separate fields (like x, y, address, unique ID, address)? The VLookup can do this if the address portion of each set is separated out.  ... View more

Jake: I see that your tool is trying to automate the Add Field, Calculate Field, Delete Field, Alter Field (to rename it) workaround steps that normally have been done when the original feature class/table is changed rather than creating a new fc/table.  The Alter Field step of the tool will only work if the input is within a geodatabase.  For shapefiles you have to do a second Add Field, Calculate Field, Delete Field to get the original field name back.  Your tool should test the input to determine if the Alter Field step can be done and otherwise do the 3 alternative steps.  Of course, this workaround technically is not altering the original field, just the original fc/table. The unfortunate consequence of this workaround is that the fields are reordered, with the new version of the field being added to the end of the fc/table's field set rather than remaining in its original position, but if retaining the ObjectIDs of the original features/rows is important, your approach would be necessary.  The only way to keep the field order is to create a new fc using a tool like the Feature Class to Feature Class tool as Gabriel suggested, but then all ObjectIDs will be renumbered (and I think that GlobalIDs also regenerate or cease to function). ... View more

After looking more closely at the IName interface I see that it has an Open method that can instantiate the workspace or dataset, even when no feature class is included in the IName.  The IName help says: "A Name object is a persistable software object that identifies and locates a geodatabase object such as a dataset or a workspace or a map object such as a layer. A Name object supports an Open method that allows the client to get an instance of the actual object (for example, the dataset or workspace) given the name object. A name object thus acts as a moniker that supports binding to the named object. The geodatabase supports methods on workspaces that hand out name objects that can be used by browsing clients to display the names of datasets in the workspace and to instantiate any specific dataset." I suppose I would have to extract just the IFeatureDatasetName portion of the full tool output and cast that to IName prior to using the Open method, since otherwise the full output Name in the IGPValue would include a feature class that does not yet exist.  So I guess I can go from IGPValue to IName to IFeatureDatasetName, back to IName, then use the IName Open method to create an instance of the IDataset and then get an IGeodataset (or possibly open the IGeodataset directly using IName) and finally get the Spatial Reference. ... View more

Ken: Thanks for pointing that out.  I never looked at the snippets and all help searches on IFeatureDataset never led me to IGeoDataset to get to the Spatial Reference. Can an IFeatureDatasetName be cast to an IFeatureDataset, IDataset or IGeoDataset directly?  Is there a better way to take the text path to get one of those interfaces?  It seems so convoluted with no obvious bridge between the two interfaces. I appreciate the other suggestion, but the point of this post is that no feature class exists to pass to any method.  I intend to create one, but until the tool completes no feature class would exist in the feature dataset.  Anyway, the IGeodataset interface is will do what I need if I can convert a workspace path to that interface. ... View more

Ben: Your suggestion will not work, since there are duplicate values in every individual column and only the first row with a given column value would be returned for each VLookup, which in most cases would have nothing to do with each other.  Only the concatenation of all 4 columns will look up the correct row in the original spreadsheet.  There is no way to do this without at least creating a new column in the original spreadsheet.  Once that was done perhaps the VLookup could be written in the new sheet without adding a column, but that unnecessarily complicates the formula in a way that would waste my time with debugging unneeded complexity.  The approach I suggested was easy to set up. ... View more

I appreciate getting information that brings me up to date on what is happening with da cursors in the latest versions of ArcGIS.  I don't have 10.3, and only recently got 10.2.1 installed.  I tried the Order By option at 10.1 with the release of the da cursor, but I gave up on it.  I have not tried it since then. This has happened to me several times where I try something that should work in an early release and discover that it has serious issues that make it either fail or perform horribly.  Once I give up on code that fails me it can be hard to give Esri another chance.  Generally figuring out a workaround took so much effort that I resent the original method that should have worked for wasting so much of my time.  If a workaround is very effective, then even if the workaround is complex, I forget to even consider the possibility that the original approach that is simpler might have been fixed in the latest release.  Anyway, thanks for bringing me up to date. ... View more

She attached a png to her post called notworking.png.  It shows a table that appears to following no particular order. If the table shown in that picture is following a sorted order it must be based on a multifield sort.  My code can increment to follow a multifield sort by just replacing the OID@ field name with the alternative secondary sort field to control the multifield sort. ... View more

Dan: I get this by looking at her picture.  She wants whatever order the table view randomly picks without any sorting of any field to be sequentially numbered to fit that (dis)order.  She has not mentioned any field that she would like to order by and as far as I could see her picture was not sorted based on any field value at all. The autoincrement code always uses ObjectID order, because that is the order that the field calculator and any unsorted cursor always uses to process records in a table. ... View more