Skip to content

Latest commit

 

History

History
249 lines (200 loc) · 13.2 KB

README_en.md

File metadata and controls

249 lines (200 loc) · 13.2 KB
Raw

License Release Continuous integration

LADM-COL Assistant

QGIS plugin to capture and maintain data compliant with LADM-COL as well as to generate INTERLIS interchange files (.XTF) to be used by several actors in land administration.

License: GNU General Public License v3.0

Links of interest: Documentation, Gallery

A project of: SwissTierras Colombia (BSF-Swissphoto AG - INCIGE SAS)

➡️ With the current version of LADM-COL Assistant, we suggest you to use QGIS v3.22.0 or higher, which are available at https://qgis.org/downloads/

Support per DB engine

Module PostgreSQL/PostGIS GeoPackage MS SQL Server
Data management ✔️ ✔️ ✔️
Data capture and structuring ✔️ ✔️ ✔️⚠️
Load layers ✔️ ✔️ ✔️
Supplies management ✔️ ✔️ ✖️
Quality ✔️ ✔️ ✔️
Queries ✔️ ✔️ ✔️
Reports ✔️ ✖️ ✖️
Change detection ✔️ ✔️ ✔️⚠️
Transitional System ✔️ ✔️ ✔️

Minimum requirements

To use the LADM-COL Assistant you need:

  • Operating System:
    • Windows 8 or Windows 10
    • GNU/Linux
    • macOS (limited support)
  • Base software:
    • QGIS v3.22.0 Białowieża or higher.
    • Java v1.8.
    • PostgreSQL 9.5 or higher (PostgreSQL 10, 11 or 12 work as well).
    • PostGIS 2.4 or higher.
    • (Optional) SQL Server 2012 or higher.
  • QGIS plugins (installing LADM-COL Assistant using QGIS Plugin Manager will also install these automatically):
    • MapSwipe Tool v1.2
    • Invisible layers and groups v2.1

Gallery

  • Quality Rules

    quality_rules_new_generation.mp4

  • Queries

    Queries

  • Reports

    Reports

  • Change detection

    Change detection

  • Integration with Transitional System

    insumos

Functionalities

The current version (4.0.1-beta) of the LADM-COL Assistant allows users to:

  • Integrate with the Transitional System:
    • Authentication
    • Task management: start, cancel and finalize tasks.
    • Tasks of cadastral supplies generation and assisted integration of supplies (partial support).
      • ETL to generate cadastral supplies from cadastral authority (IGAC) data (SNC source).
      • ETL to generate cadastral supplies from cadastral authority (IGAC) data (Cobol source).
  • Roles support and GUI for each role.
  • Create database structures for the LADM-COL v3.1 model using the national map projection.
  • Two database engines to manage LADM-COL data:
    • PostgreSQL/PostGIS: Total support.
    • GeoPackage: Total support (except reports).
  • Capture data for the Application Model Cadastral Survey v1.2 (download).
  • Import data from transfer files (.XTF).
  • Export data to transfer files (.XTF).
  • Import/export data from/to transfer files (.XTF) disabling data validation.
  • Search for LADM-COL data by component:
    • Basic information.
    • Legal information.
    • Property record card information.
    • Physical information.
    • Economic information.
  • Add points to the Boundary Point, Survey Point and Control Point layers:
    • From CSV files.
      • Validate and avoid insertion of overlapping points.
    • From another layer with any structure, setting a field mapping.
  • Define Boundaries:
    • By digitizing on the map.
      • Aids for digitization:
        • Automatic snapping configuration and default field values.
        • Build boundaries from selected lines.
    • From another layer with any structure, setting a field mapping.
  • Create Plot:
    • From selected boundaries.
    • From another layer with any structure, setting a field mapping.
  • Fill topology tables automatically:
    • BFS Points (relates Boundary Points to Boundary)
    • More BFS (relates Boundaries to Plot)
    • Less (relates Plots to their inner rings)
  • Create Right of Way:
    • By digitizing on the map the polygon or a centerline with width.
      • Aids for digitization:
        • Automatic snapping configuration and default field values.
    • From another layer with any structure, setting a field mapping.
    • Create relations of benefited and restricted Parcels.
  • Associate addresses to Plots, Buildings and Unit Buildings.
  • Create Parcels:
    • Using preconfigured forms.
      • And associating the new Parcel to selected Plots and/or Buildings.
    • From another table with any structure, setting a field mapping.
  • Create Buildings and Building Units:
    • By digitizing on the map.
      • Aids for digitization:
        • Automatic snapping configuration and default field values.
    • From another layer with any structure, setting a field mapping.
  • Create Natural Parties and Legal Parties:
    • Using preconfigured forms.
    • From another table with any structure, setting a field mapping.
  • Create Group Party:
    • Using a preconfigured form.
  • Create Spatial Sources and Administrative Sources:
    • Using preconfigured forms.
      • And associating the new Spatial Source to selected Plots, Boundaries or Points.
    • From another table with any structure, setting a field mapping.
  • Create Source Files:
    • Associate sources to source files.
    • Upload source files to a server at saving-edits time or later, in batch mode.
  • Create Rights, Restrictions and Responsibilities:
    • Using preconfigured forms (associating the new object to selected Administrative Sources).
    • From another table with any structure, setting a field mapping.
  • Select in a dialog layers to load from any model in the database or schema.
  • Load layers with configured forms, relations and domains.
  • Load preconfigured layer sets.
  • Check quality rules (topology):
    • Check overlaps in Boundary Points.
    • Check overlaps in Control Points.
    • Check overlaps in Boundary.
    • Check overlaps in Plot.
    • Check overlaps in Building.
    • Check overlaps in Right of Way.
    • Check missing Boundary Points that do not have Boundary nodes correctly associated.
    • Check missing Boundary nodes that do not have Boundary Points correctly associated.
    • Check dangles in Boundary.
    • Check that Boundaries are not split.
    • Check overlaps between Right of Way and Building.
    • Check that Plots have no gaps in between.
    • Check that Plot boundaries are covered by Boundaries and their relations are correctly recorded in topology tables (MoreBFS and Less).
    • Check that Boundaries are covered by Plot boundaries and their relations are correctly recorded in topology tables (MoreBFS and Less).
    • Check that Right of Way has no multi-part geometries.
    • Check that Buildings are within their corresponding Plots.
    • Check that Building Units are within their corresponding Plots.
  • Check quality rules (consistency):
    • Parcel should have one and only one Right.
    • Table records should not be repeated.
    • Group Party Fractions should sum 1.
    • Check that the departamento field of the predio table has two numerical characters.
    • Check that the municipality field of the predio table has three numerical characters.
    • Check that the zona field of the predio table has two numerical characters.
    • Check that the numero_predial has 30 numerical characters.
    • Check that the numero_predial_anterior has 20 numerical characters.
    • Check that attributes are appropriate for parties of type natural.
    • Check that attributes are appropriate for parties of type legal.
    • Check that the type of parcel corresponds to position 22 of the numero_predial.
    • Check that Spatial Units associated with Parcels correspond to the parcel type.
  • Generate report of the quality checks.
  • Generate reports based on selected Plots (Annex 17).
  • Generate reports based on selected Plots (ANT map).
  • Generate reports of missing supplies.
  • Detect parcel changes:
    • Compare a collected database versus the supplies database and show differences by batch or per parcel.
  • Configure automatic values for namespace and local_id attributes.
  • Load styles for newly added layers from preconfigured QML files.
  • Online/offline help.

Testing

Unit tests

Unit tests are automatically executed after every commit made to the repository. Results are available for:

To run the tests locally you need to have docker and docker-compose installed. We suggest to:

Before running unit tests, you need to set these 2 environment variables (make sure you use your own repository's root path for the first one; the second one corresponds to an official QGIS Docker Hub's tag):

export GITHUB_WORKSPACE=/home/Asistente-LADM-COL
export QGIS_TEST_VERSION="final-3_22_9"

The command to execute unit tests is (execute from the repository's root folder):

docker-compose -f .docker/docker-compose.yml run --rm qgis

If you need to recreate the docker image, you can use:

docker-compose -f .docker/docker-compose.yml down --rmi local && docker-compose -f .docker/docker-compose.yml build

Assisted tests (for the GUI)

The LADM-COL Assistant uses QGIS Tester plugin to support assisted tests for GUI functionalities.

Prerrequisites:

In order to run the assisted tests, you need to install:

See the docs for usage instructions.

If these prerrequisites are not met, the LADM-COL Assistant will continue running smoothly and will put a warning in the QGIS log.

How to be notified of new relases of the LADM-COL Assistant?