Latest Contributions by TimHodson

Hi Ryan, There is this Add-in that gives some extended abilities to help you remove inconsistent records such as these. It includes a tool that lets you drag a box around the orphan points to delete them, and a utility accessed via the fabric context menu, that reports and optionally removes inconsistent records for the whole fabric. See also this thread about orphan points. Regarding your question about LGIM not showing features: you may need to calculate the Type for the particular parcel layer. For example, the Tax Parcels layer has the following definition query: (SystemEndDate IS NULL) AND ("Type" = 7) To make them appear, drag a new instance of the fabric's parcel class onto the map from the catalog window, start editing, and select the parcels that are to become tax parcels. Use the field calculator and assign the Type = 7 on the selection, then save your edits. You can then remove the extra instance of the layer you added, and those Tax parcels should now appear in LGIM fabric. Another approach would be to temporarily remove the definition query on the Tax parcels layer, make the same edit, and then set the definition query on the layer back to (SystemEndDate IS NULL) AND ("Type" = 7) -Tim ... View more

Hi Dan, Thanks for sharing the file. I've taken a look; I understand what's happening, and I have a resolution for you. Since the original file format has no built-in notion of the different line categories, when the data is first loaded the parcel editor grid is not able to identify (or assume) which lines form a closed loop, and so it is flagging the parcel as unclosed. You've already noticed that the lines all automatically come in as boundary lines. You've correctly set your first two lines as category 6- Origin Connection lines. The only other thing that you need to do is set the parcel's "unclosed" attribute to false. It's possible that this field may not be turned on for the target parcel layer, so you'll need to turn that field on first, as shown in the graphic: [ATTACH=CONFIG]28108[/ATTACH] -Tim ... View more

Within the US the only place I'm aware of that have plans that use South Azimuth is Hawaii. You would never see both North Azimuth and South Azimuth on the same plan, and so you'd definitely not be switching between the two while entering information on the same plan. However, there are also differing conventions on placement of the bearing in relation to the line, with respect to which way the line is running. For example, you'd ask yourself the question "Is the bearing annotated on this line oriented from point A to point B or is it going from point B to point A?" If you are at point B, and you want to get to point A, but the bearing shown on the plan is going the other way, then you need to add or subtract 180 degrees from the bearing to enter the value to run the line the correct way. I see what you're referring to about the comparison between the first and second curves. There is an apparent inconsistency in the way the radial bearings are oriented. If your plats are in North Azimuth, then in the first image the radial lines are oriented from the center point of the curve, towards the curve's points, whereas on the second curve they are oriented away from the curve's points towards the center. When entering information for radial lines using parcel editor, the orientation is expected to always be towards the center point of the curve. So, if changing plan settings to now use North Azimuth, it'd mean that the bearing on the first line entered, as annotated on the plan, is oriented away from the parcel and not towards the parcel, as I first thought, so that bearing would need to be reversed. Setup and entry for case1, using north azimuth would be: Setting the plan properties as follows: [ATTACH=CONFIG]23662[/ATTACH] Entry of the first 4 lines would be: [ATTACH=CONFIG]23663[/ATTACH] For the reversed bearing cases, if needed you can enter the value as shown on the line, and then use the Reverse Bearing command on the context menu: [ATTACH=CONFIG]23664[/ATTACH] ... View more