Latest Contributions by TimHodson

Hi Marius, I'm responding here again, for the benefit of others who run into this scenario. Thanks for putting out this post. The geometry itself is not getting altered, but the circular arc is so flat that the geometry engine is not able to recompute the radius with any degree of precision that would return a meaningful value. If you use edit vertices, and move one end of the line you can see that the segment is still a circular arc. There is no discernible difference between the chord length and arc length, and the chord height is 0 (or very close to it). You can use the offset tool to see this: This is one of the reasons that it’s important to use/store the COGO attributes separate from the geometry. This is unfortunately a case where the geometry is not mathematically stable enough to get meaningful values, and so it thinks there is a straight line here… You can manually enter the radius and the arc length into the COGO attributes, but then you do need to be careful not to overwrite those again by using the Update COGO tool. For a future release we need to make the Update COGO tool smarter to avoid this problem where the COGO attributes are overwritten with straight line values for very flat circular arcs. The geometry engine starts to consider the circular arc to be a "straight line" for a central angle of around about 2 degrees. In this case the central angle is a lot smaller than that: (5.67/1640) radians x 180°/pi  0.00345732 radians x 180/pi = 0.198 degrees ... View more

Hi Marius, I will e-mail you to get your dwg.  ... View more

@LebowskiThis is a good candidate for the Parcel Fabric Ideas board Thanks, Tim ... View more

@DeanAnderson2- I just read from your original post that you are on 2.8.3. As mentioned in the prior response, this is fixed in 2.9. ... View more

@jcarlson- thanks for your post. Based on our screen-share this morning, the issues you’ve helped us to uncover are as follows: 1. The default angular unit is in Degrees for new projects. A project template would help with this. You could create a project template that has this setting pre-defined to be Degrees Minutes Seconds. There are few other benefits to using a project template. See the help topic here: https://pro.arcgis.com/en/pro-app/latest/help/projects/create-your-own-project-template.htm 2. When the traverse pane is open, and you go to the backstage to change a distance, direction or angular unit setting, the new unit settings don’t take effect immediately in the already-open traverse pane. You have to close the traverse pane and start a new one to see the unit changes. We'll explore some approaches to improve on this experience for future releases. -Tim ... View more

@jcarlsonthat's very strange. The only other thing I was wondering about is whether you tried it in a completely fresh project? ... View more

Hi jcarlson, what you describe sounds identical to a bug that was fixed for 2.5. (Esri internal reference: 1486)  Are you working on Pro 2.5 or higher? If so, I'm not sure what might cause this bug to reappear. Here's a video showing use of the "+" and "-" in 2.9:   And just to confirm you're looking in the right place for the Angular Unit settings in the project backstage:   Good idea, Paul, about remembering the deflection angle when modifying the previous line.   ... View more

After internal discussion with others on Esri staff ( @Scott_Harris   @JenniferCadkin ) we may need some more information. However, based on what you’ve indicated so far we think that you are using the “Vary symbology by attribute” property to rotate point symbols. Is that correct? Going with this, we put together a mini test workflow to rotate an Arrow point symbol to be oriented along the same direction as existing features. This should help to show the relationship between the measure tool’s direction units and values, and the point symbol's Rotation style. The test workflow is as follows: Create a double field on a points feature class and call it “Direction” Add the point feature class to the map On the point layer, set the properties on the point symbol to be an arrow. Rotate the symbol so that it is pointing north in its default state. Do this under Properties -> Rotation, set the angle to 90°: Using the Vary symbology by attribute, set the Field to Direction, and set the Rotation style to Arithmetic: In the project backstage go to Options -> Units > Direction Units and set the default direction to Polar. Also, click the cell in the number column to get the Direction Formatting, and change the direction base unit to Decimal Degrees, and set decimal places: Add point features near or on the segments that will be measured. Use the Measure Direction Distance tool and snap to and click the first point on the segment, then snap to and double-click the second point. Select and copy the Direction component from the measure tool dialog Select the point and open the attributes pane, and paste the direction into the Direction field. The arrow points in the same direction as the measured line:   ... View more

Hi Pascal, CopyLineFeaturesToParcelType does extra things that do not apply to connection lines. For example, it will look for closed loops and create a seeds for the closed loops that it finds. Such behavior is not needed for connection lines. But these are not hidden rules, they are documented in the parcel API SDK. As for connection lines, one coding rule I can think of is to make sure you have an Active Record when you write the new connection line feature so that it goes to the correct record, but this is also documented and is not only a coding rule; it applies also when using the editing tools. All rules should be documented. If there’s missing information, then it’s important that we make sure it’s documented for everyone. If you mean geometry / topology related rules, these are available to everyone via the properties of the topology that is used with the fabric. Since you're aware of the editing API, I presume that you have written code that creates connection lines, but you believe that these are not the correct result, or else you believe that there was too much code to write? Can you be more specific about what you're encountering so that we can understand your request better? Thanks. -Tim ... View more

Hi Pascal, If I understand your request correctly, this is already available using the standard editing API. Connection lines are standard features in a standard feature class. The SDK is not as specialized as it is for the ArcMap fabric, and so this gives developers a lot more access to edit the Pro fabric's feature classes. I can help with sample code but before I start working on that have you looked at the sdk documentation for editing concepts and editing snippets? https://github.com/esri/arcgis-pro-sdk/wiki/ProSnippets-Editing https://github.com/esri/arcgis-pro-sdk/wiki/ProConcepts-Editing -Tim ... View more

You could also try the GP tool called Table Compare. It has a "Schema Only" compare type. ... View more

Hi Mike, It looks like you need to check for nulls: var RecFeatRow = First(FeatureSetByRelationshipName($feature, 'RecordHasLand',['Name'], false)); if (RecFeatRow != null) {return RecFeatRow.Name;} ... View more