AnsweredAssumed Answered

Reverse Geocoding: locationToAddress missing forStorage parameter

Question asked by SparkyT19 on Apr 3, 2018
Latest reply on Oct 22, 2018 by bforbhavin



We're implementing geocoding and reverse-geocoding using the Locator class in version 3.23 of the API.  The addressToLocations method allows specifying a forStorage value in order to persist the results of the operation when using the World Geocoding service, but I can't find any way to do the same with the locationToAddress method.


Is there some other way to indicate that the results of the reverse geocode operation are for storage and should consume the required credits?  Can we use the Locator class for this, or do we need to use the reverseGeocode method of the REST service directly?