POST
|
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!
... View more
09-24-2015
06:24 AM
|
0
|
1
|
184
|
POST
|
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.
... View more
09-23-2015
11:23 AM
|
0
|
8
|
467
|
POST
|
Oh how I wish I could; unfortunately this data has privileged information.
... View more
09-23-2015
10:20 AM
|
0
|
10
|
757
|
POST
|
Thanks Mitch Muskchamp, but selecting 'ONLY FID', deleted all the data in the attribute table.
... View more
09-23-2015
10:08 AM
|
0
|
12
|
757
|
POST
|
It's weird. This particular intersection has changed the name of the original fields altogether. Thanks for your time.
... View more
09-23-2015
09:29 AM
|
0
|
0
|
757
|
POST
|
I am using 10.3. Attribute table BEFORE intersect: Attribute table AFTER intersect:
... View more
09-23-2015
09:11 AM
|
0
|
0
|
757
|
POST
|
Why does the attribute name fields change after performing an intersect?
... View more
09-23-2015
08:55 AM
|
0
|
21
|
6373
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|