GPKG define validation steps about geonode-importer HOT 3 CLOSED

• RQ5: validation of geometries is too much imho, it means iterating over each feature
• RQ9 / RQ10: do we really need this? I don't think so. We're just doing a sequential read of the DB, we will never use the spatial index

from geonode-importer.

This library provides some basic validation steps that we can use to validate the input geo package https://github.com/PDOK/geopackage-validator
The validations step can be provided via config or via code.

At the moment the following validation steps are performed:

RQ1: Layer names must start with a letter, and valid characters are lowercase a-z, numbers or underscores.
RQ2: Layers must have at least one feature.
RQ5: Geometry should be valid
RQ9: All geometry tables must have an rtree index
RQ10: All geometry table rtree indexes must be valid.
RQ13: It is required to give all GEOMETRY features the same default spatial reference system
RQ14: The geometry_type_name from the gpkg_geometry_columns table must be one of POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, or MULTIPOLYGON
RQ15: All table geometries must match the geometry_type_name from the gpkg_geometry_columns table
RC2: It is recommended to give all GEOMETRY type columns the same name.

Is also possible to provide a JSON or a YAML file with the configuration and validate the geo package against that

from geonode-importer.

• RQ5: validation of geometries is too much imho, it means iterating over each feature

We can remove them, actually yes it may be too much looping on all geometries

• RQ9 / RQ10: do we really need this? I don't think so. We're just doing a sequential read of the DB, we will never use the spatial index

agree, going to remove it

from geonode-importer.