for users, publishers and sysadmins



INSPIRE places legal obligations on public bodies to publish particular datasets.

Public bodies means:

Relevant datasets are those which meet all these criteria:

For more about INSPIRE’s scope, see UK Location Getting Started - Guide 2 - Organisation and Data Coverage (PDF).


Dataset INSPIRE? Location? Explanation
River catchment area boundaries Yes Yes Its publisher Environment Agency is a government agency, the data falls under the INSPIRE theme “Hydrography”, and the data is geo-spatial - it can be plotted on a map.
Road accidents No Yes The subject of the data is not covered in the 34 INSPIRE themes so it is not covered by INSPIRE. However the data is Location data - each accident is located using a OS grid reference (and latitude & longitude) so it is geo-spatial. So the publisher could have still published the metadata in GEMINI and provided INSPIRE-style View (WMS) and Download Services (WFS/Atom), but has chosen not to in this case, sticking to basic CSV.

Local authorities should make use of the detailed guidance from the Local Government Association which lists datasets likely to be held by LAs covered by INSPIRE: A Guide to INSPIRE compliance in local government

Publishing INSPIRE/Location data

The INSPIRE legislation requires most geo-spatial data to be published according to certain standards, and be registered on in a certain way. The records must be published in GEMINI format and be harvested. Common ways to do this are:

Harvesting metadata records

Getting your metadata records into is done by setting up a ‘harvester’. It’s recommended that this is configured to run automatically weekly, to ensure that stays in sync when the publisher updates the records.

For a complete guide to harvesting, consult: Harvesting Data into

Occasionally publishers have made the mistake of using an existing record as a template and simply using a text editor to change the key fields. The main problem with this is that you need to generate a new gmd:fileIdentifier, or will harvest it and overwrite the record that was the template! To generate a new UUID (universally unique identifier) for this field, just visit