Latest Contributions by TimHodson

JS, If you don't get an answer from this Land Records forum, you could also try the cartography forum, or the map automation forum. -Tim ... View more

Hi Christina, Here are few things to note and to check. Note: When you are zoomed in to a scale greater than 1:1, and the extent of your whole map measures in the 1/100ths of a foot, then you may see this effect: the cartography is not optimized for these highly zoomed in views, especially as your map extents begin to approach the XY tolerance of the feature dataset. This value defaults to 0.001m. There�??s a good help topic on the resolution and xy tolerance; you should not need to change these default numbers. Check 1: An important test is to figure out whether or not the geometry operations of GP tools and of the other tools in ArcMap detect any difference/gap. These geometry functions should see these lines as being the same. For example, one test in this case would be to do a select by location, starting by selecting one of the parcels that have the curve, then attempt to select the curved lines based on the �??share a line segment�?� option, as indicated in this graphic: [ATTACH=CONFIG]30056[/ATTACH] If both curved lines are selected after this, then the system identified them as equivalent, and the result is as expected. Check 2: Take a look at the attributes for each of the curves in question. Do they have different radius attribute values? Also find the radial point location for these curves. (the point at the center of the curve) Does each curve have its own radial point? If the attributed radius for each curve is the same, these radial points need to be merged into a single point that is shared by both the circular arc curves. After merging the radial points re-run the fabric adjustment. Check 3: There�??s a tool under the customize environment called Regenerate Fabric that you can use on selected parcels or on the whole fabric (whole fabric if there is no selection.) This tool will let you update the fabric geometry based on the point positions. See the graphic below on info about how to get it: drag the tool onto a toolbar, close the customize dialog, select the parcel, then click this button: [ATTACH=CONFIG]30057[/ATTACH] See also the last paragraph in this help topic. Regenerate may not change anything if, for example, the Check 2 test passes the line equivalence test. -Tim ... View more

Hi Brandon, We fixed a bug at 10.1 that addressed a problem like the one you describe. This fix is also available on the latest service pack 5 for 10.0. If you are using ArcGIS Desktop 10.0 sp5 or later, and you'd created the topology while using 10.0 sp5 or later, then it is not the same issue, and we'll need to get more information to learn why it's happening. Please contact tech support if the problem persists. Thanks, -Tim ... View more

What spatial type is your fabric stored in? If it is GEOMETRY, copy and paste the fabric as SDEBINARY and test the behavior again, and vice-versa if it is already stored as SDEBINARY (Esri Binary). You can find out the spatial type from the General tab on the properties of one of the fabric classes. [ATTACH=CONFIG]28730[/ATTACH] During copy and paste, you will be prompted to choose the spatial type. [ATTACH=CONFIG]28731[/ATTACH] Thanks, -Tim ... View more

Hi Greg, In the context of loading a topology to a fabric, the Exceptions are reserved for lines that are to be imported as non-boundary lines, or non-road frontage lines, or for lines that do not form a required boundary of a parcel and should be ignored. For example: by definition, a connection line will break the rule "Must be Covered by Boundary of" However, this should not prevent you from importing connection lines, and so you can mark these lines as exceptions, place a field on the source data called "Category" and then populate these lines with the value '3' so that they will then be imported as connection lines. If they are to be ignored then you'd mark them as exceptions and not give them a category value at all. There are some limits to what should be marked as an exception. For example, if an exception is set on a line that would be used as a boundary if it were not for its topology error, then the results of the import may result in the type of problems that you are reporting. -Tim ... View more

Mike, This is not something that I've heard reported before. I�??ve tried a few things that might explain what you�??re seeing, but nothing I�??ve done so far gives me the same results that you see. Note, that in terms of the fabric data, the parcel editing environment will always use the control point attributes over its geometry, but the control point geometry and fabric point geometry should still match their respective attributed coordinate locations. Another possible scenario that would only partially explain what you're seeing is that your original import source data itself has this same 5ft discrepancy between its geometry and it's X/Y coordinate. In this scenario the control importer honors the source XY attributes and would not match the original geometry position of the source data, unless you checked the option on the control importer to use the shape field. [ATTACH=CONFIG]28104[/ATTACH] For your data, what happens if you make a temporary small edit (0.01ft change to one of the coordinates) to the control point, (using the Maintain Control Points dialog) save the edit, and then re-edit the control point back to its original value? Do those edits move the control point to the entered attribute position? If none of this addresses or explains your case, please contact tech support to help us better understand what you are seeing. If there are any other readers of this forum that have experienced similar, please respond on this thread and also contact tech support referencing this post so that we can identify patterns and symptoms. Thanks, -Tim ... View more

Hi Mike, What is the distance between the coordinate position and the geometry's position? Is the distance close to the XY tolerance for stored geometry as described in this help topic called The properties of a spatial reference ? If this distance is small, and you are zoomed way in, then the XY tolerance may explain what you are seeing. Also, is the parcel fabric in a geographic coordinate system, and you're projecting on the fly using the map's data frame; or is the fabric's spatial reference a projected coordinate system, and the same as the map's projected coordinate system? Thanks, -Tim ... View more

Hi Daniel, Would you please copy/paste the text of the traverse file (or attach the file) so that I can try it? Not sure of the geometry properties of the data represented in the file, but loading traverse files of this format is most suited to files that each represent individual closed parcels. As you are probably aware, this file format doesn't specifically support connection lines. Though you can change the category of the lines after you've done the import, in a workflow where you are importing closed loop traverses, I'd expect ALL the lines to be either boundary lines or road frontage lines. Connection lines are more like "side-shots" to use the term from the older Workstation ArcCOGO technology. So connection lines should not be used to represent a parcel perimeter. There is more information about parcel line categories, and parcel "anatomy" in this meetup recording, starting at around about 48:30. Thanks, -Tim (Parcel Editor team) ... View more

Starting with ArcGIS 10.1, there's a tool, called Merge Courses, that will generate line-points for you after you've imported the fabric, so you don't need to worry about figuring out the line-points on the original source data, prior to the import. To use this tool you select imported parcels that you'd like to create line-points for, using the parcel selection tool, right-click to access its context menu, and click Merge Courses. More information about this functionality is available in the help topic '>Data review and cleanup tools. -Tim ... View more

Please note that the occurrence of empty geometries in the fabric is by design. These represent parcels that have not yet been joined and integrated into the rest of the fabric. These are stored in an �??unjoined�?� state, waiting to be joined (connected) with the other parcels in the fabric. They are stored in the fabric tables with empty geometries. There is more information about unjoined parcels and empty versus null geometries in this forum post. I've attempted to reproduce the case that you are experiencing with the large extents, but without success so far. If you haven�??t done so already, please contact tech support so that it can be properly tracked and recorded. Is there a particular worklfow that you can identify as causing the problem? Another question: you�??ve noted in your post that the General tab states �??Storage: High Precision using Geometry spatial type (SRID 0)�?� To confirm what you're seeing on that General property page: it does not state �??�?�using ST_Geometry spatial type�?��?� ? In other words this particular reported property has two problems; first is that the SRID is reported as 0, and the second is that it is not reporting the �??ST geometry�?�? Thanks, -Tim (Parcel Editor team) ... View more

I've attached an image for the entry of the second case, using the same Plan settings as for the first case. Chris' suggestion is for instances where you do not have enough information for a circular arc's orientation. For example, in the second case, if there were no radial bearings to define the orientation of the curve, you would start at the south east corner, cogo in the first three straight lines, digitize in the last closing course as a straight line, and then edit the last course by entering in the radius. The downside of this is that you are not getting the benefit of closure, and ensuring that no mistakes were made in the entry of the prior courses. In some scenarios you may have no choice but if there is enough information, as shown in this data, then it's better to enter the complete curve information, and get the benefit of the QA from the misclose information: [ATTACH=CONFIG]23726[/ATTACH] -Tim ... View more

Hi Daniel, In the first case you can also achieve what you need without using the tangency. In the second case it looks like the image that you attached is cutting off information for the radial line bearings to the east where the dashed lines extend? Are there bearings on those lines? For your first case, I created a new Plan with the properties shown in the image below: [ATTACH=CONFIG]23632[/ATTACH] The settings under circular curves are the most relevant for your case. I'm assuming your bearings are all South Azimuth (0 degrees south)? I used south azimuth to match your image's orientation, and assumed north is straight up the page. South Azimuth is rare, so please only use this setting if you're truly working in South Azimuth. After making this new plan, you can add a new parcel into that plan, and enter it as follows: [ATTACH=CONFIG]23633[/ATTACH] There is also more information about entering circular arcs in this post: Dealing with missing traverse information in COGO -Tim ... View more