Why does the attribute name fields change after performing an intersect?
Can you provide an example? What version ArcGIS are you using?
I am using 10.3.
Attribute table BEFORE intersect:
Attribute table AFTER intersect:
I'm using 10.0; it adds a few fields but leaves the originals intact. Sorry, can't comment on 10.3; you may have discovered an undocumented feature, aka bug....
It's weird. This particular intersection has changed the name of the original fields altogether. Thanks for your time.
Try unslecting 'ALL' from the 'JoinAttributes' field in the 'Interset' tool window. Instead, select 'ONLY_FID'.
Are you sure it is replacing the fields and not just inserting and pushing the original fields to the right?
Let me know what happens.
Thanks Mitch Muskchamp, but selecting 'ONLY FID', deleted all the data in the attribute table.
Could you zip the two files you're attempting to run this 'Intersect' process on and post them here?
Oh how I wish I could; unfortunately this data has privileged information.
Again, are you sure the new fields aren't just added fields? And they're just pushing over the older fields to the right?
I'm sure. It appears the new name is of a subset of the original name that was created after I geocoded the original file. I'm sure I just confused you there.
Synopsis: I geocoded some data, then called the layer "geocoded results" (attribute table not disturbed) then I performed the intersect. This is when the attribute field names changed automatically to "geocodi_XX (1-100)". The reason this is a problem for me...is because I am going to convert this file into an excel table and provide the data to a customer. This is a rather large dataset; encompassing over 5000 records and not a simple task of manually changing the names back. I think I may have to re-invent the wheel and perform the process all over. Thanks for your help.
Have you tried finding ways around this? Like using 'Select by Location' or 'Select by Attributes'?
I have not.
What type of output are you writing to? A shapefile? File Geodatabase Feature Class?
Uggh. The demise of modern civilization. Try it to a file geodatabase feature class and see what happens.
That's your problem right there. Shapefiles have limits on field name width, which are generally dealt with by making aliases in metadata and naming the columns to sequential names that don't conflict.
Do your analysis in FGDB then rename the columns on export to shapefile when you're done.
or use far better naming conventions for shapefiles in the first place right Vince?
That's difficult, because there aren't any good naming conventions that merge source name and field with an underscore in ten characters. It's all part of why shapefiles should be avoided (naming limits, lack of wide strings, BLOBs, CLOBs, and numeric nulls, limited date representation, 2Gb file limit...)
the files had the same field names, you can have this since you don't want to overwrite existing data, hence the field name change based upon a minimal intrusion name outcome
Thanks all. I basically uninstall/reinstall ESRI and somehow it worked. My IT team indicated that there was something going on with the malware. Thanks!
Are you sure that when you tried to run the tool, your data was not joined to a dataset?
This causes the output field names to come out as: dataset_Fields
Which then gets truncated to dataset_
So one of your datasets in the join was called geocoding?
Retrieving data ...