Skip to content

Urban Atlas 2012

marketajindrova edited this page May 14, 2020 · 5 revisions

Urban Atlas 2012

This product consists of a single status layer.

Check description: Delivery file can be unzipped.

Required check, the check cannot be skipped.

Check description: Naming is in accord with specification.

Required check, the check cannot be skipped.

Requirements: Each Urban Atlas product must be in a geodatabase (gdb) or GeoPackage (gpkg) format. The geodatabase must contain one feature dataset with one feature class.

Each product also include 2 documents in pdf format:

  • Map: name ending with „_map.pdf“
  • Delivery report: name ending with „_delivery_report.pdf“

Naming convention:

If the delivery is in Geopackage format, filename must match regex:

+-- <FUAcode>_<FUAname>_UA2012.gpkg     (Geopackage name),      e.g.: DK001L2_KOBENHAVN_UA2012.gpkg
    +-- <FUAcode>_<FUAname>_UA2012      (Layer name),           e.g.: DK001L2_KOBENHAVN_UA2012

If the delivery is in Geodatabase format, filename must match regex:

+-- <FUAcode>_<FUAname>_UA2012.gdb/      (Geodatabase name),      e.g.: DK001L2_KOBENHAVN_UA2012.gdb/
    +-- <FUAcode>_<FUAname>_UA2012/      (Feature dataset name),  e.g.: DK001L2_KOBENHAVN_UA2012/
        +-- <FUAcode>_<FUAname>_UA2012   (Feature class name),    e.g.: DK001L2_KOBENHAVN_UA2012
where
  • <FUAcode> is the code of the functional urban area;
  • <FUAname> is the name of the functional urban area;

The filename must match regex:

^(?P<aoi_code>[a-z]{2}[0-9]{3}L[0-9]{1})_.*_ua2012(_revised)?$

  • the name must start with an 'aoi code' which consists of:
    • 2 letters
    • 3 numbers
    • letter 'L'
    • 1 number
  • the name must end with _ua2012 or _ua2012_revised

Example of filename: DK001L2_UA2012.gdb or DK001L2_UA2012.gpkg

Check description: Attribute table check.

Required check, the check cannot be skipped.

Requirements:

Required attributes:
  • “country“: “string“, (length=50), country 2-letter code, e.g. DK
  • “fua_name“: “string“,
  • “fua_code“: “string“,
  • “code_2012“: “string“, (length=7), LULC class, e.g. 50000
  • “class_2012“: “string“,
  • “prod_date“: “string“, (length=4), map production year, e.g. 2015
  • “identifier“: “string“, (length=30), unique identifier, e.g. 16-DK001L2
  • “perimeter“: “real“,
  • “area“: “real“,
  • “comment“: “string“, MMU area size exception comments.

Ignored: “shape_area“, “shape_length“

Check description: CRS (Projection) check.

Required check, the check cannot be skipped.

Requirements:

  • The vector must be assigned spatial reference system EPSG: 3035 (ETRS89 ETRS-LAEA equal-area projection);

Check description: Data can be imported into database

Required check, the check cannot be skipped.

Check description: Metadata.

Optional check, the check may be skipped.

Requirements:

  • All vector deliveries must contain an INSPIRE compliant XML metadata document.
  • Each delivery must contain a 'Metadata' subdirectory with one XML document named <layer_name>.xml where layer_name is the name of the geodatabase or geopackage, e.g.
+-- DK001L2_UA2012.gdb      (Geodatabase name),
+-- Metadata/               (Metadata subfolder),
        +-- DK001L2_UA2012.xml   (INSPIRE XML metadata document)

Check description: Unique attribute check.

Optional check, the check may be skipped.

Requirements: The value in the column 'identifier' must be unique for each input/row (regarding revised, reference and change layers).

Parameters:
  • “unique_keys“: [“identifier“];

Check description: Valid codes.

Optional check, the check may be skipped.

Requirements:

Set of valid codes for attribute code_2012:

11100, 11210, 11220, 11230, 11240, 11300,
12100, 12210, 12220, 12230, 12300, 12400,
13100, 13300, 13400,
14100, 14200,
21000, 22000, 23000, 24000, 25000,
31000, 32000, 33000
40000,
50000,
91000, 92000;

Check description: Singlepart polygon check.

Optional check, the check may be skipped.

Requirements: All layers of all vector products, feature satisfying general requirements:

Feature is a single-part polygon; a single-part polygon may contain holes but may not contain multiple exterior rings. ;

Check description: Geometries are valid.

Optional check, the check may be skipped.

Requirements:

Feature satisfying general requirements:

  • Feature with valid geometries as defined by Open Geospatial Consortium’s OpenGIS specification.
  • For each feature with invalid geometry the invalid geometry reason (i. e. self-intersection) and invalid geometry location can be found in the attachment error table.

NOTE: Ring self-intersections while considered valid by ArcGIS are also reported as errors by the QC Tool. ;

Check description: Calculated area and value in the column 'area' coincide.

Optional check, the check may be skipped.

Requirements:

  • unit: 1, (value is in m2)
  • tolerance: 0.5 (calculated area and value in the column 'area' do not differ by more than 0.5 m2)

Check description: There is no gap in the AOI.

Optional check, the check may be skipped.

Requirements: AOI is defined by the AOI layer in the boundary package. The boundary unit is the polygon int the AOI layer with attribute fua_code equal to fua_code in the delivery.

Check description: Minimum mapping unit.

Optional check, the check may be skipped.

Requirements:

Feature satisfying general requirements:

  • Feature of the class 1.2.2.x;
  • Feature of the class 1 having area >= 2500 m2;
  • Feature of the class 2-5 having area >= 10000 m2;
  • Feature of the class 9;

Feature satisfying exceptional requirements:

  • Feature touching a feature of the class 9 by a line;
  • Feature touching the boundary by a line and having area >= 100m2;
  • Feature with one of the following comments in the COMMENT attribute:
Area size exception (at Urban Atlas FUA boundary)
Area size exception (at Urban Atlas FUA boundary); Areas related to boundary update
Area size exception (at Urban Atlas FUA boundary); Areas related to change
Area size exception (inside Urban Atlas FUA boundary)
Area size exception (inside Urban Atlas FUA boundary); Areas related to change

Feature satisfying warning requirements:

  • Feature touching a feature of the class 1.2.2.x by a line and having area >= 500m2;
  • Feature touching a feature of the class 1.2.2.x by a line and touching the boundary by a line and having area >= 100m2 (this requirement is already covered by the exception requirement);

Notes:

  • One feature can have multiple comments in the comment attribute. If a feature has multiple comments, they should be separated by a semicolon (;).

Check description: Minimum mapping width.

Optional check, the check may be skipped.

Requirements:

Feature satisfying general requirements:

  • Feature with minimum width greater than 10 metres

Feature satisfying exceptional requirements:

  • Linear structures (class 1.2.2.x) having a minimum width smaller than 10 m over a distance of up to 50 m. ;

Check description: No overlapping polygons.

Optional check, the check may be skipped.

Requirements:

There must be no feature having any part of its interior common with any other feature (aka overlaps). ;

Check description: No neighbouring polygons with the same code.

Optional check, the check may be skipped.

Requirements:

This check does not apply to features of class 1.2.2.x where neighbouring polygons with the same code are allowed.

Feature satisfying general requirements:

  • All neighbouring features have class distinct from the feature in question;
Clone this wiki locally