Original question:
Hi List,

I have been working on geocoding our streets for the whole city and
everything is turning out really well. The one exception is some new
sub-divisions of single family homes all with the same address, but
different unit numbers.  Does anyone have a work-around so that all 90 homes
is this sub-division are not represented by a single address?  It is much
the same problem with apartments, but at least there is a dot that
represents each building, where in this case, there is a separate building
for each unit.  Any suggestions would be appreciated (using ArcView 3.2, 8.1
or ArcInfo).

Sum:
Seems more people had the same question then an answer.  I did get one reply
from Scott Kutz that gave me the direction of how to tackle this problem
(THANKS!).  As far as I can tell, there is no easy solution, and quite a bit
of data manipulation to get this working long-term.  The procedure that I
used was to create an alias table ("Working with place name aliases", in
ArcView help.)  ArcView first looks at the alias table and translates the
incoming address to its alias value (another street address) prior to
actually attempting the geocode.
The table has two columns, Alias, and address.  For me, the table looked
something like:
Alias (actual address)      Address  (this is the new address)
10700 Kimblewyck Cir 101    110 Kimblewyck Cir
10700 Kimblewyck Cir 102    120 Kimblewyck Cir
      .                                                        .
      .                                                        .

In our case, I had to renumber the whole subdivision because odd and even
ran on both sides.  I did this somewhat arbitrarily, but renumbered by 10's,
odd on one side and even on the other (this part I did just on a piece of
paper that had all the houses on it).  Then, I went back into the streets
coverage, and renumbered, the from/to addresses to fit my new numbering
system.  Finally, when setting up the "geocode addresses..." function, I
selected the alias table I had created, and ArcView then runs through the
alias as a lookup before it geocodes.  Although there is a lot of work
up-front, it should solve the problem for all future geocode runs.  The only
real problem now, is that this will unlikely work in ArcExplorer for our
users in the office that are not running ArcView.

Good thing our city is landlocked so we don't have much left to deal with on
all the planners new "communities", that are generally GIS IN-compatible.

If anyone has any questions on these procedures, feel free to drop me a
line.

Jill

Jill Wolf
GIS Technician
City of Northglenn
11701 Community Center Dr.
Northglenn, CO 80501
ph. 303-450-8989
fax  303-450-8708