network storage of projects

Idea created by choeser on Mar 22, 2019
    New
    Score20
    • Alun_H
    • MJDenvironmental

    We are a university-based working group. We are storing project files using a NAS system which allows ease access for everybody to projects created with ArcGIS Pro 2.3.

    Creating new projects is no problem. Creating a new feature class (manually from menu or by tools) is nearly impossible.

    The creating process is setting up the table, but the resulting table does not become visible to ArcGSI Pro, because the windows cache is to slow and updated periodically, while Arc GIS Pro expects the table’s availability in the cache at once. Though the table is there but ArcGIS Pro fails to write into it, because it does not know the feature class table which has been created by ArcGIS Pro the immediate preceding step.

    Until we realise what is taking place this sort of error is very embarrassing and makes us turn back to ArcGIS Desktop or QGis.

    Finally we found a workaround described in https://support.esri.com/de/technical-article/000012722

    This option is not available for a normal user, as managing settings inside registry is not allowed for every user within a computer network, e.g. universities. And again this way cache is deactivated for everything, not only for ESRI services. Thus ESRI necessities have consequences for everything and slows down the system even if it is not in use.

    ESRI is already aware of this problem, as we learned from the link named above. We strongly recommend to integrate the problem’s solution inside the ArcGIS Pro software, a solution which does not need registry-manipulation to allow the user to use the software.

    In case ArcGIS Pro cannot force to get updated information from the cache it is necessary to inform the user that we have to wait, due to cache - in stead of ESRIs momentary idea: leave the user alone let him sacrifice hours to find out what is going on.

    Obviously “waiting for a cache” is not the original idea of a cache.  Any other solution?

    A workaround inside ArcGIS Pro necessarily needs to deal with using tools which do create and fill new feature classes in one step, too. Otherwise a seamless usage is not possible.