Hi Even,
On Wed, Nov 4, 2020 at 9:01 AM Even Rouault
wrote:
> > > Another particularity we have in GDAL is that the dataset name might be
> > > almost
> > > anything. Most of the time, it is a regular file path, or some /vsi
> path.
> > > But
> > > sometimes, it can be JSON content (the GeoJSON
Hi Even,
Thank you for the explanation (and for correcting me).
Aneta,
You can try QGIS as a possible workaround. You can use the Atlas feature
(GUI based) or write a small PyQGIS script, if you want to run it on a
headless server, on the command line.
Regards,
Jorge
Às 22:50 de 15/11/20,
Hi Even,
On Sun, Nov 15, 2020 at 7:39 AM Even Rouault
wrote:
> Hi,
>
> any comment on this before we put it to vote ?
>
> Even
>
> > Hi All,
> >
> > I would like to call for discussion on RFC77 Drop Python 2 support
> > <
>
Sean,
> It makes sense to me. I'm not aware of GDAL needing any features of Python
> 3.7, so 3.6 sounds good.
>
> Since the project hasn't dropped support for a Python version in a long
> time, maybe there should be a plan to warn in code
Idan has a pull request in
On 2020-11-11 9:00 a.m., Jon Morris wrote:
Hi Paul,
Thanks for your reply. The only reason we're trying to build locally is
to add FileGDB support - if there is a better way to add FileGDB write
support to conda-forge GDAL, I'd love to hear it! The GDAL docs are very
out of date when it
