Data Stores

In 1Integrate, a Data Store describes where external spatial or non-spatial data is being read from or written to.

This represents the data which will be analysed and edited by Rules and Actions within 1Integrate.

What Makes a Data Store?

A Data Store can be configured as:

  • Formats such as PostgreSQL, Oracle Spatial databases (with or without workspaces enabled), Esri Shapefile, MapInfo TAB files, OGC GeoPackage, OGC Web Feature Service (WFS).

  • File formats (e.g. Bentley DGN) and database formats. See Supported Data Stores.

  • Fixed schema Data Stores designed for use with specific tasks, such as generating a Non-Conformance Report.

  • Other data formats available via project-specific bespoke Data Stores.

When running a Session using a Data Store, the data is stored in the cache (see Session Cache).

     Note: All lengths, areas, and co-ordinates used in 1Integrate are in dataset units (the co-ordinate system used in the external data source). 1Integrate does not perform any automatic co-ordinate conversions.

Getting Started

First, we recommend you are clear on how Creating and Managing Data Stores works within 1Integrate, and by extension understand if there are any specific requirements for your chosen format of Supported Data Stores, or specific Geometry Support considerations.

Once you have configured a Data Store for use in 1Integrate, you'll need to understand Schemas and Schema Mapping, which has its own dedicated section of documentation.

Finally, some users may need to more detail around Coordinate Reference System or Measures and Linear Reference Systems, but this will depend on how you are using Data Stores.