[UW-GIS-L] Geocoding - dealing w/ tight clusters & confidentiality

Walker Willingham walkerw at u.washington.edu
Mon Jul 10 12:46:23 PDT 2006


I have a new geocoding project in which numbers are more important 
than exact locations.  In fact it might be better if locations were 
NOT TOO reliable as a means of protecting confidentiality.

I will describe the ideal result I'm looking for & if any of you have 
ideas that might get me close, or know someone who might be able to 
make a suggestion, I'll be thankful.

I'm making maps in residential areas, and want to visually indicate 
numbers of children in each block meeting certain criteria.  The 
number per block is important, even if there are multiples per 
address, but the location within the block - or even the side of the 
street is not important.

Ideally I would like a dot per child in a regular cluster centered 
about the mid-block, or just an integer indicating that number for 
the block.  (I believe the scale of my map will be large enough to 
accommodate my dots.)

Something like:

____* *___/_________/__*******__/____***___/_____*_____/
or

____2____/_________/____7____/_____3___/_____1_____/

or alternately the dots could go to both sides of the streets, either 
based on the side that people actually live on, or simply to be able 
to cluster more dots near the middle.

I don't mind if there is a multi-step process to solve this, perhaps 
creating a new feature class after geocoding which calculates results 
to account for the problem that geocoding multiple points too close 
together stacks points as indistinguishable.  If any of the steps 
require either an ArcEditor or full ArcInfo license, I would like to 
know that, since ArcView 9.1 is what I have handy.  Perhaps there is 
a script someone can suggest that would help.

The project is large enough with a fairly large data set that I do 
want to avoid a process which requires a per geocoded location 
tweaking in an application downstream from ArcGIS - that is I really 
want to automate some symbology that will work for this.

Thanks in advance,

Walker 



More information about the Uw-gis-l mailing list