In our download data tab in Digimap, we limit the amount of some map data products that can be downloaded in each request. The limit may be for a set number of National Grid tiles or for an area, e.g. 100km2. The limits vary between map data products.
There is no limit to the number of individual requests for data that a user may submit.
EDINA will contact any user who makes an unusually large number of requests for data to establish: whether the data are to be used for purposes permitted under the terms of the licence; whether there is an alternative, easier route for obtaining data.
Limits are in place to reduce the size of the data file that needs to be downloaded and to manage the processing load on our servers. Limits help us process your data requests faster and ensure that all orders are processed within a reasonable timeframe.
We recognise that larger areas of data may be required for specific projects than cannot be downloaded with a reasonable number of requests. We reserve the right to charge for bulk download requests that are complex or time consuming to manage offline. If you need a very large area or volume of data, please contact our Helpdesk. with an indication of which data product you need and an approximate area. If you can download the data you need in less than 10 requests we will not consider an offline bulk download. Note that sometimes you can download the area you need by selecting an area slightly within the tile boundaries for the product you need, rather than selecting by tile name.
Contact us and we can try to:
Identify other sources of the same data.
Suggest alternative data.
Suggest different ways to request the data through the download data tab such as use of national grid tile names and reference grid overlays.
We use cookies for security purposes, remembering your preferences and to analyse site traffic in order
to improve your experience using the service. This includes anonymised Google Analytics data.
We won't share your data with anyone else.
For more information please see our
Cookie Policy page.