If the imagery is highlyĬompressed this is less of a concern. Therefore, the performance of the disk system is an Memory, and ArcGIS needs to read the required pixels off the disk Imagery, it is not possible for the system to load all imagery into Drive performanceĪs defined in the section above, due to the large size of Separate locations disconnected from the originals. If the directories are read-onlyĭuring the authoring processes, these files will be stored in In additional pyramid, statistics, or metadata files being writtenĪlong with the source files. It is recommended to not set the directory in which theįiles are stored as read-only, since many of the workflows result That the original files are not modified and that they are backed up multiple By having image files set as read-only you can help ensure Optionally change the file, but alternately modify the associated Some processes (such as setting the spatial reference)
Possible and recommended to set the main imagery files (.tif, and so on)Īs read-only. Files such as pyramids (.ovr)Īnd metadata (.aux.xml) files may be added, but mostly it is It is generally better to create subdirectories based on some It can take a long time to list the files in Catalog or Explorer. Is no specific maximum and this does not affect performance of dataĪccess, but if there are very large numbers of files in a directory, Try to keep the number of files per directory under 1,000.
Keep all metadata that comes with the imagery in the same location as the imagery. Unique names can help later in linking metadata attributes. If creating new files, it is best to include key descriptors in the name, such as date and some geospatial indicator.
It is recommended that you do not rename any files. The names of the files are generally defined by the data provider. Granularity makes it easier to extend later. Specific subcategory, planning in advance with sufficient A typical hierarchy couldįor example: Satellite\GeoEye\GeoEye1\Europe\2001Įven if you initially only have imagery of one The following are recommendations for data structure: Directory structuresĭefine a hierarchy that makes sense for the data, and plan ahead It is better to structure imagery based on aĭirectory naming convention and hierarchy agreed on by the organization. Structure the files to simplify data management. If new data isīeing acquired, recommendations may be given on how to Otherwise, existingĪpplications may have difficulty accessing the data. Terms of directories is not important, and it is often best to leaveĮxisting data in its original structure. In most cases, the structure of how the data is stored on disk in
0 kommentar(er)
