How to handle one to many relationships when working with parcels?

[LeahMontoya]

Can someone tell me the best way to handle one to many relationships when working with parcels.  We have condominiums that we have spatially represented with one polygon feature and one parcel number.  They are represented in the Assessors database with multiple Assessor's parcel numbers.  Any input as to how to best handle this situation would be very helpful.

[christopherfricke2]

Your best bet is to use a spatial view if you are using an SDE database.  This will allow you to create the stacked polygons w/o requiring you to duplicate data.  Also, this allows for a more dynamic process.  The most up to date data is returned every time the client makes a request to the spatial view.  The python tool example means that there is always a lag time between edits performed on parcels or assessor info and what is visible to the clients.

You need to make sure that you pull a unique OBJECTID from the joined table.  Otherwise queries will return really crazy results. 

I have also used this method to pull in Assessor info from external databases (like BSA).

SELECT Assessor.OBJECTID, Assessor.OwnerName, Parcel.ParcelID, Parcel.Shape 
FROM dbo.Parcel 
INNER JOIN dbo.Assessor
ON Parcel.ParcelID = Assessor.ParcelID

--------------
Christopher Fricke
GISi

[RyanKelso]

I've found the 'Tax Parcel Publishing' script in the ParcelPublishingTools toolbox from the TaxParcelEditingfor10.1 that I believe is supposed to migrate our data from the Parcel Editing dataset to the Parcel Publishing dataset.  I have not been successful in running this tool.  Looking at the updatetaxparcels.py in the same Parcel Publishing folder I cannot figure out where to change the python code to make this script work.  Is there an updated version of this script or any reason for it to not be working?

I want to provide an answer to this question since I had the same problem as b.blackman and this thread came up for me in a search.

If you have enabled the Local Government Information Model on your parcel fabric, which you would have if you want to use the Tax Parcel Editing Template, then there is no "Parcels" sub-layer in the fabric.  This is why the following line fails:

parcels = r"%s_Layer\Parcels"%(name)

With the LGIM enabled on the parcel fabric, there is a sub-layer called "Tax Parcels", which is what you want to use.  So change the line I mentioned before to:

parcels = r"%s_Layer\Tax Parcels"%(name)

Also, the Tax Parcels sub-layer has already queried out historical parcels, so the query in the following line will return 0 parcels so none will be appended to the parcels publishing feature class:

arcpy.management.SelectLayerByAttribute(parcels, "NEW_SELECTION", """Type = 7 AND Historical = 0""")

So remove AND Historical = 0 from the query to get the proper results.  I suppose you could even completely remove the Select Layer By Attributes line because the Tax Parcels sub-layer has already been queried to only include Type 7.  These are the things I had to do to get the script working, I hope this helps anybody with this problem.

edit: sorry for reviving such an old thread, but it came up on a google search and I only noticed the last two posts were from a month ago!