ArcGIS 10 SP4 Spatial Join Bug

4658
26
04-04-2012 12:57 AM
BenHolmes
New Contributor
Hi

Just to let you know I've experienced the spatial join bug found in SP4.

I was joining 740000+ points to 13 polygons
Just under 19000 records had attribute data come across. The rest were all null.

I've run the exact same data on another machine with ArcGIS 10 SP3 and it worked fine.

I see there was a bug listed ( NIM079126 ) but for some reason it's been declined. Not sure why this is, but you should know this is happening to others.

One thing I noticed was the last record to have an entry before the attributes failed to populate was a point that was outside all polygons I was trying to join to. I'd suggest creating a point dataset with one point outisde the main body of a join polygon to test this. Maybe then we can see some work towards a solution.

Thanks
Ben
0 Kudos
26 Replies
NobbirAhmed
Esri Regular Contributor
Any other suggestions to get this to work?


Sorry that you are having trouble. For a workaround you can call tech support. I'll also lookup for a suggestion.
0 Kudos
DanLee
by Esri Regular Contributor
Esri Regular Contributor
I cannot calculate the proper length of the polylines and copying to another feature class within the gdb does not fix it. Only thing that works is an export and re-import to/from a shapefile.


Sander,
Could you try Copy Features to see if it results in a recalculation of the shape_length?
0 Kudos
SanderSchaminee
New Contributor
@Nobbir:
I'm currently running Windows XP 32 bits Professional (but will be moving to 7 64 bits soon).
The lines are indeed my target features. I've attached a screendump of my field mapping below.
I realize my feature class names are quite long, but the mapping seems to go right here. However, the result is wrong.
[ATTACH=CONFIG]13336[/ATTACH]

Maybe my long feature class names are abbreviated in such a way that their names become identical somehow, causing the tool to mix up the SHAPE_Length fields?

@Dan:
I already tried Copy Features, but strangely enough, that didn't reset the SHAPE_Length. Only export and (re)import via shapefile did the trick.


I would say that the issues related to the Spatial Join are severe enough (disruptive for workflow, maybe even for data integrity etc.) to issue a little patch until SP5 (or 10.1) comes out.
0 Kudos
DanLee
by Esri Regular Contributor
Esri Regular Contributor
Hi Sander,

First: we are working hard on a special patch on 10 SP4 to fix the problems. Hope it will come out soon.

Second: Copy Features tool worked for my test data. I reproduced the wrong shape_length (for the target lines) and then run Copy Features to gdb output. The output shape_length values reflect the original/input line lengths. Will you be able to share your data so I can try?
0 Kudos
TonyAlmeida
Occasional Contributor II
I get Nulls when i run Spatial join with service 10 sp4 and it runs VERY SLOWWWW now.
0 Kudos
SanderSchaminee
New Contributor

First: we are working hard on a special patch on 10 SP4 to fix the problems. Hope it will come out soon.

Ok, that's great news!


Second: Copy Features tool worked for my test data. I reproduced the wrong shape_length (for the target lines) and then run Copy Features to gdb output. The output shape_length values reflect the original/input line lengths. Will you be able to share your data so I can try?

Good to know that you were able to reproduce the SHAPE_Length problem.
As for the Copy Features bug: this issue might have been a freak occurence, related to my geodatabase. My gdb is quite large (too big to share), so I tried to create a "light" copy for you holding only the relevant data - and test Copy Features again at the same time. This time, the tool worked as expected. But that's not the only thing: I cannot reproduce the problem anymore with my original gdb. Even when I run the Spatial Join again and run Copy Features afterwards, SHAPE_Length will be properly recalculated.
0 Kudos
JohnBryant
New Contributor II
Howdy, count me in as waiting for a patch.  This bug has disrupted a number of geoprocessing models I rely on for several ongoing projects.

I gotta say, it is refreshing to hear an ESRI staffer taking the blame on the company's behalf for a bug.  ESRI has really picked up their game in the past few years as far as customer support goes.

Anyway - would love to see that patch ASAP!  Thanks.
0 Kudos
DanLee
by Esri Regular Contributor
Esri Regular Contributor
We have heard all of you. My colleagues and I thank you for your patience.
0 Kudos
ChrisFox3
Occasional Contributor III
The attached Toolbox contains a model that may be helpful in working around this issue until the bug is resolved. It has proved helpful for some customers.
0 Kudos
MaliaSpaid-Reitz
New Contributor
When will SP5 be available?
0 Kudos