{
  "url": "https://openlegislation.uk/eu-regulation-2013-1253/annex-II",
  "json_url": "https://openlegislation.uk/eu-regulation-2013-1253/annex-II.json",
  "legislation": "eur/2013/1253",
  "legislation_title": "Commission Regulation (EU) No 1253/2013 of 21 October 2013 amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC as regards interoperability of spatial data sets and services",
  "legislation_url": "https://openlegislation.uk/eu-regulation-2013-1253",
  "path": "annex/II",
  "kind": "annex",
  "number": "II",
  "heading": null,
  "text": "Annex II to Regulation (EU) No 1089/2010 is amended as follows:\n(1) Throughout the text, the sentence ‘This code list shall not be extended by Member States.’ is replaced by the sentence ‘The allowed values for this code list comprise only the values in the table below.’.\n(2) Throughout the text, in the headings of all tables that are specifying code list values, the text ‘Allowed values for the code list’ is replaced by the text ‘Values for the code list’.\n(3) In Section 1.1, the following indents are added:\n‘“mean sea level” (MSL) means the average height of the surface of the sea at a tide station for all stages of the tide over a 19-year period, usually determined from hourly height readings measured from a fixed predetermined reference level (chart datum).\n“lowest astronomical tide” (LAT) means the lowest tide level which can be predicted to occur under average meteorological conditions and under any combination of astronomical conditions.’\n(4) Section 1.3.3 is amended as follows:\n(a) the second indent is replaced by the following:\n‘For the vertical component in the free atmosphere, barometric pressure, converted to height using ISO 2533:1975 International Standard Atmosphere, or other linear or parametric reference systems shall be used. Where other parametric reference systems are used, these shall be described in an accessible reference using EN ISO 19111-2:2012.’\n(b) the following indents are added:\n‘For the vertical component in marine areas where there is an appreciable tidal range (tidal waters), the Lowest Astronomical Tide (LAT) shall be used as the reference surface.\nFor the vertical component in marine areas without an appreciable tidal range, in open oceans and effectively in waters that are deeper than 200 meters, the Mean Sea Level (MSL) or a well-defined reference level close to the MSL shall be used as the reference surface.’.\n(5) Section 2.2 is amended as follows:\n(a) The first paragraph is replaced by the following:\n‘Either of the grids with fixed and unambiguously defined locations defined in Sections 2.2.1 and 2.2.2 shall be used as a geo-referencing framework to make gridded data available in INSPIRE, unless one of the following conditions holds:\n(1) Other grids may be specified for specific spatial data themes in Annexes II-IV. In this case, data exchanged using such a theme-specific grid shall use standards in which the grid definition is either included with the data, or linked by reference.\n(2) For grid referencing in regions outside of continental Europe Member States may define their own grid based on a geodetic coordinate reference system compliant with ITRS and a Lambert Azimuthal Equal Area projection, following the same principles as laid down for the grid specified in Section 2.2.1. In this case, an identifier for the coordinate reference system shall be created.’\n(b) Section 2.2.1 is amended as follows:\n(1) the title is replaced by ‘Equal Area Grid’.\n(2) the sentences ‘The grid defined in this Section shall be used as a geo-referencing framework where grids with fixed and unambiguously defined locations of equal-area grid cells are required.’ and ‘The reference point of a grid cell shall be the lower left corner of the grid cell. ’ are deleted.\n(c) Section 2.2.2 is replaced by the following:\n‘2.2.2.\nZoned Geographic Grid\n1.\nWhen gridded data is delivered using geodetic coordinates as specified in Section 1.3 of this Annex the multi-resolution grid defined in this Section may be used as a geo-referencing framework.\n2.\nThe resolution levels are defined in Table 1.\n3.\nThe grid shall be based on the ETRS89-GRS80 geodetic coordinate reference system.\n4.\nThe origin of the grid shall coincide with the intersection point of the Equator with the Greenwich Meridian (GRS80 latitude φ=0; GRS80 longitude λ=0).\n5.\nThe grid orientation shall be south-north and west-east according to the net defined by the meridians and parallels of the GRS80 ellipsoid.\n6.\nFor grid referencing in regions outside of continental Europe data providers may define their own grid based on a geodetic coordinate reference system compliant with ITRS, following the same principles as laid down for the Pan-European Grid_ETRS89-GRS80zn. In this case, an identifier for the coordinate reference system and the corresponding identifier for the grid shall be created.\n7.\nThis grid shall be subdivided in zones. The south-north resolution of the grid shall have equal angular spacing. The west-east resolution of the grid shall be established as the product of angular spacing multiplied by the factor of the zone as defined in Table 1.\n8.\nThe grid shall be designated Grid_ETRS89-GRS80zn_res, where n represents the number of the zone and res the cell size in angular units, as specified in Table 1.\nTable 1\nCommon Grid_ETRS89-GRS80: Latitude spacing (resolution level) and longitude spacing for each zone\nResolution Levels\nLATITUDE SPACING(Arc seconds)\nLONGITUDE SPACING (Arc seconds)\nCell size\nZone 1(Lat. 0°–50°)\nZone 2(Lat. 50°–70°)\nZone 3(Lat. 70°–75°)\nZone 4(Lat. 75°–80°)\nZone 5(Lat. 80°–90°)\nLEVEL 0\n3 600\n3 600\n7 200\n10 800\n14 400\n21 600\n1 D\nLEVEL 1\n3 000\n3 000\n6 000\n9 000\n12 000\n18 000\n50 M\nLEVEL 2\n1 800\n1 800\n3 600\n5 400\n7 200\n10 800\n30 M\nLEVEL 3\n1 200\n1 200\n2 400\n3 600\n4 800\n7 200\n20 M\nLEVEL 4\n600\n600\n1 200\n1 800\n2 400\n3 600\n10 M\nLEVEL 5\n300\n300\n600\n900\n1 200\n1 800\n5 M\nLEVEL 6\n120\n120\n240\n360\n480\n720\n2 M\nLEVEL 7\n60\n60\n120\n180\n240\n360\n1 M\nLEVEL 8\n30\n30\n60\n90\n120\n180\n30 S\nLEVEL 9\n15\n15\n30\n45\n60\n90\n15 S\nLEVEL 10\n5\n5\n10\n15\n20\n30\n5 S\nLEVEL 11\n3\n3\n6\n9\n12\n18\n3 S\nLEVEL 12\n1,5\n1,5\n3\n4,5\n6\n9\n1 500 MS\nLEVEL 13\n1\n1\n2\n3\n4\n6\n1 000 MS\nLEVEL 14\n0,75\n0,75\n1,5\n2,25\n3\n4,5\n750 MS\nLEVEL 15\n0,5\n0,5\n1\n1,5\n2\n3\n500 MS\nLEVEL 16\n0,3\n0,3\n0,6\n0,9\n1,2\n1,8\n300 MS\nLEVEL 17\n0,15\n0,15\n0,3\n0,45\n0,6\n0,9\n150 MS\nLEVEL 18\n0,1\n0,1\n0,2\n0,3\n0,4\n0,6\n100 MS\nLEVEL 19\n0,075\n0,075\n0,15\n0,225\n0,3\n0,45\n75 MS\nLEVEL 20\n0,03\n0,03\n0,06\n0,09\n0,12\n0,18\n30 MS\nLEVEL 21\n0,015\n0,015\n0,03\n0,045\n0,06\n0,09\n15 MS\nLEVEL 22\n0,01\n0,01\n0,02\n0,03\n0,04\n0,06\n10 MS\nLEVEL 23\n0,0075\n0,0075\n0,015\n0,0225\n0,03\n0,045\n7 500 MMS\nLEVEL 24\n0,003\n0,003\n0,006\n0,009\n0,012\n0,018\n3 000 MMS\nFACTOR\n—\n1\n2\n3\n4\n6\n—\n’\n(6) Section 4 is replaced by the following:\n‘4.\nADMINISTRATIVE UNITS\n4.1.\nStructure of the Spatial Data Theme Administrative Units\nThe types specified for the spatial data theme Administrative Units are structured in the following packages:\nAdministrative Units\nMaritime Units\n4.2.\nAdministrative Units\n4.2.1.\nSpatial object types\nThe package Administrative Units contains the following spatial object types:\nAdministrative Boundary\nAdministrative Unit\nCondominium\n4.2.1.1.\nAdministrative Boundary (AdministrativeBoundary)\nA line of demarcation between administrative units.\nAttributes of the spatial object type AdministrativeBoundary\nAttribute\nDefinition\nType\nVoidability\nbeginLifespanVersion\nDate and time at which this version of the spatial object was inserted or changed in the spatial data set.\nDateTime\nvoidable\ncountry\nTwo-character country code according to the Interinstitutional style guide published by the Publications Office of the European Union.\nCountryCode\nendLifespanVersion\nDate and time at which this version of the spatial object was superseded or retired in the spatial data set.\nDateTime\nvoidable\ngeometry\nGeometric representation of border line.\nGM_Curve\ninspireId\nExternal object identifier of the spatial object.\nIdentifier\nlegalStatus\nLegal status of this administrative boundary.\nLegalStatusValue\nvoidable\nnationalLevel\nThe hierarchy levels of all adjacent administrative units this boundary is part of.\nAdministrativeHierarchyLevel\ntechnicalStatus\nThe technical status of the administrative boundary.\nTechnicalStatusValue\nvoidable\nAssociation roles of the spatial object type AdministrativeBoundary\nAssociation role\nDefinition\nType\nVoidability\nadmUnit\nThe administrative units separated by this administrative boundary.\nAdministrativeUnit\nvoidable\n4.2.1.2.\nAdministrative Unit (AdministrativeUnit)\nUnit of administration where a Member State has and/or exercises jurisdictional rights, for local, regional and national governance.\nAttributes of the spatial object type AdministrativeUnit\nAttribute\nDefinition\nType\nVoidability\nbeginLifespanVersion\nDate and time at which this version of the spatial object was inserted or changed in the spatial data set.\nDateTime\nvoidable\ncountry\nTwo-character country code according to the Interinstitutional style guide published by the Publications Office of the European Union.\nCountryCode\nendLifespanVersion\nDate and time at which this version of the spatial object was superseded or retired in the spatial data set.\nDateTime\nvoidable\ngeometry\nGeometric representation of spatial area covered by this administrative unit.\nGM_MultiSurface\ninspireId\nExternal object identifier of the spatial object.\nIdentifier\nname\nOfficial national geographical name of the administrative unit, given in several languages where required.\nGeographicalName\nnationalCode\nThematic identifier corresponding to the national administrative codes defined in each country.\nCharacterString\nnationalLevel\nLevel in the national administrative hierarchy, at which the administrative unit is established.\nAdministrativeHierarchyLevel\nnationalLevelName\nName of the level in the national administrative hierarchy, at which the administrative unit is established.\nLocalisedCharacterString\nvoidable\nresidenceOfAuthority\nCenter for national or local administration.\nResidenceOfAuthority\nvoidable\nAssociation roles of the spatial object type AdministrativeUnit\nAssociation role\nDefinition\nType\nVoidability\nadministeredBy\nAdministrative unit established at same level of national administrative hierarchy that administers this administrative unit.\nAdministrativeUnit\nvoidable\nboundary\nThe administrative boundaries between this administrative unit and all the units adjacent to it.\nAdministrativeBoundary\nvoidable\ncoAdminister\nAdministrative unit established at same level of national administrative hierarchy which is co-administered by this administrative unit.\nAdministrativeUnit\nvoidable\ncondominium\nCondominium administered by this administrative unit.\nCondominium\nvoidable\nlowerLevelUnit\nUnits established at a lower level of the national administrative hierarchy which are administered by the administrative unit.\nAdministrativeUnit\nvoidable\nupperLevelUnit\nUnit established at a higher level of national administrative hierarchy that this administrative unit administers\nAdministrativeUnit\nvoidable\nConstraints of the spatial object type AdministrativeUnit\nAssociation role condominium applies only for administrative units which nationalLevel=“1st order” (country level).\nNo unit at lowest level can associate units at lower level.\nNo unit at highest level can associate units at a higher level.\n4.2.1.3.\nCondominium (Condominium)\nAn administrative area established independently to any national administrative division of territory and administered by two or more countries.\nAttributes of the spatial object type Condominium\nAttribute\nDefinition\nType\nVoidability\nbeginLifespanVersion\nDate and time at which this version of the spatial object was inserted or changed in the spatial data set.\nDateTime\nvoidable\nendLifespanVersion\nDate and time at which this version of the spatial object was superseded or retired in the spatial data set.\nDateTime\nvoidable\ngeometry\nGeometric representation of spatial area covered by this condominium\nGM_MultiSurface\ninspireId\nExternal object identifier of the spatial object.\nIdentifier\nname\nOfficial geographical name of this condominium, given in several languages where required.\nGeographicalName\nvoidable\nAssociation roles of the spatial object type Condominium\nAssociation role\nDefinition\nType\nVoidability\nadmUnit\nThe administrative unit administering the condominium\nAdministrativeUnit\nvoidable\n4.2.2.\nData Types\n4.2.2.1.\nResidence Of Authority (ResidenceOfAuthority)\nData type representing the name and position of a residence of authority.\nAttributes of the data type ResidenceOfAuthority\nAttribute\nDefinition\nType\nVoidability\ngeometry\nPosition of the residence of authority.\nGM_Point\nvoidable\nname\nName of the residence of authority.\nGeographicalName\n4.2.3.\nEnumerations\n4.2.3.1.\nLegal Status (LegalStatusValue)\nDescription of the legal status of administrative boundaries.\nAllowed values for the enumeration LegalStatusValue\nValue\nDefinition\nagreed\nThe edge-matched boundary has been agreed between neighbouring administrative units and is stable now.\nnotAgreed\nThe edge-matched boundary has not yet been agreed between neighbouring administrative units and could be changed.\n4.2.3.2.\nTechnical Status (TechnicalStatusValue)\nDescription of the technical status of administrative boundaries.\nAllowed values for the enumeration TechnicalStatusValue\nValue\nDefinition\nedgeMatched\nThe boundaries of neighbouring administrative units have the same set of coordinates.\nnotEdgeMatched\nThe boundaries of neighbouring administrative units do not have the same set of coordinates.\n4.2.4.\nCode Lists\n4.2.4.1.\nAdministrative Hierarchy Level (AdministrativeHierarchyLevel)\nLevels of administration in the national administrative hierarchy. This code list reflects the level in the hierarchical pyramid of the administrative structures, which is based on geometric aggregation of territories and does not necessarily describe the subordination between the related administrative authorities.\nThis code list shall be managed in a common code list register.\n4.3.\nMaritime Units\n4.3.1.\nSpatial object types\nThe package Maritime Units contains the following spatial object types:\nBaseline\nMaritime Boundary\nMaritime Zone\n4.3.1.1.\nBaseline (Baseline)\nThe line from which the outer limits of the territorial sea and certain other outer limits are measured.\nAttributes of the spatial object type Baseline\nAttribute\nDefinition\nType\nVoidability\ninspireId\nExternal object identifier of the spatial object.\nIdentifier\nbeginLifespanVersion\nDate and time at which this version of the spatial object was inserted or changed in the spatial data set.\nDateTime\nvoidable\nendLifespanVersion\nDate and time at which this version of the spatial object was superseded or retired in the spatial data set.\nDateTime\nvoidable\nAssociation roles of the spatial object type Baseline\nAssociation role\nDefinition\nType\nVoidability\nsegment\nSegment of a baseline.\nBaselineSegment\n4.3.1.2.\nMaritime Boundary (MaritimeBoundary)\nA line depicting the separation of any type of maritime jurisdiction.\nAttributes of the spatial object type MaritimeBoundary\nAttribute\nDefinition\nType\nVoidability\ninspireId\nExternal object identifier of the spatial object.\nIdentifier\ngeometry\nGeometric representation of the maritime boundary.\nGM_Curve\ncountry\nThe country that the maritime zone of this boundary belongs to.\nCountryCode\nlegalStatus\nLegal status of this maritime boundary.\nLegalStatusValue\nvoidable\ntechnicalStatus\nThe technical status of the maritime boundary.\nTechnicalStatusValue\nvoidable\nbeginLifespanVersion\nDate and time at which this version of the spatial object was inserted or changed in the spatial data set.\nDateTime\nvoidable\nendLifespanVersion\nDate and time at which this version of the spatial object was superseded or retired in the spatial data set.\nDateTime\nvoidable\n4.3.1.3.\nMaritime Zone (MaritimeZone)\nA belt of sea defined by international treaties and conventions, where coastal State executes jurisdictional rights.\nAttributes of the spatial object type MaritimeZone\nAttribute\nDefinition\nType\nVoidability\ninspireId\nExternal object identifier of the spatial object.\nIdentifier\ngeometry\nGeometric representation of spatial area covered by this maritime zone.\nGM_MultiSurface\nzoneType\nType of maritime zone.\nMaritimeZoneTypeValue\ncountry\nThe country that this maritime zone belongs to.\nCountryCode\nname\nName(s) of the maritime zone.\nGeographicalName\nvoidable\nbeginLifeSpanVersion\nDate and time at which this version of the spatial object was inserted or changed in the spatial data set.\nDateTime\nvoidable\nendLifepanVersion\nDate and time at which this version of the spatial object was superseded or retired in the spatial data set.\nDateTime\nvoidable\nAssociation roles of the spatial object type MaritimeZone\nAssociation role\nDefinition\nType\nVoidability\nbaseline\nBaseline or baselines used for the delineation of this maritime zone.\nBaseline\nvoidable\nboundary\nThe boundary or boundaries of this maritime zone.\nMaritimeBoundary\nvoidable\n4.3.2.\nData types\n4.3.2.1.\nBaseline Segment (BaselineSegment)\nSegment of the baseline from which the outer limits of the territorial sea and certain other outer limits are measured.\nAttributes of the data type BaselineSegment\nAttribute\nDefinition\nType\nVoidability\ngeometry\nGeometric representation of the baseline segment.\nGM_Curve\nsegmentType\nThe baseline type used for this segment.\nBaselineSegmentTypeValue\n4.3.3.\nCode lists\n4.3.3.1.\nBaseline Segment Type (BaselineSegmentTypeValue)\nThe types of baselines used to measure the breadth of the territorial sea.\nThe allowed values for this code list comprise only the values specified in the table below.\nValues for the code list BaselineSegmentTypeValue\nValue\nName\nDefinition\nnormal\nnormal\nThe normal baseline for measuring the breadth of the territorial sea is the low-water line along the coast as marked on large-scale charts officially recognized by the coastal State.\nstraight\nstraight\nThe baseline for measuring the breadth of the territorial sea is the straight baseline established by joining the appropriate points.\narchipelagic\narchipelagic\nThe baseline for measuring the breadth of the territorial sea is the straight baseline joining the outermost points of the outermost islands and drying reefs of the archipelago.\n4.3.3.2.\nMaritime Zone Type (MaritimeZoneTypeValue)\nType of martime zone.\nThe allowed values for this code list comprise only the values specified in the table below.\nValues for the code list MaritimeZoneTypeValue\nValue\nName\nDefinition\ninternalWaters\nInternal Waters\nThe waters on the landward side of the baselines of the territorial sea of the coastal State.\nterritorialSea\nTerritorial Sea\nA belt of sea of a defined breadth not exceeding 12 nautical miles measured from the baselines determined in accordance to the United Nations Convention of Law on the Sea.\ncontiguousZone\nContiguous Zone\nA zone contiguous to a territorial sea of a coastal State, which may not extend beyond 24 nautical miles from the baselines from which the breadth of the territorial sea is measured.\nexclusiveEconomicZone\nExclusive Economic Zone\nAn area beyond and adjacent to the territorial sea of a coastal State, subject to the specific legal regime under which the rights and jurisdiction of the coastal State and the rights and freedoms of other States are governed by the relevant provisions of the United Nations Convention on Law of the Sea.\ncontinentalShelf\nContinental Shelf\nA maritime zone beyond and adjacent to the a territorial sea of a coastal State whose outer boundary is determined in accordance with Article 76 of the United Nations Convention on the Law of the Sea.\n4.4.\nTheme-specific Requirements\n1.\nEach instance of spatial object type AdministrativeUnit, except for the country level unit representing a Member State and co-administered units, shall refer exactly to one unit at a higher level of administrative hierarchy. This correspondence shall be expressed by the upperLevelUnit association role of AdministrativeUnit spatial object type.\n2.\nEach instance of spatial object type AdministrativeUnit, except for those at the lowest level, shall refer to their respective lower level units. This correspondence shall be expressed by the lowerLevelUnit association role of AdministrativeUnit spatial object type.\n3.\nIf an administrative unit is co-administered by two or more other administrative units the association role administeredBy shall be used. The units co-administering this unit shall apply inverse role coAdminister.\n4.\nAdministrative units at the same level of administrative hierarchy shall not conceptually share common areas.\n5.\nInstances of the spatial object type AdministrativeBoundary shall correspond to the edges in the topological structure of the complete (including all levels) boundary graph.\n6.\nThe spatial extent of a condominium may not be part of the geometry representing the spatial extent of an administrative unit.\n7.\nCondominiums can only be administered by administrative units at country level.\n4.5.\nLayers\nLayers for the spatial data theme Administrative Units\nOne layer shall be made available for each code list value, in accordance with Art. 14(3).\nLayer Name\nLayer Title\nSpatial object type\nAU.AdministrativeUnit\nAdministrative unit\nAdministrativeUnit\nAU.AdministrativeBoundary\nAdministrative boundary\nAdministrativeBoundary\nAU.Condominium\nCondominium\nCondominium\nAU.Baseline\nBaseline\nBaseline\nAU.<CodeListValue>\nExample: AU.ContiguousZone\n<human readable name>\nExample: Contiguous Zone\nMaritimeZone (zoneType: MaritimeZoneTypeValue)\nAU.MaritimeBoundary\nMaritime boundary\nMaritimeBoundary\n’\n(7) Section 8 is amended as follows:\n(a) In Section 8.2, the indent ‘Hydro – Reporting’ is deleted.\n(b) In Section 8.5.1, the following indents are deleted:\nHydro Power Plant\nInundated Land\nOcean Region\nPipe\nPumping Station\n(c) In Section 8.5.1.4, the sentence ‘This type is a candidate type to be considered by the spatial data theme Natural risk zones in Annex III to Directive 2007/2/EC.’ is deleted.\n(d) Sections 8.5.1.9 Hydro Power Plant (HydroPowerPlant), 8.5.1.10 Inundated Land (InundatedLand), 8.5.1.14 Ocean Region (OceanRegion), 8.5.1.15 Pipe (Pipe), 8.5.1.16 Pumping Station (PumpingStation), 8.5.4.3 Inundation (InundationValue) and 8.6 Hydro – Reporting are deleted.\n(e) Section 8.5.1.19 is amended as follows:\nThe sentence ‘This type is a candidate type to be considered by the spatial data theme Land cover in Annex II to Directive 2007/2/EC.’ is deleted.\nThe row for the attribute ‘geometry’ in the attribute table is replaced by the following row:\ngeometry\nThe geometry of the shore.\nGM_MultiSurface\n(f) In Section 8.5.1.24, the following constraint is added after ‘Constraints of the spatial object type Watercourse’:\n‘The shores on either side of a watercourse shall be provided (using the bank property) as two separate Shore objects.’\n(g) In Section 8.5.1.25, the sentence ‘This type is a candidate type to be considered by the spatial data theme Land cover in Annex II to Directive 2007/2/EC.’ is deleted.\n(h) In Section 8.5.4.4, the sentence ‘This type is a candidate type to be considered by the spatial data theme Land cover in Annex II to Directive 2007/2/EC.’ is deleted.\n(i) In Section 8.8, the table is replaced by the following table:\n‘\nLayer Type\nLayer Title\nSpatial object type(s)\nHY.Network\nHydrographic Network\nHydroNode, WatercourseLink\nHY.PhysicalWaters.Waterbodies\nWaterbodies\nWatercourse, StandingWater\nHY.PhysicalWaters.LandWaterBoundary\nLand-Water Boundaries\nLandWaterBoundary\nHY.PhysicalWaters.Catchments\nCatchments\nDrainageBasin, RiverBasin\nHY.PhysicalWaters.HydroPointOfInterest\nHydro Points of Interest\nRapids, Falls\nHY.PhysicalWaters.ManMadeObject\nMan-made Objects\nCrossing, DamOrWeir, Embankment, Lock, Ford, ShorelineConstruction, Sluice\nHY. PhysicalWaters.Wetland\nWetlands\nWetland\nHY. PhysicalWaters.Shore\nShores\nShore\n’",
  "extent": "E+W+S+N.I.",
  "status": null,
  "version": "current",
  "annotations": [
    {
      "type": "footnote",
      "label": "f1",
      "text": "One layer shall be made available for each code list value, in accordance with Art. 14(3)."
    }
  ],
  "outstanding_effects": [],
  "provenance": {
    "source": "legislation.gov.uk",
    "source_url": "https://www.legislation.gov.uk/eur/2013/1253/annex/II",
    "retrieved_at": "2026-11-01T14:48:11.591101+00:00"
  },
  "licence": "Open Government Licence v3.0",
  "licence_url": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
  "attribution": "Contains public sector information licensed under the Open Government Licence v3.0. Source: legislation.gov.uk, The National Archives."
}