Importing information into the Plan Directory (Description Field)

[JohnFell]

I am interested in using the plan directory as the source search dialogue for our parcel editing workflows. We have subdivision attributes that include a document number (Volume/Page) and legal date(filed at county clerks) that I would like to include in the search criteria. I can import the plan name by adding the plan field when importing using the topology loader. Is there a way we can import this document number into say the "Description" field of the plan table? If the description field cannot be populated what are our other options? Concatenate a plan name and document number field into one and search on that? Any insight would be appreciated.

[BryndaHatch]

I am also interested in this. I've copied a quote from the Help saying, "In the fabric, parcels can be grouped by their plan, plat, or record of survey. Plan information is stored in the Fabric_Plans table. Each parcel has a PlanID attribute field containing the ID of the plan in the plans table. Plan information can be migrated into the parcel fabric or created during editing." It's the last sentence that I'm focusing on. I have a BookAndPage number I'd like to carry through during migration. Does anyone know, if I put a BookAndPage field in my source polygon attribute table, and a matching field in my target fabric plan table, will it migrate across? This is a new field, and not the currently existing Description field as fellj is trying to do. Although, if it works for one, it should work for the other, I'd imagine.

[BryndaHatch]

I answered my own question.  It doesn't work the way I hypothesized.  But I haven't given up hope yet.  I'll keep you posted.  I also tried calling it PlanBookAndPage in the polygons and BookAndPage in the plan table, since that's how you do it for the PlanName (polygons) and Name (plan) fields.

[MarkJohnson]

Hi Brynda,

Here's how I'm (attempting) to do this:

• First off, I have a plats polygon layer with a unique ID field PLAT_ID and all my attributes that I do a spatial join with my parcels to assign the plat attributes to each parcel.  (I generate PLAT_ID from OBJECTID)


• I add PLANNAME to parcels and calculate it = PLAT_ID.


• In my empty fabric, I add my plats fields to the Plans table.


• After importing parcels into the fabric, I create a table view of the Plans table and join it to the original Plats layer by PLAT_ID.


• Calculate each Plats field into the fields you created in the Plans table.  Calculate over the PLAT_ID values in NAME with your actual plat names.

Maybe there's a way to do some sort of append to the Plans view instead of manually recreating the fields like I did?

Mark Johnson
GIS Specialist
Summit County Fiscal Office

[TiffanyPuett]

At 10.1 you can isolate out the plans table.  If you are able to populate the description field with the correct plan name (from a subdivision layer, say) then if you add the book & page ref fields to the plan table, you should be able to populate the values by joining on the "description."

[TiffanyPuett]

...Just wanted to update this information a bit.  Once you get your information populated for your poly's you can get them into the plans table using the Fabric Plans tool found here:  http://resources.arcgis.com/gallery/file/ArcObjects-.NET-API-Code-Gallery/details?entryID=57ECE6F0-1...

[ChrisNelsen]

I am going about loading my Plan data in the following method.
1. Make a Table view of the plans by using the Parcel Fabric Toolbox - Make Parcel Fabric Table View
2. I then joined that table with a table of data I wanted to populate, ex. Surveyor, Book & Page
3. I just do a field calculate of the joined table field and save.

Really I think the key part is making the Table view. Once you have that I believe it's more like the workflow you currently are us to.