The LINZ Data Service rate limits its web services to avoid overuse and abuse. Find out how they work.
The LINZ Data Service API allows you to make a limited number of requests within a given timeframe. ‘Reasonable use’ rate limiting has been implemented for LINZ Data Service web services to guarantee API performance for all LDS customers and to guard against overuse or abuse of our services.
Our services are designed for use in internal GIS applications or small to medium volume web mapping applications. For large volume or high profile public mapping services, you may wish to establish your own tile server or use a corporate service.
Rate liming applies to:
- all APIs methods (including OGC web services, tile APIs and vector query APIs) except for Catalogue methods
- all API clients, at the API key and IP address level
As with all LDS web services, API requests do not require separate authentication as your API key identifies you as a registered LDS customer.
Hourly and per minutes limits
Our rate limits are enforced on a per-minute and per-hour basis, so you may have to wait up to an hour for your limit to be released.
API usage is being monitored. This information will help us understand usage and track any persistent breaking of the limits.
Abuse or persistent overuse of our APIs
Frequently Asked Questions
How can I avoid hitting the request cap?
A key technique is to cache data where possible. If you are developing an application, we recommend that you cache data client-side and that you avoid requesting tiles that have not changed. By default, most GIS or web map tile clients should do this for you already.
How can I tell if I’m being rate limited?
If you exceed the request cap in a web mapping client your request will be rejected and you will see a HTTP 429 "Too Many Requests” response code.
It is unlikely that an individual GIS user will experience rate limiting. If you do, you may receive an error message or your request may not return any data.
There seems to be variance in the request caps for WMTS. Is this the case?
No, not strictly. However, requests for tiles cached on the CDN are not counted against the rate limit. This means reaching a cap will be influenced by whether the tiles you are requesting tiles at any one time are already on the tile cache.