Formats used in checks

The list of updated formats is visible in the application schema rtest.xsd which is available at: http://schemas.veremes.net/rtest/2.0/rtest.xsd

List of formats in rtest.xsd :

<xs:attribute name="format" use="optional">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="POSTGRES"/>
      <xs:enumeration value="POSTGIS"/>
      <xs:enumeration value="ORACLE_NONSPATIAL"/>
      <xs:enumeration value="ORACLE_SPATIAL"/>
      <xs:enumeration value="ESRISHAPE"/>
      <xs:enumeration value="SHAPEFILE"/>
      <xs:enumeration value="FFS"/>
      <xs:enumeration value="SPATIALITE"/>
      <xs:enumeration value="SQLITE3"/>
      <xs:enumeration value="XLSXR"/>
      <xs:enumeration value="PDF2D"/>
      <xs:enumeration value="TEXTLINE"/>
      <xs:enumeration value="GML"/>
      <xs:enumeration value="ACAD"/>
      <xs:enumeration value="FILEGDB"/>
    </xs:restriction>
  </xs:simpleType>

Each format is identified by the short name of the FME format visible in the "View Format Gallery" menu of FME Workbench.

ESRISHAPE is the name of the old Esri Shapefile format Rreader (before FME 2020). This short name is currently usable with all versions of FME. SHAPEFILE is the name of the new Esri Shapefile Reader (since FME 2020), it only works if scenarioPlayer is running on FME 2020 or higher.

It should be noted that the FFS format evolves regularly. To use it with rTest it is necessary that the version of FME running scenarioPlayer is higher or equal to the version used by the processes producing the datasets.

Datafile formats

  • ESRISHAPE

  • SHAPEFILE

  • FFS

  • SPATIALITY

  • SQLITE3

  • XLSXR

  • PDF2D

  • ACAD

  • FILEGDB

  • TEXTLINE

  • GML

Database formats

  • POSTGRES

  • POSTGIS

  • ORACLE_NONSPATIAL

  • ORACLE_SPATIAL

  • SPATIALITY

  • SQLITE3

Particularity of the SQLITE3 and SPATIALITE formats

Datasets in SQLITE3 or SPATIALITE format can be considered as files or as databases. The two examples below produce the same result. The value returned is the "name" attribute of the second record.

In the first case, it is considered a data file (type="datafile") and the built-in function attributeValue() is used.

</check>
<check label="Country name in second record from request=attributeValue()">
  <source type="datafile" format="SPATIALITE" dataset="result\dbcountry.sqlite" request="attributeValue()" requestparams="country,name,2"/>
  <condition comparator="eq" expectedvalue="Switzerland"/>
</check>

In the second example, we consider that the SPATIALITE format is a database (type="database") and we query it by SQL. This method is more efficient and should be preferred if possible.

<check label="Country name in second record from dbrequest">
  <source type="database" format="SPATIALITE" dataset="result\dbcountry.sqlite" dbrequest="select name as observedvalue from country where OGC_FID=2;"/>
  <condition comparator="match" expectedvalue="Switzerland"/>

Particularity of the ORACLE_SPATIAL and ORACLE_NONSPATIAL formats

since scenarioPlayer accesses the data to be checked only in read mode and via SQL queries, there is no need to distinguish between these two formats, which are treated in exactly the same way by scenarioPlayer. Spatial queries are therefore possible using Oracle's own syntax.

To use these formats, the Oracle client software must first be installed on the workstation. See Safe Software's documentation on the installation of the Oracle client software