Quality: Lineage

LINEAGE (GeM+)

The lineage describes the history of a dataset in terms of source material, dates, processing applied and responsible organisations.

The ISO standard has a metadata section (Ll_Lineage) that includes:

- the metadata entry that describes the lineage in general: statement.
- two metadata subsections: the first refers to each process (Ll_ProcessStep) and the other to the sources used to produce the data set (Ll_Source).

General description
[QUALITY:LINEAGE] (REL file)

Name of the GeM+ entry: Description
Name of the REL file key: LineageStatement

Description and considerations: This is a general explanation of the knowledge of the producer about the lineage of the map database.

Follows the proposal of : ISO

Obligatory ISO: Yes, if there is no information about either the sources or the processes that have produced this database.

Cardinality:1

Key type: C

AppliesToLayer : Yes
AppliesToSeries : Sí

(Back to index)

Source
[QUALITY:LINEAGE] (REL file)

Name of the GeM+ entry: Description
Name of the REL file key: DescripcioFonts

Description and considerations: Description of sources (whether cartographic or not) used to make the cartographic data base.

Follows the proposal of: ISO

Obligatory according to ISO: No

Cardinality: 1

Key type: :C

AppliesToLayer : Yes
AppliesToSeries : Yes;

(Back to index)

Process
[QUALITY:LINEAGE:PROCESS] (REL file)

The spirit of the CEN is that wherever there is information about the LINEAGE referring to a PROCESS, this should include data on WHO (organisation), HOW (history), WHY (purpose), and WHEN (date). The MiraMon support applications (MSA) automatically document the processes that they perform on a dataset and fill these fields where possible.

It is recommended to use GeM+ to document in detail both the processes performed to produce a dataset from the source material (such as data capture, format conversions, georeferencing, etc) and the processes carried out during the use of the data (corrections, etc).

It is possible to document, for each process, one or more tolerances in the [QUALITY:LINEAGE:PROCESS:TOLERANCE] section of the REL file although, naturally, this only makes sense for certain types of process.

(Back to index)

Name of GeM+ entry: Organisation
Name of the REL file key: organisation

Description and considerations: This is the organisation that is responsible for performing the process on the dataset. Although different organisations may perform a number of processes on the dataset, only one organisation can be responsible for each process.

This organisation is not necessarily the same as the organisation financing the dataset (Promotion key) or that coordinates the dataset (a unique organisation, Coordinator key, that is charged with producing the dataset and is responsible for its technical content).

The MiraMon support applications (MSA) will automatically document this field with the name of the MiraMon licence holder.

Follows the proposal of: The CEN

Obligatory according to the CEN: Yes

Cardinality: N

Key type: C

AppliesToLayer: Yes
AppliesToSeries: No (contains information about the Layer)

(Back to index)

Name of GeM+ entry:History
Name of the REL file key: history

Description and considerations: Details of the processes that have been performed on the dataset giving details of the inputs and methods used, including references to documents containing further details, algorithms, etc).

The MiraMon support applications (MSA) will automatically document this field, taking the command line used to run the processes.

Follows the proposal of: The CEN

Obligatory according to the CEN: Yes

Cardinality: N

Key type: C

AppliesToLayer: Yes
AppliesToSeries: No (Contains information on the Layer)

(Back to index)

Name of GeM+ entry: Purpose
Name of the REL file key: purpose

Description and considerations: The purpose for which the process was undertaken and the reasons for using the chosen method.

The MiraMon support applications (MSA) will automatically document this field with the descriptive title of the application (which appears in the applications title bar and the title of the help). It is recommended that, when necessary, this information should be complemented manually to explain the choice of parameters used when running the program.

Follows the proposal of: The CEN

Obligatory according to the CEN: Yes

Cardinality: N

Key type: C

AppliesToLayer: Yes
AppliesToSeries: No

(Back to index)

Name of GeM+ entry: Date
Name of the REL file key: date

Description and considerations: The date on which the process was completed. This date should not be confused with the date on which the dataset was updated.

The MiraMon support applications (MSA) automatically document this field with the date on which the application was run (in the usual format: YEARMONTHDAY HOURMINUTESSECONDSTENTHS, eg., 20010630 14420790 corresponds to 30 June 2001, at 14:20 hours and 7.90 seconds).

Follows the proposal of: The CEN

Obligatory according to the CEN: Yes

Cardinality: N

Key type: D

AppliesToLayer: Yes
AppliesToSeries: No (Contains information on the Layer)

(Back to index)

Process Tolerances (GeM+)
[QUALITY:LINEAGE:PROCESS:TOLERANCE] (REL file)

A number of tolerances may be documented for a single process. The forward and back buttons (< >) allow the associated values to be viewed.

Name of GeM+ entry: Name
Name of the REL file key: name#

Description and considerations: The type of tolerance used when carrying out a process.

This scheme allows different types of tolerances to be documented such as, for example, those defined automatically in a topology structuring process, or any other type of tolerance. (It is possible to type in the desired name or to select from the pull-down list).

The tolerances defined by MiraMon for topology structuring are:

Precision (Fuzzy tolerance) (in the REL file this must be set as "Precisión")
Pseudo-generalisation tolerance (in the REL file this must be set as "Pseudogeneralización")
Arc snap tolerance (in the REL file this must be set as "Arc snap")
Undershoot tolerance (in the REL file this must be set as "Undershoot"
Node snap tolerance (in the REL file this must be set as "Node snap")
Dangle tolerance (in the REL file this must be set as "Dangle")

Unless the "tolerance" key of the older documentation files, is 0 or "unknown", a process and a tolerance are created in the metadata. In this automatic transformation the type of tolerance created depends on the type of file documented. For instance, for the case of a structured point file, in which the file tolerance indicated:

tolerance : 1E-8

metadata would be created:

[QUALITY:LINEAGE:PROCESS1]
date=unknown

[QUALITY:LINEAGE:PROCESS1:TOLERANCE]
name1=Node snap
value1=1E-8

Note that in order to define a section that derives from [QUALITY_LINEAGE:PROCESS#], it is essencial that the section contains some key. In such cases it is recommended that at least one key "date=" is registered in the section. (In the automatic transformation of the older documentation files "date=unknown" is documented).

Follows the proposal of: GeM+

Obligatory according to GeM+: Yes

Cardinality: N

Key type: C

AppliesToLayer: Yes
AppliesToSeries: No (contains information on the Layer)

(Back to index)

Name of GeM+ entry: Value
Name of the REL file key: value#

Description and considerations: The value used to apply the tolerance.

Follows the proposal of: GeM+

Obligatory according to the GeM+: Yes

Cardinality: N

Key type: F

AppliesToLayer: Yes
AppliesToSeries: No (Contains information on the Layer)

(Back to index)