-
-
Notifications
You must be signed in to change notification settings - Fork 27
ENH: add support to read, write, list and remove /vsimem/
files
#457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 30 commits
7e327b9
0c1458b
8f7733d
949e30f
72c5248
4786a2b
c7c7a2c
4d69b9a
82b08d4
33f55a6
8d281cf
d9ad3d7
b728332
3621218
1b15004
504cc3d
2c5f522
149a0ad
9870fdf
37cd30e
e4ab48d
68a595a
cfdfd7c
a997cef
d610f00
63a8cb6
2c11d77
07b500a
8806612
c3a01e5
a12f78d
774a6e8
bf2b455
bc8edd2
6436be1
bd51c70
76cf286
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,6 +5,7 @@ on: | |
branches: | ||
- main | ||
pull_request: | ||
types: [opened, edited] | ||
workflow_dispatch: | ||
|
||
jobs: | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,6 +21,9 @@ | |
read_bounds, | ||
read_info, | ||
set_gdal_config_options, | ||
vsi_listtree, | ||
vsi_rmtree, | ||
vsi_unlink, | ||
Comment on lines
+24
to
+26
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we explicitly want to expose those functions publicly (top-level) to our users as well? (are there specific use cases we are thinking of?) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I struggled with this as well. Some of them may be useful in order to leverage GDAL's VSI interface. That said, if you are using a different package to create VSI resources (e.g., the If we do want to keep this public, want to put these in the top-level interface? Maybe we should move the VSI related functions to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it is practical/logical when it is possible to create files in e.g. /vsimem/ that the functions to remove them again are available as well without having to install another package... Putting them in a seperate interface is possible, but I don't really see an obvious advantage. |
||
) | ||
from pyogrio.geopandas import read_dataframe, write_dataframe | ||
from pyogrio.raw import open_arrow, read_arrow, write_arrow | ||
|
@@ -37,10 +40,13 @@ | |
"set_gdal_config_options", | ||
"get_gdal_config_option", | ||
"get_gdal_data_path", | ||
"read_arrow", | ||
"open_arrow", | ||
"write_arrow", | ||
"read_arrow", | ||
"read_dataframe", | ||
"vsi_listtree", | ||
"vsi_rmtree", | ||
"vsi_unlink", | ||
"write_arrow", | ||
"write_dataframe", | ||
"__gdal_version__", | ||
"__gdal_version_string__", | ||
|
Uh oh!
There was an error while loading. Please reload this page.