Frequently Ask questions


The spatial data contribution has to go through 5 sequential steps:


  1. Choose the spatial topic

  2. Choose the spatial layer

  3. Check the requirements of the targeted spatial layer

  4. Prepare the data

  5. Upload the data





  1. Choose the spatial topic:


You can contribute spatial data in NELGA LDH portal in one or more of the following spatial topics:


    1. Land Tenure


    2. Cadastral Map


    3. Land Cover


    4. Mineral Tenure


    5. Land Conflict


    6. Land use


For instance,  if You want to contribute cadastral related spatial data, then the data has to be contributed in the “Cadastral Map” topic.





  1. Choose the spatial layer


You have to choose the spatial layer of which their contributed spatial data fits. The following table shows a list of spatial layers for each spatial topic.





  1. Check the requirements of the targeted spatial layer


The data has to be uploaded in a specific schema that makes sense in the context of every spatial topic and layer. In this regard, a data schema has been designed specially for every spatial layer. The schema of the targeted category must be followed.


Land tenure

land_tenure

The land_tenure spatial layer schema consists of 6 columns as shown in the following table and the following ERD diagram.


Column name

Data type


id

UUID 

Mandatory

This column works as the unique identifier (primary key) of each land tenure feature. Though, this column has to be filled by you for each feature. 

land_tenure_cat

Integer

Mandatory

Every land tenure feature has to be categorized as one o four main land tenure categories:

  1. Private Land

  2. Communal Land

  3. Open Access Land

  4. State Land

valid_to

date

Optional

It represents the date when the land tenure parcel data validity ends.

valid_from

date

Optional

It represents the date when the land tenure parcel data validity begins.



  1. Cadastral_zoning layer

The schema for this spatial layer is designed to contain cadastral zones data. Cadastral zones can be defined as intermediary areas (municipalities, sections, blocks, etc.) for example. Cadastral zones are hierarchical areas. For instance, municipalities are higher in hierarchy than sections and contain sections. On the other hand,  sections are higher in hierarchy than blocks and contain blocks.

The purpose of having cadastral zones is to divide the national administrative units into cadastral parcels. Though, a cadastral parcel should belong to the lowest cadastral zone level in the national cadastral hierarchy levels of zones that contain it spatially. 


Column name

Data type


id

UUID 

Mandatory

This column works as the unique identifier (primary key) of each cadastral zone. This column has to be filled by you for each feature. 

iso2

varchar(2)

Mandatory

Every cadastral zone has to belong to a country. The ISO2 code of the country that the cadastral zone belongs to has to be provided by you. To assist you to perform a correct input in this field, a code list with country names and ISO2 codes has been provided (please check this external link).

label

varchar(100)

Mandatory

The zone’s name.

Level_name

varchar(100)

Mandatory

The name of the cadastral level varies from a country to another. Though, you need to input the name of the cadastral level for every zone.


valid_to

date

Optional

It represents the date when the cadastral zone data validity ends.

valid_from

date

Optional


Please note that in the following ER Diagram there are 3 spatial layers with the following names:

  1. cadastral_zoning_lvl1

  2. cadastral_zoning_lvl2

  3. cadastral_zoning_lvl3

The previous table represents a blueprint for these layers schemas. The only difference between these layers is that every layer schema is designed to contain the zones of only one level. For instance, cadastral_zoning_lvl1 layer would only contain the cadastral zones which belong to the highest level of the national cadastral hierarchy levels of zones. On the other hand, cadastral_zoning_lvl3 layer would only contain the cadastral zones which belong to the lowest level of the national cadastral hierarchy levels of zones.


cadastral_parcel layer

Cadastral parcels are areas which are defined by land registration authorities and can be owned or benefited from by individuals, authorities, organizations, etc. [1]. The data of which category can be stored and retrieved in NELGA LDP as vector data according to the following schema.



Column name

Data type


id

uuid 

Mandatory

This column works as the unique identifier (primary key) of each cadastral parcel.This column has to be filled by you for each feature. 

iso2

varchar(2)

Mandatory

Every cadastral parcel has to belong to a country. The ISO2 code of the country that the cadastral parcel belongs to has to be provided by you. To assist you to perform a correct input in this field, a code list with country names and ISO2 codes has been provided (please check this external link).

cadastral_zone

uuid

Optional

The lowest cadastral zone in the national cadastral hierarchy levels of zones that contain the parcel.

label

varchar(100)

Mandatory

The parcel’s label.

disputed_parcel

smallint

Mandatory

This column indicates whether the parcel is under dispute or not. If the value in this column is 0, then the parcel is not under dispute. On the other hand, if the value is 1, then the parcel is under ongoing dispute.

dispute_details_ en

text

Optional

If the parcel is under dispute or was under dispute, you can add details about this dispute in English in this field.

dispute_details_fr

text

Optional

If the parcel is under dispute or was under dispute, you can add details about this dispute in French in this field.

resolved_dispute

smallint

Mandatory

This column indicates whether the parcel was under dispute or not. If the value in this column is 0, then the parcel was not under dispute. On the other hand, if the value is 1, then the parcel was under dispute and the dispute is resolved.

valid_from

date

Optional

It represents the date when the parcel data validity begins.

valid_to

date

Optional

It represents the date when the parcel data validity ends.


[1] https://inspire.ec.europa.eu/theme/cphttps://inspire.ec.europa.eu/theme/cp

Land Cover

  1. land_cover (vector) Layer

Land cover data can be uploaded in two different spatial data types, vector and raster.

Every vector land cover feature represents a land cover unit. A land cover unit is a homogeneous land cover area that can be categorized in one of the following main five categories:


  1. Artificial surfaces

  2. Agricultural areas

  3. Forest and semi natural areas

  4. Wetlands

  5. Water bodies



Column name

Data type


id

uuid 

Mandatory

This column works as the unique identifier (primary key) of each land cover unit. This column has to be filled by you for each feature. 

iso2

varchar(2)

Mandatory

  1. Every land cover unit has to belong to a country. The ISO2 code of the country that the land cover unit belongs to has to be provided by you. To assist you to perform a correct input in this field, a code list with country names and ISO2 codes has been provided (please check this external link).

corine_land_cover

integer

Mandatory

Every land cover unit has to be categorized as one of five main land cover categories:

  1. Artificial surfaces

  2. Agricultural areas

  3. Forest and semi natural areas

  4. Wetlands

  5. Water bodies

The numbers beside the category name in the previous list represents the value which you needs to input in this field, not the title of the category. For instance, if the inputted value for a land cover unit is 1, then this land cover unit is categorized as an “Artificial surface. 

valid_from

date

Optional

It represents the date when the land cover unite started to exist in the real world.

valid_to

date

Optional

It represents the date when the land cover unite started not to exist in the real world.







B. land_cover (raster) Layer


land_cover (raster)

While preparing the land cover raster image, the following colors schema has to be followed for the five main categories:


Category

Color

Artificial surfaces

#C20041

Agricultural areas

#B8B879

Forrest and semi natural areas

#448700

Wetlands

#7979BA

Water bodies

#00758A

  1. Mineral Tenure


mineral_parcel


Column name

Data type

Necessity

id

uuid 

Mandatory

This column works as the unique identifier (primary key) of each mineral parcel. Though, this column has to be filled by you for each feature. 

iso2

varchar(2)

Mandatory

  1. Every mineral parcel has to belong to a country. Though, the iso2 code of the country that the mineral parcel belongs to has to be provided by you. To assist you to perform a correct input in this field, a code list with country names and iso 2 codes has been provided (please check this external link).

license_type

integer

Optional

The legal license type of the parcel. In other words, the permitted mining activity of the parcel. The parcel can only have one of the mining activity:

  1. Mining

  2. Exploration

  3. Prospection

  4. Development

  5. Retention

  6. Artisanal


scale

integer

Optional

The scale of the activity. The value can be only one of the following values:

  1. Small

  2. Medium

  3. Large

mineral

integer

Optional

The mineral that is concerned with the activity of the parcel:

  1. Petroleum

  2. Iron

  3. Gold

  4. Coal

  5. Copper

  6. Spar

  7. Construction Material

  8. Other

label

varchar(100)

Mandatory

The parcel’s label.

disputed_parcel

smallint

Mandatory

This column indicates whether the parcel is under dispute or not. If the value in this column is 0, then the parcel is not under dispute. On the other hand, if the value is 1, then the parcel is under ongoing dispute.


dispute_details_ en


Optional

If the parcel is under dispute or was under dispute, you can add details about this dispute in English in this field.

dispute_details_fr



If the parcel is under dispute or was under dispute, you can add details about this dispute in French in this field.

resolved_dispute



This column indicates whether the parcel was under dispute or not. If the value in this column is 0, then the parcel was not under dispute. On the other hand, if the value is 1, then the parcel was under dispute and the dispute is resolved.

valid_from

date

Optional

The date when the parcel was legally established

valid_to

date

Optional

The date when the parcel will/has been be ceased.



Land Conflict


Land conflict data can only be shown in two different spatial topics which are (Cadastral map and Mineral Tenure). The spatial layers (cadastral_parcel and mineral_parcel layers) can contain dispute data as shown in the previous sections.


Land Use

Land use data can be uploaded in two different spatial data types, vector and raster. 


Spatial_plan Layer


In this spatial layer schema, you can add data of an ongoing/ceased spatial planning project whether it was a national development project or private investment.




Column name

Data type

Necessity

id

uuid 

Mandatory

This column works as the unique identifier (primary key) of each land use spatial plan. Though, this column has to be filled by you for each feature. 

iso2

varchar(2)

Mandatory

  1. Every land use spatial plan has to belong to a country. Though, the iso2 code of the country that the and use spatial plan belongs to has to be provided by you. To assist you to perform a correct input in this field, a code list with country names and iso 2 codes has been provided (please check this external link).

official_title

varchar(100)

Mandatory

The official title of the spatial plan.

valid_from

date

Optional

  1. It represents the date when the and use spatial plan started to exist in the real world.

valid_to

date

Optional

  1. It represents the date when the and use spatial plan not to exist in the real world.

details_en

text

Optional

Any additional info in English regarding the land use spatial plan can be added here.

details_fr

text

Optional

Any additional info in French regarding the land use spatial plan can be added here.



Land_use_object Layer


Every vector land use feature represents a land use object. A land use object is a homogeneous land use area that can be categorized in one of main 13 categories according to hillucs_land_use codelist as shown in the following ER Diagram.



Column name

Data type

Necessity

id

uuid 

Mandatory

This column works as the unique identifier (primary key) of each land use object. Though, this column has to be filled by you for each feature. 

iso2

varchar(2)

Mandatory

  1. Every land use object has to belong to a country. Though, the iso2 code of the country that the land use object belongs to has to be provided by you. To assist you to perform a correct input in this field, a code list with country names and iso 2 codes has been provided (please check this external link).

hillucs_land_use

integer

Mandatory

Every land use object has to be categorized as one of 13 main land use categories:

  1. Other uses

  2. Commercial services

  3. Forestry

  4. Agriculture

  5. Utilities

  6. Cultural entertainment and recreational services

  7. Residential use

  8. Energy production

  9. Community services

  10. Transport networks & services

  11. Mining and quarrying

  12. Industry

  13. Aquaculture and fishing

The numbers beside the category name in the previous list represents the value which you needs to input in this field, not the title of the category. For instance, if the inputted value for a land use object is 2, then this land use object is categorized as an “Commercial services”. 

observation_date

date

Optional

  1. The date when the land use object was observed in the real world.

valid_from

date

Optional

  1. It represents the date when the land use object started to exist in the real world.

valid_to

date

Optional

It represents the date when the land use object not to exist in the real world.

spatial_plan

uuid

Optional

A land use object can be part of an ongoing spatial planning project whether it was a national development project or private investment.






land_use (raster) Layer


While preparing the land use raster image, the following colors schema has to be followed for the five main categories:



Category

Color

Other uses

#6e6e6e

Commercial services

#870046

Forestry

#162918

Agriculture

#255929

Utilities

#B8B879

Cultural entertainment and recreational services

#087353

Residential use

#adab65

Energy production

#470000

Community services

#ab2727

Transport networks & services

#84abab

Mining and quarrying

#a80c4d

Industry

#2e2e2e

Aquaculture and fishing

#1e5069


You can prepare the data for contribution in NELGA LDH according to the schemas shown in the previous questions. The data preparation step can be done practically in one of the GIS applications for spatial data processing such as Esri ArcMap or QGIS.

Inorder to contribute spatial data in NELGA LDH, you don’t need to create the schema for the spatial data layers you want to contribute from scratch. All you need to do is to download a template for your spatial data topic and then you can fill the data in your chosen template using your favorite GIS application.


You can do that by going to the Administration panel and then click on spatial data in the side menu.


After clicking on Spatial data from the side menu, a sub menu will drop down. You can choose any of the spatial data topics. Then, a page to contribute spatial data for this topic will open. You can scroll down a little bit on this page until you see the “DOWNLOAD TEMPLATE” button. Please click on it and choose the data type of the template. It can be either shapefile or geopackage.


In this example a land cover geopackage template will be used in QGIS.



The attribute table for this file, shows the attributes that need to be filled with data. You can simply fill this file with spatial data and then upload it in NELGA LDH.

Share this page