Patrick,
Is there any advantage to doing this vs writing features directly to a
MVT datasource?
no there's no advantage in going through the Memory driver. Not sure why
I did that when writing the tests.
Also, is there a way to create just a single MVT with the driver? I
think the answer
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
Greg,
What's unclear is to what extent things continue to be ok on compilers
not supporting C23, and if they are, if those systems start to be second
class.My overall feeling is that it is vastly too early to be
depending on C23.
The RFC is clear enough this is an optional feature ("C23 is
Even Rouault via PROJ writes:
> Sending to both gdal-dev and proj, as this is intended to be a joint RFC.
>
> Summary: This RFC uses C23 ``#embed`` pre-processor directive, when
> available, to be able to embed GDAL resource files directly into
> libgdal. It is also intended to be used for PROJ,
Hi,
Sending to both gdal-dev and proj, as this is intended to be a joint RFC.
Summary: This RFC uses C23 ``#embed`` pre-processor directive, when
available, to be able to embed GDAL resource files directly into
libgdal. It is also intended to be used for PROJ, in particular for its
proj.db fi
