The only limitation I'm familiar with is reverse geocoding of coordinates via CLGeocoder , which says:
Geocoding requests are limited in speed for each application, so running too many requests in a short amount of time may cause some requests to fail. When the maximum speed is exceeded, the geocoder passes an error object with the value kCLErrorNetwork your completion handler.
Unfortunately, I have never seen this limitation quantified.
Personally, I always assumed that this was a warning that people should not write code that tried to abuse the API, using it to programmatically develop a geocoding database by re-geocoding each point in the grid or whatever you have. I have never encountered this limitation in the standard interaction with the map.
source share