Latest Contributions by TimHodson

Revision 12-20-2017. Fixed bugs in "Create Fabric Radial Lines" to better handle Oracle in-clause token count limit. Fixed problem where error message occurs when following tools attempt to write to temporary feature classes in the default geodatabase: "Aggregate Boundary Lines From Polygon Layers" "Create Topology Fabric Source By Polygon Filter" and "Create Fabric Radial Lines"       (The fix was to update the code to use an explicit path to the default geodatabase.) --------------------------- Revision 12-14-2017. Enhancements include: The tool “Transfer Parcel Type To Line” was fixed to address the problem reported in the item comments.  The tool "Find Close Vertices" had some bugs fixed, where: the default database was not always used for temporary outputs causing the tool to fail, and close vertices were not always found because there was an error in the algorithm that compares search circumference with buffer perimeters. "Find Close Vertices" was also enhanced to use fabric points, control points and other point features. The tool "Iteratively Load Parcel Fabric" had a bug fixed where if there were no polygon centroids in a grid cell the tool would fail. The process will now skip over grid cells with this characteristic instead of failing. --------------------------- Revision 3-22-2017. The Parcel Fabric Geoprocessing Tools item has been updated based on your feedback. Updates include: Removed limitations on radial line creation. The tool “Create Fabric Radial Lines” can now be used when in an edit session, and in any SDE version. Added help content for the tool “Create Fabric Radial Lines” Added new message about being in an edit session on the source lines for the tool: “Create Topology Fabric Source By Polygon Filter” Improved messaging for tool “Export Fabric To Simple Feature Classes” - it is limited to run only in the Default version. A new message is presented to indicate when not in the default SDE version. Improved the installer for overwriting older install versions of the toolboxes. Added video to AGOL item, describing the install process. This process ensures the dependent files are installed in the correct place. --------------------------- Revision 3-15-2017. The Parcel Fabric Geoprocessing Tools item has been updated based on the feedback from the Meetup and other requests. The Revision 3-15-2017 updates include: Improved messaging in the tools to indicate if it supported on the client machine's install and license level. Enhancements to convert the GP models into python scripts for: making radial lines and, for exporting fabric classes to standard feature classes. Bug fixes in tools to accommodate layer names with spaces, and Present better messages when attempting to run certain tools in an edit session. Updated the installer to accommodate installing to 10.3, versus 10.4 and higher. Attempts to install to an earlier client will result in a message, and will not install the toolboxes. Notes: All the tools will work on 10.4 and higher, however *some* of them will be available on 10.3 as well. We are not able to support all of the toolboxes and scripts on releases 10.3 and earlier, as certain of the functionality was not present. -Tim ... View more

Jeff, Thanks for the feedback. I've added a bug to the issues list on GitHub, Bug -Parcel Fabric Quality Control: Make Coordinate Inverse work in ArcCatalog · Issue #17 · Esri/parcel-fabric-desktop-…  -Tim ... View more

Dan, I've reproduced the problem and have started working on a fix. In the meantime, for your workflow you can get around the problem as follows: when in the PolygonToLines gp tool, go to the Environment Settings, expand the Z Values, and for the parameter called "Option has Z Values" set the drop down to "Disabled". Thanks for reporting the problem to Tech Support. -Tim ... View more

Larry, it is strange that you are seeing this message during use of the Load a Topology to a Fabric tool. Since the Loader is a GP tool, any messages should be going to the GP message log. I'm not sure what would cause this, since I've not seen this message when doing an import. To confirm: the dialog box shows up during the actual loading process? That message you are seeing would appear if you did something like the following workflow: Select 2 parcels that are not connected to one another, right-click and click Unjoin In the Parcel Explorer window select both parcels, right-click, and then click Rejoin. As you can tell from these steps they are not directly associated with the Load a Topology GP tool. ... View more

Hello Monica, Does the problem occur for any CAD file that you try, or is it only this CAD file that reports the message; have you successfully completed this workflow previously with other data? This was reported once before in 2011, and in that case an ArcMap restart solved the problem: https://community.esri.com/thread/39908 This may be a data related problem with some possible causes being: There is geometry in the CAD file that is outside the projection such as a line that connects to a coordinates at 0,0. There are lines in the CAD file that have a circular arc geometry with extremely flat curves. When you go to join, the parcel editor attempts to store the center point of these flat curves, but the radius is so long that the point falls at a distant location that is outside the spatial reference extent. A couple of things to try out: Open the parcels you’re attempting to join and look for circular arc lines with very high radius values. This may happen when a line that is supposed to be straight is instead stored as a flat curve. For this case just delete the high radius value in the grid and the curve will be converted to a straight line. I presume you are using copy and paste to bring your CAD lines into a construction and then building the parcels from the construction? If so, on the paste step, have you tried the paste both with and without the option checked to “Preserve coordinates from source geometry”? If you are not able to work this out please contact support so that your workflow and data can be worked on in more detail. Thanks, -Tim Land Records​ ... View more

Hi Betty, Here is a post with more information about rotations on parcels, and how they work. The lot with a rotation of  359-37-37 is OK, it's just the same as a negative 0°22'23" since 360° is the same as 0°, so 360° minus 0°22'23" = 359°37'37" With regards to the rejoin and the parcel flying off the screen, I have not been able to reproduce it yet, but does your parcel have long origin connection? What will happen is that if you click the button on the joining dialog that says "Bring joining parcel to map extent" (4th button from the left) the parcel's first point on the origin connection is placed at the center of the map extent. So if you have a long origin connection line, this would place all the other lines off the screen. If you click the button that says "Reset X and Y" (3rd button from the left) this should place the joining geometry back in the correct location. Would you please contact tech support and go through the steps so that we are able to reproduce it? Thanks, -Tim ... View more

Hi Betty, The problem with the Control point moving when joining has been fixed, and was also released in a patch for 10.3. Do you have the latest patches installed? See: Patches and Service Pack - Esri Support Also, the message about the radial lines is a known problem, but it does not affect the end result, the message is just incorrect, and it typically occurs when there are origin connections attached to the parcel. That is also fixed in 10.4. Regarding the problem of the bends in the lines; is there any rotation on the parcels? Also, you inferred that for some of the lines you do not have record values. For those, did you set the line accuracy to a 6? If you have concerns about one, some, or all of the radial lines within the cul-de-sac, then you could set one or more to accuracy 7, and see if that improves the result. If necessary and in order to maintain the structure of the cul-de-sac, you could also set ALL the radial lines in the cul-de-sac to accuracy category 7, but then work out the correct radial bearing and distances, and add 3 or 4 connection lines to serve as radial lines. When creating connection lines, the bearings always go in a direction outward, away from the parcel, and be sure to make the bearings on the connection lines be relative to the parcel that they are connected to. (Related note, for origin connections the bearings go the other way, 180 degrees different, lines proceed in sequence in towards the parcel.) Do you notice high computed minus observed (c-o) residuals, and what are you using for your Distance Residual Tolerance? You could start to set that tolerance lower, until you force it to report a failure, so that you look for the '##' again as it may provide some clues. Also check if you have any Close points reported, and if you do you can use the mean points tool to merge them. Also take a look at long lines that are not boundary lines, because error/mistakes in those lines are magnified compared to the shorter lines, and they also don't show up in the parcel misclose information. Double-check to make sure their distances are in ground, and confirm that their bearings are a match with the rest of the parcel relative to the parcel's rotation. One quick way to do this is to open the parcel with a long connection line and use measurement view to see if the line goes off at an unexpected angle. Are there any multi-part parcels, or parcels with inner rings (donut parcels)? If so check the part connector bearings. Also, regarding the control points. The bending of the lines could be due to an ill-fit with the control points. How many control points and parcels in this adjustment? You can do a check-fit on the control dialog to see if there are any significant outliers in the control points. Find the largest outlier, de-activate it, then re-run the check-fit. This way you can try to find any potential problem control points. This is does not work as well for parcel data that has a lot of initial distortion. It's not necessarily a good idea to de-activate multiple control points at once, so if you find a possible bad control points, de-activate just the one with the highest residuals from the check-fit, then run the adjustment...etc. If you discover that although you know you have entered all good record bearings/distances, that somehow the system generated lines (that were not directly COGO'd) are inconsistent with the data you actually COGO'd, then take a look at the add-in called The Parcel Fabric Quality Control. The add-in will allow you to filter for big outliers, and inverse bearings and/or distances based on your filter settings, so as to keep the good/original entered record data intact. Of course, when inversing data proceed with caution(!) since it works off geometry, and so if the geometry is distorted the inversed data will not be as close to record as you'd like. The Parcel Fabric Quality Control add-in is here: http://arcg.is/1nRHU30  Once you've installed the add-in click the help button on the toolbar to see the details about how to use the different tolerances. -Tim ... View more

Ryan, The jobs are used for handling the multi-user environment implemented for parcel fabrics. Once the edit in a version has been reconciled and posted, the jobs are committed. Committed jobs have a limited role and serve only as a way to track parcels that had been edited, but this (parcel edit tracking) can also be achieved by standard editor tracking. Committed jobs can be cleared without adversely affecting the parcel fabric. If you are on 10.4 and are using SQLServer, then you may benefit from improved performance by clearing committed jobs from the job book. To learn more about that, please see the thread in this post: 10.4 Parcel Fabric processes have slowed considerably -Tim ... View more

Mike, Thanks again for reporting this, and for sharing your data via tech support. I'm responding again here to share findings with other customers who may have experienced similar issues with SQLServer. The delay was caused by a combination of 2 things: some changes made to the cursor model for 10.4 on SQLServer, and the Uncommitted records (Status=0) in the jobs table. The latter records are accumulated when editing directly against default, instead of in a version. We recommend editing in a version since posting the version will automatically commit the job for you (Status=1). If there is a need to edit directly on default, then after the edit we'd recommend manually committing the job afterwards. To clear out the jobs table, you can un-register the fabric as versioned, then use the Delete Fabric Records add-in 's Truncate command to "Drop all fabric jobs" -Tim ... View more