Latest Contributions by RichardFairhurst

Essentially there is no alternative other than deleting the Geometric Network, doing the flip and rebuilding the network.  A custom script might do it using cursors.  However, the update cursor would almost definitely have to do the flips while set up for versioned editing and it is possible that even then the cursor may throw an error as well.  Unfortunately, I don't have any geometric networks set up and I really am too busy at this time to do any experiments on this. ... View more

Eva: Geometric Networks and Network Analyst networks are not simple polyline feature classes.  They are complex, because they are controlled by relationship classes and other programming that integrates several feature classes together as a network.  If a tool only operates on simple feature classes then that means that the feature class cannot have these kinds of relationships to other feature classes.  I did not mention that in my response before, because I have never used a Geometric Network and at the time not used a Network Analyst Network, so it did not register that this would be an issue. ... View more

Glad to hear you got it working. Now you know why I put "Turbo Charging" in the Blog title. ... View more

Try making the first field a string like you do when you are building the dictionary.  So change: keyValue = updateRow[0] + "," + str(updateRow[1]) + "," + str(updateRow[2]‍‍‍‍ to keyValue = str(updateRow[0]) + "," + str(updateRow[1]) + "," + str(updateRow[2] ‍)‍‍  Also add the end parenthesis on that line for the last str() method. ... View more

I posted the AddIn under a blog which is located here. ... View more

When I try FIELDNAME IN (' ') all I get are fields that have no characters (but not Null) or that have any number of space characters, but no words. I think the table may be corrupt.  It was converted from another database using a CSV file that included several special characters.  While I manually removed those I could find that popped up when I converted back to a CSV file using Python (which didn't like them), I did not try to clean up the original CSV file and start the conversion fresh.  There may still be some hidden characters that have damaged the way SQL reads the table with this particular query. At this point I have done too much editing to start fresh from the original file, but I think exporting the data will work or else converting to the CVS file with the Python script and then using that file to recreate the table. ... View more

I am just using the Search by Attributes dialog within ArcMap Desktop (from the table view menu).  The queries are all being done interactively during a QC process.  I pretty much always use the field list to build my query expression and even click the LIKE button.  I only type '% %'.  I will try using the % button.  I have not tried to script this type of query. ... View more

For the source tab picture I need you to scroll to the bottom of the list in the text box to see the coordinate settings.  I oly see two lines of part of the spatial settings for your layer and not all of them. I have faith in the Geometry Calculator.  I suspect corruption in your layer or your map.  Complex self-intersecting polygons like bow-ties have to observe all of the ArcMap geometry rules for ring order and boundary orientation to avoid strange results being produced.  I don't know that R respects all of those rules.  I would run the Repair Geometry tool on the layer and export it to a new layer.  I would also add the new layer to a blank map and do the Geometry Calculator on the whole thing to see what output it gives. I also want to be sure that each feature is just a single bow tie and none of these features are disjointed multi-part features with large gaps between parts.  Select one of the features with an odd coordinate in edit mode and zoom to the feature extent.  Verify you see a single bow tie and that the centroid crosshair is inside the polygon at the center of the bow tie. ... View more

I have to assume the new coordinates calculated are correct for the projection your data is in if both the Geometry Calculator and Attribute Assistant produce similar results.  How were your original coordinates assigned? What is your layer's projection and what is your data frame projection?  You should not edit spatial data when they are different.  Look at the layer properties on the source tab and print a screenshot of the coordinate system it shows.  Then right click the map view and choose properties and screenshot the coordinate system tab.  If they are different you would need to either use the Project tool to get your layer to match the desktop, or change the desktop projection to match the layer before doing any spatial editing. As far as moving the polygons to the same location, how are you doing that?  The centroid of each polygon must be set to the position you assigned to get the output to match. ... View more

You need to use Attribute Assistant to do automatic updates during editing.  It has X and Y Coordinate methods for maintaining centroid coordinates or the end points of lines (which for a polygon are both the location of boundary closure).  You can download Attribute Assistant here by pressing the Download button.  You then need to modify the dynamicValues table to include lines for the X and Y coordinate methods that target your polygon feature class.  Here is an example of the rows you would need in the dynamicValue table if the Feature Class is named MyPolygons and the fields to maintain are called X_COORD and Y_COORD: Table Name Field Name Value Method Value Info MyPolygons X_COORD X_COORDINATE Null MyPolygons Y_COORD Y_COORDINATE Null   These rows should check as True the options to update when features are created and geometry is updated.  Add that table to the map where you are going to edit your layer.  Make sure the Attribute Assistant is active in the Attribute Assistant toolbar. For features you moved previously use the Geometry calculator on your fields to bring them up to date (right click the field column name, choose Geometry Calculator and choose Centroid X and Y options as appropriate) and then maintain them going forward with Attribute Assistant. ... View more

I would use the Create Route tool on the polyline to make it a linear referenced route with measure coordinates.  Then I would use the Locate Features Along Route tool to overlay the polygons on the line.  This will add the Route ID and two measure fields to the output table.  The measure fields will sort according to the order the polygons cross the polyline in the direction the measures increase (ascending sort) or decrease (descending sort). ... View more

The dictionary does look as expected, so it is most likely not the problem.  I would go back to the original code and do the count this way, now that you know the error hits on record 546 or 547.  I start checking from count 540 on to be sure to catch the erroneous record.  Watch to see if the error occurs after the print of row or the dictionary record.  Hopefully the print will show the record causing the problem, but it may throw the error on the record that fails to print just after the one that does print, so you would have to look in the table at that record you are updating. count = 0 with arcpy.da.UpdateCursor(targetFC, ["PROPNUM_GIS","SHAPE@"]) as uCur:     for row in uCur:         count += 1         if count >= 540:            print('Count = {0}'format(count))            print('Row is {0}'.format(row))         PROPNUM = row[0]         if PROPNUM in valueDict:             if count >= 540:                print('Count = {0} and dictionary value is {1}'.format(count, valueDict[PROPNUM]))             row[1] = valueDict[PROPNUM][1]             uCur.updateRow(row)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

Did you create your own post with the code that is not working?  You should and then link to it in a post here so I will be notified. ... View more