You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using pyogrio for working with ESRI FileGDB files and found a couple of features that could be improved:
Datasets in List Layers:
The list_layers function only shows layers, not the datasets holding them. In ogrinfo, you can see both layers and their datasets. It would be helpful if pyogrio could also show this information to better understand how data is organized.
Access to Domains and Relationships:
I also noticed that pyogrio.read_info doesn’t show domains and relationships. These are important for knowing how data is connected and its rules. ogrinfo can show this with a command like this:
ogrinfo -ro -al -json -so input.gdb > output.json
Here’s a short version of what ogrinfo outputs in output.json:
Thanks for the suggestion; handling of advanced driver specific properties like domains / relationships could be improved.
Can you point us to a small, publicly accessible FileGDB file that has domains / relationships set, or instructions on how to use ogr2ogr to create them from an existing dataset?
I don't understand what you mean by showing datasets in the context of listing layers; since the dataset is input to the list_layers function, there is only the one, right? Can you give us more of an example where listing layers would be showing layers from multiple datasets?
Hello Pyogrio Team,
I'm using pyogrio for working with ESRI FileGDB files and found a couple of features that could be improved:
Datasets in List Layers:
The
list_layers
function only shows layers, not the datasets holding them. Inogrinfo
, you can see both layers and their datasets. It would be helpful ifpyogrio
could also show this information to better understand how data is organized.Access to Domains and Relationships:
I also noticed that pyogrio.read_info doesn’t show domains and relationships. These are important for knowing how data is connected and its rules. ogrinfo can show this with a command like this:
ogrinfo -ro -al -json -so input.gdb > output.json
Here’s a short version of what
ogrinfo
outputs inoutput.json
:The text was updated successfully, but these errors were encountered: