Personal Geo-databases and File Geo-databases

22.4.2014 Benjamin Gubler

Both personal and File Geo-databases can be freely made use by using ArcEditor, ArcView and ArcInfo systems. They can be used to draw topologies cataloguing rasters, dataset networking, locators of addresses etc. The restriction is that they allow only a single user and you cannot undertake versioning on these databases. Though file database allows multiple editors simultaneously, only if they are working on different datasets, tables or using stand-alone features.

In their latest versions both the geo-databases they aim to help users with freely and easily available simple solutions which are scalable to all users. They also aim to provide a simple geo-database which works with any operating system and handles huge datasets. Users have found that they keep the promise of providing very good scalability, supporting individual datasets having more than 300 million fields, as also datasets which can go beyond 500 GB per file with very quick results.

Both these geo-databases require a good data structure which has been optimized both for storage and performance. File geo-databases are known to use a third of feature geometry-storage necessitated for shape-files. With a view to help reduce storage space requirements file geo-databases allow for compressing vector information to read-only. File geo-databases can excel shape-files performance, for work which engages attributes and scale size-limits of data well beyond the limits offered by shape-files.

Personal Geo-databases have been in use by ArcGIS, using the .mdb file or using the Microsoft Access file structure, supporting files which are of 2GB or less size, though the really effective size in these databases is limited to 500 MB, as otherwise the database will be slow in performance. Moreover, personal geo-databases are supported only by Microsoft Windows. Users have prefered in Microsoft Access for text handling.

Do you think this article is useful?

Register Box

Login Box