GeoConcept Enterprise Solution (GCES) is a client/server solution based on the GeoConcept geographic information system (GIS) and relational database technology.

Our solution designed around the GeoConcept GIS is particularly open, and so offers a high degree of flexibility in the choice of architecture. While GeoConcept itself has its own (object-oriented) database, GCES enables interconnectivity with Relational DataBase Management Systems (RDBMS). This means that data storage in GeoConcept and/or an external database can be combined.

GeoConcept’s software configuration as regards access to external databases offers the possibility of a dynamic or replication link between GeoConcept and the RDBMS. GeoConcept Enterprise Solution in this way enables storage of a GeoConcept map base of objects in an external RDBMS (Oracle, DB2, Sybase etc.). This functionality opens the way to constructing architectures perfectly suited to integration of mapping in decision-support systems.

Any kind of geometric or attribute data can be held centrally in the RDBMS.

Irrespective of where the RDBMS is located, or the operating system (UNIX, Windows…) used by the server on which it runs, the user benefits from a high degree of flexibility. This is because all updating, access control, security and archiving functions are performed by the RDBMS.

GeoConcept Enterprise Solution for Oracle Spatial or locator offers additional functions over and above those provided by Oracle for storing geometric data: for example, utilisation of OpenGIS format, a relational object format (from version 8.i onwards).

The geometry is stored in the RDBMS in native GeoConcept format, to avoid the need for conversions and to achieve optimum performance. Where the reference database is Oracle, OpenGIS format (relational object format) can be useful if the data has to be shared by different applications. Attribute data is stored on the client workstation (with data replication on the server), or only on the central database if it has to be shared in dynamic mode.

Communication standards

The technology developed by GeoConcept SA uses OLE-DB links for most SQL-type databases (SQL Server, DB2, Sybase, …). However, the use of a native link, SQL-Net, is maintained for accessing Oracle databases, since it delivers better performance.

Data transfer modes

Three modes of communication between GCES and the RDBMS are possible: import link, export link and permanent link.

Import or Export link

The import (or export) link provides partial access to the central database, through import (or export) of all or part of the database into GCES (in the case of a consultation terminal) at set intervals; or simply on request for a user with the appropriate access rights. Where data is being exported, the GCES data serves to enrich the central database (for a data input terminal or a production workstation).

Permanent link

The permanent link brings together both import and export modes; all or part of the central database is replicated in GCES, thus enabling a reduction in network traffic particularly during display, selection, and querying… (because local actions make no demands on the server).

Permanent link with journal facility

The use of a journal enables replication to be managed by optimising access and limiting network loading: only the latest modifications are replicated, rather than the whole of the central database. This improves system performance significantly in comparison with the simple permanent link.

The journal is updated each time a table used by GCES is modified in the RDBMS. Updating is initiated by means of standard ‘Triggers’. When a GCES client wants to update replicated data, it interrogates the journal, reading only the data that has been modified since it was last read. In addition, to guarantee the availability of the application, (journal) readings only take place when the user workstation is inactive.