The introduction of GlobalIDs opens up interesting possibilities in system design. As of the forthcoming GEONIS release, all GEONIS data models are equipped with GUIDs as the database key.
Now all data relationships are managed on the basis of these GlobalIDs. The introduction of GlobalIDs opens up interesting possibilities in system design. Thanks to data-base replication based on GlobalIDs, data repositories can be distributed and then brought back together.
Database replication at various locations
A customer operates multiple offices and wants to manage their data independently of these locations. Until now the only convenient way to do this was with Terminal Server. Now you can replicate the entire database at each location. Any changes can be replicated or duplicated in both directions, at any time. The only condition is the use of a database server and ArcSDE at each location.
Separation of production and publication databases
Many customers have expressed the wish to separate their production and publication data environments (Web GIS, for example) in order to allow independent operation and update of those data repositories.
If the data are edited in a Web GIS, with a replicated database it is now possible to perform a quality check on these edits before synchroniz-ing them back with the production database.
For a read-only web mapping application it would suffice to set up a one-way replication, which could be executed at any time. File Geodatabases (FGDB) offer an excellent solution as they offer better performance and save the expense of a separate SQL-Server or Oracle license.
Synchronization of GEONIS gear
Editing in GEONIS gear is only possible thanks to GlobalIDs. Synchronization happens via an ArcGIS Server Feature Service.
Better Support for Esri Apps
Esri offers various apps for ArcGIS Online and Portal, for example Collector for ArcGIS. Thanks to the new GEONIS models, these can be used optimally on- or off-line.
Further information about distributed data can be found here.