Latest Contributions by TimHodson

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 ... View more

My current understanding of the requirement: select points that are not used by any connections lines, not used by any parcel type lines, and not used by any historic parcel type lines. Depending on the subsequent action, control points may also need to be excluded from the resulting set. When I first tried this on Friday I found this is not as easy to do in a map with multiple parcel types. In working on this again today, I found the following approach worked: Select all points in the points layer. If you want to exclude control points from the final selection then start by only selecting points that are not control. for each line layer (connection lines, parcel type lines, historic parcel type lines) use the Select By Location to remove from the selection, using following the approach. Press Apply after each layer to keep the dialog up:   This could also be automated via python scripting. ... View more