4 ms·
What's the terms on your forward geocoding? Many providers have terms that require live lookup of address->latlong, no caching permitted. My client's use case h
by johncalvinyoung 3y ago
What's the terms on your forward geocoding? Many providers have terms that require live lookup of address->latlong, no caching permitted. My client's use case has long-lived addresses that may need to be mapped many times, and currently we're paying for one of the only geocoding services that permits us to persist the coordinates involved.
- nickpatrick 3y agoOur standard policy is that you can cache responses for up to 30 days: https://radar.com/documentation/maps/geocoding#caching https://radar.com/documentation/maps/geocoding#caching
- amluto 3y ago> Licensee shall not … store any address or point of interest data from Radar's geocoding, autocomplete, or place search APIs for more than thirty (30) days; So if an e-commerce site user starts typing their address, it’s autocompleted via Radar, and the user confirms it, then the site must delete the user’s address after 30 days? This seems wrong.
- flir 3y ago*crickets*
- johncalvinyoung 3y agoThanks for the reply. I was reading docs but missed that somehow.
- warpspin 3y ago> and currently we're paying for one of the only geocoding services that permits us to persist the coordinates involved. I'll ask blatantly: Which one is that?
- freyfogle 3y agoHi, we allow you to store geocoding results as long as you like: https://opencagedata.com https://opencagedata.com