An exception raised with IsADirectoryError while writing FGDB layer

[samsun-tomtom]

While writing FileGDB with this call on the incomplete FileFGDB path, the exception occurred at line 2275 in _io.pyx

write_dataframe(gdf, path, driver="OpenFileGDB", layer="layer_name", append=False)

==>

Exception: IsADirectoryError(21, 'Is a directory')

see

pyogrio/pyogrio/_io.pyx

Line 2275 in d3ff55b

os.unlink(path)

Expected behavior:
The incomplete FileGDB are re-created or fully overwritten in append=False mode

[theroggy]

Apparently the filegdb/directory you are writing to cannot be succesfully opened as a filegdb. So with incomplete, do you mean corrupt, or invalid? Or simply that the layer you want to write to is incomplete and you want to write it again?

To be clear, FileGDB's can contain multiple layers. For file types that support this:

• for append=False:
  • if the layer doesn't exist yet in the file, pyogrio will add the layer to the file
  • if the layer does exist already, pyogrio will overwrite this single layer (but won't delete the entire filegdb as there could be other layers in it
• for append=True:
  • if the layer exists, the records will be appended to the existing layer

So deleting the filegdb file/directory is defilnitely an option is the file is coirrupt, but it is a bit tricky, as we don't want to accidentaly delete other layers.

[samsun-tomtom]

Apparently the filegdb/directory you are writing to cannot be succesfully opened as a filegdb. So with incomplete, do you mean corrupt, or invalid?

yes, it failed to open and fallback to os.unlink to remove single file, but filegdb itself is a file. In our case, the filegdb is corrupted

Or simply that the layer you want to write to is incomplete and you want to write it again?

The filegdb is corrupted in our case. Could the directory be deleted when append=False mode in a corrupted filegdb?
Because generally we have a workground on top of pyogrio to delete the corrupted or invalid filegdb and then re-create it