Knowledge Base - Technical Articles


Technical Article   Bug:  The Spatial Join tool produces NULL results for some fields/features on ArcGIS 10 SP4

Article ID: 40174
Bug Id: NIM079126
Software:  ArcGIS - ArcEditor 10 ArcGIS - ArcInfo 10 ArcGIS - ArcView 10
Platforms:  Windows XP, Server 2003, Vista, Server 2008, Windows 7

Description

The Spatial Join tool does not populate fields in the output feature class correctly when some target features have no matching join features.

 This issue has been fixed with the release of the ArcGIS 10.0 SP4 Spatial Join Tool Patch.


Cause


 The problem is found in 10.0 SP4 but not in SP3 or earlier patch levels.

A Spatial Join is used to append fields from a 'Join' feature class to a 'Target' feature class, where the association is defined by a spatial relationship (intersects, contains, within, closest, etc.), rather than attribute matching. If every target feature is matched with at least one join feature, the fields in the output table are populated correctly.

However, if a target feature is not matched with any join feature, the fields in the output feature class attribute table are empty (or zero) in most cases, even for target features that were successfully matched with a join feature. Not only are the fields appended by the join empty, but also the fields of the target feature class in the output table are empty.

This issue is resolved in SP5 for 10.0. A patch is planned to be released around the end of April/early May 2012 that resolves this defect.

Workaround

A model tool is provided that works around the issue in most scenarios: Toolbox with model tool

The the model tool functions as follows:

1. The tool Selects by Location all target features that have the desired spatial relationship with records in the join features.

2. The tool performs a Spatial Join only on the selected features, joining with the join features, which allows the joined fields to be populated correctly for the selected target features.

3. The selection on the target features is then 'switched' (inverted) so that only the non-matching target records are selected. Those target records are appended to the output of the Spatial Join, to get all the non-matching features into the output. The selection on the target feature class is then cleared.



Related Information


Created: 4/18/2012
Last Modified: 6/26/2012

Article Rating: (3)

Comments

By geoid23 - 05/10/2012 3:30 PM

The article needs to be updated.

It should be noted that the only Match Option for the fix is Intersect so the full tool functionality is not really there.

Rating:

By rich6626 - 05/01/2012 10:14 AM

Other - See details below.

This issue has been fixed as of May 1, 2012 with the release of the ArcGIS 10.0 SP4 Spatial Join Tool Patch found at this url: http://resources.arcgis.com/content/patches-and-service-packs?fa=viewPatch&PID=160&MetaID=1857

By euibel - 05/01/2012 5:38 AM

The article needs to be updated.

Maybe worth mentioning: the Spatial join option whithin "joins and relates" (right-clicking on the target layer) populates the output feature class correctly! Problems occur only when using the tool from the toolbox.

Rating:

By sacdou - 04/30/2012 10:02 AM

Other - See details below.

@jrv27: FAQ: Can an Esri service pack be uninstalled for Esri ArcGIS products version 10.x? http://support.esri.com/en/knowledgebase/techarticles/detail/38511

By rich6626 - 04/27/2012 11:10 AM

Other - See details below.

We (Esri) are actively working on a patch for this issue that should be available in the next week or so. Please watch this KB article, it will be updated once the patch is available. Alternatively, you may set up an RSS feed from our Patches and Sevice Packs page (http://resources.arcgis.com/content/patches-and-service-packs); this method provides notification when any new service pack or patch is available.

By jrv27 - 04/25/2012 10:57 AM

I would like to see a new article that discusses the topic outlined below.

How can a previous version of a service pack be installed?

Rating:

By stuskier - 04/25/2012 9:19 AM

I would like to see a new article that discusses the topic outlined below.

Why doesn't ESRI just fix the damn SP4 spatial join problem NOW, instead of unloading the "fix" on the user? Typical ESRI arrogance...