Chris Toney

@goergen95 , I experimented with your example above. I noticed that the USA buildings .fgb file is pretty large at 36 GB with 145 million features. There are close to...

@goergen95 , thanks for the additional information. I'm still experimenting with the building footprints. It's likely just throughput that's limiting for the ~9 million in NC. It sounds like Source...

Hi @goergen95, That is correct, we are currently not able to write features, at least with the prototype of `GDALVector`. The class definition in the specification document is intended to...

@goergen95, Correction to the above >Currently, the only way to know what has actually been implemented in the prototype is to scan through the header file in the `gdalvector` branch...

Another minor correction to the above. Using `ogrinfo()` to edit data might be a little clunky only in the cases when we want to edit by operating on individual feature...

Utility functions for managing vector data sources have been added in main (#343), to be included in a 1.11 release in the next week or two hopefully. Documented at: ogr_manage...

I just updated branch gdalvector from main. I generally try to keep it up to date, and I usually install from there for my local working instance of gdalraster. But...

The document "Draft Bindings to OGR" has been updated for recent changes and ongoing development in branch gdalvector. Mainly, sub-headings were added under the heading [Description of the interface](https://usdaforestservice.github.io/gdalraster/articles/gdalvector-draft.html#description-of-the-interface). New...

Branch `gdalvector` has been merged into `main` and further development will be done there. Documentation for class `GDALVector` is now available in the development version of the package, and online...

`ogr_proc()` was added in #451, with online documentation at: https://usdaforestservice.github.io/gdalraster/reference/ogr_proc.html Feedback is welcome if we need improvements to the interface or other changes.