I need to create a series of maps for a property that has many parts/easements (polygons). Each easement can have many owners, and many easement types. Eventually, I need to create a series by owner, and then by easement type. For example, I need a series of maps for Owner A, and then a map showing telecomuniciation easements under Owner A, and another for vehicular access under Owner A. Wash, rinse, repeat for Owner B, C, etc. So, many parts/easements can have multiple types and owners associated with it.
My original thought was to create an attribute table of the polygon feature class with parts, and then have booleans:
| PART | Owner A | Owner B | Owner C | Type A | Type B | Type C |
| 1 | 1 | 1 | 0 | 1 | 0 | 1 |
| 2 | 0 | 1 | 1 | 1 | 1 | 1 |
| 3 | 0 | 0 | 1 | 1 | 1 | 0 |
Then I can query the data later. But I don't think this will work if I only want to use one map and many layouts or a map series. I think my original idea requires a map for each Owner to Type.
Currently I have a polygon feature class with all the easements. Then a reference/look-up table listing all the possible types of easements the parts could be, and another table of all the possible owners.
Or should I just have records in one feature class that'll overlap eachother but are all the possible combinations for that specific part?
I'm more comfortable in Microsoft Access which is probably why I'm structuring this like I would in that program, but I understand ArcPro is very different. Any advice would be very helpful.
