I'm faced with an interesting problem. Under state law, there are a number of addresses state-wide that are restricted from public access; law enforcement officer's residences, judges residences, etc. With address point data and parcel polygon data it's pretty easy to simply <null> out the address field, and if those data are used for geocoding purposes, they won't validate addresses that don't 'exist'.
The problem comes in with a publicly accessible composite geocoding service that utilizes address points, parcels and street centerline data with address ranges. Let's say Judge Smith lives at 150 Penny Ln. No problem with the parcels and address points but when the composite hits the center lines, there he is.
I suppose we could split the segment of Penny Ln that has the range of 100-200, and range the two new segments to exclude 150. (100-148, 101-149 and 151-199, 152-200). I don't like that idea too much.
If you are still with me, here's the question; Is there a way to block an address or a set of addresses from resolving without altering the data being used to match against? So, if on that same publicly accessible composite someone enters 150 S Penny Ln, some sort of message pops up to the effect of 'Sorry, that address does not exist'