Latest Contributions by RichardFairhurst

I have a help ticket open with Esri to try to get them to log this as a bug.  I have demonstrated that just by including a field in the update cursor field list that is part of the label expression trigger for the feature linked annotation and updating a row inside an edit session that the annotation updates itself.  This occurs even if all I do is open an edit session, open an update cursor and use updateRow on a row without using the update cursor to modify or read any of the field values in the row. So all update cursor updateRow events are treated by the Editor as though every Modify Record edit event included modifications to every field in the field list, even if no modifications of any kind were done.  When the field list includes a trigger field for the feature linked annotation the field is always considered to have been modified by the Editor when the updateRow event is processed and the row's annotation is always rebuilt to replace any prior manual annotation edits. This is a severe bug or at least a behavior that requires a highly visible warning in the update cursor help so that users of feature linked annotation do not unknowingly use update cursors to trash months or years of manual annotation edits like I did.  If I did not have a backup of the annotation this incident would have been an utter disaster. ... View more

The Mark as Helpful option is hidden in the Actions drop down menu.  That is even less obvious than the old forum's buttons on the right side of each post that all new users overlooked.  This option should be more obviously exposed if it is the new basis of MVP rankings. Are Likes considered?  Likes are the only thing I see anyone do consistently here and the only thing I could easily see that I could apply to each post. ... View more

I switched the correct answer to yours, although I would say all of the answers I have seen are correct.  It only lets me mark one, but since yours included the code I can paste into my script and was posted first, I switched the answer to yours.  (I gave all of them Like points). ... View more

Thanks. I had read that many months ago, but forgotten.  I did consult the help for Get Count when I wrote the code, but obviously I only glanced through it and overlooked that it was returning an object and not a number. ... View more

You cannot do this will shapefiles, but with a file geodatabase you can use the Address Data Management tools available at this website‌ (The Open button contains the download).  These tools includes a feature construction tool that allows you to draw a new line in an edit session that will split any existing lines where they are intersected along with making proportional splits to the address ranges.  It also comes with Attribute Assistant which can do many automated updates in an edit session, such as maintain a length field that is in units other than the feature units and or query intersecting features like Cities and ZIP code boundaries for information during an edit session.  This should be in your maintenance toolset for address management. However, no tool does correct proportional editing of address ranges in a batch process.  This would be a challenging script to write, primarily because it is hard to control the order of the many segments a line can be divided into so that you can correctly extract the range portions belonging to each segment.  The math is not that hard if you know the original line length and could get the segments belonging to the original line to always be in an order where the TO end of the last line you processed was the FROM end of the next line If the lines had M values based on length, then such a script might be possible to write, because the M values can be written to fields that could maintain the correct sort of the segments.  All you need then need is the original FROM and TO measure of the original line written to fields before doing the split and the current measures of the line to derive the address range portions.  I have done that process with Route Events. ... View more

Here is the majority of the solution using a geoprocessing approach without scripting.  It requires an Advanced license to use all of the tools listed here.  A script may be able to bypass the need for so many tools, but the basic steps to get from a set of lines to a divided buffer should more or less follow this process. I do know that the first step is to get a buffer shape that will form the overall outline to be segmented.  That shape will dissolve all lines together without any attributes dividing the segments.  I would use Flat ends.  See the resulting exterior boundary of the buffer shown in the picture at the bottom (interior lines are created in the rest of this process): It is that buffer which must be divided at the joints and the resulting divided set of polygons must be attributed by the original divided lines. Next I need the intersection point at every line junction where the attributes change and there are separate lines.  Preferably unnecessary pseudo nodes have been eliminated.  I would use the Intersect tool with the POINT option on the segmented lines to extract those points.  This does not create a box at 4 way intersections, it creates an X, which is the only way to have polygons that only cover one line.  A box would have to be created a different way and a manual choice would have to be made to assign only one line's attribute set. Next I added two double fields for the X and Y coordinates of the intersection points and a text field with a concatenation of the points.  Then I do a Summary Statistics with the XY concatenation as the unique case value and the MIN_X and MIN Y coordinate summary to get an XY Event table of the points.  Make that table into an XY Event layer. Create a fairly small buffer around these XY Event Layer intersection points.  I used 20 feet and kept the X_Y_LINK, FREQUENCY, X_COORD and Y_COORD fields. Then I used the Features to Lines tool to convert the outer circular buffer boundaries around the intersections to lines as a SHAPEFILE  You cannot output to a file geodatabase because it will use true curve arcs which won't work for the steps that follow..  Dissolve these arcs keeping the X_Y_LINK, FREQUENCY, X_COORD and Y_COORD fields to rejoin overlapping buffer outlines that are split up by the Features to Lines tool back to their circular shape. Next extract the end point of the circular lines to find the position where the circle will split that does not touch the original lines using the Feature Vertices to Point tool with the START option. Now I can intersect these circular lines with the original lines and use the POINTS option to get all positions on the circle cut by the original lines. I can then use the Split Line at Points tool on the circular lines with these latest points where the circle is cut by the intersecting original lines.  I used a search tolerance of about .01 Now select all of the points that were at the start of the circle.  Do a Search by Location to Remove from the Current Selection all points that are within about 1 foot of the points that cut up the circle.  This may miss some very small arcs where a line and the circle start are close together, which may need to be cleaned up manually after the next step. The remaining circle ends should select the cut up lines on the circle outline to find the pair that should merge together that are not intersected by an original line.  Dissolve these lines keeping the X_Y_LINK, FREQUENCY, X_COORD and Y_COORD fields and use the Unsplit lines option to create a new feature class.  You may delete these arcs from the cut up circle outlines.  Now clean up any small arcs where the start of the circle was close, but not on an original line manually. For the remaining arcs that were not touched by a circle starting point use the Feature Vertices to Points tool with the MID option on the remaining circle portions.  Do the same with the Dissolved circle portions and append the two point feature classes together.  This will only work correctly if the circular arcs are in a shapefile and not a file geodatabase. Add an X_TO and a Y_TO double field to these latest bearing points and calculate the coordinates of these new points into them. Use the XY To Line tool to make the X_COORD and Y_COORD the start of the line and the X_TO and Y_TO the end of the line. Convert the original buffers of the dissolved lines to lines using the Features to Line Tool. Copy these buffer outline into the Bearing lines feature class.  Save the edit. Now use the Extend tool and extend double or triple the distance of the original buffer and use the Extend to Extensions rule.  Examine the result for anomalies involving arcs that are greater than 180 degrees or intersection points within the buffer of each other. Use the Features to Polygons to convert the extended lines to polygons.  Use the bearing lines to select polygons that actually enclose lines, the reverse the selection and delete the polygons from the buffer holes.   Use the Spatial Join tool to transfer the attributes of the original lines to the points that divided the intersection circles.  .Use these points to Spatial Join attributes to the polygons.  The end result looks like the picture below: If certain roads were supposed to take away the triangular areas and you wanted a box intersection, a separate process would have to be developed by only buffering those roads with their attributes and cutting the intersection again and reassigning the triangular pieces to that line segment.  The circle would only divide on those lines to form the bearing cut angles that would divide the box.  However, without a way to classify the road that takes priority at the intersection, I cannot think of a way to get the box effect easily   Wither way attributes would not divide the buffer on a through road at the intersections., but the lines segment end points would divide the circle and create the cuts at the center of the intersection genearly in line with the cross street. ... View more

For anyone wanting to create emf files, I have found that PowerPoint is the easiest editor to work with that outputs a clean emf file.  Illustrator is hard to set up to avoid unwanted background elements in the emf file. Pasting an image into PowerPoint is easy to do by just pressing the paste button after doing a screen capture (Print Scrn button).  I use the freeform drawing shape from the Drawing group on the Home tab to create a closed polygon.  I also use the Fill Shape and Shape Outline drawing tools on the Home tab to adjust the color of the shape to solid black.  When the shape is selected I can use the Drawing Tools Format tab for the Rotate tools (rotation of mirrored flips) to adjust the orientation of the shape to make the house front face north and create its mirrored layout. I have changed my Model Number values to put the tract first followed by the model.  This makes symbols sort together in the symbology tab, which makes them easier to work with. ... View more

Attribute Assistant, which comes with the Local Government Information Model (LGIM) downloads, does this behavior through the X_COORDINATE and Y_COORDINATE rules and lets you choose if you want the centroid, start or end of a line/polygon outline. It also does much more automation, including maintaining sequential numbering using Max values or the GenerateID table, field caluculations thta can maintain date stamps or other values, user name stamps, validate values from a lookup table, maintain other related fields affected by lookup values in another field, etc.  These rules are set up in the DynamicValues table, which must be added to the map where you want Attribute Assistant to follow the rules.  A non-versioned GenerateID table can keep track of sequential numbering, and a MasterStreetName table can validate street names for centerlines/addresses. All DynamicValue table rules can be controllled to respond to feature/record creation, attribute updates, geometry updates, or manual triggering, or any combination of those triggers.  Rules fired by the same trigger are processed in the order that they were entered in the Dynamic Values table, so multiple rules can operate in sequence on one field if needed.  All feature classes/tables referenced by the DynamicValues table must be within the map for the rules to work, otherwise the rules that follow a missing item will not fire. You do not need to use the LGIM schemas or set ups to use the Attribute Assistant.  Here is the Address Data Managment model download (click the OPEN buttton) as an example that contains the Attibute Assistant and some common rules set up in the DynamicValues table to support that edit flow. ... View more

I suspect that Simplify would have had the same result as converting to a shape file, because a simplification occurs when you downgrade from a high precision file geodatabase feature class to a low precision shape file.  Additionally, buffer creates bezier curves in a file geodatabase feature class output, which are downgrade to densified points when you convert to a shape file, so perhaps the Densify tool would have fixed this problem also. Anyway, I am glad you got to the result you wanted. ... View more

Is the curve in the original route densified points or a bezier curve?  I would expect the bezier curve to cause issues and not be preserved by the route tools.  I have similar problems with the Locate Features Along Routes tool when I try to overlay line features on to a route built from bezier curves originally. ... View more

Abhishek: Please see the revision below. You cannot use the & for AND in a logical expression. That only works for concatenating strings. ... View more

It appears that this method is more powerful than I thought and at least in my case.  I believe I can solve a significant portion of the Step 16 time consuming process of manually identifying the correct model number for each address from aerials within a large portion of my tracts. 1. It turns out that the address points had the parcel number they were associated with so they could be linked to parcel data. 2. The parcel data had legal description information that I appended to the addresses. 3.  The legal description (Tract and lot) could be concatenated in a standard format that matched a field in my building permit data so that I could create a join on the concatenated legal description field of the addresses to my Building Permits. 4.  I extracted the residential building permits that had reached a status of Final and that had a model number specified in their description field. 5.  I parsed out the Model Number into its own field from the description.    Each tract typically used model numbers starting at 1.  Often the reverse/mirrored version was followed by an R, but not always, so I did have to manually add an R version when the plan was reversed in the case of several tracts.  Sometimes model numbers would have letters like A, B, or C after the number to indicate variant versions of the base model number. 5.  I calculated the MODEL_NUMBER for the addresses to be the parsed Model Number from the permit description followed by the Tract Number.  Using these values means that the model numbering is not randomly assigned, but connected to real permit model numbers.  This will help associate the shapes to any permit plans that may exist.  Although I do not have access to those plans, someone else in my jurisdiction does and could probably help me create a hyperlink to scanned files of the plans for their use. 6.  These Model_Numbers will be used for the emf file names.  If I find that multiple tracts used the same model set I don't have to draw each model and can simply group that set of tracts for each model number in the layer symbol categories once I had created the emf file for one of the tracts. This process worked for 35032 address points.  If every tract  phase model set was unique then there would be 7,236 unique model numbers.  However, a majority of the tract phases would use the same model set as the final phase despite the different map numbers, so probably less than a third of that amount are actual unique models footprints. So for a significant portion of my data as soon as I can create and apply an emf drawing of the model set for a given tract to the address point layer symbology, the model outlines will immediately appear somewhere within the all of the correct lot numbers for that tract.  Then the only time consuming part will be fine tuning of the rotation and position of the building outlines and validating an odd appearing address/permit associations created by user error when the permit data was typed. ... View more