Crystal: ...I found that if I click on the QOA poly [source],
then turn off that layer in the TOC, it will then activate the
tool if I click on the NQOA poly [destination] underneath . I was
only able to recreate this with your data as coverages. When
converted to shapefile, you don't have to work through the steps
of turning the source layer off in the display to click on the
shape beneath it.
It was mentioned at this year's User Conference in July that with
the release of 8.3 you will not be able to edit coverages using
ArcMap. http://gis.esri.com/uc2002/qa/index.cfm (ArcGIS, Question
#10). You will still be able to edit coverages using Workstation
ArcEdit -- but ArcMap will be the editing environment for
shapefiles and geodatabases.
The process that you are performing is often refered to as
conflation -- or attribute conflation.
I've never had to do that in the past, but I did a search and
found this link for some automated tools to perform conflation on
coverages using Workstation ArcInfo:
I've never used these tools, so I cannot make any claims to their
One thing I was thinking is that you could do some tricks.
If the centroids of the "QOA" polys still fall into the exact
polygon (and only ONE polygon) that they match, then you could
probably do some type of overlay processes to pass point
(original poly label points) to polygon attributes for the
destination feature class.
One process that might work is to do a spatial join in ArcMap.
Add the label point feature class from the QOA coverage. Then
add the polygon feature class from the NQOA coverage.
Right click the NQOA polygon layer in the TOC ->Join -> change
the top drop down option to 'Join data based on spatial location'
Choose the option to join the attributes of the label point QOA
layer to the polygons of the NQOA layer (the second option).
This creates a new layer (which would be a shapefile or
I think a similar process could be accomplished keeping them as
coverages, but I can't remember (it's been so long!) how to do
point in polygon attribute transfer directly using Workstation
commands or Toolbox tools. I don't think Identity will cut the
mustard because it will output a point coverage, which is what
you don't want. Here's an AML sample on the ArcScripts site that
does pass point attributes to polygons in coverages
Obviously, if your input polygons (using the label points) don't
line up exactly so that their label points fall in the other
coverages associated polygons, this might not work. It was just
a thought. You could always edit the label points if you have a
few poly label points that fall into the incorrect destination
polygon, but that would require manual updates.