STRUCTURE OF THE HELP FILE
Information refering to each GeM+ entry

Ckicking on any key will lead to help structured in the following way:

GeM+ entry name: Name of the key as displayed in GeM+. This is an idiomatic description.
Name of the key in the REL file: The name of the key as it is stored in the REL file. This description is not idiomatic; normally the English names correspond to the specific proposals of CEN, FGDC, etc, whilst the names in Catalan correspond to keys developed specifically for GeM+ (see technical note at the end of this document.)

Description and considerations: Describes the content of the key, as well as other considerations which could be of help.

Follows the proposal of: May have the following values: CEN, FGDC, ISO, GeM+.

Obligatory according to ____: May have the following values:

• Obligatory according to CEN: Yes/No (only applies when the CEN proposal is followed)
• Obligatory according to FGDC: Yes/No (only applies when the FGDC proposal is followed)
• Obligatory according to ISO: Yes/No (only applies when the ISO proposal is followed)
• Obligatory according to GeM+: Yes/No (only applies if optional according to CEN, FGDC and ISO, or it is a key only used by GeM+)

Should the key be obligatory according to different standards, then "Obligatory according to..." is only indicated once. In the case where the key is obligatory for some and optional for others it is only indicated when obligatory. Remember that the obligatory keys are also distinguished by being written in bold.

Cardinality: The cardinality of the key. May be 1 or N (many). If the cardinality N, many, affects a section, the # sign is used after the name of the section (eg. [QUALITY:LINEAGE:PROCES#] since there could be as many sections as there are documented processes.

Key type: May take the following values : L, C, N, F, D, H

• L, logical: Use 1 for TRUE and 0 for FALSE.
• C, character string. Maximum 254 characters.
• N, integer number (long), e.g. 0, -2000 or 192745.
  The maximum permitted range is between [-2147483648,+2147483647].
• F, double precision real, eg. -3.141592 o +2.8E-12
  The maximum permitted range is between [±3.4E±38].
  In the REL file the decimal point should always be used, never a comma, and no separator for thousands.
• D, date. The date, in the REL file, must be expressed in the same format used for writing MiraMon commands
  (YEARMONTHDAY HOURMINUTESECONDSHUNDREDTH), eg. 20010630 14420730).
• H, is a link to a document (hyperlink). The address may be absolute (eg. C:\DOCUMENTOS\INFORME.DOC), relative (..\DOCUMENTOS\INFORME.DOC), UNC (\\SERVIDOR\DOCUMENTOS\INFORME.DOC) or URL (http://www.creaf.uab.es/miramon/new_note/notes/tablescr.htm).

ApplyToLayer: Yes or No, depending on whether it applies to a layer or not.
AppliesToSeries: Yes or No, depending on whether it applies to a series or not.

Technical note: This idiomatic mix of REL section names and keys responds to a wish to respect as much as possible the names proposed by international organisations and, at the same time, to avoid using new GeM+ keys that in future could also be proposed by international organisations but with a different meaning. It is also worth noting that the REL file section and key names are only of interest to advanced users and programmers who wish to edit the file directly.