Using the Import Fabric Data wizard log file to locate errors in migrated parcels

This topic applies to ArcEditor and ArcInfo only.

You can log the results of an import of data to the parcel fabric in the final step of the Import Fabric Data wizard. The importer will log errors in these circumstances:

• Incorrect COGO attributes are found (in other words, when COGO attributes differ significantly from the line shapes).

  The parcel is generated from the dimensions of the line shape geometry instead.

• COGO attributes for parcels do not form a closed loop.

  A parcel with invalid lines is generated. This parcel should be identified and fixed.

• Invalid curve attributes are found on parcel lines (radius too short, chord distance not consistent with its delta angle, and so on).
• A parcel is found with more than 2,000 lines.

  The parcel is not imported.

• A densified arc that represents a curve is found with no COGO attributes.

  A densified arc that is found with COGO attributes will be converted into a true curve during the import process.

• X,y coordinates are missing for a row when importing control points (all other x,y coordinates exist).

  The control point will not be imported.

• The shape field is missing for a row when importing either parcel data or control points.

  The parcel or control point will not be imported.

• A field is found to be of the wrong type.

  For example, you added an Accuracy field to your source parcel polygons to migrate parcel accuracy. If your Accuracy field is not a long integer type, the values will not be imported.

• Source parcel lines reference points that cannot be found in the source parcel points table.
• The fabric source data is in a different projection from your parcel fabric dataset.

Steps:

When migrating parcel data using the Import Fabric Data wizard, make sure to specify a log file by clicking the Log import results to a file option in the final step of the wizard.
1. After migrating your fabric source data into your parcel fabric, open your log file.

If the log file contains errors, the parcel IDs, line IDs, and point IDs refer to the system COGO feature IDs in your fabric source data, not in the parcel fabric.

2. To identify a parcel or line error reported in the log file, load both the source parcel polygon or line feature classes and the parcel fabric into ArcMap.
3. Open the attribute table of your source parcel polygons or source parcel lines.
4. Click the underscore (_) or pound sign (#) field name to select the entire field, for example, AlachuaCounty_ field.
5. Click the Options button and click Find & Replace.
6. In the Find and Replace dialog box, type the parcel or line ID reported in the log file in the Find What text box.
7. Click Find Next.
8. Click Cancel to close the Find and Replace dialog box, then select the row in the attribute table containing the ID you searched for.

9. Right-click and click Zoom To to zoom to the selected line or parcel in your fabric source data.

You have now located the parcel in your parcel fabric that has the problem.

10. Turn off your fabric source feature classes, select the corresponding parcel in your parcel fabric, then open the parcel.
11. Select the parcel in either the parcel explorer or the map to open the parcel in the parcel traverse environment. You might need to select the parcel in the parcel explorer because sometimes, if the parcel is badly skewed, you cannot select it in the map.

When the parcel is opened in the parcel traverse environment, it is displayed according to its COGO dimensions in the parcel traverse. Bad misclosures due to bad lines are easily identified in the parcel traverse environment.

Tip:

You can use the values in the MiscloseRatio and MiscloseDistance fields in the parcel fabric parcels attribute table to locate those parcels with large misclosures.