topic Re: join table only does the first row in ArcGIS Pro Questions

join table only does the first row

DavidHirschberg — Mon, 28 Sep 2020 18:54:32 GMT

So my problem is here.

I have two tables one that has all the census data and the other that has observation data based off the FID that is found in the census data.

here is the structure for table 1

CASES, FID,DATE

structure for table 2

FID, other information

the data in table one has multiple values going to FID 10

I really want to join the table with the layer using FID but whenever I do that only the first row is populating to the table. I am trying to use temporal analysis and look add the data using a time slider but I can't get passed this hurdle. Any help would be appreciated.

Re: join table only does the first row

JoeBorgione — Mon, 28 Sep 2020 19:02:35 GMT

Sounds like you are trying to make a 1 to Many join, and out of the box ArcMap or ArcGIS Pro don't do one to many joins: use a relate or relationship class.

Re: join table only does the first row

LukasFalk — Mon, 28 Sep 2020 20:24:50 GMT

Hello David,

Joe is right, ArcMap and ArcGIS Pro don't support One to Many cardinality on Joins. Using a relate or relationship class are two alternatives you can utilize. If for some reason you are set on using a Join however, there are some roundabout ways you can achieve this. Below is the URL for documentation about how to achieve this in ArcMap, although all the core concepts should carry over to ArcGIS Pro.

How To: Create a one-to-many join in ArcMap

However if you're not dead set on using a join, setting up a relate will be the more straightforward workflow.

I hope this helps!

Lukas

Re: join table only does the first row

TimOrmsby — Tue, 29 Sep 2020 03:37:45 GMT

Hi David,

a one-to-many join is for most purposes not a recommended workflow in Pro, but it is possible and can be used for temporal visualization. It may be that the data in your tables needs to be reorganized using the Transpose Fields tool or some field calculations. Documentation is not extensive but there is a tutorial that works in detail through a similar scenario: Visualize temporal data. It's a bit of a time investment but it should give you insight into how your table data needs to be structured.