Hi,
Would you mind to include your whole ogr2ogr command (no passwords etc.) and if
possible, link to some small shapefile? And confirm that your aim is to save
shapefiles with Latin1 encoding into PostGIS database that is using UTF-8
encoding.
-Jukka Rahkonen-
-Alkuperäinen viesti-
L
Yes, that is true. It happened to me once.
What I mean is that the plain vanilla without all defaults (no overviews,
no tiles) is currently manageable. Changing only the "tiled" default would
make the vanilla case unmanageable. And some not expert users will complain.
Maybe it is good to document
Hi,
On the other hand those QGIS users pay the price every time when they zoom
close to the same image because then QGIS must read many super wide rows of
data instead of just the tiles that intersect the view. Not even overviews
which are created on top of striped image do not help when user h
Le 30/11/2021 à 16:33, Javier Jimenez Shaw a écrit :
Hi
I want to cancel the writing of a DXF file. It has, let's say, a
million points. Before adding each point I check if the user canceled
the task.
I have noticed that while I am writing point by point, the actual file
in the disk that is
Hi
I want to cancel the writing of a DXF file. It has, let's say, a million
points. Before adding each point I check if the user canceled the task.
I have noticed that while I am writing point by point, the actual file in
the disk that is growing is called "file.dxf.tmp", and only when I close
the
Ok thanks, too bad that this is not implemented. I think the inversion
of this transformation would be a nice feature to be added in GDAL. It
would be very useful to me (especially if it is accessible via the
Python bindings) and would ease the implementation in a processing
pipeline for the up
Le 30/11/2021 à 12:52, Daniel Scheffler a écrit :
Thanks a lot for taking the time, Even, I got the transformation from
cartesian to projected coordinates to work in memory with the GTiff
driver. With MEM, NUMPY or VRT it does not work because these formats
are either not readable from /vsimem
Thanks a lot for taking the time, Even, I got the transformation from
cartesian to projected coordinates to work in memory with the GTiff
driver. With MEM, NUMPY or VRT it does not work because these formats
are either not readable from /vsimem/ or don´t have a regular file path
which is needed
Hi Rahkonen and Even,
thanks for the answers. If I add -oo PRELUDE_STATEMENTS="SET
client_encoding TO LATIN1" the I get this error:
Warning 6: driver ESRI Shapefile does not support open option
PRELUDE_STATEMENTS
and I think it that makes sense because I want to put in a UTF8 DB some
LATIN
On Tue, 30 Nov 2021 at 03:21, 박소원 wrote:
>
> Dear sir,
>
> Could you please take me off mailing list?
Go to https://lists.osgeo.org/mailman/listinfo/gdal-dev
Scroll to the bottom and follow the instructions starting
with "To unsubscribe from gdal-dev,..."
Best regards,
--
Mateusz Loskot, http:/
Hi Jukka
I don't think it is a good option.
TL;DR: tiled without overviews is extremely slow for a global view.
If you have a (big) image with TILED=YES but without overviews, it is
really really slow in QGIS (from seconds to many minutes).
The reason (I guess) is that QGIS is by default sub-samp
Sorry, in the message below I meant one needs to explicitly specify
OGR_WFS_PAGING_ALLOWED YES, with a suitable OGR_WFS_PAGE_SIZE.
Den 2021-11-30 kl. 09:34, skrev Hernán De Angelis:
Thank you, Jukka. I did that and worked. I also had another case where
it is important to get this right. It is
Thank you, Jukka. I did that and worked. I also had another case where
it is important to get this right. It is when the total number of
features exposed by the service exceeds the maximum number of features
allowed to be fetched in one request (CountDefault). In this case it is
also important
13 matches
Mail list logo
