-
Notifications
You must be signed in to change notification settings - Fork 27
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
Question about dest
input to unsafe_gdalbuildvrt
#358
Comments
Can you try |
I'm a little unclear on how to use
|
That is the signature of the do block syntax, like in https://docs.julialang.org/en/v1/manual/functions/#Do-Block-Syntax-for-Function-Arguments. But I believe the same arguments as you used for the unsafe version are also supported. It just doesn't appear in the docstring. |
unfortunately 'gdalbuildvrt' does not accept the same inputs as
|
Ah you're right there is a difference between the two. ds = ArchGDAL.read("LC08_L2SP_196026_20180101_20200902_02_T1_SR_B2.TIF")
vrt = ArchGDAL.unsafe_gdalbuildvrt([ds]; dest="a.vrt")
ArchGDAL.destroy(vrt) And using do-blocks to directly clean up: ArchGDAL.read("LC08_L2SP_196026_20180101_20200902_02_T1_SR_B2.TIF") do ds
ArchGDAL.gdalbuildvrt([ds]; dest="b.vrt") do vrt
# do something with vrt dataset if needed
end
end In the first example, the VRT is only written on the call to |
I previously had
and To get the same functionality with
Is that right? If so it seems a bit counterintuitive to have to wrap this in a do block |
I guess this is related issue #164 that was partially resolved by allowing looking at Working with Files it seems that |
Yeah I think so as well. Let's keep this issue open to track that. |
Yeah it is, thank you for filing and explaining! |
When supplying
dest
kwarg toArchGDAL.unsafe_gdalbuildvrt
i would expect the .vrt file to be written todest
but this is not the case. Is this the expected behavior?The text was updated successfully, but these errors were encountered: