ArcGIS 10 SP4 Spatial Join Bug

3301
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
KimOllivier
Regular Contributor II
Worked fine for me, with a small dataset.

Maybe your environments are different. Scratch workspaces, swap space, full disk, default workspace not a filegeodatabase...
0 Kudos
DanLee
by Esri Regular Contributor
Esri Regular Contributor
See this similar discussion:
http://forums.arcgis.com/threads/54102-Spatial-join-tool-vs.-right-click-spatial-join-producing-diff...

I have confirmed that we introduced a bug in 10 Sp4. Really sorry about that! The problem will be fixed in 10 SP5.

Just FYI (according to my colleague):
The tool works fine if all input points find spatialy related polygons (i.e. Join_Count > 0). The problem happens when a point is encountered without any related (e.g., INTERSECT) join features, all subsequenct records in the output gets null values from the join features. One workaround (if you want to continue using Spatial Join) would be to uncheck 'Keep All Target Features' parameter on tool dialog or use 'KEEP_COMMON' option in script.
0 Kudos
BenHolmes
New Contributor
Thanks for that Dan

All points in this case should really of been within the polygons!

I'll can just make an envelope polygon to pick up any that are just outside the admin boundaries.
Should do the job until SP5

Thanks
Ben
0 Kudos
SanderSchaminee
New Contributor
See this similar discussion:
http://forums.arcgis.com/threads/54102-Spatial-join-tool-vs.-right-click-spatial-join-producing-diff...
<SNIP>
One workaround (if you want to continue using Spatial Join) would be to uncheck 'Keep All Target Features' parameter on tool dialog or use 'KEEP_COMMON' option in script.


Yes, that is correct. However, I noticed something else as well.
When joining polyline features with a (circular) polygon feature class in a file geodatabase, the SHAPE_Length is not transferred/recalculated properly (even with the 'Keep All Target Features' parameter unchecked).
This happens with the default field mapping. Seems that the SHAPE_Length from the polygon join features is transferred to the polylines instead, which should not happen, since this is a reserved field that belongs exclusively to the output geometry. SHAPE_Leng_1 on the other hand (which should contain the joined polygon perimeters), is <Null>.
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.

See picture below (unfortunately, I've already deleted the SHAPE_Leng_1 field).

[ATTACH=CONFIG]13268[/ATTACH]


Sander
0 Kudos
JenniferLishman
New Contributor
See this similar discussion:
http://forums.arcgis.com/threads/54102-Spatial-join-tool-vs.-right-click-spatial-join-producing-diff...

I have confirmed that we introduced a bug in 10 Sp4. Really sorry about that! The problem will be fixed in 10 SP5.

Just FYI (according to my colleague):
The tool works fine if all input points find spatialy related polygons (i.e. Join_Count > 0). The problem happens when a point is encountered without any related (e.g., INTERSECT) join features, all subsequenct records in the output gets null values from the join features. One workaround (if you want to continue using Spatial Join) would be to uncheck 'Keep All Target Features' parameter on tool dialog or use 'KEEP_COMMON' option in script.


I am using a spatial join in geoprocessing model and I am having this problem joining points to points (using intersect and a specified distance) even when the Join Count > 0. Attribute values for most features come across as NULL. One of the outputs that we need is the join counts so running an Intersect instead is not an option.

I tried the suggested workaround to uncheck "Keep All Target Features " but I am getting the same NULL values output.  This processworked fine in SP3.  This is causing quite a hiccup in workflow for our project, and the deliverable is due soon, way before the anticipated July release of SP5.  We can't downgrade back to SP3.  Any other suggestions to get this to work?
0 Kudos
DanMcCoy
Occasional Contributor III
I have confirmed that we introduced a bug in 10 Sp4. Really sorry about that! The problem will be fixed in 10 SP5.


Dan,

Is this NIM079126 or a different BUG#?
http://support.esri.com/en/bugs/nimbus/TklNMDc5MTI2

May just be a matter of timing, but NIM079126 is listed as "Declined" in the link above and "Non-Reproducible" in our Support Bugs in Customer Care Portal.

Thanks,

Dan M.
0 Kudos
JenniferLishman
New Contributor
Perhaps it is a different bug. Whatever the case, I am getting NULL attribute values when running the spatial join tool. I will file an incident report tomorrow and see if we can figure out what is going on.

Thanks,
Jen
0 Kudos
DanLee
by Esri Regular Contributor
Esri Regular Contributor
We are checking on this matter. I will update once I know what's going on.
0 Kudos
NobbirAhmed
Esri Regular Contributor
This happens with the default field mapping.


From the graphics I guess your lines are your "target" features, right?

What is your operating system?

Could you please post a screenshot of your default field map - just the wo fields for SHAPE_Length. For example, here is my field map:

[ATTACH=CONFIG]13283[/ATTACH]
0 Kudos