nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Joining Large files (900,000 records)

BrianRizzo

Join operation takes about 12 hours to complete in Pro. (900,000 records with about 10 variables). Desktop operation takes about 6 hrs. Is this normal? If so, how does this speak to BIG data as this is not really representative of BIG data.

platform - recent I7, 16 GB, SSD.

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

DanPatterson_Retired

Attribute join? or spatial join?

IanMurray

You may try to find a better solution.

https://community.esri.com/blogs/richard_fairhurst/2014/11/08/turbo-charging-data-manipulation-with-python-cursors-and-dictionaries

JoshuaBixby

In addition to Dan's question, can you provide some more information on where the data is stored (file geodatabase, enterprise geodatabase, etc...) and how exactly you are implementing the join (using a geoprocessing tool, dialog box in UI, etc...).

BrianRizzo

Point fc file stored in a file GDB. Attempting to join an attribute from a csv.

DanPatterson_Retired

I am wondering if the csv is the issue, have you tried to convert it to a geodatabase table and then join?

BrianRizzo

While the join itself works and seems to happen very quickly, saving the join is the real problem. Converting the csv file to a GDB table doesn't seem to provide any gains.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.