Latest Contributions by TimHodson

‎01-26-2023

Hi Frank and Jason, What you describe is a bug, and is not the intended design. Thank you for reporting it. When using planarize, the COGO distances are recomputed when the lines are split; in these cases the existing COGO attributes get re-proportioned, and the COGO Type is then set to "Computed" on the resulting shorter lines. For the cases where planarize is snapping line ends together and the lines are not getting split, then the COGO distances should not be getting updated. Instead of using Planarize to do this snapping, you could instead use the GP Snap tool on the line selection, use the End snapping as the snap type, and use a small tolerance. In my tests of this it seems to be an effective solution. Example something like the following: Does this work to solve the problem? -Tim

‎01-06-2023

I'd recommend contacting Esri tech support and reference this post and the case number as per our e-mail correspondence. That would help add weight for us to get patches based on the release you're using.

‎01-05-2023

Hi Michael, The short answers to both questions is yes. Beziers are different to circular arcs, and they are a supported geometry type for features in a parcel fabric. There are, however, some limits to using beziers in the current release, described below. Additional information: Feature geometry is built up from segments. A segment can be a straight line, or a parametric geometry. A parametric geometry can be a circular arc, an elliptic arc, or a bezier. These parametric geometries are referred to generically as "curves", but when used in the context of parcel data and COGO we are, 99.9% of the time, referring to circular arcs. In the COGO world "true curves" and circular arcs have become synonymous. Limits of beziers when using Build command: Beziers may be used in the fabric model to represent natural boundary features, however we have seen cases where straight lines have been turned into bezier curves even though they are still geometrically straight. Beziers should be reserved for natural boundaries. If your fabric has very large natural boundary features with many bezier curve segments there are known limits that cause performance problems when running the Build command, for example. These issues are being addressed and fixed for the next release of Pro. (3.1) We are also investigating the feasibility of providing a patch for this on earlier releases. What about transition curves and spirals? The other curve we see in COGO workflows is the "transition curve" used for highway and rail centerlines. This incorporates the use of spirals, and combining them with circular arcs and/or straight lines to form smooth, tangential transitions to represent long linear features. Spirals cannot be represented parametrically in Pro; they are handled differently and are represented as a densified polylines. (For more specific info see this topic in the Concepts documentation for the COGO SDK) -Tim

‎12-16-2022

Hi Josh, you had me thinking there for a minute... The reason that is not available as a topology rule is that there is only one point feature class that's shared between all parcel types. You could add the rule "Point must be covered by end point of" for all of your parcel types' lines, and for your connection lines, but then you would have an error feature on all of your points except for those points that happen to be on the endpoint of a line of ALL the parcel types that connected at that one location, and there would also have to be a connection line's end at that same location: that'd be a rare case.

‎12-15-2022

Hi Matt, The beziers may have been introduced as a result of running the GP Smooth Line tool, or by using the editing tool called Generalize with the Smooth option. The SLACA tool intentionally does not alter the geometry of features with parametric segments such as beziers, circular arcs and elliptical arcs, as this would be considered to be data corruption by customers who'd like to keep their beziers intact. To answer your question, I have not found an out-of-the-box way to detect bezier curve geometries in Pro. I was looking into the GP tool called Calculate Geometry Attributes, but it does not report on specific parametric geometry types. That may be a good Idea to add as an enhancement for that GP tool. There is an add-in (currently unpublished) that I can share with you. It will select features (within the active map's extent) that have geometry segments that are beziers. I'll direct message you to find out more about your ArcGIS Pro release etcetera. -Tim

‎12-15-2022

Hi Jerry, On the least squares adjustment front for 3.1, our focus has been on improvements for handling Z attributes/elevations on fabric points. Support for geodetic bearings is still in the product plan, and we've moved into the design phase. I hope to be able to report more progress in this when we meet in Redlands next month. -Tim

‎11-04-2022

This 6 minute video shows how to transform a CAD file from a modified projection into its corresponding projected coordinates. For more information about modified projections see the blog post: Transform CAD Layers in ArcGIS Pro For more information about using the placed CAD to get new parcels into the parcel fabric, see these other videos: How to automate and process a cad file to create parcels DEMO: Bringing CAD lines into the Parcel Fabric using ArcGIS Pro 2.8

‎10-28-2022

@AngelaP- the second problem that you mention with saving the traverse file is a bug that is fixed with the latest patch, IE ArcGIS Pro 3.0.2. It sounds like you may need to update to that. For the first problem, that is not as easy to discern. Do you have a definition query set on the layer? If it's what @JeffWard mentioned, you could also try to turn off the scale dependency on the connection lines layer, by setting the "Out beyond" to <None>:

‎10-26-2022

@MahindaAbeykoon- what you describe regarding the Merge Parcel Points tool is not the same problem as outlined in the original description of this post. The good news is that there is also a solution for your case. We have, by default, allowed the merging of multiple points that have their Is Fixed attribute set to "Yes". This allows an editor to accommodate workflows where they need to merge what are sometimes referred to as "porcupine corners" where there are multiple "Fixed" points at a single corner, and they need to be merged. To solve your case, where you'd like to protect from an accidental deletion when merging points, you can create a new Constraint attribute rule on the points, using the arcade expression: if ($feature.IsFixed == 1) { return false; } return true; and inserting it as follows:

‎10-12-2022

Hi Bill, I see that too. But if you click the Play button: ...you should be able to watch/start the video. That works for me, does it work for you? -Tim

‎10-12-2022

Hi Atish, this is not possible, but it's an interesting question. Can you provide some more information about your goal? What parts of the Parcel API are you interested in using to edit standard feature classes? It should be noted also that any parts of the API (geometry/editing/geodatabase etcetera) can be used on the parcel fabric feature classes, and that you are not limited to use the Parcel API exclusively when making customizations for the parcel fabric. -Tim

‎09-08-2022

Hi @DrewDowling - I've been working through your goal to add subtypes to connection lines and to fabric points. Thank you for your post. First, to answer your specific questions. Are subtypes supported in Parcel Fabric lines and points? Yes. Is the parcel fabric topology modifiable? Yes, but with some known limits, as described more fully below. Here are some key points: What you are attempting is possible with the parcel fabric. However, there may be a problem that you’re experiencing that I’ve not identified. Please respond here if this post does not solve any elements of your scenario, and we’ll continue work on figuring it out. Two software user interface defects were found, and they have workarounds. These are both described under a logged support item (Reference: BUG-000152163). These defects and workarounds are described below. There are some behaviors and user experiences that you may have encountered that are by design; some of these behaviors and user experiences are different from similar functionality in ArcMap. Software user interface defect 1: When a subtype code has a value of 0, it is not presented properly in the user interface when viewed in the topology properties. The topology rule is incorrectly shown to indicate that it applies to a subtype although it actually applies to the entire class. Workaround: Instead of using a 0 code, use subtype codes starting at 1. Software user interface defect 2: When a class level rule exists, and there is a subtype field on the class, if there is any row that contains a null in the subtype field, it should cause the topology validation to present an error message (this is by design.) The user interface defect is that when running validate, the validation does not show the expected error message dialog. The Validate does not run, and the dirty areas are not removed, but there is no information presented about why nothing happened. Workaround: Use the GP tool Validate instead to get this error message. For the specific error message that’s returned, you can solve it by making sure that your feature class with a subtype has valid and non-null subtype codes in their subtype field for all features. Related to the specifics of the fabric generated topology: - The Remove button is disabled for fabric generated topology rules. This is by design. We are considering allowing the removal of these rules in future releases. - You are not able to alter the fabric generated topology rules. In terms of adding new topology rules, when you click the Add button you do not get a new dialog; instead a new row is added to the grid on that page, and you can double click on the first cell for “Feature Class 1” in the first column to select the first feature class, and then do the same for the other columns. You can also click in the last row in the grid that says “Click here to add a new rule.” -Tim

‎09-06-2022

Hi @LadyFranciscarKassama Here is how to do that: function NorthAzimuth2Quadbearing(azimuth){ return ConvertDirection( azimuth, {directionType:'North', angleType: 'Degrees'}, {directionType:'Quadrant', angleType: 'DMS', outputType: 'text', format: 'p d[-]mm[-]ss b'}) } NorthAzimuth2Quadbearing($feature.Direction) Note, I have also made an update to the original answer. The updated code is reduced to a single line within the function, and shows how to use the text output type, and the use of formatting capabilities available on the ConvertDirection function. This approach is also included in the snippet above on this post for your request. To learn more about this function see: convertdirection -Tim

‎07-22-2022

Hi Greg, yes you've correctly identified the workflow that should be used in 3.0. Running traverse courses from the point of commencement to the point of beginning should be considered as its own traverse. When you click the New button, the new traverse has its start point automatically set to the last point of the previous traverse. This is also documented here in a new section that was added for this update. The new section has the title "Create a parcel traverse with a connection from a point-of-beginning" : https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/createnewparceltraverse.htm

‎06-16-2022

Paul, Good news... this is implemented in 3.0! -Tim

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by TimHodson

Re: How to quickly "snap" all lines together in a subdivision?

Re: Is there an easy way to track down features that contain bezier curves in the parcel fabric?

Re: Is there an easy way to track down features that contain bezier curves in the parcel fabric?

Re: Tool to quickly identify 'Orphan Points."

Re: Is there an easy way to track down features that contain bezier curves in the parcel fabric?

Re: Exposing Direction Types in Parcel Fabric Least Squares Adjustment

DEMO: Using the Transform CAD add-in. Placing data that comes in a modified projection.

Re: Traverse tool will not work with connection lines

Re: Constrained Point is being moved

Re: How to migrate from polygons to the parcel fabric?

Re: Regarding Parcel fabric

Re: Topology rules and Parcel connection line subtypes

Re: Change the Pro COGO 'Direction' number format into a text string?

Re: Connection lines in Arcgis Pro 3.0

Re: Create point using Absolute XYZ does not automatically populate new feature's XYZ fields

Re: Help Entering Meets & Bound Call

Re: Help Entering Meets & Bound Call

Re: Help Entering Meets & Bound Call

ArcGIS Pro .Net SDK 3.7 for COGO Traverse

Re: Connection lines creating new vertices when cr...

PLSS Editing

ArcGIS Parcel Fabric - SDK for Add-ins and Scripting