Is there a way to store our reference data as state plane, but allow the geocoding service to accept lat/longs for reverse geocoding calls?
I have all my reference data in state plane, but a vendor who will use our geocoding service needs to enter lat/longs. Our reverse geocoding on the locator only works if you enter state plane coordinates.
Solved! Go to Solution.
According to the on line help, it shouldn't be a problem:
If the spatial reference of the input feature class is different from that of the locator, the locator will transform the coordinates on the fly and try to find the match. The output feature class will be saved in the same spatial reference as the input feature class....
Emphasis on shouldn't be a problem.
According to the on line help, it shouldn't be a problem:
If the spatial reference of the input feature class is different from that of the locator, the locator will transform the coordinates on the fly and try to find the match. The output feature class will be saved in the same spatial reference as the input feature class....
Emphasis on shouldn't be a problem.
Thanks Joe!