Latest Contributions by TimHodson

The ability to apply Ground to Grid corrections will become available soon, with the release of ArcGIS Pro 2.3. -Tim ... View more

The Stated Area field on the Parcel Fabric parcels is calculated from the Direction and Distance attributes that form the parcel boundaries. The Stated Area and the shape_area will be different in scenarios where the parcel shape has been altered by the change in position of fabric points. Fabric point position changes do not ever automatically change direction and distance attributes. So this means that changes in the fabric point locations also do not alter the Stated Area. Some examples of how fabric points can move include: Joining and/or re-joining parcels using (doc) Fabric Adjustment (doc) Transform Parcels toolbar (doc) Fabric Point Move To Feature Add-in It is also possible that the Direction and Distance attributes do not mathematically close back onto the starting point, resulting in a misclosure error. The Stated Area is calculated based on the "measurement based" polygon that results AFTER the misclose is adjusted by Compass Rule. You can see this representation of the parcel by using the Measurement view. (doc - section called "Open parcels using dimensions instead of shape") The Stated Area is also sometimes called the Record Area because it is calculated from direction and distance records. ... View more

Hi Jeff, You may have already seen a hint of forthcoming support for spirals in ArcGIS Pro; when you COGO-enable a lines feature class, you will notice that there is a Radius2 field.   The 10.x ArcGIS support for spirals is available only via the SDK. There is a recent addition (yesterday) to the Parcel Edit Helper Add-In that allows you to create a spiral as part of the Edit Sketch. The add-in is here (10.4 and higher): http://arcg.is/2fXvAO8 That same add-in allows the edit sketch to be turned into a parcel in the fabric. Note that this particular add-in is only supported as SDK product; the functionality you see is used as a set of examples by developers for customizing the parcel fabric editing experience. However, if there are bugs or issues that you encounter while using the add-in, please report them anyway, at the GitHub location, where you can also find the code: https://github.com/Esri/parcel-fabric-desktop-addins/commits/master/WorkflowUtilities/ParcelEditHelpers/AddIn_ParcelEditHelpers/SourceCode   When a spiral is created the resulting polyline is a series of straight segments that approximate a spiral. However the end point of that polyline is accurately computed, regardless of how the polyline was densified (there are 3 different methods of densifying the spiral.)   Since spirals are often used as a tangent into, or a tangent out of, a circular arc or straight line, the Spiral add-in is designed to capture the exit tangent of the computed spiral and constrain the sketch bearing to the tangent of the last spiral created. Some care should be taken not to use Tangent Curve command after a spiral is constructed because that tangency would be based on the last segment of the polyline approximation of the spiral rather than the true tangent of the spiral itself. Therefore, for the true tangent, accept the sketch constraint that gets set after clicking Create on the Spiral dialog.   Example; when constructing a series of courses in the sequence: straight line, spiral, transition curve, spiral, straight line, proceed as follows: Create straight line with edit sketch using any of the normal methods Right-click to get Edit Sketch context menu, click Deflection, enter 0° for deflection to constrain the sketch rubber-banding to a tangent bearing Right-click, Spiral, accept the given bearing in the first entry of the dialog, and enter the other parameters for the spiral, click Create. The spiral is created and the sketch is constrained to tangent exit bearing from the mathematically computed spiral, and is different to the tangent that would be calculated off the last segment. Right-click, Spiral, accept the given bearing in the first entry of the dialog, and enter parameters of the circular arc by entering the same radius value for Start Radius and End Radius; a tangent circular arc is created. Keep the tangent direction constraint rubber-banding from the circular arc, or since the circular arc is a true parametric geometry, it would also be OK at this point to hit Esc key to free the constraint and then use the Deflection = 0° to reset it; the result should be the same tangent. Enter the distance for the straight line. Finish Sketch/ finish Part, add another segment, etc. Jonathan McDowell‌ - including Jon, as he has written a similar tool for the ORMAP group. Thanks, -Tim ... View more

Hi Anna, I was able to reproduce the problem when the fabric layer references a source that is a version other than default. When changing the data source to the default version the export succeeds. If you reference the default version, does it work for you? ... View more

Hi Anna, What is your default geodatabase set to? Please try to change your current map document's default database to a file geodatabase, or something separate to the geodatabase that holds your fabric (if it's not already?) and try again. The error messaging needs to be improved here, regardless, so thanks for reporting this. -Tim ... View more

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