Avoiding the pitfalls of GIS engines containing a geodatabase
Conventional GIS suppliers often promote their GIS engine claiming that it levers a “powerful geodatabase.” The presence of a geodatabase in the GIS engine is thus positioned as an advantage, and even a necessary prerequisite to run a successful geospatial data management architecture.
This may trigger a number of questions when organizations seek a solution for exploiting their geospatial data. For example,
- Why do GIS engines offer (and even require) the use of an additional geodatabase,
when I have already stored my geospatial data in a spatial database of my own?
- What are the advantages and disadvantages of running a GIS engine that relies
on a built-in geodatabase?
The present white paper aims to help you answer such questions