Jukka:
Thank you, interesting, lat,lon interpreted as string by gdalinfo.
Request 1
ogrinfo file1.csv -al -so
INFO: Open of `file1.csv'
using driver `CSV' successful.
Layer name: file1
Geometry: None
Feature Count: 1000
Layer SRS WKT:
(unknown)
lon: String (0.0)
lat: String (0.0)
id: S
I work in local coordinates resulting in a grid. Is there an easy way to
translate the grids X and Y coordinates, eg add 580,000 to X and add
5,840,000 to Y shift (which would then be a common EPSG)?
There are many options to hack this, eg edit an ERS file, but it would
be nice to be able to d
Thomas,
part of the unexposed options are indeed due to:
- sometimes desynchronization between the C++ and Python API
- sometimes not finding quickly a good enough Python name, and the
option being of marginal use
- or because the handling of the switch must be done when
opening/creating th
Hello all,
Due to question at
https://gis.stackexchange.com/questions/398223/how-to-remap-gdal-options-from-string-version-to-a-dictionary-version
I've taken a look at code
When trying to use gdal.Warp from Python, most options are supported but
some seems to be missing
Although an approach with
Hi,
Please add couple of rows from your CSV file. Maybe the lon and lat fields
are otherwise OK but GDAL does not recognize them to contain numbers but
perhaps text. You can also check what sort of attributes ogrinfo reports
with
ogrinfo file1.csv -al -so
-Jukka Rahkonen-
Al Piszcz wrote
> I
I am having a challenge determining the right position or entry for the
Field entry, the spatial filter error below indicates my VRT format is not
correct. Is there a better approach? Thank you.
>ogrmerge.py -overwrite_ds -single -o __sdg\merge_02.csv __sdg\merge_01.vrt
*Warning 1: The 'lon' and/
Javier,
I have not looked at the code, but seems that the mask is requested
only for the first band.
You're right. GDALRegenerateOverviewsMultiBand() in
https://github.com/OSGeo/gdal/blob/master/gdal/gcore/overview.cpp#L5057
always takes the mask from the first band. Which is OK for an alph
Thank Even.
I think I found the reason of the problem. It is reproduced with more
bands. I created a second band just swapping the values in the diagonal.
Then, adding the second band to the tmp.vrt (2 normal + 1 alpha), and
following your steps, it is noticeable in the second band of the output:
Javier,
mixing Alpha and NoData is generally not a good idea. Behavior will be
different according to which part of the code is triggered. As far as I
can see, the warping code should be able to handle both, but overview
building will use the return of GDALRasterBand::GetMaskBand(), and when
Hi
I have a GeoTIFF with this characteristics:
- 6 bands
- last band is "Alpha" (with values 0 or 255, nothing else)
- Float32
- NoData value = -1
The 5 first bands may have "nodata" pixels, not necessarily on all bands
simultaneously. (nodata pixels are usually broken or saturated pixels fro
10 matches
Mail list logo
