41–50 of 81 posts
Earlier quoted context omitted.
More details in the post, but Google starts at $7 per 1K map loads and $5 per 1K geocoding API requests, whereas Radar starts at $0.50 per 1K for both. We've roughly been helping our enterprise customers cut their maps bill in half.
How can you afford to be 10x cheaper? Google being overkill?
Earlier quoted context omitted.
More details in the post, but Google starts at $7 per 1K map loads and $5 per 1K geocoding API requests, whereas Radar starts at $0.50 per 1K for both. We've roughly been helping our enterprise customers cut their maps bill in half.
How can you afford to be 10x cheaper? Google being overkill?
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.
Radar CEO here. Welcome any questions or feedback!
Then, when zooming in, you have to zoom very very far in before street names show up. This makes a map zoomed slightly less far in mostly useless, because you can’t tell where you are. I realize that people mostly don’t navigate by map any more, but if you are literally selling map tiles, presumably mostly not tied to the end user’s GPS, then whoever is looking at the map would like to know where they’re looking. For example, in Manhattan, the actual useful coordinates are the cross-streets, and the map is not very helpful without the street names.
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.
Our standard policy is that you can cache responses for up to 30 days: https://radar.com/documentation/maps/geocoding#caching
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.
You had me until this pricing page: https://radar.com/pricing?type=consumer I'm interested in the address autocompletion in particular, but you guys don't want to tell me how much it's actually going to cost apparently. I also have no idea what a "monthly tracked user" is or how it's relevant. LMK when you drop the "Contact Sales" aspect.
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.
Our standard policy is that you can cache responses for up to 30 days: https://radar.com/documentation/maps/geocoding#caching
But not actual RADAR maps, with weather and aircraft returns.
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.
I'll ask blatantly: Which one is that?