Radar Maps Platform
radar.com
radar.com
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.
Odd
At an early stage, it's often easier and more lucrative to build for and support a few large customers than many small ones.
Why did they name themselves "Radar"?
Short, easy-to-spell name that suggests location. It's worked out pretty well for us, and we got the dot com!
Not really.
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.
I'll ask blatantly: Which one is that?
Thanks for this great Project!
I sometimes find myself caring about if the basemaps look good and fit my use case more than the API cost.
I have a pihole on my network and the "stock" block list contains api.radar.io
The list https://raw.githubusercontent.com/StevenBlack/hosts/master/h...
The list is for people who don't want to be tracked by third parties. That's who we serve, and that's why we do what we do.
Based on this...
... note the "tracked users" feature, unless I'm missing something, this isn't going to change.
The commit's comment is "major update from adaway.org"
> Best-in-class accuracy down to 5 meters
> Open-source SDKs with smart presets and customizable tracking options to maximize battery efficiency, responsiveness, and accuracy.
> Add geofencing to your apps with confidence. Visualize and debug every location update and geofence event with Radar’s dashboard.
Looks like this is used to follow the location history of app/website users on a map in the backend.
I haven't dug into it much further, but if their API is used for tracking, it should stay on the list.
Edit: looks like they provide a dashboard to follow the location history of any user using their API. Yeah, no, I'm adding this to my personal blacklist just in case.
This trend of “our branding takes priority over the required attribution for the free map data we’re using, but hey, they’re a little nonprofit so can’t afford to sue us” really ticks me off. Mapbox started it as a calculated move, and since then others have followed claiming it’s “the standard”.
But in this case I’ll assume good faith for now and hope it’s fixed. A simple “© OSM” would be fine.
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.
The other options I considered were Mapbox and MapTiler, since it seems that actually self-hosting everything yourself is a bit demanding on hardware resources. I mean, I love that you can get the OSM dataset into PostGIS pretty easily, but getting the vector data or raster tiles to the client can take a bit of CPU power and bunches of storage! I wonder whether I missed any other good cloud services, or a self-hosted stack that would make things easier.
That said, I wonder why so many seem to be moving away from raster tiles to vector data. I guess you can cache both and vector data is actually less storage intensive, but at the same time pretty much every vector map implementation lags badly on my phone and sometimes even a bit on my netbook (Radar still lags for me, although less than Mapbox, probably because Mapbox does the whole fancy 3D globe thing with fog and stuff).
Either way, major props for making this exist and pricing it so competitively! Would be cool to also fix the attribution text that's on the lower right on desktop but doesn't show up on mobile, at least for me.
(note, that I'm not affiliated with them, but they use some source code from us for the efficient import and also contributed to GraphHopper, but this did not influence my experience ;) )
> I wonder why so many seem to be moving away from raster tiles to vector data.
The flexibility of styling. And you can easily serve customers that need different default languages. This makes maps also more accessible for countries without Latin alphabet. Also when you rotate the map (like for GPS navigation) the labels can rotate too if necessary.
Maps: $0.50/1K map loads. Geocoding: $0.50/1K API calls
Halfway down the page under "Cut your maps bills in half" heading.