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
[...] it may sometimes be desirable to transfer between OGR sources without reading them into memory. Minimal support for querying and writing a SpatVectorProxy for an arbitrary source was added in 8f3cae4... but a more general solution would use an ogr2ogr-like interface, rather than going through a SpatVector/R intermediate object.
To clarify--this may require incremental reading into memory--but the key goal is that sources that are too large to fit in memory will not be read in their entirety, but rather read/write in chunks.
brownag
changed the title
Transfer OGR sources without reading them into memory
Transfer OGR sources incrementally that are too large to fit in memory
Mar 3, 2024
An alternative to hand rolling an approach for this would be to use gdalraster::ogr2ogr()--a new feature in current development (1.9.0.9070) version--which should be able to do exactly what this issue calls for; related to #19
[...] it may sometimes be desirable to transfer between OGR sources without reading them into memory. Minimal support for querying and writing a SpatVectorProxy for an arbitrary source was added in 8f3cae4... but a more general solution would use an ogr2ogr-like interface, rather than going through a SpatVector/R intermediate object.
Originally posted by @brownag in #15 (comment)
The text was updated successfully, but these errors were encountered: