Hi,
If you work with a Postgres database, why don't you do this directly in the
database? It seems odd to use ogrinfo to do such updates in database.
Regards
Alexandre
Le jeu. 9 juin 2022 à 08:50, Andreas Oxenstierna <
andreas.oxenstie...@t-kartor.com> a écrit :
> Dear developers
>
> Ogr SQL up
Dear developers
Ogr SQL update capabilities are really impressing but there is one major
performance issue with update of many features, exemplified by:
ogrinfo -dialect sqlite -sql "UPDATE SET x = 1" PG:”"
This is painfully slow because ogr updates features one by one and furthermore
updates
Hi all,
I'm trying to import a layer from a filegeodatabase into postgis and clip
it to a separate postgis layer. Is that possible? I can successfully clip
using the clipsrc argument with a bounding box I've read that it will also
work for a shapefile, but I'd prefer to use a postgis layer as the
Chris,
Please file a ticket about that at https://github.com/OSGeo/gdal/issues/new
Even
Le 08/06/2022 à 09:11, Chris Smemoe via gdal-dev a écrit :
I’m not sure whether this is a bug or some issue with how I’m doing
things (like maybe my WKT is bogus), but when I try to define a
compound pro
Hi,
there has been positive feedback in the github pull request. Does
someone need extra time to review before I submit this to vote ?
Even
Le 01/06/2022 à 10:49, Even Rouault a écrit :
Hi,
I've posted in https://github.com/OSGeo/gdal/pull/5830 a new RFC to
add a column-oriented read API f
I'm not sure whether this is a bug or some issue with how I'm doing things
(like maybe my WKT is bogus), but when I try to define a compound projection
for a GeoTIFF with a local projection, the vertical projection information
does not get saved to the GeoTIFF and I get an error reported from PROJ.
