If it was a feature dataset you tried to add with the tool (e.g., 1985īelow) you can't start with a number, you would have to add bsst1985 forĮxample. Immediately causes it to error when it tries to perform the copyRaster. Try to create a folder in the the File GDB for each folder traversed which Output workspace and use the traverse folders option, it appears the tool will To ArcGIS rasters" - a very nice tool, but if you specify a file GDB as
#Arcgis file already exists error code#
There is a minor error in the code for the tool "Find HDF and convert SDS Subject: Find HDF and convert SDS to ArcGIS rasters error? Other suggestions, I'd be happy to hear them. I will look into making these improvements. To look up other raster naming rules for GDBs One subdirectory level (the raster catalog name) is allowed in the outputĬatalog name, if present, must not begin with a number
Detect problems and report sensible error messages, rather than. GDB, set Raster Management Type to Unmanaged, otherwise use Managed Raster catalog does not already exist, create the raster catalog: If output raster path includes a raster catalog name, and the. But that leads me to enumerate the ways that we could improve The MGET tool currently cannot automatically create the rasterĬatalogs for you. Just prepending 'bsst' + to the middle component. But youĬould also have modified the default _expression_ that comes with the tool by Than assuming you have the rasters stored in subdirectories by year. This is extracting the year directly from the file name, rather 'bsst' + os.path.basename(inputFile), os.path.basename(inputFile).split(u'.')) Then modify the Python _expression_ to be something like this: ForĮxample, you could create raster catalogs called bsst1985, bsst1986, and so on. Level of the file GDB, you can create raster catalogs to hold them. If you find it inconvenient to have all these rasters in the root I haven't tried thousands of rasters in a file GDB before, so I can't I'm not sure if you're planning to try the entire AVHRR PathfinderĪrchive. This new _expression_ should copy the rasters directly into the file Into subdirectories: 1985, 1986, and so on. That component was obtaining the subdirectory(s) that came between theĭirectory To Search and the HDF itself. I removed the middle component of the os.path.join call, which _expression_ to not include the year as a subdirectory. You should be able to fix this by modifying the Output Raster Python That is presumably bad, because you're not supposed to tamper with the internal The Winter4kmBSST.gdb directory was actually a file GDB, rather than a regular directory. If you view the directory E:\Biophysical Oceanograpic Data\AVHRR\Pathfinder\Version5.0\Seasonal\Winter\Winter4kmBSST.gdb and seeĪ 1985 folder there, that is what happened. Went ahead and created a 1985 subdirectory inside of the directory that houses In the second case, ArcGIS is not failing it all. In the first scenario, ArcGIS does fail properly but the error message Is supposed to work in the way you have attempted them, but MGET is relying on theĪrcGIS Copy Raster tool to detect the problem and report a sensible error
0 kommentar(er)
