There should be no problem here. Each parcel should have its own unique tax ID. Every time the parcel itself is changed (for example a portion of it is sold) it should get a new number and the old one retired. If that is how you do it, then there should be a unique tax id that can serve as a "key" field. While one could anticipate the maximum number of owners and have separate fields for owner1, owner2 etc, there is a better way.
In another table, you would store owner data, including the TAX ID along with what ever specific data such as date purchased, mailing address, etc. Hopefully this is obtained as an export from another data base that tracks the parcels (we use BS&A's "Equalizer" here). This table would have no unique field, as one person could own many parcels and one parcel could have many owners. Now, geocode the owners table to the parcel table and each record should fall to the centroid of each parcel. If a parcel has 3 owners, there would be 3 records geocoded to the parcel. The boundary select tool works great here, clicking on the parcel selects all the objects within the parcel region. As a drawback to a normalized data base, there would be multiple records containing duplicate data where one person owns multiple parcels, but we cant force too much relational stuff on MI's back, and you probably have a small number of these cases. <<<<<<OR>>>>> pull the data together in an SQL, Select * from Parcels, Owners where parcels.TaxID = owner.TaxID into selection. (all records) Select * from Parcels, Owners where parcels.TaxID = owner.TaxID AND Parcels.TaxID ="[enter the tax id for a specific parcel here]"into selection (A specific record) <<<<Notum Beni for geocoded records>>>> When you geocode a record to the centroid of an object, then do a buffer selection, for example, to send out a public notice to properties within 300 feet of a rezoning, and the centroid (and hence the geocoded records as well) falls outside of the buffer, then you have to do a join after selecting the parcels. Here there are 3 tables: Parcels, Owners, Buffers. Buffers should only hold the buffer's for the task at hand. Select your target parcel and create a buffer of the desired radius. Select * from Buffers, Parcels, Owners where Buffers.Obj Intersects Parcels.Obj And Parcels.PID=Owners.PID into Selection William "Woody" Woodruff Zoning Administrator Charter Township of Union, Isabella County, Michigan -84.80947000 43.61095100 2010 S Lincoln Rd, Mt. Pleasant, MI 48858 (989) 772 4600 EXT 41 Visit our web site at http://www.geocities.com/ctuzoning/index.htm -----Original Message----- From: Michael Smith [mailto:[EMAIL PROTECTED] Sent: August 11, 2004 09:28 To: [EMAIL PROTECTED] Subject: MI-L multiple owners for one parcel Hi List, I was wondering how if some of you have a resolution to handling multiple owners for one parcel. I have a parcel layer with a single db field using the Tax ID Number from the County Tax Assesor's office that I use to tie to our county tax database based on these Tax ID Numbers. The problem I run into is that if I tie my parcel to a Tax ID number, there can be multiple accounts associated with a single parcel because of multiple owners of a single parcel. As a fix, I have added multiple parcels (to represent each owner i.e. tax id number) on top of one another and entered in the tax id number for each one for each of these parcels. I just was curious as to how any of you may handle this or if it is a problem that you have encountered. I am not sure if I have made myself clear in the question I am asking so feel free to ask for an example. Any suggestions are welcome. Thanks in advance. --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 12922 --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 12945
