02/16/2017 Parcel Fabric for ArcMap Geoprocessing Script Tools

[AmirBar-Maor]

Parcel Fabric Geoprocessing tools have been organized and modified. You can now download them in a single location and easily deploy them.
The collection of toolboxes cover the following areas: data migration, feature adjustment, parcel fabric adjustment, export and reporting, field calculation and useful samples for python (script tools) developers.

In this meeting we'll demo how to get and deploy the tools + demo some of the tools we are excited about.

All the tools can be found in this location: http://arcg.is/29QobNB 

[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:

1. "Aggregate Boundary Lines From Polygon Layers"
2. "Create Topology Fabric Source By Polygon Filter" and
3. "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

[anna_garrett]

Hey yall! I was stoked to try the export to simple feature classes tool for our public release, but I've tried a few times and run into this error. States the tool can't be used in an edit session, which I already knew from the notes. I'm not in an edit session. I'm using 10.4.1. I'll provide any other details I can to help.

[TimHodson]

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

[Anonymous User]

Is there a limit to how many polygons/lines/parcels that can be run through these GP tools?

Thanks for this great tutorial. I've been looking for something like this for a while now.

-Matthew

[AmirBar-Maor]

Hello Matthew,

Thanks for the feedback.

you can restrict the number of processed features for any geoprocessing tool using selection. 

Another option is to modify the script. Here is an example:

featuresSelected=len(arcpy.Describe(inputPolygonLayer).FIDSet.split('; '))
if featuresSelected>maxNumberOfParcelsToProcess:
    arcpy.AddError("\n\n\nToo many polygons selected. Select less then {0}. \n\n\n Aborting.".format(maxNumberOfParcelsToProcess))
    return None

Amir

[anna_garrett]

Hi Tim,

The default geodatabase is the original default, a file geodatabase on my hard drive under Documents\ArcGIS. The fabric resides on our server. 

[Anonymous User]

I'm running into an error and I've narrowed it down to what seems to be the polygon causing the error (it keeps highlighting this particular polygon). Why am I receiving this error? 

UPDATE: I have found that having all your data under the same GD helps with these GP's.

Cheers

[TimHodson]

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?

[anna_garrett]

Hi Tim,

I'll give a shot in the next day or so and will get back with you. I can't recall if I was using the default or not.