Loading Parcel Types into Parcel Fabric

Question

All:

My org is about to load legacy parcel data into the Parcel Fabric (PF) in the production environment.  In lower testing environments we found issues with inactive parcel layers being loaded into the PF.

As such I am curious what other orgs have done when migrating previous parcel data into the PF?

Did you load inactive parcels or did you ignore them in the data load and just recreate the inactive parcels via COGO in the PF?

Any feedback and/or actual workflow information is greatly appreciated.

AmirBar-Maor · Answer

@MichaelVolz

The parcel fabric is part of the 'System Of Record' concept. As such we try to be as true to the legal record as possible.

200 lines might not be worth too much effort, but if you had 200,000 it would have been worth the effort to bring them in, assuming they are a good representation of the legal record they came from. 
Without seeing your data it is hard to provide any advice. Just keep in mind that in the parcel fabric:

* The COGO direction and the line direction (geometry) are assumed to be the same.
* You can run the geoprocessing tool Set Parcel Label Position and set the label to be right/left or centered.

If you do end up recreating the lines and want the COGO dimensions to be close to the record, make sure to apply to correct ground to grid correction (combined scale factor and basis of bearing).

I hope this helps

MikeVolz · Answer

Hi AmirBar:

Please correct me if I'm wrong about the cause of the COGO label errors my org is seeing and our proposed solution.

The COGO label errors are caused because the lines were entered in ArcMap where information is stored differently.  The storage of this information conflicts with the code for the parcel lines labels which is quite complex as it is approximately 200 lines.

My org will just bring in the inactive parcel polygons (No lines) and let the Parcel Fabric create the lines from these polygons so they will follow the ArcGIS Pro standards that the ArcMap lines did not meet.

Does this appear to be a solution for getting past these COGO label errors?

AmirBar-Maor · Answer

Hello @MichaelVolz

If you find business value in historic parcels, I would load them in.

BUT...

* Make sure they align with the current parcels first.
* Ideally, you can populate the 'RetiredByRecord' field with the record that retired them, but if not: you can associate them all to a record called 'Inactive Legacy' (or similar). And if that's too much work,  populate it with the guid '{DDDDDDDD-DDDD-DDDD-DDDD-DDDDDDDDDDDD}'.

I hope this helps and that other organizations share their experiences. We are curious too.