byezy
commented
5 years ago Hi John to start this tool we will need some examples of what you are looking to accomplish... i.e. some data in an fgdb and an mxd with inputs and results, push that into it's own branch in the test repo (ask Tom or I if unsure how to do this when you have some data ready). Making a clip of representative data for development makes it easier if the data are large sets. That code from esri is helpful but a little obtuse, the python is not too flash. We should be able to do this using pandas, which will be blisteringly fast in comparison to joining using loops - but need some examples to be sure about this. Looks like fun!
imagesbyjohnyoung
@TomWaterat @byezy The purpose of this tool is to join multiple tables (generated from e.g. Tabulate Intersection process) to a base zone/grid file.
Ideally, in a search table (this having a field that has the geodata, the table name, and field to join on, and priority order) it could be used to loop through, based on priority (important to be able to group like features together) and apply the joins to the zone/grid file.
Currently there appears to be an issue with the standard join table tool (Data Mgmt > Joins > Join Field) with being slow to process. This may be due to no indexing.
E.g. of slowness 17hrs to join ~45 tables to a hex grid of 28k features.
It does appear as a common question to esri.
Attached is an alternative code from Esri, that seems quicker, but having issues when attempting to join multiple tables as a batch.
The ability of joining tables (even though no data may exist after tabulate intersect) still needs to be available. Reason, this identifies that the particular layer/asset doesn't exist within the zones - important to know this. Join_Field.zip