Skip to main content

Profile feature types

The Feature types section displays the feature types contained in the profile's schema. For each feature type, hale»connect displays its name and properties.

The search box at the top of the page allows you to filter feature types by name. Toggle the Show inherited properties switch to view additional, inherited properties for each feature type. Toggle the Show diff switch to view the feature types that are extended by the profile.

For each property in a feature type, the name and data type are listed. Click the » button to view additional information on the property, such as constraints defined on it.

Setting type level constraints

To make a single feature type mandatory, toggle the switch in the feature type header. A mandatory feature type has to occur at least once in any document. This is particularly useful in GML Feature Collections, when you want to state which types of objects have to be present.

Setting property level constraints

Click the «Edit» icon next to the name of the feature type to add property level constraints.

Required fields, range values, cardinality and tagged values can each be defined on the property level. Click the » button next to the property's data type to expand the panel.

Content required Click the drop down menu to make the property optional or mandatory. This is only possible if the property was not previously mandatory.

Allowed values This function can be used to restrict which values ​​may be present in the data. This restriction can narrow down an already existing restriction or define a new restriction. A typical use case is when only one code list value in the context of the profile should be allowed.

To specify valid values ​​for any string, enter them in the text box, separated by a comma.

To select valid values ​​for a field with a code list or enumeration, select them from the list of options.

To set a value range for a numeric field, enter an upper and a lower limit. This must be narrower than existing limitations at the schema level.

Minimum and Maximum count The cardinality can be restricted on the property level, e.g. from [1..n] to [1..1]. Enter the minimum and maximum values in the text boxes. Only narrower values ​​are allowed than defined at the schema level.

Tagged values This function can be used to identify profile elements that will be used to generate test suites and example files. To specify a tagged value, select a tag name from the drop down menu. Enter the value in the text box provided. Multiple tagged values for the same tag name are not possible.

There are a number of different tagged values:

  1. Testcase-label (ATS-Titel): The reserved tag ATS-Titel can be used to label the test case in the ETF test suite.
  2. Testcase-description (ATS-Beschreibung): The reserved tag ATS-Beschreibung can be used to describe the test case in the ETF test suite, or to describe the manual check required when a Manuelle Prüfung tag is added.
  3. Module-id: The reserved tag module-id can be used to signify that a test case belongs to a module, or group of tests, that are grouped together in the ETS file.
  4. Example: The reserved tag example can be used to provide an example of a valid value for the element.
  5. Example XML: The reserved tag example-xml enables users to provide an XML fragment as an example value in the example XML document export. The example-xml tag is available for any feature type and any property. First, add a tagged value and select the example-xml tag from the available options in the dropdown list. Next, enter a valid XML code block in the editable field. Fragments must be valid, parsable XML. If the fragment includes namespaces, the namespaces must be defined in the fragment.
  6. Manual check (Manuelle Prüfung): The reserved tag Manuelle Prüfung enables users to require a manual check of test results. ETS files which contain tests labeled with the Manuelle Prüfung tag are displayed in yellow when executed. A description of the manual check required by end-users can be provided in a Testcase-description (ATS-Beschreibung) tag.

Examples of valid fragments:

<gco:CharacterString xmlns:gco="">Example-text</gco:CharacterString>


Example of an invalid fragment:


In this example, the example-xml tag is used to provide a character string value in the gmd:language element.

The file below is the example XML document export which contains the character string value provided in the example-xml tag.

  <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<gmd:MD_Metadata xmlns:gmd="" xmlns:gco="" xmlns:gml="" xmlns:xsi="" xsi:schemaLocation="">
<gmd:CI_RoleCode codeList="" codeListValue="custodian"/>
<gco:CharacterString>example string</gco:CharacterString>
<gmd:CI_DateTypeCode codeList=" codeListValue="creation"/>
<gco:CharacterString>example string</gco:CharacterString>
<gco:CharacterString>example string</gco:CharacterString>

When you are finished adding constraints to the selected feature type, click «Update»