I don't know all the reasons for Access Geodatabases but here is what I do know.

When ArcINFO started turning into the desktop product there was a move to get things into a "database". ESRI had used INFO/Coverages for years. I think the quickest way to get to that end was Access. You could fold all your vector data into Access. It is slow from ArcGIS. You can't store raster. It has the habit of becoming very large very quickly and imploding. I think somewhere between 500Mb and 2 Gb were the problem sizes. They introduced file based geodatabases which aren't databases and aren't file based - they are directories and in my opinion are coverages Part II. File based databases are stable and much easier to work with - and too proprietary for my tastes now. You can get the data out but it isn't easy.

Randy

Randal Hale, GISP
North River Geographic Systems, Inc
http://www.northrivergeographic.com
423.653.3611 [email protected]
twitter:rjhale
http://about.me/rjhale

On 9/22/2012 9:10 AM, Johan Nilsson wrote:
Fist. I know very little about using dedicated realationdatabase in GIS. I not sure about why ESRI support mdb then they quiet strongly recommend you NOT to use it.

http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?topicname=types_of_geodatabases

I think to hold files in a directory (folder) are a very sheep price compared to slow performance limited storage to max 2 GB.

Does anyone know if there may be other problems with MS Access files? Missed seached data and so on?

Cheers


2012/9/22 Andre Joost <[email protected] <mailto:[email protected]>>

    Am 22.09.2012 09:43, schrieb Johan Nilsson:

        Okey. I'm new to database use i GIS and have only used file
        database that
        ESRI recommend. But if mdb are a propretarian and only work
        well with MS
        access, how can it then be highly portable?


    I thought of "portable" in the sense of taking a database from one
    computer to another. MDB  and sqlite are just one file, Shapefile
    a couple of files, and PostgreSQL/Postgis is very complicated to
    share/take with you or make a security copy.

    Greetings,
    André Joost


    _______________________________________________
    Qgis-user mailing list
    [email protected] <mailto:[email protected]>
    http://lists.osgeo.org/mailman/listinfo/qgis-user




_______________________________________________
Qgis-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-user

_______________________________________________
Qgis-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-user

Reply via email to