brazil-data-cube/lccs-db

Land Cover Classification System Database Model

Land Cover Classification System Database Model

About

Currently, there are several data sets on regional, national and global scales with information on land use and land cover that aim to support a large number of applications, including the management of natural resources, climate change and its impacts, and biodiversity conservation. These data products are generated using different approaches and methodologies, which present information about different classes of the earth's surface, such as forests, agricultural plantations, among others. Initiatives that generate land use and land cover maps normally develop their own classification system, with different nomenclatures and meanings of the classes used.

LCCS-DB (Land Cover Classification System Database) provides a data model that represents the various classification systems in use and their respective classes. The LCCS-DB aims to provide a data repository to facilitate access and visualization of classes and their symbologies in each classification system employed in projects that provide land use and land cover maps in Brazil: PRODES, DETER, TerraClass and MapBiomas.

In addition, the LCCS-DB allows mapping between classes of classification systems in order to simplify joint data analysis.

The following diagram shows the tables used in this system:

This is the base package for other softwares in the Brazil Data Cube project:

• LCCS-WS-SPEC: Land Cover Classification System Web Service specification.
• LCCS-WS: Land Cover Classification System Web Service implementation.
• LCCS.py: Python Client Library for Land Cover Classification System Web Service.
• WLTS-SPEC: Web Land Trajectory Service Specification.
• WLTS.py: Python Client Library for Web Land Trajectory Service.
• BDC-Catalog: Brazil Data Cube Image Metadata Catalog.

Installation

Install from GitHub:

pip3 install git+https://github.com/brazil-data-cube/[email protected]

Documentation

See https://lccs-db.readthedocs.io/en/latest/

License

Copyright (C) 2023 INPE.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

lccs-db's Issues

Review file lccs_db/cli.py according to isort rules in run-test.sh

Review the header in files

Move folder "spec" under "doc"

Add the transition table to the model

This table must have the following fields:

• source_class_id
• source_class_id
• order
• create_at
• update_at

Database model review

• Tables could be associated to the schema luc.
• Remove from table class_mapping the attributes from target/source systems.
• In table classification_system replace column name system_name to name.
• Add relationships with table class_mapping.

Add a new document named CONFIGURE.rst that contains the list of variables related to the package configuration

Improve the documentation on how to install the package

Should we keep the file alembic.ini in the root folder of the repository?

Data model enhancements

Add an abstract about the LCCS-DB in the main README.rst

Improve the documentation and the command line support for creating the database model

• Review the documentation in RUNNING.rst
• Add a Click command to read an SQL file and execute the statements in the DBMS.

Fix file MANIFEST.in

Fix load_dbdata to use pkg_resources support for locationg the default sql script

Add new table to define possible transition classes

Support for I18N

• Class system name and description
• Class name and description

Add the skeleton for a Unit-test module

Change command line syntax

• Replace init-alambic for create-tables

• Replace insert-db for populate-db

Update README.rst

Change the abstract to English.

Add PyPI deploy

Release version 0.8.0

Tasks:

• Inform the right version in: lccs_db/version.py
• Run all the tests.
• Review the ER diagram and the Draw.io models.
• Create a branch named: b-0.8.
• Create a tag named: v0.8.0.
• Notify users that a new version is released.

Fix setup.py dependency: bdc-db v0.4.2

Fix PEP-8 style in file setup.py

Data model reviews

• Create the namespace lccs for all tables.

• Change table names to: class_systems, classes and class_mappings.

Review content in file run-test.sh

Class system versioning and lineage

Suggestion:

• Lineage: create a new table named classification_system_src.
• Versioning: add two new columns in classification_systems, one named version_predecessor and the other version_successor.

Add UniqueConstraint(name, version) in classification system

Add title in classification system ?

Add Unit-test module

Improve documentation on how to run LCCS-DB in the command Line

Change file name: sql_insert.sql to default_class_systems.sql

Add a PNG with the ER model under the folder 'doc/spec'

Change sub-dir name: db_data to data

Review Travis CI configuration

Release version 0.4.0

Tasks:

• Inform the right version in: lccs_db/version.py
• Run all the tests.
• Review the ER diagram and the Draw.io models.
• Create a branch named: b-0.4.
• Create a tag named: v0.4.0.
• Notify users that a new version is released.

Register LCCS namespace in BDC-DB

Release version 0.6.0

Tasks:

• Inform the right version in: lccs_db/version.py
• Run all the tests.
• Review the ER diagram and the Draw.io models.
• Create a branch named: b-0.6.
• Create a tag named: v0.6.0.
• Notify users that a new version is released.

Change name of table class_systems to classification_systems

Review usage.rst file

Review duplicate install requires

Add CliRunner intests for CLI commands

Integration with the Database Management Extension for Brazil Data Cube Applications and Services

Integrate with the bdc-db. (https://github.com/brazil-data-cube/bdc-db)

Review the description in the main README.rst

Fix requirements.txt file

The requirements.txt file should include all the dependencies informed in setup.py in the key install_requires and their dependencies.

Change Alembic to Flask-Alembic

To integrate lccs_db with sample_db, a solution found by @raphaelrpl was to use Flask-Alembic. This way you can keep the migrations of the two packages.

Release version 0.2.0

Tasks:

• Inform the right version in: lccs_db/version.py
• Run all the tests.
• Review the ER diagram and the Draw.io models.
• Review the CHANGES.rst.
• Create a branch named: b-0.2.
• Set links in the following files:
  • CHANGES.rst
  • README.rst
• From the branch b-0.2, create a tag named: v0.2.0.
• Merge branch b-0.2 into master branch.
• In the master branch increase version in lccs_db/version.py to 0.4.0.
• Set links in the following files:
  • CHANGES.rst
  • README.rst
• Notify users that a new version is released.

Update CHANGES.rst

• What are the changes/improvements in the data model since version 0.2.0?

• Does it have bug fixes?

Add class and functions to the Sphinx documentation system

add drone integration

Add production installation from GitHub

review INSTALL.rst

Add Index in tables