Parcel Fabrics

[JeffScott1]

Hello All!

I'm newly getting into the GIS game and need some help
I have been asked to spearhhead my city governments transition from shapefiles to parcelfabrics and I need some help. is there a one stop answer all questions kind of resource availiable to take me from novice to expert? most of the resuorces i find here seem to be fragmented and patchy.

Also i am wondering about managing multiple parcel types within a single fabric. I have created a test fabric out of a 2 block portion of our city and imported lots and tax parcels and easments into the model but cannot really see how this would be better than having 1 fabric and simply associating the relavent feature classes to it. is there a reason? is there a way to differentiate them other than using symbology?

any help would be appreciated.

[Zeke]

There are a lot of resources on the forums and in the resource center, but you're right, they tend to be somewhat scattered rather than centralized. The main advantage to a parcel fabric I see is that it takes care of topology - move one boundary, and corresponding and/or related boundaries adjust as well. There might be other advantages as well, but I'm pretty new to it myself.

The Land Records part of the Local Government Model (LGM), which uses a parcel fabric in a particular geodatabase schema, allows you to use a variety of predefined maps, workflows and applications that ESRI has designed. You don't have to adopt the whole LGM if you don't want, but it's designed to integrate between functions - land records, public safety, public works, etc. - if you do. You can use a parcel fabric without the LGM, but it can save you some work.

As far as different parcel types, those are taken care of by geodatabase domains, in the LGM anyway. So while you have one parcel fabric, there's a field called Type that uses a domain to differentiate between lots, tax parcels, subdivisions, etc.

The hardest part, in my experience, is cleaning up the data to get it ready to load into the fabric. A good start is this white paper. HTH.

[JeffScott1]

hey thanks for the help.
I'll try those