Hi,
I'm having a problem when reverse geocoding intersections, with an custom address locator based on dual range data. The result is only correct for points very near to intersections. Raising the search distance doesn't help.
The odd thing is that points further from an intersection adopt the address data and location of the last found intersection. So if one point gets the correct data (because it is close to an intersection) the next one (not close to an intersection) gets the same data, and so on until again a point is close to an intersection.
I did install the service pack 1 for ArcGIS 10. So reverse geocoding addresses based on projected data works. Also the address inspector, which actually does the same as reverse geocoding, does also work.
Anyone an idea? Is this another bug?
Thanks,
Thibaut
