Skip to main content
Cartegraph Campus

Cartegraph and Versioned Geodatabases

Introduction

Esri allows geodatabase administrators to create versions of multi-user SDE databases. The Cartegraph database can integrate with any of these versions. Cartegraph keeps its data synchronized real-time with the particular version the administrator selects. Changes are then propagated to and from other versions during Cartegraph‘s regularly scheduled background synchronization process.

If your organization uses multiple versions of the geodatabase, the business rules and processes need discussion and consideration so the impact of Esri’s reconcile and post commands have the desired effect. Consult Esri’s documentation for details on how to create database versions and then reconcile and post commands. When integrating with Cartegraph, the important question is which particular geodatabase version to integrate with the Cartegraph database. The next sections describe different version architectures to help you make that determination.

Default Geodatabase Version

Your organization may choose to use only the Default version of an SDE database. When the Default version of the geodatabase is associated to a Cartegraph recordset, data is shared by both data sources through Cartegraph’s synchronization engine. Information flows seamlessly between the applications. The GIS Reconcile and Post commands are not used.   

Cartegraph not Associated to Default

Post in Favor of Edit Version

The Default version of the database is the central repository of geodatabase information. Version A of the geodatabase contains information about a single feature class which is associated to a Cartegraph recordset. 25 records have been added to Geodatabase Version A which is associated to the Cartegraph database. When the Version A changes are reconciled and posted to the Default geodatabase favoring the Edit version of the geodatabase, the additional records from Version A are added to the Default version. After posting, the Default, Version A, and the Cartegraph database all contain 125 sign records. Any changes to associated fields will also be reflected in the Default version of the geodatabase.

Post in Favor of Default Version

In this scenario, 25 records have been added to the Default version of the geodatabase. When the Version A changes are reconciled and posted to the Default geodatabase favoring the Default version of the geodatabase, the post moves the records to Version A. The Cartegraph background map engine then adds the new records to the Cartegraph database. The Cartegraph database includes the values of any associated fields as recorded in the Default version of the geodatabase.

Associated Feature Class and Child Version

The Default version of the database is the central repository of geodatabase information.  Version A of the geodatabase contains information about a single feature class which is associated to a Cartegraph recordset. The Child Version of the geodatabase has Version A as its parent. Child Version will be used to collect data for signs in a new subdivision.  25 records are added to Child Version. Reconcile and post favoring the edit version is run on the Child Version and data is sent to Version A. The Cartegraph background map engine subsequently sends the data to the Cartegraph database. A second reconcile and post favoring the edit version is performed on Version A adds the new records to the Default version of the geodatabase.

Multiple Versions with Same Parent

The Default version of the database is the central repository of geodatabase information. Version A of the geodatabase contains information about a single feature class which is associated to a Cartegraph recordset. Version B collects data for signs in a new subdivision and has the Default version as its parent. Compare to the previous scenario, where the Child Version has Version A as its parent.  25 records are added to Version B. Reconcile and post favoring the edit version is run on Version B. Data is sent to the Default version. A second reconcile and post favoring the Default version is performed on Version A. This adds the new records to Version A and the background map engine adds them to the Cartegraph database.

Integrate with the Selected Geodatabase Version

The first step to any Cartegraph integration is publishing the integrated feature classes to ArcGIS Server as Feature Services. See the Cartegraph and GIS Integration document. With versioning, you must be sure the Feature Services reference the specific version you’ve chosen to integrate.

The key is when you create the map document from which you publish, be sure the Database Connection for the geodatabase targets the intended version.

To verify this:

  1. In ArcMap’s Catalog view, right-click the Database Connection for your geodatabase.
  2. Select Geodatabase Connection Properties.
  3. Select the Transactional Version to match the version you want to integrate with Cartegraph.

After setting the version, then you can add feature classes to the map and publish the feature service to use with Cartegraph.

 

  • Was this article helpful?