You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document contains the product description, mapping guidance and class description for the product "Urban Atlas" from the Copernicus "Urban Atlas" project for the 2006 reference year and the "Urban Atlas" update and extension for the 2012 and 2018 reference years.
45
46
46
-
# SCOPE
47
+
# Scope
47
48
48
49
This mapping guide aims at supporting service providers in generating an Urban Atlas mapping product. It provides guidance to achieve:
49
50
@@ -55,7 +56,7 @@ This mapping guide aims at supporting service providers in generating an Urban A
55
56
56
57
- Comparable quality of the product.
57
58
58
-
# REFERENCE DOCUMENTS
59
+
# Reference documents
59
60
60
61
The table below includes the different Reference Documents (RD) related to the Urban Atlas project. A list of abbreviations is provided in Annex 1.
61
62
@@ -79,11 +80,11 @@ The table below includes the different Reference Documents (RD) related to the U
The Urban Atlas service offers a high-resolution land use map of urban areas. Initially covering over 300 European cities with more than 100,000 inhabitants for the 2006 reference year, the Urban Atlas is available for the 2012 and 2018 reference years over nearly 800 cities with more than 50,000 inhabitants distributed among EU, EFTA and West Balkan countries plus United Kingdom and Turkey. Each Urban Atlas product is generated over the city and its surroundings, according to the Functional Urban Area (FUA) defined by the implementation of the approach developed by the DG Regional and Urban Policy (REGIO) of the European Commission.
89
90
@@ -136,7 +137,7 @@ The table provided in Annex 5.3 gives a more detailed description of the product
136
137
137
138

138
139
139
-
### ADDITIONAL INFORMATION LAYERS
140
+
### Additional information layers
140
141
141
142
The Urban Atlas Mapping Guide is related to the main product and by default refers to the Land Use / Land Cover (LU/LC) database. However, two additional information layers are also available starting from the 2012 reference year. A short description including the detailed specifications is proposed in this section.
142
143
@@ -218,23 +219,23 @@ The building height information is derived from IRS-P5 stereo images of the refe
218
219
219
220
: Detailed specifications of Urban Atlas DHM product
220
221
221
-
## GENERAL GUIDELINES
222
+
## General guidelines
222
223
223
-
### PRE-PROCESSING AND GEO-CODING OF EO DATA
224
+
### Pre-processing and geo-coding of EO data
224
225
225
226
The EO data provided to the Service Provider should already be pre-processed. In order to reach the 1/10,000 expected scale, EO data should be provided with spatial resolution less than 5 meters. Service Provider should check the geometric quality of the delivered EO data, but no further pre-processing step is expected. The EO data for the European Urban Atlas 2012 is the optical VHR2 coverage over EU 2011-2013 (DWH_MG2b_CORE_03) available on Data Warehouse (DWH) of the European Space Agency (ESA). The EO data for the Urban Atlas 2018 is an optical VHR coverage over EU 2017-2019 also available on ESA DWH. Change detection task can be supported by Copernicus Sentinel-2 data (10 m resolution).
226
227
227
-
### PRE-PROCESSING AND GEOMETRIC ADAPTATION OF NAVIGATION DATA
228
+
### Pre-processing and geometric adaptation of navigation data
228
229
229
230
The EO data are the basis for interpretation and classification. In case of geometrical differences between EO data and navigation data (COTS or OSM), the navigation data has to be corrected in line with the EO data.
230
231
231
232
The pre-processing and application of the navigation data (COTS or OSM) shall be done according to the methodology defined in Annex 5.2.
232
233
233
-
### PRE-PROCESSING OF TOPOGRAPHIC MAPS
234
+
### Pre-processing of topographic maps
234
235
235
236
Topographic maps can be used for interpretation of objects. Topographic maps should be used in digital form with precise geo-coding. The usage of printed (analogue) maps is not recommended. In case of geometrical differences between EO data and topographic maps, the erroneous data (either EO-data or topo-maps) needs to be identified using reliable datasets providing spatial reference information. The geometry of the mapping product shall then be congruent with the correct dataset.
236
237
237
-
### CLASSIFICATION AND INTERPRETATION
238
+
### Classification and interpretation
238
239
239
240
Application of automatic classification routines, such as segmentation and clustering, may be applied whenever appropriate:
240
241
@@ -244,13 +245,13 @@ As the backbone for the object geometry, the navigation data network (COTS or OS
244
245
245
246
Manual refinement and classification at the finest level of the LU/LC classification especially within urban areas by means of visual interpretation of EO data remain necessary to be compliant with the product specifications. For this purpose, the following sections provide the rules and principles to be applied.
246
247
247
-
### USE OF COPERNICUS HRL IMPERVIOUSNESS
248
+
### Use of Copernicus HRL imperviousness
248
249
249
250
Among the reference products from Copernicus Land Monitoring Services (CLMS), the pan-European High-Resolution Layer (HRL) Imperviousness (formerly named Fast Track Sealing layer, FTS) is used for the classification at level 4 of the residential or mixed use urban fabric units classified 1.1.2 from EO data
250
251
251
252
The assignment of the imperviousness/soil sealing levels or density (i.e. classes 1.1.2.1 - 1.1.2.4) shall be carried out using the HRL Imperviousness layer or similar one. The Quality Assurance (QA) process will check only if the technical approach agreed with DG REGIO is respected but will not assess the absolute accuracy of these classes.
252
253
253
-
### DATA FORMAT OF THE FINAL PRODUCT
254
+
### Data format of the final product
254
255
255
256
ESRI ArcGIS compatible or open source OGC-standard vector format with polygon topology:
256
257
@@ -270,7 +271,7 @@ CODE_yyyyy: 5 digits in Long Integer format without decimal places (values allow
270
271
271
272
The complete description of the data format is provided in section 5.4.
272
273
273
-
### INTERPRETATION RULES
274
+
### Interpretation rules
274
275
275
276
- The delineation is to be done on the EO data. EO data should be considered as the primary (guiding) data source.
276
277
@@ -294,7 +295,7 @@ The complete description of the data format is provided in section 5.4.
294
295
295
296
- Analysis scale : 1:5 000
296
297
297
-
### LU/LC CHANGE DETECTION AND LAYER GENERATION
298
+
### LU/LC change detection and layer generation
298
299
299
300
In case of the required production of an update of the Urban Atlas LU/LC database for a historic or new reference year, change detection task shall be performed and an additional layer shall be produced by the service provider, the Land Use / Land Cover (LU/LC) change layer. For the European Urban Atlas, following the LU/LC product generation for the 2006 reference year, change detection were performed successively for generating the 2012 and 2018 products.
300
301
@@ -314,7 +315,7 @@ As it is often quite difficult to predict the future LU/LC over an area resultin
314
315
315
316

316
317
317
-
### STREET TREE LAYER
318
+
### Street tree layer
318
319
319
320
The Street Tree Layer 2012 (STL2012) and Street Tree Layer 2018 (STL2018) are separate layers from respectively the UA2012 and UA2018 LU/LC Layers, which are produced within the level 1 urban mask for each FUA. They include contiguous rows or patches of trees covering 500m² or more and with a minimum width (MinMW) of 10 m over "Artificial surfaces" (nomenclature class 1) inside FUA (i.e. rows of trees along the road network outside urban areas or forest adjacent to urban areas should not be included).
320
321
@@ -340,7 +341,7 @@ STL patches do not cover roads (codes 12210 and 12220) or railways (code 12230)
340
341
341
342

342
343
343
-
### DIGITAL HEIGHT MODEL LAYER (DHM)
344
+
### Digital Height Model layer (DHM)
344
345
345
346
A 10 m raster layer containing height information is generated for core urban areas of capital cities of the EEA38 and the United Kingdom as part of the Urban Atlas project (see table 2), based on the methodology described hereafter.
346
347
@@ -414,7 +415,7 @@ Each Building Block Height model (DHM) is clipped exactly to the AOI and assigne
414
415
415
416

@@ -458,7 +459,7 @@ In order to ensure that relevant LU/LC changes are appropriately extracted, the
458
459
459
460
Considering this MMUs, exceptions are made in case of areas where changes involve road and railway networks (classes 12210, 12220, 12230); polygon features classified as road or railway for one date or directly connected to such element are extracted even if area is lower than MMU in order to keep consistency of the transportation network.
460
461
461
-
### ACCURACY ASSESSMENT AND VALIDATION
462
+
### Accuracy assessment and validation
462
463
463
464
In addition to the usual QA/QC procedure implementation, which implies visual checks for ensuring thematic and geometric positional accuracies and automatic checks for ensuring completeness and logical consistency during the post-processing phase of the production, accuracy assessment and validation must be performed independently from the production for providing the evidence that the results are fully compliant with the product specifications.
464
465
@@ -480,7 +481,7 @@ For the DHM layer, Quality controls are conducted for each stage of the producti
480
481
481
482
Every product is accompanied by a DHM QC Report, which shows the results of the external Quality Check and an INSPIRE compliant xml file: [Building Height 2012 --- Copernicus Land Monitoring Service](https://land.copernicus.eu/local/urban-atlas/building-height-2012?tab=download).
482
483
483
-
## LU/LC NOMENCLATURE
484
+
## LU/LC nomenclature
484
485
485
486
The Urban Atlas Land Use / Land Cover classification is derived from CORINE Land Cover and is composed of 27 classes distributing among 5 thematic groups, namely:
486
487
@@ -586,17 +587,17 @@ A decision matric below illustrate the rules followed to apply LULC nomenclature
586
587
587
588
: UA LULC nomenclature (in bold, classes without any further subdivision)
588
589
589
-
## DECISION RULES
590
+
## Decision rules
590
591
591
592
Affectation of LULC classes follow the below decision matrix. A detailed matrix concerning artificial areas is illustrated next page.

596
597
597
-
## DESCRIPTION OF LU/LC THEMATIC CLASSES
598
+
## Description of LU/LC thematic classes
598
599
599
-
### 1. ARTIFICIAL SURFACES {.unnumbered}
600
+
### 1. Artificial surfaces{.unnumbered}
600
601
601
602
Surfaces with dominant human influence and without agricultural land use.
602
603
@@ -1088,7 +1089,7 @@ Caravan parking used for commercial activities → class 1.2.1.
1088
1089
1089
1090
Soccer fields, etc. within e.g. military bases or within university campuses → class 1.2.1.
1090
1091
1091
-
### 2. AGRICULTURAL {.unnumbered}
1092
+
### 2. Agricultural {.unnumbered}
1092
1093
1093
1094
Please note that Classes 2.1 to 2.4 are grouped together in Class 2 in UA2006.
1094
1095
@@ -1128,7 +1129,7 @@ Please note that Classes 2.1 to 2.4 are grouped together in Class 2 in UA2006.
1128
1129
1129
1130
- Agroforestry areas.
1130
1131
1131
-
### 3. NATURAL AND SEMI-NATURAL AREAS {.unnumbered}
1132
+
### 3. Natural and semi-natural areas{.unnumbered}
1132
1133
1133
1134
Please note that Class 3.1 are included into class 3 and classes 3.2 and 3.3 are included into class 2 in UA2006.
1134
1135
@@ -1209,7 +1210,7 @@ e) [Snow and ice:]{custom-style="NormalLine"}\
1209
1210
1210
1211
-[Glacier and perpetual snow.]{custom-style="NormalLine"}\
1211
1212
1212
-
### 4. WETLANDS {.unnumbered}
1213
+
### 4. Wetlands {.unnumbered}
1213
1214
1214
1215
Please note that Class 4 is included into Class 2 in UA2006.
1215
1216
@@ -1243,7 +1244,7 @@ Greenhouses → class 1.2.1.
1243
1244
1244
1245
Inland salinas → class 1.3 1.
1245
1246
1246
-
### 5. WATER {.unnumbered}
1247
+
### 5. Water {.unnumbered}
1247
1248
1248
1249
> *MMU 1 ha*
1249
1250
@@ -1281,7 +1282,7 @@ Not included are:
1281
1282
1282
1283
Shallow water areas covered with reed \> MMU → class 2 Seasonal rivers, if the water course is not visible in the EO data → class 2.
1283
1284
1284
-
### 6. MISCELLANEOUS {.unnumbered}
1285
+
### 6. Miscellaneous {.unnumbered}
1285
1286
1286
1287
Concerning the UA2006 products, areas with EO data provision problems were classified in separate classes described below.
1287
1288
@@ -1295,9 +1296,9 @@ b) [No data (Missing imagery)]{custom-style="NormalLine"}\
1295
1296
1296
1297
This class 9.2 (code 92000) includes areas without available satellite image or inadequate imagery (e.g. no STL data can be produced as the image acquisition is outside the vegetation period).
@@ -1334,7 +1335,7 @@ This class 9.2 (code 92000) includes areas without available satellite image or
1334
1335
| UA | Urban Atlas |
1335
1336
| VHR | Very High Resolution |
1336
1337
1337
-
## PRE-PROCESSING AND GEOMETRIC ADAPTATION OF NAVIGATION DATA
1338
+
## Pre-processing and geometric adaptation of navigation data
1338
1339
1339
1340
The navigation datasets (COTS or OSM) by default include a specific and hierarchical classification of the road network. Two basic categories are important within the context of the Urban Atlas. The first category gives information about the Functional Road Class (FRC), i.e. the road type, the second one gives information about the importance of each road within the city traffic network (Net2Class).
1340
1341
@@ -1434,7 +1435,7 @@ POST-PROCESSING
1434
1435
1435
1436
Post-processing will be implemented according to service provider's production chain.
1436
1437
1437
-
## DETAILED PRODUCT SPECIFICATION TABLE
1438
+
## Detailed product specification table
1438
1439
1439
1440
**Product features**
1440
1441
@@ -1509,7 +1510,7 @@ Post-processing will be implemented according to service provider's production c
1509
1510
-[Vector]{custom-style="NormalLine"}\
1510
1511
1511
1512
1512
-
## PRODUCT TYPES AND ATTRIBUTE FIELD DESCRIPTIONS
1513
+
## Product types and attricute field descriptions
1513
1514
1514
1515
The different types of cartographic products available in the Urban Atlas are described below.
1515
1516
@@ -1569,7 +1570,7 @@ This data corresponds to the reviewed version of the FUAs produced for the Urban
1569
1570
1570
1571
: UA 2012 LULC FIELD DESCRIPTION
1571
1572
1572
-
### UA 2006-2012 LULC CHANGE MAP
1573
+
### UA 2006-2012 LULC change map
1573
1574
1574
1575
The change 2006-2012 layer is derived from the combined 2006 and 2012 UA data products and corresponds [only to the changes of Land use/Land cover]{.underline} between those two dates. It concerns 305 FUAs produced for both the 2006 and 2012 reference years. The MMU is reduced up to 0.1 ha with some exceptions (see Section 4.7 LULC change layer).
1575
1576
@@ -1631,7 +1632,7 @@ This data corresponds to the Urban Atlas Land use/Land cover over 788 FUAs for t
1631
1632
1632
1633
: UA 2018 LULC FIELD DESCRIPTION
1633
1634
1634
-
### UA 2012-2018 LULC CHANGE MAP
1635
+
### UA 2012-2018 LULC change map
1635
1636
1636
1637
The 2012-2018 LU/LC change layer is derived from the combined UA2012 and UA2018 data products with exceptions in order to correspond [only to the actual changes of Land Use / Land Cover]{.underline} between those two dates. The MMU is reduced up to 0.1 ha with some exceptions (see further information provided in Section 4.7 LULC change layer).
1637
1638
@@ -1665,7 +1666,7 @@ The 2012-2018 LU/LC change layer is derived from the combined UA2012 and UA2018
1665
1666
1666
1667
: UA 2012-2018 LULC CHANGE FIELD DESCRIPTION
1667
1668
1668
-
### UA 2012 STL (STREET TREE LAYER)
1669
+
### UA 2012 STL (street tree layer)
1669
1670
1670
1671
This data corresponds to the Urban Atlas - Street Tree Layer (STL) for the 2012 reference year.
1671
1672
@@ -1687,7 +1688,7 @@ This data corresponds to the Urban Atlas - Street Tree Layer (STL) for the 2012
1687
1688
1688
1689
: UA 2012 STL FIELD DESCRIPTION
1689
1690
1690
-
### UA 2018 STL (STREET TREE LAYER)
1691
+
### UA 2018 STL (street tree layer)
1691
1692
1692
1693
This data corresponds to the Urban Atlas - Street Tree Layer (STL) for the 2018 reference year.
1693
1694
@@ -1709,7 +1710,7 @@ This data corresponds to the Urban Atlas - Street Tree Layer (STL) for the 2018
0 commit comments