Hello,
I translated some geojson to flatgeobuf where the geojson features have a
variable number of properties (e.g. some features have a bunch of
translations for the name of a place pulled from OSM).
I noticed in the ogrinfo output that while the summary info has all the
fields possible,
name:
Ah thanks, yeah I see now with a '-dsco METADATA=NO' option ogrinfo doesn't
recognize the output geometry column as geometry.
On Fri, Oct 25, 2024 at 3:46 PM Even Rouault
wrote:
>
> Le 25/10/2024 à 23:40, Patrick Young via gdal-dev a écrit :
> > Hello,
> >
>
Hello,
I noticed in the docs
https://gdal.org/en/latest/drivers/vector/sqlite.html#regular-sqlite-databases
that there is some support for treating a plain sqlite db as a vector
format.
I've been dumping some vector data into a table with a geometry column full
of WKB plus some properties, but I
Hi,
I've been playing around a little with the MVT driver and noticed in the
test suite, features are written first via the Memory driver and then
gdal.VectorTranslate is used to create the MVTs.
Is there any advantage to doing this vs writing features directly to a MVT
datasource? From what I c
uault
wrote:
> Hi,
>
> this is likely a bug. I would need access to the file to investigate,
> ideally through /vsicurl, /vsis3, etc. . I don't have storage to host
> 300 GB. And possibly try to reduce the file size by removing upper zoom
> levels
>
> Even
>
>
Hello,
I've been exploring the pmtiles driver a bit, what a great way to read
giant blobs of tiles off of cloud storage, really impressed by how fast
this is.
I've been encountering a "Non increasing tile_id" when attempting to read
from coarser zoom levels for a large (~300GB) pmtile file:
http
