topic Re: Structuring Data with One-to-Many Relationships in ArcGIS Pro Questions

Structuring Data with One-to-Many Relationships

Re: Structuring Data with One-to-Many Relationships

Re: Structuring Data with One-to-Many Relationships

Re: Structuring Data with One-to-Many Relationships

MapsterMind — Thu, 24 Oct 2024 18:15:50 GMT

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:

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?

Part	Owner	Type
1	A	A
1	A	B
2	A	A

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.

DavidSolari — Thu, 24 Oct 2024 18:42:21 GMT

One-to-many relationship classes should work here, but something that works in ArcGIS Pro might fall apart once it gets into a server based workflow due to edit tool limitations. It looks like you just want to tag every easement polygon with an Owner and Type, with a set list of options for both. In that case you might want to use Coded Value Domains to lock those options in, then you can filter on those two fields instead of trying to do relationship-based selections.

MapsterMind — Thu, 24 Oct 2024 19:02:21 GMT

Fortuntately this is for a one-time project, but there may need to be edits later. This is all happening in a local GDB.

If I have a Coded Value Domain, can I select multiple options? For example, if Part 1 was was a telecom type for Owner A, and a watermain type for Owners A and B, then I can select two Type options and two Owner options?

Part	Owner	Type
1	A, B	Telecom, Watermain

Owner A

Owner B

Owner C

Type A

Type B

Type C

DavidSolari — Thu, 24 Oct 2024 19:47:20 GMT

Sadly no, and there's no news of a multi-choice domain type on the horizon. In this case you'd need a many-to-many relationship class between the easements and each of the choice tables, then do some stuff with calculating data or attribute rules into a redundant field to get the final table.