Is there a limit to the number of admin layers that can be included in a parcel fabric?

AlisonKelsey

Hi,

I am working on a project where there are 115 layers that need to be included either as administrative layers or feature classes outside of the parcel fabric that topologically relate it. 

Is there a practical limit on the number of administrative layers that can be included in a parcel fabric?  

Additionally, is it possible to create feature classes that exist outside of the parcel fabric that topologically interact with parcel types within the parcel fabric?

Alison

 

AmirBar-Maor

115 layers is a map sounds way too many.

Regardless of the data source, a map with so many layers is hard to manage and might be slow to draw and refresh.

As for the number of parcel types in a parcel fabric:

I would try to limit them to around 10  - the reason is that for many operations a database cursor is used to open the table and if you have 10 parcel types it translates to 20 cursors. On top of that many operations are impacted by topology (dirty areas, error features). For example: if you delete a feature we also check that there is no error associated with that feature + create a dirty area.
So if you have so many 'types' of entities the recommendation is to try to consolidate them into a reasonable number of parcel types. For example: if you have 20 easement types they can all be in a single parcel type called 'Easements' and use a field called 'EasementType' to symbolize the different easement types.

 

Can you include feature classes that are not controlled by the parcel fabric in the parcel fabric topology?

YES. Just make sure to create them in the same feature dataset.