RateLimitExceptionIsDueToRateLimitOnLocationChanges Property

public bool IsDueToRateLimitOnLocationChanges { get; }

Public ReadOnly Property IsDueToRateLimitOnLocationChanges As Boolean
	Get

Property Value

Location-limited accounts are low-end accounts that are used for fetching regular updates from a limited number of locations. The number of locations allowed depends on the location-limited account in question.

Allowed locations are set automatically. If a location-limited account successfully fetches data from a given location, that location is assigned to the account, and the account is able to continue fetching data from that location as time goes on (e.g. fetching daily/weekly/monthly updates).

A certain amount of location turnover is allowed. Offices and people move to new buildings, and occasionally weather stations go down and replacements need to be found (see IsDueToLocationNotSupported for more on this). As new locations are added to an account's list of allowed locations, older locations are removed on a least-recently-used basis. There are limits on the number of "location changes" that a location-limited account can make in any given period of time. These limits aren't explicitly published, and may change over time, but the idea is that it should be very unlikely for a location-limited account to hit its limit on location changes. Location-limited accounts are built for a certain style of usage only (fetching regular updates from a mostly-fixed set of locations).

From a programming perspective, dealing with a rate limit on location changes is unlikely to be any different from dealing with the usual rate limit on the number of API requests. If you have a user-driven application, you might want to call this method to help you decide what message to show in the UI... But, if your program is a background task that fetches data at regular intervals, you probably won't need to distinguish between a limit on API requests (all accounts have these) and a limit on location changes (only location-limited accounts have these). If an account hits a rate limit (whether on requests or location changes), you'll get a RateLimitException e, and you'll generally just want to wait the specified number of minutes until the rate limit is reset (e.ResponseMetadata.RateLimit.MinutesToReset).

Reference